Discovery — what happens before any design starts

Discovery is the phase where a supplier finds out what a business actually needs before any design work begins. It happens first because every later stage — scope, wireframes, design direction — is an answer to a question, and discovery is where the questions get asked properly.

A discovery phase that is skipped or rushed does not usually produce a bad-looking website. It produces a good-looking website that solves the wrong problem: navigation organised around how the business owner thinks about their own operations rather than how a customer searches for a service, a homepage that leads with the company’s history when the actual audience wants pricing and location, or a design built for one audience when the paying customer is a different one entirely.

What discovery actually establishes

Question discovery answers	Why it has to come first
Who is the site actually for	Design and content decisions downstream all assume an audience
What does the business need the site to do	Drives whether the project is a brochure site, a lead-generation site or an online store
What exists already	Old content, an existing domain, existing brand assets and their state of use
Who are the real competitors	Not a generic industry list — the specific businesses a customer is choosing between
What has failed before	If this is a redesign, what specifically was wrong with the previous site matters more than what looked wrong
Who makes the final decision	The person answering questions in discovery is not always the person who signs off design later

Each of these has a concrete downstream effect. “Who is the site actually for” determines the entire information architecture — see wireframing for how that gets translated into a structure. “What does the business need the site to do” is the difference between a project scoped as five pages and one scoped as an online store with fifty product listings, which is answered properly at scoping and estimating.

Who is responsible for what during the discovery stage

Discovery is a genuinely two-sided stage, more than most that follow it. The supplier leads the conversation and asks the questions; the client supplies the actual knowledge of their own business, because nobody else has it. A supplier who runs discovery as a monologue about their own capabilities, rather than a structured set of questions about the client’s business, has skipped the point of the stage.

Common inputs a client is reasonably asked to bring: existing analytics or enquiry numbers if any exist, any existing brand guidelines or logo files, competitor research covering the actual businesses they lose customers to (not a generic list of “other businesses in the industry”), and access to whatever the current site is built on, if one exists. On a project with more than one stakeholder on the client side — an owner, a manager, a marketing lead — naming who those stakeholders are during discovery, rather than discovering mid-project that someone else also has an opinion that matters, avoids a second round of the same questions later.

What a rushed discovery looks like in practice

The most common shortcut is a supplier who treats discovery as a formality to get through before “the real work” — meaning the visible design work — begins. The signal is a discovery conversation that is entirely about the supplier’s process and portfolio, with no genuine questions asked back about the client’s business, audience or goals. Another common shortcut is running discovery once, generically, across a template that gets reused for every client regardless of industry, which produces sites that look professionally made and perform identically to every competitor’s, because they were built from the same set of unexamined assumptions.

The candid version of this: a thorough discovery phase costs a supplier real time with no billable design output to show for it yet, which is exactly why it is the stage most likely to be compressed under time pressure. A client evaluating a quote is entitled to ask how much time is actually allocated to discovery specifically, separate from design.

What a business owner should expect to be asked

At minimum, a proper discovery conversation covers: the specific action the site needs a visitor to take (call, book, buy, enquire); who the site is competing against for that action, by name; what has to be true of the finished site for the project to be considered a success, stated in terms that can be checked later rather than in vague terms like “look professional”; and what constraints already exist — an existing domain that must be kept, a brand style that cannot change, a platform the business is contractually tied to for another system such as a booking calendar or point-of-sale.

Discovery, user research and the written brief

Discovery conversations are frequently the source material for a written brief, even when no formal document called “the brief” exists. On a larger build, discovery can extend into genuine user research — short conversations or a survey with actual customers, rather than only the business owner’s own assumptions about them — though for most small-business projects the business owner’s direct knowledge of their customers is the primary source and a separate research phase is not proportionate. Some suppliers run discovery as an informal conversation and write the brief up themselves afterwards for the client to confirm; others hand the client a structured questionnaire to complete first, then discuss the answers. Neither approach is wrong, but the output should be the same either way: a written record of what was agreed, that both sides can refer back to when a disagreement arises later about what was originally scoped.

If you want to prepare your own answers to the questions above before a supplier conversation, rather than answering them cold in a meeting, the project brief tool on this site walks through the same structured questions and produces a document you can bring to any supplier — not only this one.

Where discovery sits in the sequence

Discovery precedes scope, and scope precedes a quote. A supplier who quotes a fixed price before a genuine discovery conversation has happened is quoting against assumptions rather than against the actual project — which is a common way a quote later turns out to be wrong once the real scope becomes clear. See scoping and estimating for how the output of discovery becomes the input to a defined, quotable scope.