Raising prices in Service Autopilot without a cancel wave

A well-run price increase costs you one to three points of extra cancels. A botched one costs three times that, and the difference is almost never the number. It's the cadence, the segmentation, and the communication. Here's how to run an increase through Service Autopilot so the announcement lands like a professional notice instead of a surprise on an invoice.

How much churn should you actually expect?

Plan for a bump, not a wave. Operators commonly report ranges like these (illustrative, your service quality and market set the ceiling):

Increase size	Communicated well	Discovered on the invoice
3–5%	~0.5–1.5% extra cancels	2–4%
6–9%	~1–3% extra cancels	4–8%
10%+ (targeted accounts)	~3–6% extra cancels	8–15%

Now the math that makes the fear look silly. Say 1,200 recurring clients averaging $700/season. A 6% increase adds roughly $50,400 of annual revenue. If it costs you 2% extra cancels (24 clients at $742) that's about $17,800 lost. You're up $32,600, your routes get lighter, and the clients who left were disproportionately your price-shoppers. The increase pays even at double the expected churn. (Full pricing framework in our pricing strategy guide.)

When should you announce, and in what order?

Give 30–60 days of notice, timed to your off-season or renewal window: never mid-service, never mid-contract. A cadence that works:

• Day −45: the letter (or primary email). The real announcement: new rate, effective date, why, and what they get.
• Day −21: reminder email. Shorter, links back to the details, invites questions to a real person.
• Day −7: text. Two sentences: the date and where to read more.
• Day 0: it just happens. The first invoice at the new rate should surprise no one.

Every touch in that sequence can be built once in automations and fired off a tag, which matters because you won't send one version. You'll send three.

Which customers should get which increase?

The lazy increase is a flat percentage on everyone. The smart one is segmented by margin, and Service Autopilot already holds the data: rates, services, visit history, and route assignment. Three buckets cover most companies:

• Below-card accounts (biggest correction). Clients whose rate drifted under your current rate card, often your oldest accounts. They get a correction toward card, even if it's 10%+, with the most careful letter.
• Mid-pack (standard increase). The bulk of the base. Standard percentage, standard letter.
• A-clients (modest increase + thank-you). High-margin, on-route, full-program clients. Smaller bump, warmer letter, maybe a loyalty perk. These are the clients your competitors would love; treat the letter accordingly.

Tag each bucket in Service Autopilot, and the whole rollout (letters, reminders, texts, save-call tasks) runs off three tags. While you're in there, techs' condition notes often reveal underpriced properties the rate data misses: the 8,000 sq ft lawn billed as 5,000 since 2019.

What should the letter actually say?

Four parts, one page, no groveling:

1. The change, plainly. "Beginning March 1, your per-visit rate moves from $52 to $55." Exact numbers: vagueness reads as hiding something.
2. One honest reason. Labor, materials, insurance: pick the true one. Skip the three-paragraph economics lecture.
3. The value recap. Specific things they got this year: visits completed, issues caught, response times. Synced visit data makes this a mail-merge field, not a writing project.
4. A human to talk to. A name and a direct way to reach them. Questions routed to a person don't become cancellations posted to Facebook.

What to leave out: apologies ("we hate to do this"), blame, and any sentence that invites negotiation. You're informing, not asking permission.

Where does grandfathering go wrong?

Grandfathering feels generous and compounds like a debt. The traps, in the order companies fall into them: permanent grandfathering means your longest routes (often your most expensive to serve) become your least profitable forever. Forgotten legacy rates pile up until "one more year at the old rate" becomes forty accounts nobody can explain. And secret selective grandfathering eventually gets discussed over a fence between neighbors, which costs more goodwill than the increase ever would. If you want to reward tenure, do it with an expiration ("your rate holds through this season") or convert it into a visible perk (a free add-on visit, priority scheduling) that doesn't silently reprice your book every year.

How do you handle the cancel calls?

Expect them, route them, script them. A tag-triggered task queue puts every price-mention call in front of your best save person with the account's margin bucket on screen. The save script: acknowledge, restate value specifically, and offer one fallback: a smaller package at their old budget, not a quiet discount on the same package. Discounting on demand teaches your base that threatening to cancel is an annual coupon. A smaller package keeps the client, keeps the rate card honest, and keeps the route. The same retention machinery you should already be running (churn automations) does double duty here.

Who shouldn't raise prices right now?

Honesty check: if your review trend is falling, your visits are behind schedule, or you just had a rough service season, fix that first: an increase on top of shaky service is how real cancel waves start. Same if you're mid-contract on commercial work (wait for renewal) or mid-season on prepaid residential programs (the increase lands with next season's renewal, ideally alongside the pre-pay offer). Raising prices is a confidence move. Earn it, then make it.

Questions owners ask us

How much churn does an increase actually cause?

Commonly one to three extra points on a well-communicated 4–7% increase; roughly triple that when customers find out from the invoice. Illustrative ranges, your service quality sets the ceiling.

When should we announce?

30–60 days out, in the off-season or at renewal. Letter at −45, email at −21, text at −7. Nobody learns from the invoice.

Same increase for everyone?

No, segment by margin. Below-card accounts get the correction, mid-pack gets the standard bump, A-clients get a modest one with a thank-you.

Is grandfathering a good idea?

Only with an expiration date. Permanent grandfathering compounds into your oldest routes becoming your least profitable.

What about customers who call to cancel?

Route them to a save flow with one fallback: a smaller package at the old budget, never a secret discount on the same package.

The takeaway: the number matters less than the notice. Segment by margin, announce 45 days out in three touches, write a plain one-page letter, grandfather only with an expiry, and let the math, not the fear, make the decision.

Run the increase

1. Pull rates vs. your current rate card and tag three buckets: below-card, mid-pack, A-client.
2. Do the math on paper first: added revenue vs. expected cancels at double your worst guess.
3. Write three letters, one per bucket, and load the −45/−21/−7 sequence into automations.
4. Build the save-call task queue and script before the first letter mails.
5. Set an annual review date: small yearly increases beat traumatic five-year corrections.