Discovery sprint before development: PRD, architecture, prototype and fixed estimate
In 1–2 weeks we turn an idea into a document a team can build from. Requirements, architecture, screen prototype, integration list and risks. You get a fixed development estimate within 2–3 days after the sprint.
What hurts
Vendor estimates can differ several times over. One says a month, another says half a year. You cannot compare them because each vendor understood the task differently.
Your last project ran twice as long because requirements kept changing. Midway it turned out the CRM did not expose the fields you needed and the design had to be redone.
You do not want to sign a large contract without knowing what you will get. You need a small step after which it is clear what to build, what it costs and what can go wrong.
What we build
- Working sessions with your team and future users
- PRD: goals, user flows, roles, requirements and scope limits
- Solution architecture and AI model selection
- Integration map for CRM, ERP, telephony and messaging
- Clickable Figma prototype of key screens
- Hands-on check of APIs and data in your real systems
- Risk register with mitigation steps
- Week-by-week delivery plan with weekly demos
What you get
- Editable PRD
- Architecture and integration diagrams
- Figma prototype shared with your team
- Fixed estimate and delivery schedule
- Success metric ready to go into the contract
How we measure the result
- Gap between the fixed estimate and the final cost
- Number of scope changes during development
- Time from contract signature to the first demo
- Success metric agreed before development starts
Systems and stack
Industries
Questions
How much does a discovery sprint cost?
From $5,000 for 1–2 weeks. The price depends on the number of user flows, roles and systems to integrate. A single agent with one CRM fits into a week. A platform with several integrations and a client portal needs two weeks.
What does a fixed estimate mean?
We name the price and timeline for the build, and they do not change unless the scope changes. If we exceed the estimate through our own fault, we finish at our own cost. Scope changes from your side are estimated separately before any work starts.
Can we take the discovery results to another vendor?
Yes. The PRD, architecture and prototype are yours. They are written so that any competent team can estimate and build from them. We do not lock you in through discovery documents.
What access do you need during discovery?
Test credentials or API documentation for the systems we plan to connect, and a few hours with people who know the process. We sign an NDA before we start. Real personal data is usually not needed at this stage.
What if discovery shows that AI is not the right tool?
Then we tell you. Sometimes a plain automated workflow or a setting in your existing system solves the task. Discovery exists so that the development budget is not spent on the wrong solution.
Related services
More in this section
Describe the task. We reply within one business day, the first call is with the founder.
Describe the task. The first call is with the founder.
We reply within one business day. 30 minutes to tell you whether it is worth doing and what it costs.