When a Web Design Client Says It's Too Expensive
I have heard "that's more than I was expecting" more times than I can count. Early on, it gutted me. I would either cave and slash the price on the spot, or I would get defensive and start listing every feature like a guy reading off a cereal box. Both reactions lost the deal. One lost it cheap, one lost it loud.
Here is the thing nobody tells you when you start selling websites to local businesses: "it's too expensive" is almost never about the number. It is the most common objection you will hear, and it is also the most misunderstood. Below is exactly how I handle it now, after a lot of blown deals taught me the hard way.
"Too expensive" is rarely about the price
When a plumber or a dentist tells you $3,000 is too much, they are usually saying one of four things:
- I do not understand what I am getting. The number feels random because the value is fuzzy.
- I do not trust that you will deliver. They have been burned by a "web guy" before. Half of local owners have.
- It is genuinely outside my budget right now. Real, but more rare than you think.
- I am comparing you to Wix and a $20/month plan. They do not know why yours costs more.
Notice that only one of those four is actually about money. If you respond to all four with a discount, you are solving the wrong problem three times out of four — and training the client to think your price was fake to begin with. The moment you drop $500 the second they flinch, every other number you ever quote them becomes negotiable too.
The first move: get curious, not defensive
The instinct is to justify. Resist it. When you hear "it's too expensive," the best next words out of your mouth are a question, not a feature list.
I say some version of:
> "Totally fair — can I ask what you were expecting it to land around?"
This does two things. It buys you the real number in their head, and it tells you which of the four objections you are actually dealing with. If they say "I figured maybe $400," you have a value-and-comparison gap, not a budget problem. If they say "I just can't do more than $1,500 this quarter," that is a real budget signal and a different conversation.
You cannot handle an objection you have not diagnosed. Most freelancers start talking before they know what they are even arguing against.
Reframe price as cost-of-the-problem
Once you know what they expected, anchor the conversation back to what the website is for. A local business website is not a design purchase. It is a customer-acquisition tool.
The line I come back to constantly: what is one new customer worth to you?
A roofer's average job might be $8,000. An HVAC install, $6,000. A dentist's new patient, $1,500 in year one and far more over a lifetime. When the site you are building needs to land one of those to pay for itself, a $3,000 price tag stops sounding like an expense and starts sounding like the cheapest salesperson they will ever hire.
Make them say the number out loud. "So if this site brought you two extra jobs a year, what's that worth?" When they do the math themselves, you are no longer the expensive option. You are the obvious one.
Break the price into a payment they can picture
Sometimes the total is the scary part, not the value. $3,000 feels like a wall. The same money framed as a build fee plus a small monthly plan feels like a normal business expense — the kind they already pay for insurance, for their truck, for their phone.
This is also where recurring revenue quietly does its job: a maintenance-and-hosting plan makes your number easier to say yes to and gives you income after the build ships. You are not discounting; you are restructuring.
When the price is real, change the scope — not the rate
If it turns out the budget genuinely is not there, do not lower your rate. Lower the scope. Drop your hourly value and you teach the client your time is worth whatever they push for. Instead:
- Ship a 3-page starter site now, phase 2 in 90 days.
- Cut the custom photography and use what they have.
- Remove the booking integration for v1.
Same rate, smaller project. They get in the door, you keep your pricing integrity, and the upsell is already half-sold for next quarter.
Know when to walk
Not every "too expensive" deserves a save. If someone wants a 12-page site with custom illustration for $300 and will not budge, that is not a price objection — that is a mismatch. Walking away from a bad-fit client is a profit decision. The cheapest clients almost always demand the most revisions. Let your competitor have the headache.
One way I avoid this entirely now is by prospecting better — going after businesses whose current site (or lack of one) clearly costs them money, so the value conversation is half-won before I open my mouth. Mahinatar's Prospector finds local businesses that already need a site, scores how badly, and drafts the outreach — so you spend your pitch time on owners primed to see the value, not talking strangers off a Wix plan.
Related reading: see our guide on building a web design proposal that closes for how to frame price before the objection ever comes up.
FAQ
Should I ever lower my price to win a web design client? Lower the scope, not the rate. Cutting your price signals the original number was inflated and trains the client to negotiate every future quote. Reducing scope keeps your value-per-hour intact while still getting them in the door.
What do I say the moment a client says "too expensive"? Ask what they were expecting it to cost. That single question diagnoses whether you are dealing with a value gap, a trust gap, or a real budget limit — and you cannot answer an objection you have not identified.
How do I justify charging more than Wix or a DIY builder? Reframe the site as a customer-acquisition tool, not a design purchase. Tie the price to the value of one new customer. When a single job covers the build, your price stops competing with $20/month software and starts competing with hiring a salesperson.