What is a discovery phase?

Discovery is the up-front phase, sometimes a single meeting, sometimes a short paid workshop, where you and the client establish what's actually needed, before you write a detailed scope of work or price it.

What it means in practice

Discovery exists because pricing a job accurately before you understand it is guesswork. A good discovery phase surfaces the client's real requirements, existing systems and constraints, and any technical risks worth flagging early, so the quote that follows is closer to what the job actually costs rather than a number pulled from a similar-looking past project. It can be a free scoping call for smaller jobs, or a paid, time-boxed phase for larger ones, often priced as a percentage of the eventual project value, or as its own fixed fee.

What comes out of discovery, the platform, the rough shape of the work, the risks worth a contingency line, is what determines the structure the rest of the quote is built on.

Example

Before quoting a Shopify migration, a studio runs a half-day paid discovery workshop to review the client's existing catalogue and integrations. The findings shape which platform and sections the quote is built from, rather than guessing at the scope up front.