The Discovery Call That Changes Everything
My worst project happened because I skipped the discovery call.
The client seemed straightforward. A local restaurant wanted a new website. We'd exchanged a few emails. They sent over a Word document with their menu and some phone photos. I quoted based on a "standard restaurant site," which in my head meant about five pages, a menu section, reservation link, and contact information. They accepted the quote the same day.
Three weeks later, I was knee-deep in a project that included two separate menus (lunch and dinner, changing seasonally), a private dining section with its own booking system, a catering arm with a different brand identity that needed to live on a subdomain, an events calendar for monthly supper clubs, an online shop selling branded merchandise, and a blog where the head chef wanted to publish weekly recipes with step-by-step photography.
What I'd quoted as a five-page brochure site was actually a multi-faceted digital ecosystem. I'd underquoted by roughly 70%. The project took three times longer than planned, the client was frustrated by the delays, and I resented every hour I spent on it because I was essentially working for free.
All of this was avoidable. Not with better quoting. With a better conversation before the quoting happened.
What a Discovery Call Actually Is
A discovery call is a structured conversation before any proposal, quote, or commitment. Its purpose is to understand three things: what the client needs (not what they say they want, which is often different), what the project actually involves, and whether you're the right person for it.
Most designers treat the initial client conversation as a sales call. They're trying to impress, to prove their value, to close the deal. This is backwards. The discovery call isn't about selling. It's about listening. You should be talking for approximately 20% of the call and listening for 80%.
The insight you gain from a good discovery call is worth more than any amount of design skill, because it determines whether the project is set up to succeed or doomed to scope creep, misaligned expectations, and mutual frustration.
The Questions That Matter
Over hundreds of projects, I've narrowed my discovery call to a core set of questions that consistently reveal what I need to know.
"Tell me about your business." Open-ended on purpose. How the client describes their own business tells you how they think about it, what they prioritise, and how they communicate. Are they focused on the craft? The customers? The growth? The competition? Their answer shapes every design decision you'll make.
"What's prompted this project right now?" This question reveals the real motivation. Are they embarrassed by their current site? Have they just rebranded? Are they launching a new service? Have they lost a client who said "your website put me off"? The trigger is often more useful than the brief, because it tells you what success looks like. If the trigger is "we're not getting enough enquiries," then the design must be judged by whether enquiries increase, not by whether it looks good.
"Who is your ideal customer, and what do they need from your website?" Clients who can answer this clearly have a business that's ready for a good website. Clients who answer vaguely ("everyone, really" or "anyone who needs our services") need help defining their audience before the design can begin. This might be part of your scope, or it might be a red flag that the client isn't ready for the project yet.
"What does your current website do well? What doesn't it do?" This prevents you from throwing the baby out with the bathwater. Sometimes the existing site has strong SEO, a well-structured blog, or a booking flow that works well. Knowing what to preserve is as important as knowing what to change.
"Do you have all the content ready, or will that need to be created?" The content question is the one that derails more projects than any other. If the client assumes you'll write the copy, create the imagery, and produce the blog content, that's a fundamentally different (and larger) project than if they're providing everything. Get clarity on this before you quote. Be explicit about what's included and what isn't.
"What's your budget range?" Many designers are uncomfortable asking this directly. Get over it. You need to know whether the client's expectations align with reality. If they want a ten-page e-commerce site with custom photography and content creation, and their budget is £500, you need to know that before you spend three hours writing a proposal. A range is fine. "Are you thinking closer to £2,000 or closer to £10,000?" is a low-pressure way to open the conversation.
"What's your timeline?" Urgent projects cost more. Projects without a deadline can drift indefinitely. Knowing the timeline helps you assess feasibility and prioritise.
"Who will be involved in decisions?" If the person you're speaking with isn't the final decision-maker, you need to know that. Projects with multiple stakeholders (business partners, boards, committees) require different management than projects with a single decision-maker. They also take longer and involve more revision rounds, which should be reflected in your quote.
The Red Flags
The discovery call is also where you identify projects to avoid. Some red flags:
"We need it next week." Urgency without flexibility usually means unrealistic expectations, compressed feedback cycles, and a client who'll be frustrated when quality takes time.
"Our last designer was terrible." Once is a data point. But if you probe further and discover they've been through three or four designers, the problem might not be the designers. Ask what went wrong specifically. If the answer is always some version of "they didn't understand our vision," the vision might be the problem.
"Can you just do it and we'll provide feedback?" This means no brief, no content, and no clear expectations. You'll be designing blind, and the feedback will be "that's not what we had in mind" with no specifics about what they did have in mind.
Budget and scope don't match. A client wanting a complex e-commerce site with membership areas on a small budget isn't a bad client. They might just need education about what things cost. But if the gap between expectations and budget is unbridgeable, it's better for both of you to recognise that before the project starts.
"We'll know what we want when we see it." Design is not a guessing game. A client who can't articulate what they want will not be able to evaluate what you produce. The discovery call is your opportunity to help them articulate it. If they can't after a structured conversation, think carefully about whether this project will have a satisfying conclusion.
Turning Discovery into a Proposal
The discovery call gives you everything you need to write a proposal that's specific, accurate, and hard to argue with, because it's built on the client's own words.
Structure the proposal to mirror the conversation. Start with a summary of the client's situation and goals (in their language, so they see you've listened). Then outline your proposed approach. Then detail the scope (what's included and, critically, what's not). Then pricing and timeline.
The scope section is where the discovery call pays for itself. Instead of "website design and build," you can write "five-page website including homepage, about, services, portfolio (with up to 12 case studies), and contact. Blog setup with three categories. Contact form with automated email notification. Mobile optimisation and basic SEO setup. Content provided by client." This level of specificity protects both of you: the client knows exactly what they're getting, and you know exactly what you've committed to deliver.
Any request that falls outside this scope during the project isn't scope creep. It's an additional service, quoted and agreed separately. The discovery call and the proposal it produces are the foundation that makes this boundary enforceable without being adversarial.
The Fifteen-Minute Investment
A good discovery call takes 30 to 45 minutes. A great one takes 15 minutes of preparation on top of that: reviewing the client's current website, checking their social media presence, and noting any obvious opportunities or issues.
This 45-minute investment saves you from the project that should have been scoped differently, the client who should have been referred elsewhere, and the quote that should have been twice as high. It turns "I'll figure it out as I go" into "I know exactly what this project involves," which is the difference between a project that's profitable and enjoyable and one that makes you consider a career change.
Do the discovery call. Every time. Even when the project seems simple. Especially when the project seems simple. Because the simple ones are where the surprises live, and the surprise is always bigger than the call that would have caught it.