Discovery sprint
A two-week product discovery sprint that turns an idea for a product, an internal tool or an AI feature into one scoped project, a working proof of concept on your real data, and a go/no-go you can defend.
- Typical duration
- 2 weeks
- Who it’s for
- Teams with an idea and no scoped first project
- You leave with
- One scoped first project, a working proof on your data, and a roadmap you can budget.
What you receive
- Opportunity map of the workflow, with the risky assumptions named
- A thin working proof on your real examples, measured against how the work is done today
- Architecture, data and access requirements for a first production version
- A production roadmap and an honest go/no-go, in writing
How it runs
- Days 1–3Map
Interviews with the people who do the work. We name the assumptions that could sink the project.
- Days 4–8Prove
A thin working version on your real data, measured against how the work is done today.
- Days 9–10Decide
Roadmap, requirements and a go/no-go you can take to your team or board.
Is it the right fit?
Best when
You can see room for new software or AI in operations or in the product, and you want evidence before committing budget and engineers to a build.
Not for
Teams that already know what to build. Go straight to a build.
See Custom software developmentQuestions from the first call
Related servicesCustom software developmentAI products and agents
What is a discovery sprint?
A two-week engagement that ends in a decision. We interview the people who do the work, build a thin working proof on your real data, and hand over a roadmap with a written go/no-go.
Is it only for AI projects?
No. It works for any first project: a product, an internal tool or an AI feature. Where AI is on the table, the proof tests it on your real data, and the roadmap says plainly when a conventional approach is the better answer.
What do we need to provide?
Three to six people for 30-minute interviews, sample documents or data (anonymised is fine), and a decision-maker for the go/no-go readout.
What if the answer is “don’t build anything”?
Then two weeks saved you a much larger mistake, and the roadmap says what to do instead. Often that is a process fix or an off-the-shelf tool.
Is the sprint a sales exercise for a build?
The roadmap is written so any competent team can execute it. If we are the right team we will say so; if not, we will say that too.
Can it run remotely?
Yes. Interviews and the readout run on video in your business hours. Our clients are in the US, UK, Australia and Canada.
What does a discovery sprint cost?
We don’t publish prices. The sprint has a set scope and is quoted in writing after a 30-minute call.
Start with a conversation
We reply with questions or a time for a call, then send a written scope and quote.