Skip to content
Delivery6 Aug 20266 min read

What a two-week discovery sprint actually produces

Not a slide deck. A backlog with estimate ranges, an architecture sketch, a risk register and a number you can defend to your board.

Free estimates are worth what they cost. A vendor who quotes a firm number after one call is either padding heavily or planning a change-request conversation.

The two weeks

Days 1–3. Stakeholder interviews and process observation. We watch people do the job the software is supposed to support.

Days 4–6. Domain modelling. Entities, invariants, and the rules that nobody wrote down but everybody follows.

Days 7–9. Architecture sketch and integration inventory. Every external system, its protocol, its owner, and its known unreliability.

Days 10–12. Backlog construction with three-point estimates. Every item gets optimistic, likely and pessimistic values.

Days 13–14. Risk register and presentation.

What you receive

A backlog you own, an architecture document, a risk register with named owners, and an estimate expressed as a range with confidence levels. If you take that package to another vendor, it will work there too. That is deliberate.

The cost

A discovery sprint is quoted per engagement and is a small fraction of the build it de-risks — it removes the variance that usually shows up later as a 40% overrun.

Tell us what you are building

Send a brief and a solution architect replies within one business day — with questions, not with a template.