Pricing Objection Scripts: 7 Replies When Clients Say It's Too Expensive

You sent the proposal Monday. Wednesday, the reply lands: "Love the work, but the price is a bit too high. Anything you can do?"

Cursor blinking. Coffee going cold. Your hand is already reaching for the discount button.

Quick honest note before we start. I'm not a salesperson. I'm a dev — I build DocsAura, a tool freelancers use to ship proposals fast. So I'm not going to talk like a sales coach. I just watch a lot of users get to this exact message, and I asked a few people who close deals every week what they actually type back.

What follows is seven replies. Each one keeps the price intact. Each one moves the conversation forward instead of ending it. Pick the one that fits, copy the sample message, send it before you start second-guessing.

1 — Ask what "too expensive" is being compared to

Most clients are not comparing your number to a fair market price. They are comparing it to whatever number was in their head before they opened the proposal. Find that number first.

"Thanks for the honest reply. Out of curiosity — when you say a bit too high, what were you mentally comparing it to? A previous quote, an internal budget line, a number from another freelancer? It helps me give you a real answer."

Let's say they reply "my last freelancer charged €3,500 for a site." Now you know. You're not negotiating in the dark — you're talking about why this scope is different from that one. Half the time the client themselves realizes the comparison was apples to oranges and the objection quietly drops.

2 — Quote the bigger problem, not the deliverable

A €14,000 proposal sounds expensive on its own. The same €14,000 sounds different next to "the cost of another quarter without leads" or "the cost of hiring in-house for this." Bring the bigger number into the conversation.

"Totally fair. One number that might help frame it — the alternative we talked about, hiring in-house for this, runs about €6,500/month plus three months of ramp before they ship anything. The proposal is a one-time €14k and you have the site live by end of June."

Let's say the client is a founder. The thing they actually fear is not your price. It's wasting another quarter without the site live. Name that fear out loud and your number suddenly has something to sit next to.

3 — Offer to remove a deliverable, not drop the price

Discounting tells the client your first number was made up. Removing scope tells them the price was fair and they get to choose what they want for that price. Let them choose.

"I can keep the price where it is and trim scope to fit. Two options: I can drop the three customer interviews from the discovery phase, or I can ship the site without the CMS migration and you handle that internally. Either gets us to about €11,500. Want me to lay out which makes more sense for you?"

Let's say they pick option two. You just defended your rate, gave the client agency, and made the next email easy for them to send. Nobody felt squeezed. The number per day of your work did not change.

4 — Propose a smaller paid pilot instead of a discount

If the client cannot commit to the full scope yet, do not slice the price. Slice the project. A two-week paid pilot at full rate gives them a low-risk way in and gives you a way to keep the day rate intact.

"Understood. If the full scope is too much to commit to right now, I can run a two-week paid pilot at €3,800 — we ship the home page and the lead form, you see how we work together, and if it's a fit we roll straight into the rest at the original price. If it's not, we part friends and you keep what we built."

Let's say you're a designer worried this will look needy. It doesn't. Reframe it for yourself — you're protecting your rate while giving the buyer a smaller door. The pilot is paid. You did not discount anything.

5 — Hold the price, move the payment terms

Sometimes the objection is not about price. It is about cashflow. Same number, different schedule, can turn a no into a yes.

"Price has to stay where it is — the scope is fully booked at that rate. What I can move is the schedule. Three payments instead of two: €5,000 to start, €5,000 at the halfway demo, €4,000 on launch. Same total, easier to fit into your monthly burn. Does that help?"

Let's say the client runs a six-person agency and your number is one bad month away from breaking their account. They are not going to admit that on email. Giving them a softer schedule lets them say yes without having to say "we're tight this month."

6 — Walk them through what cheaper actually looks like

If a client wants a 30% cheaper number, show them what they actually get for that number. Not as a threat — as a real picture. Most clients silently expected to lose nothing for the discount. Showing them the trade-off resets that.

"Sure, I can shape a €10,000 version. Honestly, here's what that looks like: I'd use one of my existing layout templates instead of custom design, skip the copywriting (you'd write it), and drop post-launch support to one week. It would ship, and it would work. Want me to send that version as a separate proposal so you can see it side by side?"

Let's say you send the cheaper version. About half the time the client looks at the two, sees what they would lose, and comes back to the original. The other half they pick the cheaper one and you both go in with no surprises. Either result is fine.

7 — Say a slow no is fine and step back for a week

The worst reply to "a bit too expensive" is a long defensive paragraph. The second worst is silence. The right move is to take the pressure off and let them think.

"Totally hear you. I don't want to push you into a number that doesn't feel right. Take a week, talk to the team, and if you land on a no that's a clean answer too. I'll follow up next Wednesday — either way, no awkwardness."

Let's say they come back Wednesday with "yeah, we'll go ahead at the original price." That happens more than you'd think. The pressure usually was not your number. It was the feeling of being sold to. Removing the sell often removes the objection.

A worked example — end to end

A SaaS founder writes back about a €14,000 marketing site proposal: "This is more than we wanted to spend. Can we get to €10,000?"

Monday, 4pm — you reply with Script 1:

"Thanks for being direct. Quick question — what was the number you had in mind when you opened the brief? I want to give you a real answer, not just a discount."

Tuesday morning — they reply:

"Honestly we'd budgeted €9k internally based on a quote we got from an agency last year."

So the real number you are negotiating against is €9,000 — and it is from an agency quote, not from your scope.

Tuesday, 11am — you reply with Script 2 + Script 6 stacked:

"Got it, thanks. The agency number is helpful context. The proposal is €14k because we're handling design, copy from interviews, build, and two weeks of post-launch fixes — the agency quote you mentioned was likely design + build only, which is closer to €9-10k market-wide.

I can shape a €10,000 version if that's what fits — I'd skip the customer interviews, you'd hand me copy, and post-launch support drops to one week. It ships, it works, it just won't have the lead-form copy we'd otherwise A/B-test. Want me to send that as a separate option?"

Friday — they reply:

"Send both. We'll pick over the weekend."

Monday morning they pick the original €14,000 version. They wanted to see the cheaper one to feel like they made a real choice. You never dropped the rate. You let them choose.

What to avoid

A few short tripwires:

• Don't apologize for the price in the same email you defend it. "I know this is a lot…" makes the price feel even bigger. Defend the number or remove scope. Don't do both at once.
• Don't discount on the spot, even by 10%, even just this once. Every future client of theirs you ever get will hear about it. Discount once, discount forever.
• Don't fire back the same hour. Wait an hour, write the reply, sleep on it, then send. The slower reply reads as confident. The instant reply reads as panicked.
• Don't pretend you have a "policy" you don't have. "Company policy is no discounts" sounds like a script. "I priced this at my real rate and I can move scope but not the rate" sounds like a person.
• Don't take the objection personally and disappear. Replying "no problem, totally fine, just let me know" and going dark for a week reads as offended. Stay friendly. Use Script 7 instead.

A good reply to "too expensive" is calm, short, and offers a path that is not a discount. That's it.