Map the workflow, scope the build, agree the bar before code is written.
A two-week sprint that takes "we should build something" into a fully-scoped project with budget, timeline, and a definition of done.
Why this engagement exists.
In two weeks we turn "we should build something" into a 30-50 page scoping document that becomes your SOW, your internal requirements doc, or the brief for another vendor. The document is yours: take it to your own team, to us, or to a competitor; most clients proceed with us, but that is a separate decision. We lock the scope, sketch the architecture, and estimate with real confidence bands (P50, P90), so the risk is visible, not buried in one date. The work starts aligned because the alignment was the work.
Deliverables, not promises.
Every engagement ships these artefacts. Nothing here is fluff. Each item is something your team will hold in their hands at the end.
Stakeholder interviews
Structured interviews with the people who will use, build, and pay for the system.
User journey + workflow map
Current-state and target-state workflow with friction points called out.
Technical scope
Architecture sketch, integration surface, technology recommendations.
Phased delivery plan
Phased plan with milestone-level estimates and dependency mapping.
Risk register + assumptions
What could derail this, and what assumptions we are explicitly making.
Estimate with confidence
A range with two confidence bands: P50 (our midpoint) and P90 (the date we would stake our reputation on), not a single number that hides the risk.
The process, step by step.
No mystery, no consultant theatre. This is how the work actually flows from kickoff to handover.
- Day 1-3
Stakeholder interviews
Engineering lead, product owner, end-user representative, compliance lead if applicable.
- Day 4-6
Workflow mapping
Current-state and target-state user journeys, friction points, edge cases.
- Day 7-9
Technical scope
Architecture sketch, integration surface, technology choices, risk register.
- Day 10
Delivery plan + estimate
Phased delivery plan, milestone estimates, confidence bands, final presentation.
Two weeks of discovery is cheap insurance against months of building the wrong thing. The 30-50 page document is the cheapest place to change your mind, before a line of code is written, while the scope is still just words on a page.
The questions that actually come up.
A scoping document (30-50 pages) + a presentation. The document can become the SOW for the build engagement, the requirements doc for an internal team, or the brief for another vendor.
Related services
All servicesAI Strategy & Roadmap
A 4-6 week engagement that takes you from "we should do AI" to a roadmap, an architecture, and a team plan you can defend in the next board meeting.
Architecture Review
Two to three weeks. A senior architect reviews your system, finds the cracks before they cost you. Honest, actionable, no upsell.
End-to-End Product Development
Discovery, design, engineering, launch. One team, one timeline, one definition of done.
Ready to scope Discovery Workshop?
A 30-minute call. We map your situation against the engagement, give you a real estimate, and tell you honestly whether we are the right team for this.