The Discovery Sprint That Pays for Itself: Selling Paid Scoping Before You Quote

Every agency has lost money the same way at least once: a prospect asks for "a rough estimate", you spend two weeks with your best people drawing wireframes and sizing tickets, and then they ghost you — or worse, they hire your cheapest competitor with your architecture diagram in their brief. The fix isn't tighter sales scripts. It's charging for the scoping itself.

A paid discovery sprint is the single highest-leverage change we've seen agencies make to their sales motion. Done right, it filters tyre-kickers, produces a quote you can actually defend, and turns the first invoice into a trust-building event rather than a bet. Here's how to sell it, run it, and price it without scaring off good clients.

Why free scoping is a tax on your best clients

Free scoping sounds generous. It's actually regressive. The prospects who negotiate hardest for free work are almost always the ones who'll negotiate hardest on the build, on change requests, and on the final invoice. Meanwhile, the clients who are serious — the ones with budget, urgency, and internal alignment — are perfectly happy to pay for a proper diagnosis. They do it with lawyers and accountants without blinking.

When scoping is free, three things happen:

• Your senior people become a loss leader for deals that don't close.
• Estimates get padded because you're guessing under time pressure.
• Clients don't value the artefacts, because free things aren't precious.

The agencies we've watched grow past the ~15-person ceiling almost all charge for discovery. Not because they figured out a clever sales hack, but because they stopped subsidising their pipeline with unpaid engineering hours.

What a discovery sprint actually is

A discovery sprint is a fixed-fee, fixed-duration engagement that ends in a document a competent agency (you, or someone else) could quote and build from. It is not a workshop. It is not a proposal. It is billable, contracted work with deliverables.

Our default shape:

• Duration: 1 to 3 weeks, calendar time.
• Team: one senior engineer, one product/design lead, part-time PM.
• Fee: 3 – 8% of the estimated build cost, invoiced up front.
• Deliverables: a written scope document, a rough architecture, a risk register, a phased estimate with ranges, and a go/no-go recommendation.

The fee isn't the point. The point is that once money changes hands, the relationship shifts from "vendor pitching" to "consultant hired". You get access to their real stakeholders, their real data, their real constraints. You stop performing and start diagnosing.

What goes in the deliverable

The document you hand over at the end should be something the client owns and could, in theory, take elsewhere. Don't hold it hostage — that's what makes it worth paying for.

A sensible outline:

1. Problem statement in the client's own words, edited for clarity.
2. Users, jobs-to-be-done, and the two or three critical flows.
3. Proposed scope for v1, with explicit non-goals.
4. Architecture sketch: services, third parties, data model at the entity level.
5. Risk register: technical, commercial, regulatory, and organisational risks.
6. Estimate with ranges (low/likely/high), broken into phases.
7. Recommendation: build now, build later, buy off the shelf, or don't build.

That last item is what separates real discovery from a dressed-up sales pitch. If the honest answer is "you should use Shopify plus two apps and not hire us", say so. You'll lose one deal and win five referrals.

How to sell it without losing the deal

The objection is always the same: "Other agencies do this for free." The response is not a discount. It's a reframe.

What we say, more or less verbatim:

"We used to do it for free. What we found is that free estimates are always wrong, because we're guessing under sales pressure. You'd end up with a number that's either padded to protect us, or too low and we'd fight about change requests for six months. Charging for discovery means we can actually go find the answers. If you don't like what we produce, you owe us nothing further and you keep the document."

Three things make this work:

• Anchor to their risk, not yours. The pitch is that discovery protects them from a bad quote, not that it protects you from wasted effort.
• Make the fee small relative to the build. 5% of a £120k project is £6k. That's a rounding error against the cost of building the wrong thing.
• Offer to credit it against the build. If they proceed with you within 30 days, the discovery fee comes off the first invoice. Now it's genuinely free if they were serious.

About a third of prospects will still walk. Good. Those were the deals that would have hurt you.

Running the sprint like an engineer, not a salesperson

Once the SOW is signed and the deposit clears, the mode changes completely. You are no longer selling. You are doing paid work with a deadline. Treat it like a real project.

A rough week-by-week for a two-week sprint:

Week 1
  Mon  Kickoff, stakeholder map, access to systems/data
  Tue  User interviews (3-5), competitor teardown
  Wed  Flow mapping, data model draft
  Thu  Architecture spike, third-party API validation
  Fri  Internal review, risk register v1

Week 2
  Mon  Estimate workshop with the delivery team
  Tue  Draft scope document
  Wed  Client review of draft, adjust
  Thu  Final estimate, recommendation
  Fri  Handover meeting, deliverable sent

The non-obvious rule: the people running discovery must be the people who'd run the build. If your sales engineer scopes it and a different team delivers it, the estimates will be wrong and the client will feel bait-and-switched at kickoff.

The "walk away" clause

Your SOW should say — in plain English — that either party can decline to proceed to build after discovery, with no further obligation. This sounds like it weakens your position. It doesn't. It signals that you're confident enough in the diagnosis to let the client decide freely, and it removes the fear that discovery is a slippery slope into a bad contract.

In our experience, when both sides know they can walk, almost nobody does.

Pricing math that actually works

Some rough ranges from what we've seen work across small and mid-sized agencies:

• Estimated build £30k – £75k → discovery fee £2.5k – £4k, 1 week.
• Estimated build £75k – £200k → discovery fee £5k – £10k, 2 weeks.
• Estimated build £200k+ → discovery fee £12k – £25k, 2 – 3 weeks, sometimes staged.

Don't price discovery as a rate card exercise ("two people × two weeks × day rate"). Price it as a percentage of the risk you're de-risking. The client is buying certainty, not hours.

One caveat: if you're a five-person agency and the prospect is a Fortune 500, your discovery fee needs to look serious or procurement won't take it seriously. £3k feels like a trial; £18k feels like a project. Sometimes the higher number closes faster.

What changes downstream

Agencies that adopt paid discovery tend to see the same pattern after six months:

• Proposal-to-close rates go up, because the people who pay for discovery almost always proceed.
• Build-phase margin goes up, because estimates are grounded in real investigation.
• Change request fights go down, because scope was written together, not imposed.
• Sales cycle gets shorter overall, even though there's an extra step, because discovery replaces three rounds of "can you clarify the estimate?"

The cultural change is bigger than the commercial one. Your senior engineers stop resenting sales, because they're paid for the work they were already doing. Your PMs get to plan against a real document. And your clients get a partner who told them the truth before taking their money for the build.

Where we'd start

If you've never charged for scoping, don't try to roll it out across every deal at once. Pick the next three inbound leads over your average project size and quote them a paid discovery sprint instead of a free proposal. Use a one-page SOW, a fixed fee, and the credit-back clause. See how many say yes.

Our bet: at least one will, and the deliverable you produce for that client will be better than any free proposal you've ever written. From there, it's a matter of writing the template once and never quoting into the fog again.

If you want a sanity check on your current sales-to-delivery handoff, our product strategy and delivery teams do exactly this kind of paid discovery for clients every week, and we're happy to compare notes.