The best discovery call questions for a freelance web designer cover seven things: the business goal behind the website, the audience, the current site, the content, the decision-makers, the budget and timeline, and how feedback and sign-off will work. Ask these before you send a quote, and you will spot scope creep, slow approvers and missing content while they are still cheap to fix. Skip them, and you will find the same problems in week four, unpaid.
Why most discovery calls fail before they start
Here is a call most of us have had. A potential client says "I need a new website, can you give me a quote?" You ask two or three polite questions. What pages? Do you have a logo? When do you need it? They answer, you say "great, I'll send a proposal," and the call ends after 20 minutes. You feel productive.
Then the project starts, and the real discovery happens in the worst possible format: scattered across email threads, WhatsApp voice notes and screenshots with red circles drawn on them. The "five-page site" turns out to include a shop. The "I'll send the texts next week" turns into content that arrives in month three. The person who approved the proposal is not the person who has opinions about the header, and that second person appears on day 18 with a very different idea of what "modern" means.
None of this is the client's fault. They hired you because they do not know what a good web project needs. A discovery call is where you take the lead, and most freelancers waste it by treating it as a sales call with a few questions attached.
The cost shows up later. Vague discovery leads to vague quotes. Vague quotes lead to disputes about what was included. Disputes lead to unpaid revisions, and unpaid revisions lead to that Sunday evening where you are redoing the homepage for the third time because "it just doesn't feel right." If you have read our guide on scope creep in web design, you know how this ends. The fix starts before the contract.
A good discovery call does three jobs at once. It tells you whether this project is worth taking. It gives you the information to price and scope it properly. And it shows the client that you are organised, which makes them far more likely to follow your process later.
The 10-step discovery call, in order
You do not need a 90-minute interrogation. A solid discovery call takes 30 to 45 minutes. This is the order that works, with the questions to ask at each step.
- Open by setting the frame. Say how long the call takes, what you will cover, and what happens afterwards ("I'll send a written summary and a proposal within two working days"). This takes 60 seconds and removes most of the awkwardness.
- Ask about the business, not the website. "What does the business do, and who pays you?" "What is the one thing you would like this website to make happen in the next 12 months?" If the answer is "look more professional," keep digging. Professional compared to what, and for whom?
- Ask about the audience. "Who is the ideal visitor? What do they want when they land here? What makes them hesitate?" You are looking for specifics, not "everyone."
- Ask about the current site and its problems. "What is not working today? What would you keep?" Ask for analytics access, if there is any, and ask what they have already tried.
- Ask about content. "Who writes the copy? Who provides the photos? When?" This is the question that predicts delays better than any other.
- Ask about references and taste. "Show me two or three sites you like and tell me what you like about each. Now show me one you hate."
- Ask about who decides. "Besides you, who needs to see this before it goes live? Who has the final say?" Write the names down.
- Ask about budget and timeline. Say the range out loud, even if it feels uncomfortable. "Projects like this usually land between X and Y. Does that fit what you had in mind?"
- Explain how feedback works. One link, one round at a time, comments on the page. No email threads. Tell them now, while they are still agreeing with everything.
- Close with next steps. Confirm what you heard, state what you will send and when, and ask for a decision date.
Print this list or keep it in a note. You do not have to read it like a script, but the order matters: business first, taste next, logistics last. If you open with budget, the call feels like a negotiation. If you open with a goal, it feels like a conversation.
The questions that actually change your quote
Some questions are nice to have. Others change what you charge, what you promise or whether you take the job at all. These are worth a closer look.
Content: who writes it, and when?
Content is the number one reason web projects slip. Clients routinely underestimate how long it takes to write about themselves, and they usually do not realise the design cannot be finished without real text. Ask directly: "Will you deliver all copy and images before design starts, or do you need help with those?" Then put the answer in writing, including a date. If they say "I'll write it as we go," quote content support as a separate line item or build a content deadline into the contract. We cover this in detail in how to get website content from clients.
Decision-makers: who else will have an opinion?
"Is there anyone else who needs to approve this?" is the cheapest insurance in web design. The classic disaster is the business partner, spouse or marketing manager who shows up at the review stage. Ask early, name the people, and ideally get them on the kickoff call. If three people will give feedback, tell them now that you will collect it in one place and one round. This connects directly to how to get clear feedback from clients.
Budget: say a number first
Many freelancers avoid talking about money on the first call because it feels pushy. The opposite is true. A client with a 1,500 euro budget and a client with a 15,000 euro budget want completely different things, and you are wasting both of your time if you find out at proposal stage. Try: "To make sure I propose something realistic, projects like this usually cost between 3,000 and 6,000 euros. Is that in the right area?" Silence, a laugh or a nod all tell you something. If pricing is where you struggle, see how to price web design projects.
Success: how will we know this worked?
"What would make you say this project was a success six months from now?" is a fantastic closing question. It surfaces the real goal (more enquiries, fewer support emails, a better first impression at trade shows) and gives you a standard to design against. It also protects you. If success was defined as "more booking requests" and you delivered a site built to convert, the conversation about whether you did a good job gets a lot easier.
Technical constraints: what are we building on?
Ask which CMS they use or prefer, who handles hosting and the domain, and whether there are integrations such as a booking tool, newsletter service or payment provider. A "simple brochure site" that needs a custom booking system is not a simple brochure site. Also ask who will maintain the site after launch. That is a natural opening for a website maintenance package.
Red flags to listen for on the call
A discovery call is also your chance to decline. These signals do not always mean "walk away," but each one should change how you price, structure or protect the project.
- "We'll know it when we see it." Fine, but it means more revision rounds. Price for that and limit the rounds in writing.
- "My nephew does websites too, so I'll check with him." Someone else will have opinions about your work. Ask what role the nephew plays.
- No one can name the decision-maker. The project will stall at approval.
- Budget is "whatever it takes, but also I found a quote for 500 euros." The client is anchored on a price that does not match the scope.
- The previous freelancer "disappeared." Sometimes true. Often there is a story. Ask what happened, and pay attention to how they describe it.
- Pressure to start before the contract. Never start without a signed agreement and a deposit. Our contract template guide covers what to include.
If you see three or more of these, it may be time for a polite no, or a higher price. In the worst case, read how to fire a web design client before you need it.
Turn the call into a written brief within 24 hours
The call itself creates no value until you write it down. Within a day, send a short summary: goals, audience, deliverables, content responsibilities, decision-makers, budget range, timeline and next steps. Ask the client to reply with "confirmed" or corrections.
This one email does a lot of work. It catches misunderstandings while they cost nothing. It gives you a document to point to when something drifts. And it becomes the backbone of your proposal and your design brief.
Keep it to one page. If you write four pages, nobody reads it, and a document nobody reads does not protect anyone.
A good summary email has five parts: what you understood about the goal, what is in scope, what is explicitly out of scope, what you need from the client (and by when), and what happens next. The "out of scope" part is the one freelancers skip, and it is the one that saves the most arguments later. Write "Not included: copywriting, photography, shop functionality, multilingual versions" and let the client react. If they say "wait, I thought the shop was included," you have just saved yourself a month of unpaid work.
Plant the feedback process on the first call
Most freelancers explain how feedback will work at kickoff, if at all. The better moment is the discovery call, because that is when the client is most open to being guided.
Say something like: "Once the design is ready, I will send you one link. You click on anything you want to change and leave a comment right there. No account, no email threads. I collect all feedback in one round, then revise." You have just set the expectation that feedback is structured, that it happens in one place, and that you run the process.
With dotts, this is literally how it works: the client opens a shared link, clicks anywhere on the website, PDF or image, and leaves a pinned comment. No login, no screenshots, and browser and device details are captured automatically. But the principle works with any tool. What matters is that the client hears the rules before the first review, not after the first chaotic round. For the full process, see our guide on the web design revision process.
A real-world example: Mira's before and after
Mira is a freelance web designer in Hamburg. She used to run discovery calls by feel. She asked about pages and colours, sent a quote, and started work.
Before. A physiotherapy practice asked for "a simple five-page site." Mira quoted 2,800 euros. In week two she learned that the practice had two owners who disagreed about the branding. In week three, the copy still had not arrived. The owners sent feedback separately, one by email and one by WhatsApp, and the two sets contradicted each other. The project took 11 weeks instead of 5, and Mira worked out later that she had earned roughly 18 euros an hour.
After. Mira built a one-page discovery checklist based on the ten steps above. For her next project, a similar practice, she asked three new questions on the call: "Who else needs to approve?", "Who writes the copy, and by when?" and "What does success look like in six months?" The answers: two partners, copy not started, and "more online bookings."
She quoted 3,400 euros including a copywriting option and a firm content deadline. She named both partners in the written summary and told them feedback would come through a single review link with comments on the page. Both partners left their comments in the same place, saw each other's notes and resolved the disagreement themselves before Mira touched a pixel. The project took six weeks, with one revision round, and she earned more than double her hourly rate from the first project.
Nothing about her design skills changed. She only changed the questions she asked before saying yes.
How to prepare for the call
The call itself is only half the work. Ten minutes of preparation changes what you get out of it.
First, research the business. Open their current site, look at their social profiles, and check two or three competitors. You do not need to be an expert, but you should be able to say "I noticed your current site doesn't mention pricing, is that on purpose?" That one sentence shows you took them seriously and gives you something specific to talk about.
Second, send a short intake form before the call. Three to five questions is enough: business goal, current site URL, reference sites they like, rough budget, and desired launch date. Clients who fill this out arrive prepared, and the call becomes a conversation about their answers instead of a list of basics. Clients who ignore the form tell you something too.
Third, decide in advance what a good project looks like for you. What is your minimum budget? What types of clients do you want more of? If you do not know your own criteria, every call becomes a negotiation with yourself.
Bottom line
A good discovery call is the cheapest scope protection you have. Ask about goals, content, decision-makers, budget and feedback before you write a quote, send a written summary within 24 hours, and tell the client how feedback will work while they are still listening. Thirty minutes of better questions saves you weeks of unpaid revisions.
FAQ
How long should a web design discovery call be?
Aim for 30 to 45 minutes. Shorter than 20 minutes usually means you skipped the questions about content, decision-makers and budget. Longer than an hour tends to mean you are doing paid strategy work for free. If the project is large, book a second, paid discovery session instead of stretching the first call.
What are the most important web design discovery call questions?
Five matter most: what business goal should the site support, who else needs to approve the work, who provides the content and by when, what is the realistic budget range, and what would make this project a success in six months. These five questions predict scope, timeline and conflict better than anything about colours or layout.
Should I charge for a discovery call?
A short first call (20 to 30 minutes) is normally free because it is part of selling. A longer, deeper strategy workshop should be paid, and it often becomes the first line of your project fee. Charging for deep discovery also filters out clients who are not serious. If you charge, credit the fee against the project if they sign.
Should I ask about budget on the first call?
Yes. Ask early, and name a range yourself instead of asking "What's your budget?" Saying "projects like this usually fall between 3,000 and 6,000 euros" lets the client react without feeling cornered. If their budget is far below your range, you save both of you time, and you can offer a smaller scope or a polite no.
What should I send after a discovery call?
Send a written summary within 24 hours covering goals, scope, what is not included, content responsibilities, decision-makers, timeline and next steps. Ask the client to confirm or correct it. This summary becomes the base of your proposal and your design brief, and it is your reference point when something shifts later.
How do I handle a client who cannot answer the discovery questions?
Many clients do not know what they want, and that is normal. Offer them structure: show two or three example sites and ask what they like, or use a simple questionnaire to collect answers over a few days. If they still cannot define goals, quote a paid strategy phase before the design project. Vague goals without a paid discovery phase almost always lead to endless revisions.
How do I explain my feedback process during a web design discovery call?
Keep it short and concrete: "You will get one link, click on what you want changed, and leave a comment right on the page. I collect everything in one round, then revise." Setting this expectation early prevents feedback from arriving by email, WhatsApp and phone call at the same time. A tool like dotts makes it easy because clients need no account.
What if the client brings someone new into the project after discovery?
Add a clause to your contract that all feedback comes from named decision-makers and arrives in one consolidated round. If someone new joins, treat it as a change request and adjust timeline or budget if needed. Naming decision-makers on the discovery call makes this conversation much easier, because you can point to what was agreed.
Better discovery starts with better feedback. Collect client comments on websites, PDFs and images with no login. [Try dotts free →](https://dotts.se)
