Discovery phase

Discovery is not a sales meeting and it is not design. Its output is a shared understanding written down: who the product is for, what it must do first, what already exists, what could go wrong and roughly what it will cost. That written understanding usually becomes the project brief and the basis for the scope of work.

People often skip it because it feels like paying for talk. The point is the opposite: a few days of questions are far cheaper than rebuilding a page, a booking flow or a database after launch because nobody asked the right question at the start.

How it works

A typical discovery runs from a few days to a few weeks. It starts with interviews with the owner and the staff who will use the system, then reviews the current website, analytics, competitors and any tools the business already pays for. Where possible, the team talks to a handful of real customers or watches them use the current site.

The findings are turned into concrete artefacts: a list of goals and success measures, user personas, a rough site structure, a prioritised feature list, technical risks and an estimate. The client signs off on these before design or development begins.

The quality of discovery depends on the questions. Useful ones are specific: where do enquiries come from today, what happens to an enquiry after it arrives, which tasks staff repeat every day, what the current site cannot do, and what would make the project a failure in a year. Vague questions such as "what style do you like?" belong later, in design.

Example

A dental clinic asks for a new website with online booking. During discovery the team learns that the clinic's practice software already has a booking module, that most new patients call rather than book online, and that the receptionist spends an hour a day answering the same three questions. The project changes shape: connect the existing booking module instead of building one, add a clear FAQ and a click-to-call button, and spend the saved budget on local search.

The written summary for that clinic runs to four pages: goals (more first-time patients for implants and orthodontics), audiences (new local patients, existing patients checking hours), constraints (the booking module only works on certain plans of the practice software), a page list and an estimate with a range rather than a single number. The clinic uses it to compare two suppliers on the same basis.

Why it matters for your business

Discovery protects the budget. Many cost overruns come from requirements that were unclear or missing rather than from slow work, and they are cheapest to fix on paper. It also gives you something you own: even if you choose a different supplier afterwards, the research and the brief remain useful. For a very small, well-understood job, such as a five-page brochure site for a business that already knows exactly what it needs, a short call may be enough and a formal discovery would be overkill. You can check whether a supplier's discovery was real by reading the summary: if it could describe any business in your sector, the research was too shallow.

Common mistakes

• Treating discovery as optional and jumping straight to designs, then discovering missing requirements halfway through the build.
• Inviting only the owner, so the people who will use the system every day are never asked how they work.
• Ending discovery without a written summary that both sides sign off, which makes the findings easy to forget or dispute.
• Asking for a fixed price before discovery, which forces the supplier to guess and pad the quote for risk.

Questions people ask

How long does a discovery phase take?

For a small business website, discovery usually takes a few days to two weeks. Larger products with integrations, several user types or regulatory requirements can take longer. The length depends on how many people need to be interviewed and how much of the existing setup needs to be reviewed.

Do I have to pay for discovery separately?

Many studios charge for discovery as a separate, smaller engagement because it produces useful work on its own: research, a brief and an estimate. Some include it in the project price. Paying separately lets you take the findings to another supplier if you prefer.

Is a discovery phase the same as a project brief?

No. Discovery is the research process, and the project brief is one of its outputs. You can write a brief without formal discovery, but a brief written after proper discovery is usually far more accurate about goals, users and constraints.