Every prospect we've ever worked with has asked the same question: "Can we just skip the Discovery Sprint and start building?" The honest answer is yes, you can, and it will almost always cost you more in the end. Here's why we charge for it, what you actually get, and the maths on whether it's worth the £1,500.
What a Discovery Sprint actually produces
Five working days, output-focused. You leave with:
- Locked scope: what the MVP includes, and (crucially) what it doesn't
- User flows: the 3–5 core journeys mapped step by step
- Success metrics: what we'll measure on launch day to know if it worked
- Tech plan: stack, hosting, third-party services, what's bespoke vs. off-the-shelf
- Fixed quote: for the build itself, holdable, no surprise change requests
- Clickable prototype direction: wireframe-level, enough to trigger "actually I want it to work like THIS instead"
All of that is yours. If you decide to take the deliverable to another studio, or build it in-house, you've spent £1,500 to get clarity. That's the deal.
What happens when you skip it
We've watched this play out enough times to predict the timeline almost exactly:
- Week 2: First "actually, can we add..." comes in. Small, easy. Said yes.
- Week 4: Three more "actually"s. The original scope no longer makes sense as a coherent product.
- Week 6: Major flow needs reworking because two later requirements collided with an early architectural choice.
- Week 8: Either timeline slips, or quality drops, or both. Cost overrun starts.
- Week 10: Ship something that's 70% of what you wanted, 130% of what you budgeted.
Not because anyone did anything wrong. Because you were making decisions under deadline pressure that should have been made under design pressure.
The cost-of-skipping maths
| Path | Cost | Outcome |
|---|---|---|
| Discovery Sprint + MVP build (typical) | £1,500 + £20,000 = £21,500 | Ships on time, on scope |
| Skip discovery, MVP build with rework | £20,000 + ~25% overrun = £25,000 | Ships late, scope reduced |
Net: skipping discovery costs you £3,500 more, ships later, and delivers less.
Why we charge instead of giving it away
Free discovery work is, ironically, why most agencies do it badly. When discovery is unpaid:
- It's optimised for converting you into a build engagement, not for de-risking your project
- The studio rushes it (because it's not billable)
- You don't take it seriously (because it cost you nothing)
- The deliverable is a sales pitch, not a working plan
Charging £1,500 changes the dynamics on both sides. We do the work properly. You take the output seriously. And if at the end of the week we both decide it isn't a fit, you have a real plan you can use elsewhere.
When you genuinely don't need it
We'll tell you. If you arrive with a clear scope doc, validated user flows, an existing design system, and an obvious tech direction, we'll roll you straight to a build quote. It happens maybe once in 20 prospects. The other 19 think they're in that bucket and are not.
The only people who genuinely don't need discovery are people who've already done it, usually because they tried to skip it on a previous project and learnt the hard way.
Read about our Health & Wellness MVP Launch package, or start with a Discovery Sprint.