How to Turn Down a Client Offer Politely (Scripts)

A low-ball offer isn't just a number. It's the first move in a negotiation, and the first number tends to set the terms for everything after it. That's the useful way to think about it. The question isn't only "should I say yes or no?" It's "what will my reply do to the conversation?" A reply that starts from the client's number and works down or up from there accepts their framing. A reply that restates the project, your price and what the budget can actually buy resets it.

That matters because the instinct many freelancers have, especially earlier in their careers, is to take the work anyway: some income feels safer than none. That instinct deserves a second look. Not because taking lower-paid work is always wrong, but because the cost isn't only the lower fee. It's the hours the job really takes, the work it displaces, and what it teaches the client to expect.

A disclosure first. We make SwiftSignoff, a client-approval portal, so we sell into the same freelance market this article is about. The advice below doesn't depend on our product. We've limited research claims to what we could verify, marked where our sources are secondary or old, and said what we couldn't find.

A low offer is an anchor, and anchors work

Psychologists call the first number in a negotiation an anchor. The classic demonstrations come from Tversky and Kahneman (1974, Science), who showed that estimates move toward an arbitrary starting number. As summarized on Wikipedia (https://en.wikipedia.org/wiki/Anchoring_effect) (a secondary source), people who first saw a wheel stop at 10 estimated about 25% when asked what share of UN members were African countries, and those who saw 65 estimated about 45%. The same summary reports that in a real-estate study by Northcraft and Neale (1987, Organizational Behavior and Human Decision Processes, 39(1), 84–97), both students and real-estate agents were pulled toward a listing price, and agents denied being influenced.

The research closest to your situation is on first offers in negotiation. Galinsky and Mussweiler (2001, Journal of Personality and Social Psychology) ran three experiments in which, according to the abstract at London Business School (https://www.london.edu/faculty-and-research/academic-research/f/first-offers-as-anchors-the-role-of-perspective-taking-and-negotiator-focus), whichever party, buyer or seller, made the first offer obtained a better outcome, and first offers were a strong predictor of final settlement prices. The effect appeared in both face-to-face and email negotiations.

Two caveats before you take this as a law of nature. First, anchoring effects have limits. The Wikipedia summary notes that some studies using clearly random anchors, such as a die roll, failed to replicate the effect, and that participants sometimes treat an anchor as informative. A client's number isn't random: it may reflect a real budget, which is information. Second, these were laboratory negotiations. A client with a fixed budget isn't playing a game of anchoring and adjustment, and the right response to a genuinely fixed budget is simply "that doesn't fit."

The part of the Galinsky and Mussweiler finding worth remembering is what eliminated the advantage. According to the abstract, the benefit of making the first offer disappeared when the other negotiator focused on information that conflicted with the offer's implications: the opponent's alternatives to the deal, the opponent's reservation price, or one's own target. In plain terms, the negotiators who weren't swayed by the anchor were the ones who had thought about what else they could do and what they were aiming for. That's a preparation task, and it's the first thing to do before replying.

Before you reply: know three numbers

You can't resist an anchor you haven't prepared against. Before answering any offer, write down:

1Your target: the price you'd like for this scope.
2Your floor: the lowest price at which the project is worth doing, given everything it will really cost you.
3Your alternative: what you'd do with the time if you declined. A scheduled project, a pipeline of leads or an empty week all give very different floors.

The floor is the hard one, because the obvious version is wrong. It isn't just your hourly rate times your estimated hours. Two things push it up.

Projects take longer than you estimate

Buehler, Griffin and Ross (1994, Journal of Personality and Social Psychology) found that people tend to underestimate how long their own tasks will take, because they plan around the best case and discount the delays everyone meets. Low-budget projects aren't exempt, and a small budget often comes with a client who has less time and fewer resources to give you feedback promptly. We found no research showing that low-budget clients cause more overruns, so we won't claim it. The finding is a reason to check your estimate against your own history.

Work has costs beyond the hours

There's the admin, the revisions and the time you spend deciding to say yes.

A worked example

This scenario is illustrative, and every figure is an assumption.

A client offers $1,200 for a project you estimate at 20 hours. At face value that's $60 an hour ($1,200 ÷ 20). Your target rate is $100 an hour, so the offer is 40% below target. Now check your estimate against history. Suppose your past projects of this kind have run about 35% over your estimates. Then 20 hours becomes 27 hours (20 × 1.35), and the effective rate is $1,200 ÷ 27 = $44.44 an hour.

Now compare with your alternative. If you have a paid project available for those 27 hours at your $100 target, taking this one costs you the difference between the $2,700 you'd have earned (27 × $100) and the $1,200 you'd earn, which is $1,500. If you truly have nothing else for those hours, the calculation changes, and a lower rate may beat none. That's the difference between your floor and your target, and it's why writing down the alternative matters. The decision isn't "is $1,200 low?" It's "is $1,200 more than my next best use of 27 hours, minus the other costs?"

Why discounts cost more than the discount

The common argument against taking low offers is that a discounted rate becomes the client's expectation. There's research in the neighborhood of that claim, with limits.

Marketing research uses the idea of a reference price, which Kalyanaram and Winer (1995, Marketing Science, 14(3, supplement), 161–169) describe as an internal standard against which observed prices are compared. Their review proposes three empirical generalizations: consumers use reference prices when choosing between brands, they rely on past prices to form them, and, consistent with loss aversion, they're more sensitive to prices above the reference than below it. Applied to your situation: a client who has paid you $1,200 may use $1,200 as the standard, and a later quote of $3,000 feels like a loss to them.

The limits are real. That literature is about consumers buying products, not businesses commissioning services, and we found no study of freelance rate expectations specifically. So treat it as a plausible mechanism, not a proven one. There's a practical response that doesn't depend on the research: if you do give a lower rate, make sure the invoice shows your standard price and a labeled, one-time adjustment, so the number the client sees as "your rate" stays where you want it. That's our suggestion, built on the reference-price idea, not a finding.

Two other common claims in this space, that low-budget clients refer other low-budget clients and that declining affects your reputation, are things we looked for evidence on and didn't find. They may be true for you. We just can't tell you they're generally true.

Three ways to respond, rewritten

Here are the three responses a freelancer typically needs, with notes on what each is doing. Adapt the wording to your voice.

When you're open to negotiating: counter with scope, not a discount

The version we'd avoid is "my rate is $X, but I could do something closer to [lower number]." It starts the descent toward their anchor before the client has said why the budget is what it is, and it leaves the scope unchanged, so you're promising the same work for less.

A stronger version ties the price to what the budget buys:

Thanks for sharing the budget. For the full scope you described, my price is [$X]. With [$budget], here's what I can do well: [reduced scope: fewer pages, one revision round, a smaller deliverable]. If the full scope matters, we can talk about phasing it.

This does three things. It states your number first, it makes the budget a constraint on scope instead of a reason to lower your quality or rate and it gives the client something to say yes to. The discount isn't the lever. The deliverable is.

Watch the midpoint

Negotiations often settle between the two numbers, and the counteroffer can set where the midpoint lands. If the two sides drift toward the middle, your counter-number decides where the middle is. That's our own inference from the anchoring research, not a measured finding, and plenty of negotiations don't end at the midpoint.

Run the arithmetic before you answer. Suppose the client offers $1,000, your target is $3,500 and your floor is $2,400. If you counter at $3,500, the midpoint is ($1,000 + $3,500) ÷ 2 = $2,250, which is below your floor. If you counter at $4,000, the midpoint is $2,500, above it. You don't need to be aggressive; you need to know that a polite compromise can land below your floor if you don't plan for it. Scope tiers help here, because meeting in the middle can mean a smaller deliverable at a fair price, not the full job at a bad one.

When the gap is too large to bridge: a short, warm decline

Thank you for thinking of me. This budget is well below what I'd need for this scope, so I'm not the right fit. I wish you the best with it.

Notes on why it's short. A long explanation gives the client several premises to argue with: each reason you list is something they can answer ("but it's only a small site"). A brief decline has nothing to rebut. We don't have research showing that explanations signal uncertainty, which is a common claim, so we'd put it as a practical point: every justification is an invitation to debate it.

The Write Life's advice on handling low offers (https://thewritelife.com/freelance-writing-rates-tips/), from 2019, takes a similar line, recommending warmth, advising against lecturing the client about fair pay and suggesting you know your minimum rate before negotiating. It is practitioner advice, not research.

When you want the door open: say what would change

This budget doesn't work for this scope, but I'd be glad to look at it again if the scope or budget shifts. Feel free to reach out.

Be specific about what would change the answer. "If the scope or budget shifts" is vague. "If the project were limited to X" or "if the timeline were longer" tells them what a workable version looks like, and it's something they can act on.

If you're building a scoped counteroffer, the deliverables and revision rounds you put in writing are what make each tier concrete:

What not to do

Don't over-explain. As above, each reason invites a rebuttal.
Don't lecture. Preaching about fair pay is unlikely to change the client's mind and may cost you the goodwill that makes a future yes possible.
Don't accept by default. If you take a lower rate, decide it deliberately, for a reason you could write down. The danger isn't the exception. It's the exception that nobody chose, which quietly becomes the standard.
Don't badmouth the budget. Even a firm decline should stay professional. We found no research on how declined clients talk about freelancers afterward, so this rests on judgment, not data. But a polite no costs nothing and a sharp one can.
Don't ghost. A one-line reply takes a few minutes. We found no study on whether ignoring an inquiry harms your reputation, so we can't tell you it does. The practical reason is simpler: a brief decline keeps the option open and closes the loop.

When it's worth taking anyway

A below-target project can make sense for specific reasons: it builds a portfolio in a niche you want to enter, the client has strong future potential, or you have idle time that would otherwise earn nothing. The test is whether you chose it.

A way to make the choice deliberate is to write a short exception note before saying yes:

Why: the specific reason (niche, future work, idle time).
What it costs you: the effective hourly rate, using a realistic hours estimate.
Limits: the scope, the revision rounds and the end date.
What it doesn't change: your standard rate, stated on the invoice.

The last item is what keeps the exception from becoming the expectation. Show your standard price, the one-time adjustment and the reason for it. That doesn't guarantee the client will remember, and the reference-price research suggests past prices do shape expectations, which is why the standard rate should still be visible.

Revisit the exception when the project ends. If you'd say yes again, that's information about your rate. If you wouldn't, that's information too.

If the exception involves extra revision rounds, it's worth knowing where your limits sit before you agree to them:

If the client pushes back

Pushback is common, and it usually comes in a few forms.

"That's all we have." Believe it, and respond to it: "Understood. At that budget, here's what I can offer: [reduced scope]." If they don't want a reduced scope, the answer is a decline.
"Can you do it for [lower number]?" You can say no without a new number: "I'm not able to at that price. If the scope were smaller, I could look at it."
"It would be great exposure." You can decline politely and leave the door open: "I appreciate that, but I need to keep my work paid. If the budget changes, I'd be glad to talk."
Silence. Don't chase the same message. One short follow-up after a few days is reasonable, and then let it go.

Holding your number and being kind aren't in conflict: the scripts above do both. Whether to add a small goodwill gesture is a judgment call, and we have no evidence either way.

Keep a record of offers

Over a year, the offers you receive and what you do with them tell you something. A simple log of each offer, its scope, your estimate, your reply and the outcome shows you where your floor really sits, how often your estimates run over and which kinds of clients convert at your rate. We have no research to cite for the habit, since it's just your own data, and it's the evidence that matters for your decisions.

SwiftSignoff, as designed, lets you scope a project into milestones with their own revision limits and approvals, which makes a scoped counteroffer concrete: the client can see what each tier includes and approve one. We haven't audited that for this article, and the advice above works with a proposal document and a clear email.

A checklist before you reply

1Write your target, floor and alternative before reading the offer twice.
2Check your hours estimate against your own overruns.
3Decide whether you're countering or declining.
4If countering, lead with your price and tie the budget to scope.
5Run the midpoint arithmetic so a compromise can't land below your floor.
6Keep a decline short and warm, with no list of reasons.
7Say what would change your answer, if you want the door open.
8If you make an exception, write the reason, the limits and show the standard rate on the invoice.
9Log the offer and the outcome.

What we couldn't verify

That low-budget clients refer other low-budget clients, and that declining or ghosting harms your reputation. We found no source for either.
That a discounted rate sets future expectations. The reference-price research is about consumers and products, not freelancers and clients, so it's a plausible mechanism and not a measured effect.
That over-explaining signals uncertainty. We found no study. We argue from practice: reasons invite rebuttals.
That a counter-anchor sets the midpoint. This is our own inference, not a measured result.
Anchoring itself. Some experiments haven't replicated, and a client's number may be real information. We also couldn't open the primary papers for Tversky and Kahneman or Northcraft and Neale, so their results are as the secondary summary reports them, and we did not verify any research on how the precision of a number affects anchoring.
How clients react to a polite decline, whether they take offense or return later. We found no research.
The forum advice is from a 2008 thread of web designers and is anecdotal.
Our product's features are described as designed, not audited.

Sources

Galinsky, A. D. & Mussweiler, T. (2001), "First offers as anchors: The role of perspective-taking and negotiator focus," Journal of Personality and Social Psychology. London Business School abstract: https://www.london.edu/faculty-and-research/academic-research/f/first-offers-as-anchors-the-role-of-perspective-taking-and-negotiator-focus
Wikipedia, Anchoring effect (https://en.wikipedia.org/wiki/Anchoring_effect) — secondary summary of Tversky & Kahneman 1974, Northcraft & Neale 1987 and negotiation research.
Northcraft, G. B. & Neale, M. A. (1987), "Experts, amateurs, and real estate: An anchoring-and-adjustment perspective on property pricing decisions," Organizational Behavior and Human Decision Processes, 39(1), 84–97 (listing only; no abstract read).
Kalyanaram, G. & Winer, R. S. (1995), "Empirical generalizations from reference price research," Marketing Science, 14(3, supplement), 161–169, as described in the journal listing; we did not read the full paper.
Buehler, R., Griffin, D. & Ross, M. (1994), "Exploring the 'planning fallacy,'" Journal of Personality and Social Psychology, 67(3), 366–381.
Freelance writing rates tips (https://thewritelife.com/freelance-writing-rates-tips/), The Write Life (2019; practitioner advice).
SitePoint Community, How to decline an inquiry with a budget too low (https://www.sitepoint.com/community/t/how-to-decline-an-inquiry-with-a-budget-too-low/4123) (2008 forum thread; anecdotal).

FAQ

Is it okay to just ignore a low-ball inquiry instead of responding?

You can, but a brief decline is better practice. It takes a few minutes, closes the loop and leaves the door open. We found no study showing that ignoring an inquiry harms your reputation, so we won't claim it does, but a one-line reply costs you almost nothing and keeps the option available.

Should I explain my full rate breakdown when declining?

Generally not. A stated starting price or range is enough. Every reason you give is something the client can argue with, so a long justification tends to invite a debate you didn't need to have.

What if the client seems offended by the decline?

It happens, and it's an acceptable outcome if your reply was polite and short. We found no research on how clients respond to declines, so we can't say how often it leads anywhere. What you can control is tone: stay warm, don't lecture and say what would change your answer.

Is there a polite way to counter significantly higher than their offer?

Yes. State your price first and tie their budget to scope, for example "for the full scope my price is X; at your budget, here is what I can do well." You don't need to apologize for the gap or invent an intermediate number. Check the midpoint arithmetic, since a compromise halfway between their number and yours can land below your floor.

Should I ask for the client's budget before quoting?

There's a tradeoff, and we found no research settling it. Asking gives you information but invites the client to name the first number, and first offers tend to anchor the outcome. Naming a "starts at" price first sets your anchor but may lose a client who'd have paid more. Some freelancers qualify by email before quoting. Pick the approach whose downside you can live with.

Your rate is information, not a negotiation you owe an apology for.

See how SwiftSignoff helps you scope and price projects clearly

SwiftSignoff is not affiliated with, sponsored by, or endorsed by Wikipedia, London Business School, The Write Life or SitePoint. This article is general information, not legal or financial advice.

How to Politely Decline a Low-Ball Client Offer