Decision Sprints: How Premium Consultancies Run Two-Week Engagements

Most strategic consulting engagements last too long for the question being asked. A founder needs to know whether to build or buy a piece of infrastructure — and they get pitched a six-month transformation programme. A board needs technical due diligence on a target acquisition — and they get a £180k engagement when they wanted a £15k answer.

Decision Sprints solve this. They are a specific engagement shape — two to three weeks, fixed price, fixed scope, single question — that the better consultancies have been quietly running for years. We use them for the questions that deserve a precise answer fast.

This article explains what they are, when to run one, what to expect, and what they cost.

What a Decision Sprint is

A Decision Sprint is a paid engagement of 2 to 3 weeks that produces a single defensible answer to a single high-stakes question, with the reasoning, trade-offs, and recommended action documented in a written memo a board could read and act on.

The shape is deliberately constrained:

• One question. Not three; one. "Should we build or buy our customer-onboarding system?" Yes. "Should we restructure the operations team?" No.
• Two to three weeks. Long enough to do real work. Short enough that the answer is still relevant when you receive it.
• Fixed price. Typically £6k to £12k depending on the question's complexity. No hourly billing.
• Senior operators only. Decision Sprints are not staffed with juniors learning the trade. The work is too compressed for that.
• A written memo as the deliverable. Not slides. Not a presentation. A document that survives being forwarded.

What you get at the end is a defensible answer, written down, that you can act on within hours.

When to run one

The Decision Sprint shape fits a specific set of business questions. Five examples we have run in the last twelve months:

Build vs buy for core infrastructure. A scaling SaaS was deciding between licensing a third-party billing platform or building their own. Cost of the wrong decision: £400k over three years. Cost of the Sprint: £9k. We delivered a memo with the cost model, the strategic trade-offs, and a recommendation; the founder made the call the following Monday. (See the related article: Build vs Buy: The 2026 Framework.)

Technical due diligence for an acquisition. A private equity firm was evaluating a software business. They needed a technical due-diligence memo for the investment committee within three weeks. We assessed the codebase, the architecture, the team's capability, the technical debt, and the deal-critical risks; the memo went into the committee pack on schedule.

Vendor selection for a high-stakes integration. A UK fintech needed to pick a KYC provider. Three vendors shortlisted, none clearly better. We ran technical evaluations of each, modelled five-year cost trajectories, mapped integration burdens, and recommended one with explicit reasoning. The decision was made and the integration shipped without revisiting the choice.

Scale-readiness audit before a fundraise. A consumer SaaS was raising a Series A and the lead investor wanted comfort that the operational stack would not break at 3x current scale. We audited the systems, identified the three real bottlenecks, modelled the cost and time to fix each, and produced a memo the investor was satisfied with. The round closed on the agreed timeline.

Capability audit for a CTO hiring decision. A growing services business was deciding whether to hire a CTO or continue with fractional engineering leadership. We assessed the technical work coming over the next 18 months, modelled the cost and capability difference between the two paths, and recommended fractional with explicit triggers for revisiting the question.

The thread that runs through all five: a single, important, time-bound question with a defensible answer waiting to be found if someone senior spends two focused weeks on it.

What happens during the two weeks

A typical Decision Sprint runs in three distinct phases, with cadence built in so the client sees progress.

Days 1 to 4: Diagnostic

We start by understanding the question deeply. This means:

• A 90-minute kickoff with the leadership team to align on what specifically is being asked, what the constraints are, and what would constitute a "good" answer.
• Interviews with the 4 to 8 people who hold the most context — usually a mix of founders, engineering leads, finance, and operations.
• A thorough read of every relevant prior document, data export, contract, or analysis.
• A first-draft framing of the answer's likely shape, shared back to the client by end of week one as a working hypothesis.

The diagnostic phase is where most of the value gets created. The work is to get the question right before doing the work.

Days 5 to 10: Analysis

The analytical core of the Sprint. Specifics vary by question type but usually include:

• Cost modelling across the relevant options, with sensitivity analysis on the key assumptions.
• Risk assessment — what is the worst case under each option, and how likely.
• Comparative research — what have similar businesses done in similar situations, and what was the outcome.
• Where applicable, technical assessment — codebase walkthroughs, vendor capability checks, integration scoping.

We aim to deliver a working-draft memo to the client by day 10. Not the final version — the draft we want feedback on.

Days 11 to 14: Refine and deliver

The final phase is iteration. We take the draft memo, run a working session with the leadership team to pressure-test the recommendation, and refine in response to the questions raised. The final memo is delivered with:

• A one-paragraph executive summary the board can read in 30 seconds.
• A one-page recommended action with the reasoning.
• The full analysis, footnotes, and assumptions for anyone who wants to verify.
• An appendix of "questions we did not answer" — the things that came up that are out of scope for this Sprint but worth thinking about separately.

We close with a 60-minute handover session so the leadership team can walk through the memo with us before acting on it.

What you do NOT get from a Decision Sprint

Being explicit about scope is half the value. A Decision Sprint is not:

An implementation engagement. Decision Sprints produce decisions, not implementations. If the recommendation is "build this thing", that build is a separate engagement (typically a Build Sprint — see /services/software-development).

A blank-cheque investigation. Decision Sprints are scoped tightly. If the work uncovers a different question that also needs answering, we flag it as out-of-scope and recommend either extending the Sprint or running a follow-on Sprint. We do not silently expand.

A monthly retainer. Decision Sprints end. If you want ongoing advisory after the Sprint, that is a separate engagement under Strategic Advisory.

A guarantee that you will like the answer. We commit to a defensible answer with the reasoning shown. We do not commit to the answer you wanted before the Sprint started. The whole point of running one is to find out what the right answer is, including when it is not the obvious one.

How Decision Sprints are priced

Our standard Decision Sprint pricing is £6,000 to £12,000 fixed-price, depending on:

• Complexity of the question (a vendor-selection question is cheaper than a technical-due-diligence question)
• Depth of technical assessment required (codebase reviews push the price up)
• Number of stakeholder interviews required (more stakeholders, more time)
• Geographic or scheduling constraints (compressed timelines on the same scope cost more)

50% is invoiced on kickoff, 50% on delivery of the final memo. We do not offer credit terms because the work cannot be paused once we are in it.

For comparison: the Big Four consultancies will quote £40k to £120k for similar work, on a 4 to 8 week timeline, staffed primarily with junior associates. The trade-off is that Big Four work carries the institutional weight of the brand, which is sometimes what the situation requires (board investor committees that demand a Big Four signature). For everything else, a Decision Sprint with a senior operator is faster, cheaper, and usually more useful.

When NOT to run a Decision Sprint

Three situations where a Decision Sprint is the wrong shape.

When you already know the answer and want validation. Pay-to-validate consulting is a poor use of money. If you know what you want to do, do it. If a board is forcing you to seek validation, push back; an external memo will not actually de-risk a decision the leadership team has already made.

When the question is too small. If the decision is worth less than 10x the cost of the Sprint, the maths does not work. A Decision Sprint costs £6k+; the decision should be worth £60k+ to justify it. For smaller decisions, write the analysis yourself.

When the question is too big. "What should our 5-year strategy be?" is not a Decision Sprint question. It is a multi-month embedded engagement. Decision Sprints work for sharp, specific, contained questions — not for strategy at large.

How to scope a Decision Sprint for your business

If you are wondering whether your current question is Decision-Sprint-shaped, check it against this list:

• [ ] The question can be stated in one sentence
• [ ] A "yes/no" or "option A vs option B vs option C" answer would resolve it
• [ ] The cost of getting the answer wrong is at least 10x the cost of the Sprint
• [ ] The decision needs to be made within 30 days
• [ ] No other engagement is currently chasing the same answer

If all five are true, a Decision Sprint is probably the right shape. Book a 20-minute call to talk through whether your specific question fits. If it does, we will scope it together; if it does not, we will tell you what shape would fit better.

For full detail on engagement shapes and pricing, see /pricing.

Premium consultancy is not about long engagements; it is about precise ones. Decision Sprints exist because the best business decisions deserve a sharp answer, fast, with the reasoning shown.