Direct answer
The old rate bought the work it was agreed for. It did not buy your future at a frozen price.
You have raised your rates, fairly and across the board, and your longest standing client is pushing back: we have always paid the old number, so the old number should stand. Loyalty is being used as a lock, and it can feel rude to argue with it. The honest answer splits the work, not the relationship. Work already agreed at the old rate keeps the old rate, in full, because that was the deal. Work not yet agreed is new business, priced at the rate that stands when it is booked, after fair written notice. This page walks that split, the notice that makes it clean, the answers to the loyalty argument that keep goodwill intact, and the doors you can offer a client whose budget truly cannot move, none of which is quietly staying at the old rate forever.
Updated November 14, 2026. First published November 14, 2026. The records quoted below are real and public, read back from the live service on November 14, 2026.
Step 1. Split the work into agreed and not yet agreed, because the two piles have different rules
Pile one is work already booked at the old rate: the signed project, the confirmed dates, the retainer period already running. That pile keeps the old rate to its end, without resentment and without trying to reopen it. You sold that work at that price, and being seen to honour an agreed number completely is what makes your new number believable. Pile two is everything else: the next project, the renewal, the extra work they are assuming will slot in at the familiar figure. Pile two was never priced, so there is no old deal to break; there is only a new booking to make at the current rate. Most rate fights go wrong by mixing the piles: the client defends pile two as if it were pile one, and you start defending the rise as if you were repricing finished agreements. Name the split out loud, early, in one sentence: everything booked stands as booked, and work booked from the notice date forward is at the new rate. That sentence is fair in a way clients can feel, and it removes their strongest argument before it is made.
Step 2. Give written notice with an effective date, before the next booking, not on its invoice
A rate rise announced on an invoice is a surprise, and surprises get fought on principle. A rate rise announced in writing, with an effective date comfortably ahead, is business. The notice needs four things: the new rate as a number, the date it applies from, the confirmation that booked work is untouched, and the reason in one plain line if you want to give one, costs, demand, the rate everyone else now pays. Keep the reason short and factual; a justification that runs long reads as negotiable, while a brief notice reads as a fact of your practice. Send it before the next job is discussed, not attached to a quote for work the client already expects at the old figure. And send it to every existing client in the same terms. A rise that applies to everyone is a policy; a rise that appears for one client at a time feels like a test of what each will tolerate, and clients compare notes more often than you would like.
Step 3. Keep each booking on its own record, so the rate for a job is never reconstructed later
Rate arguments a year later are memory arguments: which jobs were quoted when, at which figure, agreed in which message. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the per job structure that keeps a booking self describing:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the structure for what it gives this problem: a job as a discrete item, its steps checked, one dated decision by the client over it. Your bookings want the same shape in miniature: each job or stage agreed at a stated rate on a stated date, accepted before it runs, so any later question about which rate governed a piece of work is answered by its own record rather than by archaeology through a chat thread. The pending record is the warning case for renewals: work sitting undecided while a rate notice takes effect is exactly where old and new figures blur. Decide the booking, at a stated rate, before the work starts, and the boundary polices itself.
Step 4. Answer the loyalty argument fairly, and offer doors that are not a discount
The loyalty claim deserves a real answer, not a shrug: long standing clients did help build your practice, and the honest recognition is already built into the split, their booked work kept its price and their notice came early. What loyalty cannot honestly mean is a permanent freeze, because that converts a relationship into a claim on every future year of your pricing, growing more expensive to you with every rise everyone else accepts. If their budget genuinely cannot reach the new rate, offer doors that respect both sides. Door one: a smaller scope at the new rate that fits the budget, with the cut items named. Door two: scheduling flexibility, work booked into your quieter periods, if and only if you choose to price that, openly, as its own term. Door three: a clean, warm handover to someone cheaper, with your records in good order. A client offered real doors rarely feels punished. What poisons the relationship is the fourth thing, the quiet permanent exception, which you will resent on every job and they will defend as the new normal.
Step 5. Put the rate and a review date in the next agreement
The lasting fix is one clause: work is priced at the rate stated for that booking, rates are reviewed on a named cycle, and a changed rate applies to bookings made after the notice date, never to work already agreed. The review date matters as much as the rate. It tells the client rises are a rhythm of your practice, not a surprise aimed at them, and it tells future you exactly when the next conversation is due, so small regular rises replace the one large rise that triggers a fight. Pair the clause with the booking habit from step 3: every job or stage confirmed in writing at its rate before it starts. With those two in place, the old rate argument cannot recur, because the question which rate applies is answered by paper both sides already hold, and the only remaining conversation is the healthy one about scope and timing.
What this page cannot settle
This page cannot override a contract that genuinely promises a fixed rate for a stated period; if you signed a rate lock, it runs to its end, and this is general information, not legal advice. It also cannot make a long standing client stay: some will leave over any rise, and a client who only values you at a price your practice has outgrown is a cost calculation, not a verdict on your work. A verifiable receipt proves the saved result was not changed since it was saved; it does not set your rate or prove a rise was fair. What the record settles is the factual floor: which work was booked, when, and at the figure both sides accepted at the time.
Frequently asked questions
I raised my rates but my old client says the old rate should still apply. What do I do?
Split the work and honour both halves of the split visibly. Work already booked at the old rate keeps it to the end, because that was the deal, and keeping it without complaint is what makes your position credible. Everything not yet booked is new business: give written notice of the new rate with an effective date, before the next booking is discussed and never first on an invoice, and confirm in the same notice that booked work is untouched. The old rate governed the jobs it was agreed for; it was never a promise about every future job, and a client relationship, however long, does not freeze a price forever. If their budget cannot move, offer scope doors at the new rate, a smaller named scope, scheduling terms you choose openly, or a warm handover, rather than a quiet permanent exception you will resent on every job. Then put the rate and a review date in the next agreement, so the question answers itself from then on.
Do I have to honour the old rate on a retainer that just keeps rolling?
A retainer runs in periods, and each new period is a new booking unless your agreement says otherwise. Honour the old rate to the end of the period already agreed and paid for, then give notice that the next period is at the new rate, with enough lead time for the client to plan or to decline. The trap is the silent roll: work that continues week to week with no period boundary, where no one ever quite books anything and the old figure hardens into an assumption. Break it deliberately and kindly: name the current period's end date, state the new rate for the period after, and get the renewal confirmed in writing at that rate before it starts. If the client declines, the retainer ends at the boundary you both can see, which is a cleaner outcome for the relationship than a rise discovered on a routine invoice.
How much notice should I give before a rate rise applies?
Enough that no client meets the new rate for the first time on work they already counted as booked: for most freelance practices that means a full booking cycle, commonly a month or a quarter, stated as a plain effective date. The quality that matters is not the exact length, it is the sequence: notice first, bookings after. A client who hears the new figure while planning next quarter's work can budget for it, trim scope, or shop around with no grievance. A client who hears it attached to a job they believed was already agreed hears something else entirely, whatever your intention. If a job is mid discussion when notice lands, the courteous line is to price that one job in writing, at one stated rate, and let the notice govern everything booked after it.
Will raising rates on old clients cost me the relationship?
It can cost you a client whose whole case for using you was the old price, and that loss is information, not failure: at the old figure the relationship was already costing your practice money on every job. Most long standing clients, handled with the split and fair notice, stay, because what they actually value is the work and the reliability, and because being told early and honestly compares well with how most suppliers treat them. The relationships a rise genuinely endangers are the ones handled by surprise or by exception: invoiced without notice, the client feels ambushed; quietly exempted forever, you feel trapped. Notice, a clean split, and real doors on scope are the handling that keeps both the client and the rate, in the large majority of cases where keeping both is possible at all.
How does a job record help when a client disputes which rate applied?
It keeps each booking's terms attached to the booking itself. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, the client accepts on that record, and the acceptance view shows status, decider, date, and release state, so which work was agreed, and when, is checkable at a link when a rate notice has taken effect between one job and the next. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next booking for an old client on one record with its rate stated at the start, so the old rate argument never has to be reconstructed from chat again: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- My client wants a lower rate now in exchange for more work later. Should I take it?
- My client says their budget was cut and wants to pay less than we agreed. What do I do?
- My client wants a discount after the work is done. What do I do?
- My client won't pay me. What do I do?
- My client promised me a bonus if I finish early. How do I make sure I actually get it?
- My client wants to own my tools and templates as well as the final work. Should I agree?
- Start with your problem: every problem in this directory, routed to its page