Convert Client Calls Into Rewarding Deals: A Web Design Sales Playbook

A few years into running discovery calls, you start noticing a pattern: the deals that fall apart aren't the ones where the client pushed back hard on price. They're the ones where you never really found out what they needed in the first place. You heard "I need a website," you quoted a page count, and somewhere between the call and the follow-up email, the whole thing quietly died.

Here's the thing nobody tells you early on - almost no one calling about a website actually wants a website. They want more customers walking through the door, or fewer people bouncing off a page that looks like it's from 2015, or a way to stop losing three hours a week to manual booking emails. "I need a website" is just the shorthand they've landed on for a problem they haven't fully worked out yet. If you take that sentence at face value and start quoting pages and features, you'll end up in a bidding war with every other agency who did the exact same thing. If you dig one level deeper and find the actual problem, you're suddenly the only person in the conversation who understood the business - and that's worth a very different number.

To be clear, the goal here is not talking people into spending more than they need to. It's the opposite, really: a project priced against a real, named problem tends to be scoped more honestly than one priced against a vague spec sheet, because you're both looking at the same target.

Show Up Having Already Done Some Homework

Nothing kills a discovery call faster than "so, tell me what you're looking for" as your opening line. It's not that the question is wrong - it's that it puts all the work on them, and it signals you haven't looked at anything before dialing in. Prospects shopping for a web designer talk to three or four people in a week. They can tell within the first couple of minutes who actually opened their site beforehand and who didn't.

Before the call, I try to answer two things - the same questions we ask before scoping any website or storefront build for a new client. First: does this project actually matter to the business, or is it cosmetic? A redesign with no real strategy behind it is a "make it look nicer" job, and it should be priced like one. But a site tied to something specific - leads that aren't converting, a catalog that's outgrown the current platform, a booking process eating up admin hours every week - is a business problem wearing a website costume. Those justify real budgets, and your job before the call is just to form a guess about which one you're walking into.

Second: who actually are these people? Ten minutes on their current site, their social pages, and one or two competitors tells you what they sell, who they're selling it to, and how (or whether) they're currently earning trust with customers. You don't need a research report. You need enough to ask a sharper question than "what pages do you need" - something like "I noticed your competitors all show pricing up front and your site doesn't - is that a deliberate call?" That single question usually tells you more about the real gap than a full requirements list would.

Let the Call Find the Problem Instead of Collecting Requirements

There's a version of this call that feels productive but isn't - the one where you go down a checklist. How many pages. What colours. Do you have a logo. That's an intake form wearing a phone call's clothes, and it puts you in the position of an order-taker instead of someone solving a problem.

A better call starts by reading the room. A solo founder juggling five roles at once responds to a very different tone than a marketing manager at a fifty-person company - one wants to feel understood, the other wants evidence and a fast pace. Get this wrong in the first few minutes and you spend the rest of the call clawing back rapport you shouldn't have lost.

From there, resist the urge to start selling. "Tell me a bit about the business first" does more work than "what pages do you need," because people tend to over-explain when you give them room, and the over-explaining is where the useful information hides. A simple "is business going well at the moment?" opens more doors than it looks like it should - the hesitation before the answer often says more than the answer itself. Follow it with "why do you think you're not getting more enquiries" and then "what's that actually costing you" and you've turned a vague complaint into something with a number attached. Ask if they've tried fixing it before, too - not to catch them out, but so you don't propose the exact thing that already failed.

Eventually, get them to say the goal out loud in their own words. "What would a good month look like for you?" or "what would that extra revenue actually let you do?" A client who's said a number out loud - even a rough one - is far easier to price against later than one who's only ever thought about it in the abstract. And ask about timeline honestly: whether they need this sorted in two weeks or two quarters should shape the shape of the proposal, not get bolted on afterward.

The Pushback You Should Expect

Even a call that goes well gets tested. "Can you just give me a rough number now?" comes up constantly, and the temptation is to throw something out just to keep the conversation moving. Don't - whatever number you say first becomes the number they anchor to, whether or not it fits the actual scope. A range tied to a condition works better: "projects like this usually land somewhere between $X and $Y depending on scope - once we've talked through what you actually need, I can get specific."

"Why is this so much more than [other agency]'s quote?" almost never means you're overpriced. It usually means the other quote was for a much narrower job, and the client has no way of seeing that unless you show them. Walk back through what you actually discussed on the call and what problem it solves - suddenly it's not two numbers being compared, it's two different projects.

And if someone goes quiet after a call that felt genuinely good, that silence is information. Maybe the budget wasn't really there. Maybe there's a business partner who needs to sign off and hasn't been looped in. Maybe the problem turned out to be less urgent once they thought about it. A direct, low-pressure "just checking in - was it the budget, the timing, or something else?" usually gets further than three follow-up emails that all say "just circling back."

Pricing the Thing You Actually Found

If the call went well, you should be able to hand the problem back to them more clearly than they described it to you - "so if I'm hearing you right, it's not really about the design, it's that people can't find your booking page." That moment of "yes, exactly" is usually where the relationship shifts from "one of several quotes" to "the person who gets it," and it's the best place in the whole conversation to price from.

A couple of things make that pricing conversation land better. Ask about budget only after the cost of the problem is already on the table - the same question asked cold at the top of the call sounds transactional, but asked after they've just told you what the problem is costing them, it sounds like the natural next step. And don't force everything into one take-it-or-leave-it package. If budget's tight, or they're still not fully sold, breaking it down - "the core build is $7,000, SEO is another $1,000, content is $1,000" - lets someone say yes to something real today instead of no to a number they can't picture.

Be honest about timelines too, and don't let two different clocks blur into one. There's the build timeline, and there's the results timeline - SEO and content compound slowly, and promising "you'll see results by launch day" alongside "the site goes live in six weeks" sets up a disappointment you didn't need to create. Then send the proposal the same day, while the specifics are still fresh. A proposal that goes out two weeks later, pulled from a generic template, loses most of the specificity you worked to build on the call. The good ones read almost like a transcript - the client's own words about their problem, handed back with your solution attached.

Your growth partner

Great work starts with a clear plan.

Websites, storefronts, mobile apps and custom internal software - designed, built and maintained by one accountable team, whatever platform the work runs on.

One accountable team, from scope to reporting.

Support for this article

Software & Product Development

See service details

• React & Next.js Development ServicesServer-rendered, App Router-based Next.js builds - fast first paint, real SEO, and a codebase a future developer can actually pick up.
• WordPress DevelopmentWordPress builds run on a clean core setup and a maintained plugin stack - not a pile of plugins nobody remembers installing.
• WooCommerce DevelopmentWooCommerce stores built around how the catalog and checkout actually need to work, rather than simply how the plugin defaults handle it.

From first conversation to delivery

01Audit02Plan03Execute04Report

Start with the real bottleneck.

We review your listings, storefront, campaigns or workflows to identify what needs attention. Bring examples of the work you want to improve.

Discuss your project

To get started, share your platform, current workload and target timeline.

None of This Is a Script

If it reads like a checklist, that's a failure of the framework, not a feature of it. In practice a good call has a shape more than a sequence: get them talking, ask why a couple of times, let them name the cost of the problem, let them say the goal out loud, then close with a proposal that's tiered instead of one flat number. The single most common way a good project turns into a race-to-the-bottom quote comparison is skipping straight from "hello" to "here's our pricing page" - everything above is really just about not doing that.

Do this well and the proposal isn't selling anything new. It's just writing down, clearly, the plan the two of you already built together on the call.

Actually Check Whether It's Working

Most people who try something like this never go back and check if it's helping. Two numbers are worth watching: how many discovery calls turn into signed proposals, and how the average deal size compares to what you'd have quoted on the spot with no discovery at all. In my experience the second number moves first - the deals that do close get bigger and better scoped almost immediately, even while your close rate is still catching up, because early on you're also figuring out which calls are worth a full discovery conversation and which ones deserve a quick, honest "I don't think we're the right fit."

It's also worth going back through the calls that didn't convert and looking for the exact moment the conversation slipped back into order-taking - where you answered "what pages do you need" instead of asking why they needed them. That slip is the most common failure even once you know the framework cold, because answering the spec question is just easier than steering back toward the real one, especially with a client who's used to being asked spec questions by every other agency they've talked to this month.

If you'd rather have someone else run this whole conversation - and the build that follows it - for you, talk to us about it.