Most freelancers wait too long to raise their rates, and when they finally do, the email takes three times longer to write than it should — because it gets treated like a confession instead of a normal business update. A rate increase isn't an apology. It's information a client needs with enough notice to plan around it, and it turns out research on how people actually respond to price increases lines up closely with that instinct, in some ways that confirm it and one or two ways that add real nuance.
What the research on price-increase communication actually finds
Most of the available research on this is drawn from consumer and retail pricing rather than B2B freelance services specifically, but the underlying psychological mechanisms it documents — fairness perception, and how people react to a message framed as a loss — are general enough to apply by reasonable analogy to a client relationship.
Plain language outperforms euphemism. Research summarized in pricing-communications analysis is consistent on this point: calling a price increase a “price adjustment,” or otherwise softening the language, tends to backfire rather than help. Direct, transparent language — actually saying “rate increase” — is more likely to maintain trust than a message that reads as trying to obscure what's happening.
An unexplained increase is perceived as the most self-serving. Research on price-increase fairness finds that when no reason at all is given, customers tend to interpret the change as pure profit-taking at their expense. A cost- or value-justified reason — the kind of explanation that points to something legitimate behind the change — is perceived as fairer than one framed purely around demand (“I'm busier now”) or, worse, no framing at all.
But over-explaining backfires just as much as under-explaining. This is the genuinely useful nuance: the same body of research warns against over-justifying or apologizing for a price increase — described memorably in one analysis as “methinks the seller doth protest too much.” A long, hedging explanation reads as defensive, which undermines the fairness perception a brief, confident reason would have supported.
The synthesis of these three findings is fairly precise: one clear, brief, legitimate reason, stated plainly, without apology — not zero reasons, not several, and not soft-pedaled language.
The framework
Give real notice, not a surprise on the next invoice. 30–60 days' notice is standard, more for retainer or ongoing work. Beyond simple courtesy, this also does real psychological work: research on how people respond to price increases generally finds that changes framed or experienced as a sudden loss are received far more negatively than the same change absorbed gradually — advance notice effectively spreads the adjustment out, softening what would otherwise land as an abrupt hit.
State it plainly, once, with exactly one reason. A short, confident statement, naming the change directly and giving one legitimate reason, tends to outperform both a bare announcement and a hedge-filled justification: “Starting [date], my rate will be [$X], reflecting [the added experience/demand for my work since we last discussed pricing]. Wanted to give you plenty of notice ahead of our next project.” One reason, stated once, then move on.
Offer existing work at the old rate if it's already scoped. “Anything currently in progress or already quoted stays at the current rate — this applies to new work starting [date].” This removes the incentive for a client to feel like they're being charged more mid-stream.
The script
Hi [Client], wanted to give you advance notice that starting [date], my rate for [type of work] will be [$X], reflecting [one brief, genuine reason]. This applies to new projects going forward — anything already scoped stays at our current rate. Let me know if you'd like to lock in any upcoming work before the change takes effect.
That last line does real work: it turns the increase into an opportunity (book now at the old rate) rather than only a cost — and, per the loss-aversion research above, giving the client an actionable choice tends to soften how the change is experienced compared to a flat, one-way announcement.
A brief real-world parallel, for scale
This dynamic isn't unique to freelance pricing. When a very large, consumer-facing company raised prices nationally in December 2024, it explicitly framed the increase as an inflation offset — a clear, brief, cost-justified reason, stated directly rather than buried or apologized for. The scale is obviously different from a freelancer's rate email, but the underlying communication choice — one plain reason, no hedging — is the same one the research above supports at any size.
Choosing which single reason to give
Since the research favors exactly one legitimate reason over zero or several, it's worth being deliberate about which one. Not all reasons land equally well:
Cost- or value-justified reasons tend to be perceived as fairest. “Reflecting the additional training/tooling/capacity I've invested in this year” points to something concrete the client can recognize as a real input cost, similar to how a cost-justified price increase is generally received better than one framed around raw demand.
Demand-justified reasons (“I'm fully booked”) are weaker, but not disqualifying. They're accurate for many freelancers and honestly stated is still better than no reason at all — the research finding is a matter of degree, not a hard rule that demand-based reasons fail. If demand genuinely is the reason, stating it plainly is still better than inventing a different one.
“Because everyone else raised their rates” or comparisons to other freelancers should be avoided entirely. This reads as neither cost-justified nor demand-justified — it externalizes the decision in a way that tends to undermine confidence in the message rather than support it.
Avoid combining more than one reason, even if several are true. If both “increased demand” and “added capability” are honestly true, research on overexplaining suggests picking the one that best represents the change rather than listing both — stacking reasons reads as building a case, which is exactly the defensive posture the research finds backfires.
A worked comparison
Weaker version, avoiding the research entirely:
Hey! So I've been thinking about this for a while and I know it's not great timing, but I really need to adjust my rates a bit — sorry for the short notice, things have just been really busy and my costs have gone up and I think this reflects my experience better too. Let me know if this is a problem!
This buries the actual number, apologizes twice, stacks three separate justifications, and ends by inviting the client to treat it as negotiable — precisely the “protesting too much” pattern the research finds undermines trust rather than building it.
Stronger version, matching the research:
Hi [Client], wanted to give you advance notice that starting March 1st, my rate for landing page copywriting will be $150/hour, reflecting the added tooling and process investment I've made this year. This applies to new projects going forward — anything already scoped stays at our current rate. Let me know if you'd like to lock in any upcoming work before the change takes effect.
Same underlying message, same honesty, radically different reception — plain language, one reason, no apology, and a concrete number stated without hedging.
Timing the announcement across multiple clients
For freelancers with several active clients, there's a real choice between raising rates for everyone on the same date versus staggering it by each client's own anniversary or project cycle. Staggering has a practical advantage the research above indirectly supports: it spreads the “loss” announcement out over time rather than concentrating it, meaning no single week involves defending the same decision to five different people in a row, which can make each individual conversation feel more routine and less like a company-wide event being justified all at once. The tradeoff is administrative — staggered dates are harder to track than one clean cutover — so the right choice often comes down to how many active clients are involved and how much that tracking overhead is worth avoiding.
What to do if a client pushes back
A reasonable client asking why is different from a client demanding you reverse it. For the former, the same brief, confident answer already given is usually enough — resist the urge to add a second or third justification just because they asked, since stacking on more reasons tends to read as increasingly defensive rather than increasingly convincing. For the latter, it's worth being direct: “I understand if the new rate doesn't work for upcoming projects — happy to discuss, but the rate itself isn't something I'm able to hold at the previous level going forward.”
Related guideHow to charge for extra revisions without the awkward conversation
FAQ
How often is it reasonable to raise rates?
Annually is common for many freelancers, though it varies by how much demand and experience have shifted — the notice period matters more than the frequency.
Should I raise rates for all clients at once or stagger it?
Either works. Staggering by client anniversary date spreads out the “notice” emails; raising for everyone at once is simpler to track and explain consistently.
Is it okay to raise rates mid-project?
Generally no — honor the rate that was in place when a project was scoped, and apply the increase to new projects going forward.
What if a long-time client simply can't afford the new rate?
It's fine to offer a modified scope at the lower rate (fewer deliverables, reduced revision rounds) rather than holding the full scope at the old price indefinitely.
Should a rate increase email include a reason, or is that oversharing?
Include one brief, genuine reason rather than none at all or several. Research on price-increase communication finds unexplained increases are perceived as the most self-serving, but a long justification or an apologetic tone tends to backfire just as much — a single clear line does more good than either extreme.
A rate increase is a fact to communicate, not a case to argue — and the research backs stating it exactly that way.
PricingSee how SwiftSignoff helps track project terms clearly on the pricing page