Shorter, sharper discovery calls for web designers and studios
Filter out poor-fit enquiries before they reach your diary, audit the prospect's current site in fifteen minutes, run a call with a fixed shape and leave with the proposal conversation already booked.
For most freelance web designers and small studios, discovery calls are where new work starts and where a surprising amount of unbilled time goes. A typical week might include a call with someone who wanted a full e-commerce build for the price of a template, a call that ran to 75 minutes because the prospect wanted free advice on their logo, and a promising call that never turned into a proposal because nobody agreed what happened next.
This guide is about the process around those calls rather than a template for them: how to decide who gets a call, what to look at before you speak, how to structure 30 minutes so you finish with what you need, how to use screen-share well, and how to move cleanly to a proposal. For the general mechanics of booking calls, see our discovery call scheduling guide; this page applies them to the way web projects are actually sold.
A discovery process built for web projects
Web design discovery has quirks other services do not. The prospect almost always has an existing site you can look at. Scope can swing wildly once you discover a booking system, a members' area or 400 old blog posts. And clients often cannot say what they want until they see examples. A good process uses these quirks rather than fighting them.
Qualify before the call, not on it
Decide which enquiries deserve a full discovery call and which need something lighter. Many designers use two levels:
- A 15-minute fit check for enquiries where budget, timing or project type is unclear. The goal is a yes or no, not a solution.
- A 30 to 45-minute discovery call for prospects who meet your basic criteria: a budget range you can work within, a realistic deadline and a project type you actually do.
Set these up as two separate event types with different lengths and different booking questions. Publish a starting price or a typical range on your site. It feels risky, but it quietly removes many of the enquiries that would never have gone ahead. Some studios also leave the full discovery link off their website and only send it after a fit check or a reply to the enquiry form.
Audit the prospect's site beforehand
Fifteen minutes before the call is enough for a useful look. A simple routine:
- Platform: which CMS or builder the site uses, which shapes migration effort.
- Size: roughly how many pages and posts, from the sitemap or navigation.
- Mobile: open it on your phone and try the main task, such as booking, buying or enquiring.
- Speed: run the homepage through a free tool such as Google's PageSpeed Insights and note the headline issues.
- Accessibility basics: colour contrast, image alt text, heading order and whether forms have labels.
- Integrations: booking widgets, shop, newsletter sign-up, payment, members' area. Each one is scope.
Write three observations you can share, one positive. You are not doing free work; you are arriving informed, which shows competence and saves ten minutes of basic questions.
A tight call structure
For a 30-minute call:
- Minutes 0 to 3: agree the agenda and confirm the time available.
- Minutes 3 to 12: their goals, in business terms: more enquiries, fewer support emails, a rebrand, a new product line.
- Minutes 12 to 20: walk through the current site together and share your observations.
- Minutes 20 to 26: scope, content, deadline and budget range, plus who signs off.
- Minutes 26 to 30: next step, booked before you hang up.
Screen-share well
- Close everything except the browser tabs you need, and switch off notifications.
- Share their site first, not your portfolio. Clients engage more with their own pages.
- Zoom the browser so text is readable on a laptop at the other end.
- Show two or three relevant examples from your work, chosen in advance, rather than scrolling your whole portfolio.
- Do not redesign live. Sketching layouts on a call creates expectations you have not priced.
Move to the proposal
The cleanest move is to book a proposal walk-through at the end of the discovery call, usually three to five working days later. Send a short recap the same day that lists their goals, the scope as you understood it, open questions and the walk-through date. The proposal then arrives into a conversation already in the diary rather than an inbox where it may sit unread.
Why discovery time decides a studio's margins
Discovery calls are unbilled. Every hour spent on a call that was never going to convert is an hour not spent on paid design or development. For a solo designer, a few poor-fit calls a week can quietly cost a day a month. For a small studio, the cost multiplies when two people join each call.
The answer is not to stop taking calls. Web projects are hard to scope without a conversation, and clients want to know who they will work with. The answer is to make each call earn its place: the right people on it, the right preparation beforehand and a clear outcome at the end. A short fit check costs fifteen minutes; a full discovery call with a poor fit can cost an hour plus the preparation and the polite follow-up.
Preparation also changes how prospects see you. A designer who opens with 'I had a look at your site on my phone and the enquiry form is hard to reach' is having a different conversation from one who opens with 'So, tell me about your business'. The first sounds like an expert; the second sounds like a salesperson.
Finally, structure protects the relationship. Calls that wander into free consulting leave both sides unsure what was agreed. A fixed shape with a booked next step keeps momentum and makes the proposal feel like the natural continuation. Agencies running several new-business calls a week will find more on dividing the work in our scheduling guide for agencies.
What a streamlined discovery process gives you
Fewer wasted calls: published price ranges and a short fit check filter out most poor fits early.
Better first impressions: a quick site audit means you open with specific, useful observations.
Predictable call length: a fixed 30-minute structure stops calls drifting into free consulting.
Clearer scope: walking through the current site surfaces integrations and content volume before you price.
Faster proposals: a booked walk-through gives you a deadline and the client a reason to read it.
More design time: hours saved on discovery go back into billable project work.
Rebuilding your discovery process in six steps
Look at your last ten discovery calls — Note how each enquiry arrived, how long the call took, whether a proposal followed and whether you won it. Mark the calls you would not take again and why.
Write your fit criteria — Set a minimum budget range, the project types you take on and the lead time you need. Publish a starting price or typical range on your site.
Create two event types — A 15-minute fit check with two or three questions, and a 30 to 45-minute discovery call with a few more. Add buffers after the longer one for notes.
Write your pre-call audit routine — Platform, size, mobile, speed, accessibility basics and integrations, plus three observations to share. Block 15 minutes before each call to do it.
Fix the call agenda and screen-share kit — Put the five-part agenda in your confirmation email and keep a folder of examples sorted by project type, ready to share.
Book the next step on every call — Create a proposal walk-through event type and book it before the call ends. Send the recap the same day.
Matching the call to the enquiry
| Feature | Best handled by | Length | Prep needed | Likely next step |
|---|---|---|---|---|
| Unclear budget or project type | Fit check call | 15 minutes | Glance at their site | Discovery call or polite decline |
| Small brochure site, clear brief | Discovery call | 30 minutes | Quick audit | Fixed-price proposal |
| Redesign with integrations | Discovery call | 45 minutes | Full audit, list integrations | Scoped proposal or paid discovery |
| E-commerce or members' area | Discovery call, possibly paid workshop | 45 minutes or more | Audit plus platform research | Paid scoping workshop |
| Referral from a past client | Discovery call | 30 minutes | Quick audit, ask the referrer for context | Proposal walk-through |
| Price-only enquiry | Email reply with published range | No call | None | Discovery call only if the range suits |
Habits of designers with efficient discovery calls
Publish a starting price or typical range; it saves more time than any call script.
Send the agenda in the booking confirmation so the prospect arrives ready.
Open the call with one specific observation from your audit.
Ask who else signs off on the website, and invite them to the proposal walk-through.
Keep discovery calls to set days so they do not break up design time.
Offer a paid scoping workshop for complex builds instead of stretching a free call.
Keep a short list of other designers or platforms to refer poor-fit enquiries to.
Where discovery calls leak time
Offering a full-length call to every enquiry, whatever the budget or project type.
Going into calls without having looked at the prospect's current site.
Sharing your whole portfolio instead of two or three relevant examples.
Sketching or redesigning live on screen-share, which creates unpriced expectations.
Ending the call with 'I'll send something over' and no date for the next conversation.
Letting calls run over because nobody agreed the time available at the start.
Example: a solo web designer in Nottingham reclaims her week
Take a fictional freelance web designer in Nottingham who builds sites for independent shops, trades and professional services. She was taking around eight discovery calls a week, each booked as an open-ended 'chat', and winning roughly one project a week. The calls were eating her Tuesdays and Wednesdays.
What she changed
- Published ranges: her services page now says brochure sites start from £1,800 and shop builds from £4,500.
- Two event types: a 15-minute fit check asking for the current website address, the main goal and a budget range, and a 30-minute discovery call she only sends after a fit check or a clear enquiry. Both use Zoom links created automatically, following our guide to syncing Zoom with a booking page.
- Set days: calls only on Tuesday and Thursday afternoons, with mornings kept for design. She followed the advice on avoiding meetings outside business hours to stop evening calls creeping in.
- Audit routine: 15 minutes before each discovery call, with three observations written into her notes.
- Proposal walk-through: a 30-minute event type booked before every discovery call ends.
Illustrative time maths
Before: 8 calls a week at about 60 minutes each, plus 10 minutes of follow-up, is around 9 hours 20 minutes a week. After, suppose 6 enquiries go to a 15-minute fit check (1 hour 30 minutes) and 4 go on to a 30-minute discovery call with 15 minutes of audit and 10 minutes of recap each (3 hours 40 minutes). That is about 5 hours 10 minutes a week, saving roughly 4 hours, in this illustrative case. If she wins the same one project a week, those 4 hours go back into paid work.
One call, start to finish
A Nottingham bakery owner books a discovery call for Thursday 22 October at 14:00. Her audit shows the site is on an older builder, has 14 pages, loads slowly on mobile and has no clear way to order celebration cakes. On the call she opens with the cake-ordering point, which turns out to be the owner's main frustration. By minute 26 they have agreed a scope range, and the owner books a proposal walk-through for Wednesday 28 October. The recap goes out that evening. Her process for keeping calls consistent draws on our guide to scheduling discovery calls automatically and the structure in the discovery call booking page template.
FAQ
Frequently asked questions
Fewer, better calls
Set up a fit check and a discovery call in minutes
Start free with one event type and email reminders. Upgrade for unlimited event types, so your fit check, discovery call and proposal walk-through each get their own length and questions.