Try SpecBot free — update a proposal and keep one share link; the client accepts in one click.
Client pushback on a proposal is normal. The goal isn’t to avoid it — it’s to handle it in a way that either closes the deal on terms you can deliver profitably, or cleanly walks away from a deal that isn’t right.
Here’s how to handle the three most common types of pushback: price, scope, and timeline.
Type 1: Price pushback (“It’s too expensive”)
Price pushback is the most common and the one where freelancers make the most costly mistakes.
What NOT to do: Lower your price immediately in response to any pushback. Instant discounting tells the client your original price was arbitrary, signals that you’ll discount again, and starts the project with an implicit question mark about your value.
Step 1: Understand the concern before responding.
“Too expensive” can mean several different things:
- “I can’t afford this at all” (budget problem)
- “I expected this to cost less” (expectation problem)
- “I don’t understand why it costs this much” (value problem)
- “I can get this cheaper elsewhere” (competition problem)
The right response to each is different. Ask: “Can you help me understand what you had in mind? Is it the total amount, or is there a specific part of the scope that feels disproportionate?”
Step 2: Address the actual concern.
If it’s a budget problem: “If your budget is $[X], I can scope a version of this project that fits. It would cover [priority items] and phase in [lower-priority items] once we’ve established the relationship. Would that work?”
If it’s an expectation problem: “I understand the number is higher than you expected. Let me walk through what’s driving the price — [explain the work that justifies the line items].”
If it’s a value problem: “You’re right to push on value. Here’s how I think about it: [connect the investment to the business outcome]. Does that framing change how you’re thinking about it?”
If it’s a competition problem: “I understand you’re comparing options. Without knowing what others are proposing, I can say that [what differentiates you — your approach, your experience, your process]. If you want to share what you’re seeing elsewhere, I can help you compare on an apples-to-apples basis.”
Step 3: If scope reduction is appropriate.
Offer to reduce scope, not price. The distinction matters:
- “I can do the same project for $1,000 less” = your price was inflated
- “For $1,000 less, we’d cut [specific deliverable] and do [smaller version of scope]” = you’re adjusting what you deliver
Specific phrase: “I can’t do the same scope for less — my pricing is based on what the work actually costs me to deliver well. But if budget is a hard constraint, I can scope a Phase 1 that covers [critical priorities] for $[X], and we can phase in the rest.”
Type 2: Scope pushback (“I need more than this”)
Sometimes clients push back because they want to add to the scope after seeing the proposal — either things you didn’t discuss, or things you intentionally scoped out.
For items not discussed during discovery:
“That wasn’t part of our discovery conversation — happy to add it. Let me put a quick change order together with the added cost and any timeline impact. Should have it to you [timeframe].”
No apology. No guilt. Just a clear, professional process for handling scope additions.
For items you intentionally excluded:
“That’s excluded from this proposal because [brief reason — usually: it would add significant complexity, it’s outside your primary specialty, or it would extend the timeline significantly]. It’s available as a separate engagement or add-on. Do you want me to scope it separately?”
For items that were misunderstood:
If the client expected something to be included that you didn’t include, don’t fight about who was right. Clarify what actually happened and find a solution: “I think we may have had different expectations here. Based on our conversation, I understood [X]. If [Y] is actually needed, let me see if I can include it in the existing budget or scope a modified version.”
Type 3: Timeline pushback (“We need it faster”)
When clients push on timeline:
If faster is genuinely possible with a rush rate: “I can compress to [X weeks] if we prioritize this project. That would require a 25% rush rate — bringing the total to $[X]. The reason is I’d need to adjust other project timelines to focus on this one. Does that work?”
If faster isn’t possible without sacrificing quality: “I could technically start earlier, but the timeline I’ve quoted is based on what produces good results — enough time for proper discovery, thoughtful design, and thorough QA. Compressing it significantly would mean cutting those steps, which typically leads to more revision cycles and a worse outcome. I’d rather take the time and get it right.”
If they have a hard deadline that’s immovable: Offer to reduce scope to fit the timeline. “To hit [date] with quality I’m confident in, we’d need to scope this to [reduced scope]. That gets you [priority deliverables] by your deadline, and we can phase in [the rest] after.”
How to revise a proposal
When you agree to revise, the process matters:
1. Make changes clearly identified. In the revised proposal, note what changed: “Updated scope to include [addition]” or “Pricing adjusted to reflect [reduced scope].”
2. Keep the structure clean. Don’t just edit in-place and hope the client spots what changed. If using a proposal tool, update the document and note the changes. If sending by email, be explicit: “I’ve revised the proposal based on our conversation — the key changes are [X] and [Y].”
3. Set a reasonable window for the revision. “I’ll have the revised proposal to you by [date].” Don’t promise same-hour turnaround unless you can genuinely deliver it.
4. Don’t revise indefinitely. If you’ve revised the proposal twice and still don’t have agreement, have an honest conversation. “I want to make sure we find the right fit here. Based on where we’ve landed, I want to check — is there a version of this engagement that works for both of us? Or is it possible the timing isn’t right?”
Knowing when to walk away
Not every deal is worth closing. Walk away when:
- The client wants the same scope for significantly less than your price can support
- The revision process has revealed misaligned expectations about quality, process, or timeline
- The client is unreasonably difficult during the proposal stage (this predicts a difficult project)
- The project would require underdelivering on what you’ve proposed to hit the budget
Walking away is a business decision, not a failure. Saying “I don’t think I’m the right fit for this project at this budget” is honest and professional. It preserves the relationship better than taking a project you can’t deliver well.
Start free on SpecBot — SpecBot turns your offers into proposals clients accept in one click, with a signed PDF for both sides. Free is 3 proposals a month with every feature; Pro is unlimited proposals at €12/month, or €9/month billed yearly. Write them in the web app, by voice, or inside ChatGPT and Claude.