How to decline a discount request without killing the conversation

“You are great, but can you do it for less?”

That message lands after you already did the thinking. Your proposal named deliverables, timeline, maybe milestones. Now the client treats price like a market stall.

Sometimes discounting makes sense. Often it trains clients to push every future project. This guide helps you respond without sounding defensive, trade scope instead of value, or exit cleanly.

For payment structure language up front, see payment terms in a proposal. For posts where the budget was low from the start, see when the job post budget is clearly too low.

First: decide if this is negotiation or a filter

Negotiation signals:

• They reference your scope and ask which part is expensive.
• They want to start smaller but stay serious (“can we phase it?”).
• They have a real deadline and compare you to one other freelancer.

Filter signals:

• They want the same scope for half the price with no changes.
• They use guilt (“others bid $X”) with no data you trust.
• They demand unpaid proof before discounting an already-low quote.

Filters are not always rude people. Sometimes they are buyers who will never be profitable. You can decline politely and move on.

Rule 1: do not discount without removing something

If you lower price, change scope, speed, or risk you take.

Examples of fair trades:

• Fewer revision rounds.
• Smaller milestone 1 (diagnostic only).
• Longer timeline.
• Async-only communication.
• They provide assets you would have created.

Write the trade in writing. “Same work, cheaper” is how projects go sideways.

Response A: hold price, offer a smaller milestone

I want to make this work. At the full scope we discussed, my rate stays [price] because [one reason: risk, timeline, specialized work].

If budget is tight right now, I can quote a smaller milestone 1: [deliverable list] for [lower price]. That gives you [outcome] without committing to the full build yet.

This respects both sides. You are not begging. You are productizing entry.

Works well with propose milestones when the client never mentioned them.

Response B: hold price, explain the cost driver

I hear you on budget. The main cost drivers here are [2 items]. If we remove [item], I can bring it to [new price]. If everything stays, I stand by [original price] because [brief reason].

Clients sometimes think you are padding hours. Naming drivers (integrations, approvals, compliance) educates without a lecture.

Response C: when they compare you to a cheaper bid

Thanks for being direct. I cannot match [low number] for the same scope and timeline. What I can do is [your differentiator: speed, niche experience, clearer milestone 1, maintenance included].

If the other bid omits [specific risk], you may pay twice later. I am happy to compare line by line if you paste their scope.

Do not attack the other freelancer. Attack scope mismatch.

Response D: when you will walk away

I appreciate the interest. At [their target price], I cannot deliver the quality and support this scope needs. I would rather pass than under-deliver.

If scope or timeline becomes flexible later, feel free to reach out.

Short. No apology tour. Professional doors stay open.

What not to say

• “I really need the work” (even if true).
• Instant yes with no written scope change.
• Sarcasm about their budget.
• A wall of text about your rent or rates in your country.

Buyers are not your therapist. They are buying outcomes.

Discount traps on marketplaces

Trap: discount before hire, then scope explodes in chat.

Fix: Confirm milestone 1 in the contract or platform offer. Link back to your proposal bullets.

Trap: “We will have lots more work later.”

Fix: Optional small loyalty note is fine. Do not fund a loss leader on a promise. Price milestone 1 for milestone 1.

Trap: repeat client asks for the same discount every time.

Fix: For repeat work, see repeat client proposal: what to cut. Raise rates on new phases instead of shrinking old ones.

If they ghost after you hold firm

That is data. Use the cadence in when the client ghosts you after a proposal, but do not chase with new discounts.

Prevent discount talks in the proposal itself

• State milestone 1 narrowly.
• Include revision limits (how many revision rounds to promise).
• Add a short out of scope line.
• Give a range when the post is vague (no budget listed).

Clear proposals attract clients who already accept your model.

Quick decision tree

1. Same scope, lower price, no trade? Usually decline.
2. Can you shrink milestone 1 and still help them? Offer B or A.
3. Are they comparing bids? Response C with scope compare.
4. Is the tone abusive or scammy? Walk away (scam-style posts).

Checklist before you reply

• I know my floor price for this work.
• Any discount has a written scope or terms change.
• I did not apologize for my rate.
• I offered one constructive path forward (smaller phase, phased build, or polite no).
• I saved the message thread if we hire on-platform.

You can be kind and firm at the same time. Clients who respect work will not punish you for pricing like a professional.