The Discovery Phase: Why the First Two Weeks Decide a Software Project

A discovery phase is a short, fixed-fee period, usually one to three weeks, at the start of a software project in which the development team studies how your business works, agrees the scope with you, designs the key screens and produces a firm estimate. It is the cheapest part of the project and the part that most determines whether the rest arrives on time and on budget.

Projects that skip discovery tend to discover their requirements during development, when every change is expensive.

What happens during discovery

Week one: understand

• Interviews with the people who will use the system and the people who manage them.
• Process walk-throughs: following a real order, request or case from start to finish, including exceptions.
• Review of current tools: spreadsheets, forms, existing software and reports.
• Systems audit: what the new software must connect to, and whether those systems have APIs.

Week two: define

• Workflows documented step by step, with business rules and approval limits.
• User roles and permissions.
• Screen designs for the main tasks, reviewed with users.
• Data model: the records the system will hold and how they relate.
• Integration plan.
• Risks and open questions.

Week three (larger projects): plan

• Phasing: what goes in the first release and what comes later.
• Estimates and a fixed price for the first phase.
• Timeline and milestones with acceptance criteria.

What you should receive

| Deliverable | Why it matters | | --- | --- | | Written specification | A shared understanding of what will be built | | Screen designs | Users can react before any code exists | | Integration and data plan | Removes the biggest technical unknowns | | Phase plan | Value arrives early; later phases benefit from feedback | | Fixed price and timeline | Budget certainty for the first phase | | Risk list | Surprises are named in advance |

You should own these deliverables outright. If you choose a different partner for development, the discovery output should still be usable.

Why discovery saves money

• Changes cost least on paper. Moving a field on a design takes minutes; moving it in built software takes days.
• Contingency shrinks. Vendors quoting without discovery add a margin for the unknown. Discovery removes much of the unknown.
• Scope stays focused. Seeing all the ideas together makes it easier to decide what the first release really needs.
• Users are involved early, which improves adoption later.

Signs of a good discovery

• The team asks about exceptions and edge cases, not just the happy path.
• They talk to the people who do the work, not only managers.
• They challenge steps that add no value.
• The output is specific enough that another team could build from it.

Signs of a weak one

• A few meetings and a slide deck.
• No screen designs.
• Integrations described as "via API" with no detail.
• A price that is still a wide range at the end.

How to prepare

• Nominate one decision-maker and make them available.
• Gather examples: spreadsheets, forms, reports, a few real orders or cases.
• Tell users why they are being interviewed and encourage honest answers.
• List what frustrates people most about the current way of working.

Frequently asked questions

How much does discovery cost?

Typically a small share of the expected project cost, charged as a fixed fee. It is usually recovered through a lower, firmer development price.

Can we skip discovery for a small project?

For very small, well-defined tasks, a short scoping call may be enough. For anything your business will depend on, discovery is worth it.

What if we already have a specification?

Discovery then becomes a review: checking the document against how work really happens, filling gaps and designing screens.

Are we committed to building after discovery?

No. A good discovery leaves you free to proceed, pause or take the output to another partner.

Start with discovery

Turbo Bytes Consulting begins every custom software project with a structured discovery phase and a fixed price for the first release. Read what a requirements document should contain and fixed price vs time and materials.

Book a 30-minute scoping call to plan a discovery for your project.