Discovery phase
The discovery phase is the time-boxed first stage of a software project, run before any build work is committed, in which a team settles scope, users, risks and architecture options into a plan: a brief, a backlog, an estimate range, or a decision to stop.
Submit a project Prepare your discovery questionsReviewed by Huy Nguyen (David), CEO · Updated 21 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while scoping a project before a build begins.
Why does the discovery phase matter?
A discovery phase exists because committing a team to build before anyone has tested the underlying assumptions is how software budgets end up spent on guesses. OutsourcingVN is operated by Netbase JSC, and the questions discovery asks — who the real users are, which risks could sink the idea, which architecture options are actually viable — are cheaper to get wrong on paper than inside a codebase already under construction. A discovery phase with no named decision at the end tends to drift into open-ended design work rather than a bounded scoping exercise with a stop button.
What is an example of the discovery phase in practice?
A logistics operator wants a route-planning tool but has not decided whether drivers need a mobile app or whether a dispatcher-only web tool would do. A discovery phase interviews three dispatchers and two drivers, maps the existing paper-based process, and tests two architecture options against a sample of real route data. It ends with a backlog ordered by risk, an estimate range for a first release, and a recommendation to build the dispatcher tool first, because the driver app depends on location data the current process does not yet capture.
What are the common misreadings of the discovery phase?
A discovery phase is not a proof of concept: a proof of concept tests one narrow technical question in isolation, while discovery maps the whole problem — users, risks, architecture options and scope — before any build commitment is made, and may conclude that a proof of concept is the sensible next step rather than a full build. It is also not the build itself: a minimum viable product is the first release that discovery scopes, not a synonym for discovery, and a discovery phase that quietly starts writing production code has become the build without anyone deciding so.
Plan the next step for your project
Common questions
Not usually. Its deliverables are documents — a brief, a backlog, an estimate range — that scope a later build or justify stopping before one starts.
The person who will decide whether to proceed, and at least one person who represents the real users, since a discovery that only talks to internal stakeholders tends to confirm assumptions rather than test them.
Which decisions does the discovery phase affect?
Preparing the specific questions a product discovery should answer about customers, tenancy, roles, integrations and releases is the subject of the SaaS product discovery questions guide, which assumes a discovery phase is already underway and goes deeper into one kind of product. Before discovery starts, the software project brief template covers what to send so the stage has something real to test against. When you have an idea whose scope needs settling before anything bigger is committed, describe it and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.