Key takeaways
- Discovery answers what to build, in what order, how it will work technically, and what it is likely to take.
- You should finish with documents you own and can take to any supplier, not a lock-in.
- It is most valuable when requirements are unclear, systems are complex, or the budget has to be justified.
- A good supplier will tell you if the project should not go ahead.
What is technical discovery?
Discovery is a short phase before development where the supplier works with you to understand the problem, the users and the existing systems, then turns that into a plan. It is not a sales pitch and it is not a build. Its output is clarity.
What does discovery cover?
- The problem and the users. Who needs this, what they do today and what success looks like.
- Scope and priorities. What belongs in the first release and what waits.
- Existing systems and data. What the new software must connect to, and what state the data is in.
- Technical approach. Architecture, hosting, security and third-party services.
- Risks. What could delay or derail the project, and how to reduce it.
- Plan and estimate. An order of work and a range based on what was learned.
What should you receive at the end?
- a written summary of scope and priorities
- a technical outline another team could read
- a list of risks and assumptions
- a delivery plan with milestones
- an estimate you can compare with other suppliers
- in some cases, designs or a clickable prototype
These belong to you. If a supplier will not hand them over without committing to the build, treat that as a warning, and read our guide on choosing a software development company.
When is discovery worth it?
It pays off when:
- requirements are unclear or disputed inside the business
- the software has to connect to several existing systems
- you need a business case or budget approval
- the cost of getting it wrong is high
A small, well-understood change may not need it. A short planning conversation can be enough.
How long does it take?
It depends on the size and clarity of the project. Many discoveries run for a few weeks, but a supplier should give you a defined scope, timeline and price for the discovery itself before you start.
What are the warning signs?
- a fixed price for the whole build after one meeting
- no questions about your users or data
- deliverables that exist only inside the supplier's tools
- no one willing to say what should be left out
The honest outcome of discovery is sometimes "do not build this yet", or "a simpler option solves it". That result is worth paying for.
For how cost is assessed once scope is known, see how much custom software costs. To talk about planning a project, see our planning and technical advice page or contact us.