The output is short, dense, and reviewable. Your engineering leadership can disagree with specific lines.
Eight pages on average. C4 diagrams. ADRs for major choices.
Top 10 risks, ranked, owned. The kind of paper that prevents quarterly fires.
Realistic phasing with a cost envelope, not a Gantt fantasy.
Even if we don’t continue together, your team is now aligned on the system.
The whole sprint exists to leave behind an artifact you’d be willing to publish internally — concrete, reviewable, honest.
8–12 page PDF + Markdown. C4 diagrams, data model, key ADRs, non-functional targets, constraints.
Top 10 risks, ranked by likelihood × impact, each with named owner and mitigation. Live spreadsheet you can update.
3–5 phases with team shape, cost envelope, critical path, and explicit off-ramp markers per phase.
Who has skin in the game, what they’re optimizing for, and what tradeoffs each is uniquely qualified to make.
A short, opinionated take from us: should you build this, with whom, on what timeline. Plain language.
Most discovery sprints are one week. We extend to two when the system spans multiple existing surfaces or when discovery turns up significant unknowns.
Stakeholder interviews, existing-system tour if relevant, constraint capture. We start writing the brief on day one, not day five.
Architecture options sketched in real-time. Two or three credible shapes considered before convergence. Risk register growing.
Phasing, team shape per phase, cost envelope as a range with named drivers. Critical path identified.
Final readout to your team with the written brief, risk register, plan, and recommendation memo in hand. Q&A. Done.
If something isn’t answered here, ask in your intro email — we keep this list short on purpose.
Yes. If we move into a Build engagement within 90 days of the sprint, the full sprint fee gets credited against your first invoice. No fine print.
You keep the brief, the risk register, the plan — all yours, all useful, regardless of who builds it. We’ve had clients use a KVB sprint to brief a different studio; that’s fine.
Yes. We have a 100% remote version of the sprint that uses async interviews + 3 live workshops. Slightly longer (2 weeks) but functionally equivalent output.
Yes. Mutual NDA in the intro packet. Usually signed within two business days of inbound.
Send a paragraph about the problem. We’ll come back inside 48 hours with a written take — team shape, cost envelope, riskiest assumptions.