Problem and goals
Who it's for, how competitors and existing tools solve it today, and what success looks like in measures you choose.
Brief
Home / Services / Product discovery
Product discovery sprint
Know what it costs.Before anyone writes code.
A short, paid sprint at a fixed price. You get a written scope, an estimate with ranges and a roadmap. Build from it with us or with anyone else.
30 minutes, free. We reply within a few hours with times that suit you.
- Senior team, you keep the code
- EU data, GDPR-first
- Fixed-price start
Sound familiar?
You asked three agencies. The biggest quote is ten times the smallest. Nobody has written down what you're actually buying.
A wide spread in quotes means big unknowns. A short, paid sprint turns them into a written scope. The next number you see is one you can plan with.
Show me examples for
Pick one. The examples on this page will switch to it.
What you get01 02 03 04 05 06 07 08
Eight documents. Enough to start building.
Written for the people who approve the budget and the people who build. If the honest answer is “don't build it”, the documents say so.
User journeys
The people who will use it. The steps they take today, and the steps they will take with the product.
Journey mapsScope: first, next, parked
Every feature goes into the first release, a later phase, or the parked list with a reason.
Prioritised backlogKey screens
Wireframes of the main flows. Everyone agrees on the product before design starts.
Clickable wireframesArchitecture and integrations
Systems, data flow and hosting. Where AI fits, and where it doesn't.
Technical outlineEstimate with ranges
Effort and cost for each item. Plus the assumptions that would move each range.
Estimate sheetPhased roadmap
The first release, what comes after, and the decision points in between.
RoadmapRisks, data and GDPR
What could go wrong. Which personal data moves where. How we would handle each risk.
Risk registerEverything is yours, in formats your team already uses. On the last day we walk you through every document.
From messy notes to a scoped roadmap
Forty pages of notes. Three opinions. No scope.
Everyone has a version of the product in their head. No two of them match on paper.
Sorted by the job each idea does.
We interview the people who will use it. Then we group every idea by the problem it solves.
Cut to what the first release needs.
Ideas that don't change the first result move to Next or Parked. Every idea is kept.
Sized, with the assumptions written down.
Each item gets a range, plus a note on what would change it.
A roadmap any team can build from.
We can build it, and so can any other team. Every document is yours.
Estimate6–8 weeksto a first release, in this example
Discovery board · field-service appRoadmap
First release
Log a visit offline M
Photo and signature on the report S
Report reaches the office the same day M
Sync with the ERP L
Next
Customer portal with report history M
Spare-parts ordering M
Parked
AI summary of every visit
Smartwatch version
Chat between technicians
Custom BI dashboard
First release · 4 items · ranges agreed6–8 weeks Estimate
How the sprint runs
One to two weeks. One fixed price. One clear answer.
Here is the two-week version. Smaller questions fit in one week.
Days 1–2
Listen
We interview the owner, the future users and whoever runs the process today.
Days 3–5
Map
Journeys, scope and the first wireframes. You review each one with us.
Week 2
Size
Architecture, estimate ranges and the phased roadmap, all written down.
Last day
Hand over
We walk you through every document. Then you decide what happens next.
Why we charge for itFixed price Yours Portable No lock-in
A fixed price keeps the plan honest.
Free scoping gets paid for later, inside the build quote. A paid sprint has one job: to tell you plainly what you need.
Agreed before we start
One price for the sprint, quoted after a free 30-minute call. We never bill by the hour.
You own every document
From the last day, the scope, estimate, wireframes and roadmap belong to you.
Take it to any team
Another team can quote from it. Compare their build quote with ours.
Stop with no obligation
If the answer is “not now”, you have spent the price of a sprint. The project budget is still intact.
Honestly
When a sprint helps, and when it doesn't.
A good fit if
- You have an idea or a problem, and the quotes you got range wildly.
- You need a number for a budget or a board before you commit.
- Your team disagrees on what to build first.
- You are changing vendors and need the scope in writing.
Not a fit if
- You already have a detailed spec and a budget. Skip ahead to a pilot.
- You want a reliable estimate in a day. We give a rough range on a call for free. A real plan takes a sprint.
- You need it live next month, with no time to talk to its users.
After the sprint
Where the roadmap usually goes next.
Questions owners ask
Before you book a call.
How much does a discovery sprint cost?
A fixed price, agreed before we start. It depends on the size of the question. We quote it after a free 30-minute call. Most sprints take 1 to 2 weeks.
Do we have to build it with you afterwards?
No. Every document is yours. Any competent team can quote and build from it. If you want us to build it, we quote from the same documents.
What do you need from us?
A few hours of your time each week. Access to the people who would use the product or run the process. Any documents, data or systems involved. We do the interviews, the mapping and the writing.
Can't you just give us an estimate on a call?
Yes, we will give a rough range on the call. It is a useful sanity check. It is not a number to put in a budget. The sprint replaces guesswork with a written scope and written assumptions.
Can you run a design sprint before we commit to a build?
Yes. When the open question is what to build, we start with a design sprint. We look at how competitors and existing tools solve the problem, work out a few possible solutions and prototype the strongest one. You approve the concept before anything is estimated or built. It has a fixed price too, quoted after a free call.
What happens after the sprint?
You decide. If you go ahead, the roadmap becomes the build plan. It usually starts with a 4-week pilot of the first release. That could be AI integration, process automation, a mobile app or a web app.
Prefer to talk? Request a 30-min call.
You talk to the senior engineer who would build it, not a salesperson. Bring one process; we tell you plainly whether it's worth automating.
Request a 30-min call30 minutes, free. We reply within a few hours with times that suit you.