Build Sprint
Working software changes the conversation faster than another planning cycle.
A short, bounded first engagement for organizations that already know what needs to change. It produces something real — and the evidence to decide whether to continue.
When it fits
The direction is clear. The capacity is not.
- A workflow the organization has outgrown and keeps deferring.
- A capability the business has described the same way for three planning cycles.
- An AI opportunity leadership wants proven rather than presented.
- A programme that needs one real artifact before the next funding decision.
Uncertainty resolving into evidence
A Sprint produces a decision, not merely software.
Someone who does the work uses what was built.
- Deploy
- Expand
- Co-Build
- Buy
- Redesign
- Stop
How it runs
Make the first commitment smaller. Make the evidence stronger.
Stopping should be an ordinary decision.
- One problem, bounded
- A single workflow or capability, scoped so that stopping afterward is an ordinary decision rather than an incident.
- Real software, real users
- The objective is working capability someone can use — not a demonstration designed only to look convincing.
- Agreed evidence
- What would count as a good result — and what would justify not continuing — is defined before the work starts.
- A production path
- Where the sprint continues, environments, controls, and release responsibilities are already understood.
Who takes part
A small group with the authority to decide what happens next.
Participation is deliberately focused. The point is evidence, not a programme.
- A sponsor who can act on the result.
- Someone who knows the workflow as it actually operates today.
- A technical contact for systems, access, and environments.
- Optionally, engineers from your team who want to build alongside ours.
Possible outcomes
Don’t begin with transformation. Begin with evidence.
- Continue — extend the work toward production.
- Adjust — the problem was real, but not the one assumed.
- Transfer — your team carries it forward from here.
- Stop — the evidence did not justify continuing.
Distinct from
A Second Opinion examines a commitment. A Build Sprint produces working evidence.
If a proposal is already on the table and the question is whether to approve it, start with a Second Opinion. If the question is whether this can be built at all, on this timeline, start here.
Stop can be a successful outcome.
Engage