What Is a Discovery Sprint? (And Why You Should Do One Before Building Anything)

A Discovery Sprint is a focused engagement that tells you exactly what to build, what it'll cost, and whether it's worth doing — before you invest in development.

A Discovery Sprint produces a build-ready specification, accurate cost estimate, and go/no-go decision in 1-2 weeks for £5,000. Here's what happens, what you get, and why it prevents the most expensive mistake in software.

A Discovery Sprint is a focused 1–2 week engagement that answers three questions before you invest in building software: What exactly should we build? How much will it cost? And is it worth doing?

The output is a build-ready specification — a document detailed enough that any competent developer could build from it, with accurate cost estimates and a confident go/no-go decision. It costs £5,000 and it's the single most valuable step in the entire service-to-software journey.

Why? Because the most expensive mistake in software development isn't a costly build. It's building the wrong thing.

Why Discovery Exists

CB Insights found that 42% of startups fail because there's no market need. For service businesses building software, the equivalent failure mode is subtler: building a product that solves a real problem but solves it in the wrong way, with the wrong features, for the wrong audience.

I've seen this pattern across 100+ builds over 18 years. A founder comes with a 30-feature wishlist. Fifteen of those features are essential for version 1. Ten are nice-to-have for version 2. Five are things they'll never build because user feedback will take the product in a different direction.

Without Discovery, all 30 features go into the build. The budget doubles. The timeline stretches. And on launch day, users only touch 5 of the 30 features regularly.

With Discovery, we identify the 5–8 features that deliver 80% of the value, defer the rest to the roadmap, and build version 1 for a fraction of what the 30-feature version would cost.

Discovery typically saves 2–3x its £5,000 cost in avoided development. That makes it the highest-ROI investment in the entire process.

What Happens Inside a Discovery Sprint

A Discovery Sprint has four components, delivered across 1–2 weeks. Here's what each involves and what it produces.

1. Business Audit

Duration: 2–3 days

This is where I get deep into your service business. Not the surface — the operations.

We examine your current service delivery process — every step, every handoff, every decision point. I'm looking for the repeatable patterns that encode well in software and the exceptions that don't.

We review your client base — who they are, what they pay, what they value most, and what they complain about. This reveals which of the 15 product types fits your business.

We assess the competitive landscape — what exists, what's missing, and where your domain expertise creates an advantage that generic competitors can't replicate.

And we look at the economics — your current revenue, your margins, what you can invest, and what return the product needs to generate to justify the investment.

Output: A clear understanding of the business context that the product must serve.

2. Product Vision

Duration: 3–4 days

This is the core of Discovery — translating business understanding into a product specification.

We define the core user flows. Who uses the product? What's their journey from first visit to regular usage? What does each screen show them? What actions can they take? For products with multiple user types (most service business products have at least two — clients and operators), we map each journey separately and identify where they intersect.

We determine the feature set for version 1. This is where the hardest decisions happen. Everything that doesn't directly serve the core user journey gets moved to version 2. This isn't about cutting corners — it's about focus. A product that does 5 things brilliantly beats one that does 20 things adequately.

We define the data model. What information does the product store? How does it relate? What needs to be searchable, filterable, or reportable? Getting this right during Discovery means the build phase goes smoothly. Getting it wrong means rebuilding the foundation mid-project.

Output: User flows, feature list (prioritised), data model, and wireframes for core screens.

3. Technical Feasibility

Duration: 2–3 days

Some product ideas are straightforward to build. Others have technical constraints that change the cost, timeline, or approach.

We assess integration requirements — what existing systems does the product need to connect with? Payment processors, email services, CRMs, booking systems, third-party APIs? Each integration adds complexity and cost.

We evaluate AI capabilities — if the product includes AI features (matching, scoring, recommendation, generation), we determine what's possible with current tools, what requires custom models, and what's better left for version 2.

We decide on infrastructure — hosting, database, deployment strategy, security requirements. For products handling sensitive data (financial, health, personal), compliance requirements shape these decisions.

Output: Technical architecture, integration map, and any constraints that affect scope or cost.

4. Build-Ready Specification

Duration: 2–3 days (synthesis)

Everything from the first three components gets consolidated into a single document that serves as the blueprint for the build.

The specification includes user stories (specific, testable descriptions of what users can do), the data model (tables, relationships, access patterns), API specifications (what the backend exposes, what the frontend consumes), acceptance criteria (how we'll know each feature is complete), a prioritised feature list (what's in version 1 versus version 2), and a cost estimate (accurate to ±15%, not a ballpark guess).

This document is yours. If you decide to build with me, it becomes the build plan. If you decide to build with someone else, it's the specification you hand them. You're never locked in.

Output: A complete build-ready specification with accurate cost estimates.

The Go/No-Go Decision

At the end of Discovery, you have everything you need to make an informed decision.

Go: The product opportunity is validated, the scope is clear, the cost is within budget, and the expected return justifies the investment. The next step is the 30-day build.

No-go: Discovery reveals that the opportunity isn't what it seemed, the cost exceeds what the business can justify, or the market isn't ready. This saves you £15,000–£45,000 you would have spent building the wrong thing.

Pivot: Discovery reveals a different — often better — opportunity than the one you came in with. This happens more often than you'd think.

RiskPod is the clearest example. The founder initially envisioned a simple job board. Discovery revealed that the real value was in his matching methodology — the process he used to connect compliance contractors with the right roles. The product pivoted from a job board to a two-sided marketplace with AI-powered matching. That pivot, identified before a single line of code was written, is the reason RiskPod generated 550+ signups in its first 48 hours.

What Discovery Costs vs. What It Saves

Discovery costs £5,000. Here's what it typically saves.

Feature cutting saves £10,000–£20,000. Most founders arrive with 25–30 features they consider essential. Discovery usually reduces version 1 to 8–12 features. At £1,000–£2,000 per feature, that's significant savings on the build.

Architecture decisions save £5,000–£15,000. Getting the data model right the first time avoids the most expensive kind of rework — restructuring the database mid-build. I've seen this add 30–50% to project costs when it happens.

Specification clarity saves 2–4 weeks. A clear spec means fewer questions during the build, fewer misunderstandings, and fewer course corrections. That translates directly to faster delivery and lower costs.

No-go decisions save £15,000–£45,000. Roughly 15% of Discovery Sprints end with a no-go recommendation. That's not a failure — it's £15K–£45K saved on a product that wouldn't have worked.

Total typical savings: 2–3x the £5,000 Discovery investment.

How Discovery Fits the Full Journey

Discovery is Phase 3 of the service-to-software playbook. It follows identification (Phase 1) and validation (Phase 2), both of which cost nothing or very little.

The full timeline:

Weeks 1–3: Identify the opportunity and validate demand (£0–£500)
Weeks 4–5: Discovery Sprint (£5,000)
Weeks 6–10: 30-day build (£15,000–£45,000)
Week 11+: Ongoing growth and iteration (£250–£2,000/month)

Each phase earns the next. You never commit to the full investment upfront. The free call earns Discovery. Discovery earns the build. The build earns the ongoing relationship.

Who Should Do a Discovery Sprint

Discovery is right for you if you've identified a product opportunity but aren't sure exactly what to build, you've collected agency quotes and want a second opinion on scope and cost, you want a build-ready specification before committing to development, or you've scored 5+ on the readiness checklist and you're ready for the next step.

Discovery might be premature if you haven't validated demand with potential users yet (do Phase 2 first), your service business doesn't have a repeatable process yet (focus on the service first), or you're not ready to invest in development within the next 3 months (wait until timing is right).

Frequently Asked Questions

What's the difference between a Discovery Sprint and a proposal from an agency?

An agency proposal estimates what they'll charge to build your idea. A Discovery Sprint challenges whether your idea is the right thing to build, refines the scope to maximise value, and produces a specification that any developer can use. The proposal is a sales document. The Discovery Sprint is a strategy engagement.

Can I do Discovery with one developer and build with another?

Yes. The specification belongs to you. It's detailed enough that any competent developer can build from it. You're never locked in. Some clients use Discovery to get clarity, then decide which development approach suits them best — agency, offshore, or AI-accelerated.

What if Discovery tells me not to build?

That's a success, not a failure. You've spent £5,000 to avoid spending £15,000–£45,000 on something that wouldn't have worked. Roughly 15% of Discovery Sprints end with a no-go or significant pivot. In every case, the founder was grateful for the clarity.

How involved do I need to be during Discovery?

Expect 10–15 hours across 1–2 weeks. This includes an initial deep-dive session (2–3 hours), daily check-ins (30 minutes each), and a final review of the specification (1–2 hours). Your domain expertise is the most valuable input — nobody understands your service business better than you.

Is £5,000 negotiable?

The price reflects the depth of work involved — business audit, product vision, technical feasibility, and specification writing. It's priced to be accessible while ensuring the output is thorough enough to guide a successful build. The ROI is typically 2–3x in avoided development costs.