HIVE80lab — Ops notes

Price Increase Announcement Template for Small Businesses

Raising prices is the highest-leverage decision most small businesses avoid for two years too long. Costs went up; the product got better; you are still charging 2022 prices because a price increase feels like asking friends for money. It is not. It is an operating decision with math on one side and a communication plan on the other — and the communication plan is the easy half.

1. Decide with math before writing a word

A raise is justified by numbers, not feelings, so write the numbers down first. Margin math: what does the current price actually cost you to deliver — support hours, payment fees, the FX spread you found at the month-end close? If gross margin is under 60% on a service or under 40% on software, the raise is a survival step, not a nice-to-have. Churn math: the raise wins if (new price × customers after churn) > (old price × customers today). A 10% raise survives even if it costs you 8% of customers; almost never does. What it funds: name it — better support hours, the second payment processor, salaries. "What it funds" is the honest core of the announcement email, and vague raises are the ones that leak goodwill. Record the decision and its numbers in the decision log so the version of you in twelve months knows why.

2. The grandfathering decision — make it once, write it down

Grandfathering (old customers keep the old price) is generous once and a ledger of resentment forever — two tiers of customers, two price lists, and a support macro nobody enjoys sending. Pick one rule and stick to it: either everyone moves (simplest books, the default), or annual terms are honored until renewal (a promise you can actually keep: nobody's mid-term price changes, and renewal is the natural reprice point). "Legacy pricing forever" is not a rule, it is an unpaid debt. Whatever you pick, it goes in the announcement in one sentence, because customers respect a stated rule more than a discount they had to ask for.

3. The 30-day clock — notice beats surprise

The surprise invoice is the only unforgivable version of a price increase. The mechanics: 30 days minimum notice for monthly plans, one billing cycle for annual ones (nobody's price changes mid-term — that is the grandfathering rule above doing real work). Time the announcement so it lands after the current cycle's charge and before the next one: an email on the 2nd of the month for a price that takes effect on the next renewal after the 30-day mark. Invoice footers and the customer portal get the same note the day the email goes out — the announcement must be findable by someone who missed the email, not just delivered once. One date, one number, everywhere.

4. The announcement email — four paragraphs, under 200 words

The template (edit the brackets):

Subject: A price update, and what it pays for

Hi [name], starting [date], [product] moves from [$old] to [$new] [per month] for new and existing customers on their next renewal. This is the first price change in [N years].

Here is what changed since then: [one or two concrete things — support hours doubled, the new export system, two years of features]. The increase funds [named thing], and keeps us a company you can rely on next year.

Your price changes on [renewal date]. Your plan, your data, and your terms otherwise don't move — annual customers keep current pricing until their renewal, exactly as promised.

If this doesn't work for you, reply to this email — a human reads it. We'd rather find an option than lose you.

What is deliberately absent: apologies, justifications-by-inflation-essay, exclamation marks, and a countdown-timer desperation discount. The customer's takeaway should be "a real company made a decision and told me like an adult." One raise email drafted in the passive voice, "prices have increased," reads like it happened to you; write it in the active voice — "we are raising" — because a company that owns its decision is a company customers trust with the next one.

5. One message, three surfaces

The email is surface one. Surface two is the invoice footer and billing portal — the same sentence with the same date, so the customer who pays without reading email is never surprised. Surface three is your support reply macros, written before the announcement goes out: the acknowledgment macro, the "here's what the new price funds" macro, the cancellation-respect macro (no retention dark patterns; a resentful customer costs more than a lost one), and the save macro below. If you have a status page or a public changelog, the raise goes there too — public pricing changes filed like release notes read as confidence, not stealth. Three surfaces, one message, zero versions of the truth.

6. The reply playbook — four kinds of pushback

Negotiators ("can you do better on price?") get options, not discounts: an annual plan at the old-equivalent rate, a lower tier, a seat trim. A one-off discount that becomes the new base price is a raise in reverse — only grant it with a decision-log line and an expiry date. Cancel threats get one honest save offer, once: the annual at current pricing, or a two-month grace at the old price for a customer you can't afford to lose — then you let them go with grace, because the save is not worth the precedent. Silent downgrades (customers who quietly drop a tier) are data, not betrayal: log them, and if more than a handful happen, the raise may be landing above your value — that is measurement, not panic. The angry email gets a human reply with no template language: acknowledge, don't argue the math, and state the door is open. Two sentences is a professional reply; two paragraphs is a debate you will not win.

7. Measure the 30 days — then stop watching

Churn happens in the thirty days after the effective date; measure that window against your baseline (your last three normal months) and write the number down. Two traps: panic rollback — reversing a price because week one was loud. Loud is not churned; the angry are the most likely to stay and the quietest cancellations are the expensive ones. A rollback is a second price change six weeks after the first, which teaches customers to fight every future one. Roll back only for a factual error (you charged someone mid-term against your stated rule — fix that instantly, individually, and in writing). The second trap is forever watching: after the 30-day cohort read, file it in the close notes and move on. The decision you revisit monthly is a decision you never finished making.

A worked example: $29 to $34, 30 days, two saves

A four-person software team on $29/month for two years runs the math at the March close: support costs are up 40%, gross margin is 61%, and the raise to $34 funds named support hours. They grandfather annual terms until renewal, email on the 2nd (under 200 words, active voice), add the invoice footer, and pre-write four support macros. The month the raise lands: churn is 11% versus a 6% baseline — higher, and survivable: net revenue is still +23% after the churn. The reply playbook handles 9 negotiators (three convert to annual, which was the goal), 1 cancel threat (the honest save offer works — the flow behind it is the cancellation flow with save offers), and 1 genuinely angry customer (a two-sentence human reply; they leave, they recommend you anyway two months later). Total lost revenue from churn: $174/month. Total gained: $680/month. The team's only regret, in the decision log: "we waited 22 months."

Related pages

  • Retainer Renewal Checklist — the natural surface for a raise: the term boundary carries the increase with 60 days of notice and two price/scope options on the paperwork, instead of an ambush at signature.

    • A price held too long is a subsidy paid out of your own margin. Decide with math, pick one grandfathering rule, give 30 honest days of notice, say what the money funds in under 200 words, run the reply playbook with options instead of discounts, and measure one 30-day window — then stop watching. Small businesses that raise prices like adults keep the customers who were buying the work, not the bargain.

    Before you announce the new price, close the quotes already on the table at the old one — the quote follow-up sequence turns the open files into signatures before the changeover date arrives. If the growth is one client's scope rather than the market's prices, the change order & scope-creep checklist bills the extras line-by-line instead of repricing the whole relationship.

    This playbook is part of the Hive80 Lab ops kit line — field-tested, instantly downloadable: