Most agency "discovery calls" are sales calls. Someone asks what you're looking for, you describe your project, they tell you it sounds great, and they send a proposal 48 hours later.
That's not discovery. That's qualification.
Discovery is the process of understanding what you're actually building, why it matters, who it's for, and what success looks like — before anyone opens a design tool. Done properly, it prevents the two most expensive mistakes in web development: building the wrong thing well, and building the right thing badly.
Discovery is not:
Discovery is structured information gathering. The output is a shared understanding of the project — constraints, users, success criteria, and technical requirements — that makes everything that follows faster and cheaper.
A genuine discovery session covers six areas:
What's the company doing, who's the customer, and why does this website exist? Not "we're a SaaS company and we need a website" — that's the premise. We want: what has to be true for this site to have succeeded in 12 months?
If the answer is "we need 200 demo signups per month" — that shapes every design decision. The call to action, the social proof placement, the form length, the analytics setup. Everything flows from this.
Who specifically lands on this site and in what context? A B2B product bought by a Head of Engineering is designed differently than a consumer app bought by an individual. The vocabulary is different, the trust signals are different, the decision-making timeline is different.
We want to know: who are the three archetypes of visitor? What do they need to believe before they convert? What objections do they arrive with?
Timeline, budget, and internal resources are not embarrassing topics. They're engineering constraints. Knowing you have six weeks and €8,000 produces a better outcome than discovering it in week five.
Constraints we ask about:
What do you already have? What's staying, what's going, what's transferring?
A site that needs to integrate with an existing auth system is a different scope than one that doesn't. We need to know before quoting.
Visual direction is one of the most common sources of late-project conflict. If a client imagines a minimal, editorial look and the agency delivers a saturated, animated dashboard — neither party is wrong. They just never aligned.
We ask for:
This takes ten minutes and prevents two weeks of back-and-forth in round-three design reviews.
What does the project hand-off look like? What do you need from us post-launch?
Discovery is unflattering for agencies that aren't good at scoping. It surfaces ambiguity. It forces the agency to admit what they don't know. It sometimes reveals that a project is larger than the client thought — which can kill the deal.
Skipping discovery protects a mediocre proposal. It lets an agency send a confident-looking quote that glosses over the hard questions. The client feels good. The problems emerge in week three.
There's also a commercial pressure: a paid discovery phase feels like a barrier. Some clients will talk to another agency that skips to a free proposal. In the short term, discovery loses deals. Long-term, it filters for clients who understand that good work requires genuine alignment upfront.
Our discovery is a 45-minute call followed by a written scope document.
The call covers all six areas above. We share a brief questionnaire (15 questions, 30 minutes) the day before so we're not spending call time on basic information gathering.
After the call, we write a 2–4 page scope document that specifies:
The scope document is the contract. If something isn't in it, it's not in scope. This protects you from bill shock and protects us from building things we didn't price.
If you're about to have a discovery call with any agency, come prepared:
A founder who comes prepared gets a better, faster, more accurate proposal. The discovery call rewards preparation.
Want to see what discovery looks like in practice? Book a call with us — we'll run through our format and tell you what we'd need to scope your project accurately.
We take on a small number of projects each quarter. Tell us what you're building.