You have not touched your rate in two years. The automation retainer price increase you keep postponing is not stalled on the number. It is stalled on the conversation.
An automation retainer price increase is a formal change to the monthly fee a client pays you for maintaining and improving their automated systems, issued with advance notice and matched to the scope you actually deliver now.
Most operators handle this two ways, and both are bad. They absorb the gap quietly until the account is no longer worth keeping, or they drop a new invoice with no warning and act surprised when the client pushes back. There is a sequence that avoids both, and it works because it removes the guesswork for the person on the other side of the email.
Key takeaways
- An automation retainer price increase is a formal change to a client’s monthly maintenance fee, issued with notice and matched to current scope.
- The U.S. Bureau of Labor Statistics reported the all items Consumer Price Index rose 3.7 percent over the 12 months ending September 2026, so a retainer held flat for two years has already lost purchasing power.
- Platform costs move independently of your rate. A Microsoft Copilot Studio credit pack lists at $200 per month for 25,000 Copilot Credits, and an Azure subscription is required to run agents.
- The RAISE Brief is a five step sequence: Record the drift, Anchor to outcomes, Issue the notice early, Set the new scope, Exit path offered.
- Give at least 60 days of notice on a monthly retainer. Notice is what separates a price change from an ultimatum.
- Present a lower tier next to the new price. A client who has a choice rarely walks.
Why your automation retainer price increase is already late
Two things move while your rate sits still. Your scope grows, and your costs grow.
Scope growth is the one you feel. You signed on to maintain three workflows. You now maintain seven, field the Monday morning questions, and get pulled in every time a vendor changes an endpoint. That drift is the subject of its own problem, and if you have not read it yet, start with how AI automation scope creep quietly eats the margin you thought you had.
Cost growth is the one you ignore. The Bureau of Labor Statistics reported on October 14, 2026, that the all items Consumer Price Index for All Urban Consumers rose 3.7 percent over the 12 months ending September 2026, with the core index excluding food and energy up 2.6 percent. Hold a price flat across two of those years and you have taken a pay cut you never agreed to.
Then there is the platform bill. Agent tooling is metered now, not flat. Microsoft lists a Copilot Studio credit pack at $200 per month for 25,000 Copilot Credits and requires an Azure subscription to run agents at all. When a client’s usage doubles, your delivery cost doubles with it while your invoice does not. If you have never measured that, the AI agent cost per run is the number to get before you quote anybody anything.
Here is the part nobody says out loud. In the Army, as a 25U Signal Support Systems Specialist, you execute with the equipment you were issued. You do not stop mid mission to renegotiate the terms. That instinct makes you excellent at delivery and terrible at pricing, because the civilian version of that discipline is just slow self funded charity.
The RAISE Brief: five steps to a price change that holds
Treat this like any other change order. Documented, scheduled, and boring. The RAISE Brief runs in five steps, in order.
R: Record the drift
Open the original agreement and write two columns. Left column is what you contracted to do. Right column is what you did last month.
Be specific. Count the workflows, the integrations, the support requests, and the hours. This document is not for the client yet. It is for you, so the new number stops feeling like a guess.
A: Anchor to outcomes
A price increase argued from your costs is a request. A price increase argued from their results is a correction.
Pull the numbers you already report. If you are running a monthly cadence, you have them: runs completed, failures caught, cycle time, dollars that did not get spent. This is why the AI agent monthly report earns its keep twice, once at renewal and again the day you raise the rate. And when you translate those numbers into money, do it honestly, because AI automation ROI built on hours saved is the weakest case you can make.
I: Issue the notice early
Sixty days minimum on a monthly retainer. Ninety if the client runs an annual budget cycle and you know when it closes.
Notice is the entire difference between a price change and an ultimatum. A client who hears about it in October for a January effective date has time to plan, approve, and tell their own boss. A client who finds out on the invoice has been ambushed, and they will remember that longer than they remember the number.
Put it in writing, in one email, with the effective date in the subject line. Then offer a call. Do not open with the call.
S: Set the new scope
A higher price for the same vague agreement teaches the client that your rate floats. Attach the new number to a written scope that names what is included, what is billed separately, and what the response time is.
This is also your chance to fix the original mistake. If the first contract never specified a support window, specify one now. The increase buys you the right to define the work, so define it. If you are rebuilding the scope from scratch, the groundwork in how to price AI automation services is the place to start.
E: Exit path offered
Give them a smaller option. Not a discount on the new tier, a genuinely narrower scope at close to the old price.
Two things happen when you do this. The client stops feeling cornered, which kills most of the resistance. And if they take the smaller tier, you keep the relationship while handing back the work that was unprofitable anyway. Either answer is a win. That is the point of offering it.
Example scenario: the retainer that drifted
Example scenario, constructed to show the mechanics and not drawn from a specific client.
You signed a $1,200 per month retainer in late 2024 to maintain three lead routing workflows. Today you maintain seven, you answer Slack questions most mornings, and the agent volume has roughly tripled since launch.
You run the brief. Record shows three workflows contracted against seven delivered plus unscoped support. Anchor shows the routing system handled 4,100 inbound leads last month with a 2 percent failure rate, which you report every month already. Issue goes out October 15 for a January 1 effective date, 78 days of notice. Set lists seven workflows, a four hour response window on business days, and anything new quoted as a change order. Exit offers a three workflow tier at $1,300 with no support window.
Your new number is not a feeling at that point. It is the arithmetic of a document the client can read in ninety seconds.
Your action steps this week
- Pick your single most drifted account. Not all of them. One.
- Build the two column drift record from the original agreement and last month’s actual work.
- Pull three outcome numbers you can already prove from your own reporting.
- Write the new scope first and the new price second. In that order, every time.
- Draft the smaller tier before you send anything, so the exit path exists when they ask for it.
- Send the notice with an effective date at least 60 days out.
Then run the same brief on the next account next month. One at a time is a system. All at once is a crisis.
Frequently asked questions
How much should I raise an automation retainer?
Price the scope you actually deliver now, then compare that figure to your current rate. The gap is your increase, and it is usually larger than an inflation adjustment because scope drift compounds faster than prices do. Inflation sets the floor, not the target: with the all items CPI up 3.7 percent over the 12 months ending September 2026, a 3 percent bump on a two year old rate leaves you behind.
How much notice should I give before raising the price?
Sixty days on a month to month retainer, and 90 days if the client budgets annually. Check your contract first, because many retainer agreements specify a notice period and that clause governs.
What do I do if the client says no?
Move them to the smaller tier you already prepared. A no to the new price is almost never a no to working with you, it is a no to the new price at the current scope, and the narrower tier answers exactly that.
Should I raise prices on all my clients at once?
No. Run one account at a time so a bad reaction costs you one conversation instead of your whole book. Sequencing also lets you improve the brief between accounts, which you will.
Do I have to explain my platform costs to the client?
You can name them, but do not lead with them. Clients do not buy your cost structure, they buy an outcome, so costs belong in the second paragraph of the notice at most. One line is enough: metered agent platforms bill by usage, and their usage went up.
Recap
An automation retainer price increase fails for one of two reasons. Either there was no notice, or there was no documented scope behind the number.
The RAISE Brief fixes both. Record the drift so you know what changed. Anchor to outcomes so the client sees their own results, not your costs. Issue the notice early so nobody is ambushed. Set the new scope so the rate stops floating. Offer an exit path so the answer is a choice instead of a loss.
Your rate is infrastructure. It should be reviewed on a schedule, the same way you review a failing workflow, and not left to run until it breaks.
Subscribe to the blog and the next one lands in your inbox tomorrow.
References
Microsoft. (2026). Microsoft Copilot Studio pricing. https://www.microsoft.com/en-us/microsoft-copilot/microsoft-copilot-studio
U.S. Bureau of Labor Statistics. (2026, October 14). Consumer Price Index: September 2026 (USDL-26-1574). https://www.bls.gov/news.release/cpi.htm
Leave a Reply