How-to guide · Getting paid

When a client says you're too expensive: what to hold, what to trade, when to walk

A prospect has a cheaper quote — sometimes half yours, sometimes a third — and now they are telling you about it. That number is information, not a verdict: a price that low usually tells you as much about what the other quote leaves out as about what it includes. The professional response is neither a discount nor a defence of your worth. It is a comparison the client can actually use — what each quote contains, line by line — plus an honest set of trades if the budget is real, and the willingness to walk away from the version of the job that cannot be done well at their price. Pushback with no rival quote in play is the wider conversation, covered in freelance rate negotiation; this guide is for the moment a specific cheaper number is on the table.

First, hear which sentence they actually said

"You're too expensive" sounds like one objection. With a rival quote behind it, it is usually one of three different sentences, and each has a different answer.

"Convince me the difference is real." The persuadable case, and the common one. They like your quote; they need the argument — for themselves, or for a partner or manager who will ask why they did not take the cheaper one. Your job is ammunition, not movement: the comparison below is written for exactly this client.

"Match it, or we go with them." The procurement reflex. Sometimes it is real — closing price gaps is literally someone's job. Sometimes it is a test of whether your first price was theatre. Either way, do not obey it before testing it: a client who would genuinely walk over the gap will usually engage with a trade; one who is testing will accept one just as happily.

"We honestly can't spend that." A budget fact, not a negotiation. Grants, fixed pots and hard ceilings exist, and arguing value at a wall does not move the wall. The answer is a smaller scope at your full rate — the packaged shapes in how to productize a freelance service exist for exactly this conversation.

One question sorts the three, asked warmly and early: "If both quotes cost the same, which would you take?" If they would take yours, you are not in a price problem; you are in a proof problem, and proof problems are fixable. If they would take the other one even at the same price, price was never the obstacle — something about fit or trust is, and discounting would only have hidden it. And if they hesitate, they do not yet know what differs between the two quotes. Most undercut conversations live in that hesitation.

Make the two quotes comparable

Two numbers cannot be compared until the things behind them are. A quote is a list of inclusions wearing a total, and the cheaper total usually belongs to the shorter list. The scope gap is normally the price gap — which is why the discipline in how to write a project brief matters before pricing, not after it.

Offer the client a two-minute check they can run on the other quote. You are not auditing a competitor; you are handing them questions:

  • Does it name the same deliverables as yours, or a summary of them?
  • How many revision rounds are included — and what counts as a round?
  • Are the source files and working files part of the hand-over?
  • Who does the unglamorous middle work — setup, migration, testing, the fixes after launch?
  • What timeline is promised, and what happens when it slips?
  • Who will you actually deal with day to day?

Two rules while you do it. First, never disparage the other quote or whoever wrote it. You have not seen their work, attacking them reads as fear, and fear loses rooms. The only line you need is: "I can only speak for what's in mine." Second, state your own inclusions once, calmly, as a list — the deliverables, the revision rounds, the middle work, the aftercare — the way the quote was built in the first place; the project price calculator shows that build. Then stop. The list does the arguing. Repeating it louder does not.

What you can trade — and what you can't

If the budget is real and the job is worth having, the price can move — but only when something moves with it. A price that drops alone is a pay cut. A price that drops against scope, time, terms or commitment is a different deal, honestly described. Each trade below is written the way the client hears it.

Scope. "I can't do the whole build for that figure — but I can do the core of it: the site and the booking flow, with the migration and training as a priced second phase." Fewer pieces, same rate, same standard.

Timeline. "At six weeks instead of three, I can meet you part-way." Work that fills a quiet stretch instead of displacing booked work genuinely costs you less to deliver. When that is true, say so and price it; when the diary is full, it is not true, and the trade does not exist.

Terms. "Half up front and the balance on delivery instead of net 30, and I can sharpen the price." Faster, surer payment is worth real money to you, so it can fairly buy some of the gap — the shapes are set out in freelance deposits and upfront payments.

Commitment. "If this becomes a monthly arrangement rather than a one-off, the numbers change for both of us." The retainer shape in how to move a client onto a retainer prices certainty: a client buying a year of you is not buying twelve one-offs.

What never trades: the quality floor — the corners your name is attached to; the unpaid extras that creep in after a cut, as if the smaller price had quietly bought the fuller scope; and the logic of the rate itself. That last one is arithmetic, not pride. Run a cut through the margin calculator's own defaults: a $1,900 price carrying $1,140 of costs holds $760 of profit — a 40.0% margin. Cut the price by 20%, to $1,520, with the costs unchanged, and the profit does not fall by 20%. It halves, to $380, and the margin falls to 25.0%. A price cut without a scope cut comes straight out of the profit, at leverage — which is why every trade above moves something real.

When to walk — and how to leave

Three tests tell you the conversation is over. Doing the job at their price would mean cutting the corners your name is attached to. The client wants the cheaper quote's price for your quote's scope — both halves of two different deals at once. Or the discount being asked for is larger than anything the trades above can honestly fund. If any test is met, the negotiation is not failing. It has finished.

Walking away well is a skill with a script. No collapse discount at the door: a price that folds at the last minute teaches the market your first number was theatre. Say this, or your own version of it (66 words):

Thank you for telling me plainly — I'd rather know where I stand. My price is the lowest I can do this work properly for: below it, I'd be cutting corners you'd end up paying for twice. If the budget is fixed, I'm happy to cut the scope instead and quote a smaller version that still lands well. Either way, I hope the project goes well.

Then leave the door open, and mean it. Some of these projects come back — when the cheap route disappoints, when the budget grows, when the second phase needs doing properly. That is a possibility to stay gracious for, never a probability to count on. The freelancer who left well is the one who gets that call. The one who collapsed, or sulked, does not.

After the conversation

If you win: the scope you agreed — after any trade — is the scope that goes in writing before work starts; freelance contract basics covers the paperwork. A trade that lives only in the call gets renegotiated by memory in week three, and memory always remembers the lower price with the fuller scope.

If you lose: debrief it while it is fresh, the way how to run a project retrospective prescribes. Was it price, proof, or fit? A price loss on a job you priced honestly is information about targeting. A proof loss means the next prospect needs better evidence, not a lower rate. A fit loss is often a win wearing a disguise.

And the rate itself stays where it was: public, steady, printed on your freelance rate card. One prospect's budget is not market research. If you want to know what the market will bear, that is an experiment — new enquiries, a defined window, a decision rule — and how to test a higher rate is the method. An existing client asking for money off a rate already agreed is a different conversation again: that one is how to handle a client asking for a discount.

Questions

Only when something moves with the price — fewer pieces, a slower timeline, better terms, a longer commitment. Matching the number alone, for the same scope, is a pay cut you volunteered for, and it teaches the client that your first price is an opening bid. If nothing can move and the number still does not work, the honest options are a smaller scope at your full rate or a gracious no.
You don't need it. Run the comparison on your own quote instead: walk them through what yours includes — revisions, source files, the middle work, the timeline — and let them hold the other quote against it privately. A client who won't share it may be protecting a negotiation, or the other quote may not exist in writing at all. Either way, your included list does the work.
No — the conversation is the same, because you're comparing scope and outcomes, not postcodes or business models. A lower price from anywhere usually reflects a different scope, a different cost base or a different level of senior attention, and any of those can be the right buy for a given client. Say what yours includes, trade only against something real, and let the comparison — not the competitor's address — decide it.
Losing some work on price is the rate working: a price everyone accepts is a price set too low. Losing nearly all of it is data, but check the other suspects first — proof (testimonials and case studies a prospect can verify), targeting (are you quoting people whose budget was never there?), and how the quote is presented — before touching the number. If the rate itself is the question, test it properly on new enquiries rather than discounting it inside live negotiations.