"That's too expensive." Three words that make most freelancers lower their eyes, and their rates. Yet answering "that's too expensive" is not a question of discounts, but of framing. As a freelancer, every pound conceded under pressure comes straight out of your net margin. This article gives you a precise method, a tested script and a worked example to turn this objection into a signature, without giving your work away.
What "that's too expensive" really means
Too expensive compared to what? The price objection is almost always a reference problem, not a budget one. The client is comparing your quote to a figure they already have in mind: a low-cost competitor, a rough back-of-the-envelope estimate, or the fantasy that "it won't take long." Your first instinct should not be to justify yourself, but to understand the point of comparison. Use tactical empathy to defuse the emotion: "It sounds like this figure has surprised you compared to what you'd pictured." You acknowledge how they feel without agreeing to a discount.
Never drop your price first
The classic freelance mistake: hearing "too expensive" and immediately knocking off 15%. You've just taught the client that your first price was padded, and that all they need to do is grumble. Hold your number. Strategic silence is your best ally here: once you've stated your rate, say nothing. Five seconds of silence weigh more than three arguments. Often the client fills the gap by revealing their real constraint: "Actually my budget caps at 4,000." Now you know where you're negotiating.
The story of Camille and the £6,200 quote
Camille, a freelance UX designer, sends a quote of £6,200 for the redesign of an e-commerce site. The client, the head of a small business, replies over the phone: "Honestly, that's too expensive, I've got another quote for 3,500."
The old Camille would have panicked and offered 4,500. This time, she applies the method. First the mirroring technique: "Another quote for 3,500?" The client elaborates, and lets slip that this competitor offers no mockups, no user testing and no post-launch support. Camille then asks a calibrated question: "How am I supposed to come down to 3,500 while still guaranteeing you the testing that will stop you having to rebuild the site in six months?"
Then she refocuses on objective criteria: the average conversion rate of an optimised site, the cost of an abandoned basket, the going day rate for a senior UX designer on the market. The "too expensive" loses its emotional anchor. She finishes with a calibrated gesture on a give-and-take basis: "I can spread the payment over three instalments, if you sign off this week." Result: signed at £5,900. Camille gave away £300 on form, and nothing on substance.
Sell the value, not the hours
"Too expensive" collapses the moment you change the unit of measurement. The client is comparing prices; you compare results. Don't sell "5 days of development" but "a checkout funnel that recovers 12% of lost baskets." Lean on objective criteria and on social proof: one client case with real figures beats ten adjectives. The contrast technique does the rest: set your full offer against the competitor's bare-bones option, and the price stops being "expensive" and becomes "justified."
Your best weapon: being willing to lose the deal
The freelancer who needs this client negotiates badly. The one who can say no negotiates hard. Work on your BATNA: a pipeline of prospects, a recurring client, a few weeks of cash in the bank. This fallback changes your voice, your posture, your walk-away point. And when the client pushes too far, a controlled withdrawal, "I understand, perhaps this isn't the right time," often triggers the opposite effect: they're the ones who come back. To sharpen these reflexes before the real meeting, practise on the simulator or browse by situation in the library.
FAQ
Should you name your price first when facing a client?
Yes, on most freelance projects. Stating your rate first sets a high anchor point that structures the whole discussion. The risk isn't anchoring, but anchoring too low out of fear of "too expensive." Set a figure you can defend with objective criteria, then hold it.
What should you say if the client genuinely has a limited budget?
Don't drop the price: cut the scope. Remove a feature, extend the deadline, take out a round of revisions. You protect your day rate and give the client something in return. That's give-and-take: less deliverable for less budget, never the same deliverable for less.
