The Discovery Sprint — How to Evaluate a Consulting Engagement Before Committing

Why the Discovery Sprint model exists

The two most common failure modes in consulting engagements are: starting a project without sufficient understanding of the actual problem, and scoping a project before both parties understand the constraints. Both produce the same outcome — work that doesn’t address the real issue, delivered at a cost that doesn’t reflect the complexity.

The Discovery Sprint is a deliberate structural fix for both failure modes. It’s a paid, time-boxed diagnostic that produces three things: a clear picture of the current state, a recommendation for what to do and in what order, and a fixed-fee scope for any follow-on work. Nothing starts until the Discovery Sprint output has been reviewed and agreed.

What happens in a Discovery Sprint

The engagement begins with a structured 45-minute call — not a free discovery call, but a paid working session with a defined agenda. The agenda covers: current situation, the specific problem or goal, constraints (time, budget, internal resources, existing tools), and existing assets (what’s already been built or tried).

Within 48 hours of the call, a written summary is delivered covering: findings from the diagnostic, recommended approach and rationale, what’s in scope and explicitly what’s out of scope, a fixed fee for the recommended work, and the timeline.

The fee for the Discovery Sprint itself — typically $1,500–$2,500 — is credited against the follow-on engagement if you proceed. If you don’t proceed, you have a professional written analysis of your situation that you can use internally or take to another provider.

How to evaluate the Discovery Sprint output

A strong Discovery Sprint output has four characteristics. First, it reflects the actual conversation — the findings should be specific to your situation, not generic recommendations that could apply to any business. Second, the scope is explicit: what’s included is defined, and what’s not included is equally well-defined. Vague scopes always expand. Third, the fee is fixed, not estimated. A well-run Discovery Sprint produces enough information to quote a fixed fee. An estimate with a range is a sign that the diagnostic wasn’t thorough enough. Fourth, the rationale is explained. You should understand why the recommendation is what it is, not just what it is.

Questions to ask before proceeding

After receiving the Discovery Sprint output, the questions worth asking before proceeding: What specific outcomes will I be able to measure at the end of this engagement? What does success look like at 90 days? What are the three most likely reasons this engagement could underdeliver, and how are they being managed? What decisions will I need to make, and when?

Good answers to these questions from a consultant indicate structured thinking and realistic expectations. Vague answers — particularly to the underdelivery risk question — are worth probing further before signing.