A strategic session looks at the business as a whole and where it should go; an MVP review assesses a first version that already exists. Discovery prepares one specific product for development, so that the price, the deadline and the team rest on documents you can check, not on a short brief.
Discovery Phase
You have an idea for a new product, an internal system or a large site, and the quotes you got are far apart, because each team is pricing its own guess about the scope. The Discovery Phase replaces guesses with a plan: in 2 to 4 weeks we work out what the product must do, for whom, how it will be built and what it will really cost.
From $4,000
9Years in the market
50+Team & partners
127Projects delivered
12Countries
Up to 700%Revenue growth
48hProject start
What the work covers
-
01.
Goals and users
What the product must achieve, who will use it and which tasks matter most. We agree on what counts as success for the first release.
-
02.
Requirements
Roles, permissions, data, reports, speed and security, written in plain language. What stays out of scope is written down too.
-
03.
User flows and prototype
The key journeys as flows, then a clickable prototype of the main screens, so you can test the product before a line of code is written.
-
04.
Architecture and stack
How the system is structured, where the data lives and which technologies fit the task and long-term support, with the reasons for each choice.
-
05.
Integrations and risks
Payments, CRM, ERP, accounting, logistics and other systems the product must talk to, checked against their real documentation. Risks are listed with ways to reduce them.
-
06.
Backlog and estimate
A prioritized backlog, a budget and timeline for each stage, and a team plan: which roles are needed and for how long.
How it works
01
04
01
04
A first call
You tell us about the product and what already exists: notes, mockups, old systems. We agree on the scope and fix the price before any work starts.
02
04
02
04
Interviews and research
We talk to you, your team and, where it makes sense, future users, and study the processes and systems involved.
03
04
03
04
Design and architecture
A business analyst writes the requirements, a designer builds the flows and the prototype, and an architect chooses the structure and the stack. You review the work every week, so there are no surprises at the end.
04
04
04
04
Estimate and handover
We present the backlog, the estimate and the team plan on a call and hand over all the files.
What you get
The documents belong to you and are written so that any team can work from them. You can continue with us in MVP development, a web application or a dedicated team, or give the package to another vendor and compare quotes on equal terms.
A requirements document with what is in and out of the first release.
User flows and a clickable prototype of the key screens.
An architecture description with the chosen stack and the reasons for it.
A map of integrations and a register of risks.
A prioritized backlog with a budget and timeline estimate for every stage.
A team plan: roles, seniority and duration.
Get a cost and timeline estimate
Pricing
From $4,000
The final price depends on the size of the product, the number of user roles and how many integrations have to be studied. The price is fixed before discovery starts.
The price includes the interviews, all documents, the prototype, the estimate and the final call. Development itself is not included; it is priced separately, based on what discovery shows.
All prices →Ask a question
Leave your contacts and we will contact you at a convenient time.
FAQ
How long does discovery take?
Usually 2 to 4 weeks. It depends mostly on the number of integrations and on how quickly the people we need are available.
Why pay for discovery when estimates are free?
A free estimate is based on a short brief, so the team either adds a large safety margin or meets the real scope halfway through the project. Discovery gives the price and the deadline something solid to stand on.
Do we have to build the product with you afterwards?
No. The documents are yours and written for any team, so you can compare vendors on the same scope.
How is this different from a strategic session or an MVP review?
A strategic session looks at the whole business and its direction. An MVP review assesses a first version that already exists. Discovery prepares one specific new product for development.
What do you need from us?
A person who can make decisions, a few hours a week for interviews and reviews, and access to existing materials and systems.
What if discovery shows the product should not be built as planned?
Then you learn it for the price of discovery, not of development. We explain what to change: a smaller first release, a different order of features or an existing tool instead of custom code.