A consultant emailed me last month with a screenshot of a reply she'd just gotten. The prospect, a SaaS founder, had read her $14,000 proposal and written back two sentences: "Love the approach. The price is a bit higher than we budgeted — is there room to move?" She'd panicked, dropped to $9,800 the same afternoon, and the deal still didn't close.
"Too expensive" almost never means what freelancers think it means.
When a prospect says your proposal is too expensive, they're not handing you a price negotiation. They're handing you a diagnostic puzzle. The wrong move — the one almost everyone makes — is to discount immediately. The right move is to figure out which of the four things they actually mean, then respond to that specific thing. Here's how to do it, with the exact wording I've watched freelancers use to recover deals they thought were dead.
The four things "too expensive" actually means
After reading hundreds of follow-up threads freelancers have shared with me, I've never seen "too expensive" mean only one thing. It's always one of these four, and your job in the first reply is to figure out which.
1. "I don't see enough value for that number." This is the most common. They believe what you're offering is real, but they can't connect your price to a business outcome they care about. The fix isn't a smaller number — it's a clearer value story.
2. "I have a real budget ceiling and yours is above it." This is a constraint, not an objection. Some companies have hard caps tied to approval thresholds (a $10k cap that triggers VP sign-off, a $5k cap that goes straight through). If you're above the cap, you either restructure scope or walk.
3. "I'm price-anchored to something cheaper I saw." They got a $4,000 proposal from someone else and yours is $11,000. They don't actually know why the difference exists. Your job is to make the gap legible.
4. "I'm using price as a soft no." Sometimes "too expensive" is the polite version of "I've already decided to go with someone else" or "I'm not actually ready to start." About 20% of the time, in my experience, this is what's happening.
Your first response should be aimed at figuring out which one it is — not at closing the deal. That comes next.
The diagnostic reply (don't skip this)
Before you discount, restructure, or walk, send this. It takes 90 seconds to write and it's saved more deals than any sales script I've seen.
Subject: Quick question on the proposal
Hi [Name],
Appreciate you flagging that. Before I come back with options, two quick questions so I can put together something that actually fits:
- Is the gap between the proposal and your budget closer to 10%, 25%, or 50%+?
- Is this a hard ceiling (procurement, approval threshold) or more of a "want to keep it under X" preference?
No need for exact numbers — a rough sense helps me figure out whether we're looking at a scope adjustment, a phasing approach, or whether I'm just not the right fit on price.
[Your name]
Why this works: you've reframed the conversation from "negotiate down" to "diagnose together." You've signaled you're willing to walk away ("not the right fit on price"), which kills the assumption that you'll fold. And you've made them give you the data you need.
In the consultant story I opened with, when she finally sent a version of this two weeks later, the founder replied: "Honestly, more like 35%, and it's not a hard ceiling, we just need to phase it." That's a deal you can save. She closed it at $11,500, paid in two milestones.
What to do once you know which of the four it is
If they don't see the value (response #1): Don't lower the price. Rewrite the proposal's first page. Most proposals lead with deliverables ("3 strategy workshops, 1 implementation plan, 8 weeks of support"). Lead with the outcome instead — what changes in their business when you're done, and what that outcome is worth.
A copywriter I know got a "too expensive" response on a $6,000 sales-page rewrite. She replied with a one-page revised summary that opened with: "Right now your page converts at 1.2%. Industry median for your category is 3.4%. If we hit median, your monthly revenue from this page goes from $3,400 to $9,600 — that's $74,400 in year-one lift." Same price. Closed the next day.
If they have a real budget ceiling (response #2): Restructure, don't discount. Cut scope to fit. Phase the work — Phase 1 fits the budget, Phase 2 comes later. Move from a fixed deliverable to a retainer. If the ceiling is $5,000 and you proposed $9,000, deliver the $5,000 version honestly: "Here's what I can do for $5k — it's narrower, but it'll move the needle on [X]. If we see results, Phase 2 can come out of the budget we generate."
If they're price-anchored to something cheaper (response #3): Make the gap legible. Send a one-paragraph comparison: "The $4k proposal you mentioned likely covers [scope A]. What I'm proposing covers [scope A + B + C], plus [risk reduction / specific deliverable / experience factor]. If you only need scope A, I can match the lower number — but I'd want you to understand what you'd be giving up." Either you reset the comparison or you find out they only needed the cheaper scope, which is also useful.
If they're using price as a soft no (response #4): You'll know because the diagnostic reply gets a vague answer or no answer. Don't chase. Send a clean breakup email two weeks later: "Sounds like the timing or fit isn't right. Closing the file on my end — if anything changes, send a message and we'll pick it up." About 15% of those breakup emails get a real response, often a "wait, let's talk."
What never to do
Never discount in the first reply. The instant you drop your price without restructuring scope, you've taught the prospect that your original number was negotiable — and they'll assume the new number is too. Every freelancer I've talked to who routinely discounts on the first reply also reports their proposals close at lower margins overall, even with clients who didn't push back.
Never apologize for your price. "I know it's a lot, I can come down if needed" is a deal-killer. It tells the prospect you don't believe your own number.
Never go silent. The worst response to "too expensive" is not responding for a week while you figure out what to do. The prospect interprets silence as confirmation that they overpaid by considering you at all. Reply within 24 hours, even if the reply is just the diagnostic above.
Never match a cheaper competitor without changing scope. If you drop to match a $4k competitor while keeping your original $11k scope, you've just confirmed your work is worth $4k. You'll resent the client and underdeliver. Match the scope or hold the price.
The 72-hour follow-up cadence after the pushback
If your diagnostic reply goes unanswered (which happens about 40% of the time, in the freelancer threads I've read), here's the cadence that works:
- Day 3: A short bump. "Just making sure my last note didn't get lost in your inbox. Happy to jump on a 10-minute call if that's easier than email."
- Day 7: A value-add. Share an article, a case study, or a quick observation about their business that's relevant. No mention of the proposal. The goal is to stay top-of-mind without pestering.
- Day 14: The breakup. "Sounds like timing isn't right — closing the file. If things shift, you know where to find me."
The breakup email pulls in about 1 in 6 responses across the data I've seen. Many of those convert. The rest free you up mentally to stop refreshing your inbox.
For a deeper breakdown of how to space follow-ups in general, the complete proposal follow-up guide walks through the full cadence with timing data. And if you want the actual templates for breakup emails, the breakup email post has three versions ready to copy.
A note on raising your prices after this happens
If you're hearing "too expensive" on more than half your proposals, your pricing isn't the problem — your positioning is. Either you're talking to the wrong prospects (companies that genuinely can't afford you) or you haven't built enough perceived value before the proposal lands. Both are fixable, but neither is fixed by lowering your prices.
The freelancers I've talked to who close at the highest rates almost never get "too expensive" replies. Not because their prices are lower, but because by the time the proposal goes out, the prospect has already mentally committed to the price range. That happens in the discovery call, not the proposal itself.
If you're sending the proposal cold and hoping the price lands well, you'll keep getting price pushback. The discovery call is where you set the anchor.
Where ChaseNudge fits
The hardest part of handling a "too expensive" reply isn't the first response — it's the 14-day follow-up cadence afterward. Day 3 bump, Day 7 value-add, Day 14 breakup. Most freelancers drop the ball somewhere in the middle because they're juggling 8 other proposals and the deal slips off the calendar. ChaseNudge is the tool I built to automate that exact cadence — when a prospect goes quiet after pushback, it sends the right follow-up at the right interval so you don't have to remember. Useful if you're losing deals in the silence between replies.
Frequently asked questions
Should I ever lower my price on a proposal?
Yes — but only with a scope change. Lowering the price without removing or phasing deliverables trains every future client to negotiate. If the budget is real, restructure what you're delivering to fit it. If you're going to do the same work for less, you've just discovered you were overpriced — fix that in your next proposal, not this one.
How do I respond if the client says "your competitor quoted half"?
Ask what scope the competitor quoted. Nine times out of ten, the comparison isn't apples to apples — different deliverables, different timelines, different experience level. Lay out the scope difference in one paragraph. If they only need the cheaper scope, match it. If they need yours, the comparison resets itself.
Is it okay to ask the client what their budget is?
Yes, and you should be doing it before the proposal goes out, not after. On the discovery call, ask "What's the budget range you've set aside for this?" If they won't share, give them a range: "Most projects like this land between $X and $Y depending on scope — does that ballpark work?" That single question prevents 80% of "too expensive" surprises.
What's a good email subject line for replying to a pricing objection?
Keep it neutral and curious. "Quick question on the proposal" or "Re: your note on pricing — couple of questions" work better than anything that hints at a discount. Don't use "Revised pricing inside" — it commits you before you've diagnosed the situation.
How long should I wait before sending the diagnostic reply?
Same day if possible, within 24 hours at the latest. Speed signals confidence. Waiting three days to "think about how to respond" signals that the pushback rattled you and they'll smell it in the reply.
The next time a prospect tells you your proposal is too expensive, don't reach for the discount button. Reach for the diagnostic. The deal you save is almost always worth more than the discount you would've given.