Discovery phase
Paid research before a build, in which the team maps what the business really needs and returns a scope and architecture it can price against.
Updated October 2026 · with examples from our own builds
What does discovery phase mean in practice?
Discovery answers the questions that make an estimate honest. Which parts of the current system or process are really used? Which rules are easy to get wrong? Which decisions can't be reversed later? The output is a written scope, a proposed architecture, a list of risks and the questions the client still has to answer.
Think of it as insurance against building the wrong thing well. It takes a few weeks, and it often ends in a smaller first release than expected, because mapping real use shows how much of the wish list nobody needs.
Its limit is that it produces decisions, not software. A discovery pack that ends in vague recommendations hasn't done its job; look for named trade-offs, a build order and open questions you can actually answer.
Discovery phase at a glance
- Output
- Scope, architecture, risk list and open questions
- Good sign
- Irreversible decisions flagged before the quote
- Not included
- Working software
Where has discovery phase come up in our builds?
We walked a legacy ERP of over 400 screens and about 20 integrations menu by menu with an admin login, recorded only what the business relies on, mapped six regulatory milestone flows and wrote ten questions the client must answer before a firm quote. No code has been written.
The research pack profiled the reference product and four alternatives, compared cloud, desktop and extension architectures, and delivered a risk register covering terms of service, maintenance, LLM cost, voice consent and the DPDP Act. Nothing was built.
Common questions about discovery phase
What should a risk register from discovery contain?
Each risk named plainly, what it would cost if it happened and what the design does about it. ZenFlow's register covered LinkedIn's terms on automation, the running cost of selectors that break, LLM spend, consent for voice cloning and DPDP Act duties.
Can discovery tell me to build less than I planned?
It should, when the evidence says so. Mapping the customs broker's legacy system showed many modules, from tariffs to the CRM, saw no use, so the proposed first phase covers the work that matters with one job engine.
Related terms
Planning a product and not sure where discovery phase fits? Ask us, or browse all 116 terms in the glossary.