How to Run a
Profitable Agency
Discovery Workshop

Most agencies treat discovery as a necessary evil on the path to the real project. They run it for free, rush through it, and wonder why the scope keeps shifting once implementation starts.

The agencies that operate at 40%+ margins treat it differently. For them, the agency discovery workshop is a product — something with a price tag, a defined agenda, a concrete deliverable, and a natural on-ramp to the work that follows. They charge for it. Clients who pay for it show up differently. Projects that follow it run cleaner.

This article is a complete blueprint for running that workshop: how to price it, what to put on the agenda, what you hand the client at the end, and how to turn the close from awkward to inevitable.

Why Free Discovery Is a Margin Problem

Before we get into the how, it's worth making the math explicit — because the instinct to give discovery away is strong, and it has to be fought with numbers.

A typical discovery engagement takes 20–30 hours of senior team time across scoping calls, stakeholder interviews, research, synthesis, and documentation. At a fully-loaded cost of $75–$100/hour, you're spending $1,500–$3,000 before the project even starts.

Now consider your close rate. If you're converting 40% of proposals to signed projects, you're giving away discovery to the 60% who don't move forward. On 15 proposals a year, that's 9 clients getting $1,500–$3,000 of your team's strategic thinking at no charge. That's $13,500–$27,000 per year in value you're subsidizing for people who never pay you.

That number tends to land differently when you write it down.

The solution isn't to do less discovery — it's to charge for it. And the best way to charge for it is to productize it into a structured workshop that clients can evaluate, approve, and pay for independently.

How to Price the Discovery Workshop

There are three pricing models that work for agency discovery workshops, and the right one depends on your positioning and client size.

Flat fee. The simplest and most common model. You set a fixed price — typically $3,500–$8,000 for a one-day workshop — and the client knows exactly what they're buying. Flat fees are easiest to sell, easiest to scope, and easiest to compare. The downside: if the workshop runs long or requires extensive pre-work, you absorb the cost. Mitigate this by defining exactly what's included in your one-pager (see below).

Percentage of projected project budget. Price the discovery at 5–10% of the estimated implementation budget. If you expect the full project to run $80,000, the discovery workshop is $4,000–$8,000. This model scales naturally with project complexity and signals that the discovery is proportionate to the stakes. It works well when you have enough information to estimate total project size early in the conversation, and when clients are already thinking in terms of total investment.

Day rate. Charge a daily rate for facilitator time — typically $2,500–$5,000/day — and scope the workshop as a one- or two-day engagement. Day rates are easy for clients to understand and easy for you to justify by credential (you're charging for an expert's time). They also create natural expansion: if a client needs more time, you add a day rather than renegotiate a fixed price.

Regardless of model, always separate the discovery cost from the implementation estimate. Clients should see a clear line between "what we're charging for today" and "what we'd propose for the full project." That separation makes discovery easier to approve internally — the decision-maker can sign off on $5,000 without committing to $80,000.

What to Include in Your Pre-Workshop Package

Before the workshop day, send clients a short pre-work package. This does two things: it primes them to come prepared, and it signals that this is a professional engagement, not an extended sales conversation.

The pre-work package should include:

• A brief intake questionnaire — 8–12 questions covering business context, current state, key stakeholders, biggest unknowns, and definition of success. Keep it focused; you're not trying to discover everything before the workshop.
• A list of who should attend — specify decision-makers and subject matter experts by role. Workshops stall when the wrong people are in the room.
• The agenda — share it in advance so attendees can prepare, not so they can optimize against it.
• A reminder of what you'll deliver at the end — clients who know what they're getting are easier to work with throughout the day.

Send this package at least five business days before the workshop. Following up the day before with a brief confirmation — "we're confirmed for Thursday, here's the Zoom link / address" — reduces no-show risk significantly.

The Discovery Workshop Agenda

The following agenda is designed for a full-day (six-hour) workshop with a team of two to six client stakeholders. Adjust timing as needed for a half-day format by cutting or condensing the research and synthesis blocks.

Two facilitation notes that make the difference between a good workshop and a great one:

First, don't present your recommendations during the workshop. The session is for listening and synthesis, not persuasion. Clients who feel heard are more open to your recommendations later. Clients who feel sold to during discovery often push back on the proposal.

Second, close the session with documented agreement, not open questions. The worst workshop endings are: "So what do you think?" or "We'll send something over." The best endings are: "Here's what we heard. Here are the top three priorities you identified. Here's what we'll deliver and when." Walk out with consensus in the room.

Deliverables That Justify the Price

The workshop itself generates alignment. The document you deliver after generates trust — and provides the foundation for the proposal that follows.

A strong discovery output document includes:

• Executive summary — a one-page synopsis of the situation, the problem, and the recommended direction. This is what the decision-maker reads before sharing with their team.
• Current state documentation — a clear map of existing processes, tools, and pain points, referenced against what came out of the workshop sessions.
• Problem definition and prioritization — the ranked list the group agreed on, with supporting rationale. This is the document stakeholders will use to justify the investment to their CFO.
• Success metrics — specific, measurable definitions of what "done" looks like, agreed to in the room and documented here. These become the scope guardrails for implementation.
• Risk register — a brief list of the constraints and risks identified, with preliminary mitigation notes. Clients who see their risks taken seriously become advocates for your work.
• Recommended scope outline — a high-level view of what the implementation phase would address, based on the prioritized problems. This is the bridge to your proposal. It's not a quote; it's a direction.

Deliver the document within five business days of the workshop. Most agencies take two to three weeks, which is long enough for momentum to die. Five days keeps the energy from the session alive and puts you in the proposal conversation while the client's pain is still top of mind.

Converting Discovery Into Project Work

Here's the part most agencies get wrong: they treat the proposal as a separate process that happens after discovery, rather than the natural continuation of a conversation that's already in progress.

When you run discovery well, the proposal is mostly already written. The problems are documented. The priorities are agreed. The success metrics are defined. What's left is translating those inputs into a scope, a timeline, and a price.

The handoff conversation — from discovery output to proposal — should happen in a dedicated meeting, not over email. Schedule it before you deliver the discovery document. "We'll be sending the output doc on Wednesday. Can we walk through it together on Thursday?" That question turns document delivery into a meeting, and the meeting is where proposals get signed.

In that meeting, your job is not to persuade. It's to confirm. "Based on what we heard in the workshop, here's what we'd recommend. Does this still match what you're trying to solve?" If the answer is yes, you move to scope and price. If the answer is no, you learn something important before you've proposed anything.

One more thing: make the proposal contingent on the discovery output explicitly. "This proposal reflects the priorities we documented on Thursday. If anything has changed, let us know before you sign — we'd rather adjust the scope than start with the wrong brief." That sentence eliminates a huge class of scope creep. It also signals that you're a professional who takes the discovery seriously, not a vendor who'll agree to anything to close the deal.

Handling the Price Objection

Some clients will balk at paying for discovery, especially if they've never been asked to before. Here's how to handle the most common pushback:

What these responses share: they reframe discovery as risk management for the client, not value extraction for your agency. Every objection to paying for discovery is really an objection to uncertainty — and your answer to every version of that objection is that discovery reduces the uncertainty the client is worried about.

The Filter Effect

One outcome of charging for discovery that agencies don't expect: it changes who shows up.

Clients who pay for a discovery workshop come prepared. They bring decision-makers. They do the pre-work. They show up on time. They engage seriously during the session. And when you present the output document, they've already invested enough that they want to see the proposal succeed — not because you've pressured them, but because they've staked something on the process.

Clients who won't pay for discovery often don't show up that way. They want a vendor who'll figure it out for them, for free, and then do it cheaply. Those engagements tend to run long, pay late, and produce work you're not proud of.

Charging for the agency discovery workshop is not just a margin improvement — it's a client quality filter. The clients who say yes to a paid workshop are telling you something about how they operate. And in agencies where every margin point matters, that signal is worth more than the fee itself.

Getting Started

If you've never charged for discovery before, start small. Design a half-day workshop at $2,500–$3,500. Define one concrete deliverable — a prioritized problem statement and a recommended scope outline. Run it for a prospect you already trust. See what happens.

What most agencies find: the client is more engaged than they expected. The output document is better than what they'd normally produce for free. And when the proposal comes, the close happens faster because the groundwork was already laid.

The first paid discovery workshop is always the hardest to sell. After that, it becomes the way you work.