every saas founder has a moment around the eighteen-month mark when they realize the pricing they set at launch is meaningfully below market. they look at the customer base, do mental math on a 12% lift, and close the tab. they tell themselves next quarter, after the next release, after the contract cycle stabilizes.
two years later, they're still telling themselves that. the customers they were trying not to scare off have either churned for unrelated reasons or signed a 3-year deal at the old rate. they're running a $2m arr business that should have been $2.5m arr. the gap doesn't widen — it compounds.
the price increase letter is the highest-roi email a saas founder will send in any given year. the cost of not sending it isn't foregone revenue. it's the implicit signal that pricing isn't a lever anyone is allowed to pull.
what the math actually looks like
start with a $2m arr book and a planned 12% price increase, grandfathered for legacy customers for six months, applied immediately to new contracts. expected logo churn from the increase — the published openview benchmarks land it at 2-3% on b2b, with the higher end on smb-heavy books and the lower end on enterprise.
the year one math is straightforward — $2m times 12% is $240k of gross lift, minus 3% incremental churn at $60k, nets to $180k. but year one isn't where the lever pays off. year two the new pricing anchors the renewal base and the lift extends to $240k. year three the gap between the company that raised and the company that didn't is more than half a million in cumulative revenue, plus the valuation multiple lift from running an arr base with demonstrated pricing power.
openview's 2024 pricing study found that companies which increased prices annually had 25% higher five-year arr than companies that never did, controlling for growth rate and segment. the increase isn't an event. it's a discipline.
why founders avoid it
every founder who hasn't raised prices recites the same objections, usually in sequence.
the first is the customer will be angry. the founder imagines a representative customer reading the email, getting offended, and writing the angry cancellation. in reality, the customer reads it, sighs, forwards it to procurement, and procurement adds it to the queue. the angry-customer email arrives in maybe 1 in 50 cases — usually a customer who was already churning for unrelated reasons.
the second is we haven't earned it. by the time pricing is meaningfully below market, the product has accumulated two years of features the original price never accounted for. the customer is already getting more than they paid for. the letter is correcting that, not extracting rent.
the third is we should wait until the next release. there is always a next release. founders who run pricing as a discipline schedule the letter on an annual cadence and let the release cycle work around it, not the other way around.
the canonical letter structure
the letter has four moves and one rule. the rule is that it comes from the founder — not from billing, not from a "team@" alias, not from a customer success manager. if it looks like an automated billing notice, the customer reads it as a billing problem. if it looks like a personal note from the person who built the company, the customer reads it as a business decision.
the first move is the lead — "as of [date], our pricing is increasing by [%] for new contracts." clear, dated, no apology. burying the lead in two paragraphs of context invites the customer to skim and miss the action.
the second move is the grandfathering. legacy annual customers keep current pricing through their next renewal. legacy monthly customers keep it for six months from announcement. this is the move that prevents the angry email — customers feel they got a fair window to react.
the third move is the "why now." one paragraph. specific. "in the last 18 months we shipped [named features], hired [named team], reached [named milestone] — the pricing is catching up to the product." not a list of generic improvements. one specific paragraph that earns the increase.
the fourth move is the personal note for the top 20% of arr — "i wanted you to hear this from me, not from billing." a short direct email from the founder, sent before the bulk announcement, to the named accounts driving the renewal book. takes a saturday morning. moves the needle on retention by orders of magnitude on the accounts that matter most.
the timing window
sixty days notice is the standard. less feels rushed, more gives procurement time to negotiate. letter goes out in week one, new pricing applies to new contracts in week nine, legacy monthly customers convert in week twenty-six, legacy annual customers convert on their renewal date.
the timing matters because it gives the renewals team time to have the "here's how the new pricing affects you" conversation with every top-20 account before procurement raises the question. founders who skip that coordination discover the angry-customer rate is 10x higher than it should be — because customers heard about it from billing before they heard about it from their account owner.
how zift handles this
zift tracks pricing-event arr lift against the published cohort before, during, and after a price increase, and surfaces the named accounts whose payment behavior shifted in the 30 days following the letter. on monday morning the briefing names the renewals that moved off the original pricing tier and the dollar impact across the converted book.
if you're a finance lead at a series b team running price increases across multiple plans, regions, or entity structures, zift handles that too.
the price increase letter is the email founders write last and should have written first. the cost of not sending it isn't measured in foregone revenue. it's measured in the company that gets built around the assumption that pricing is fixed.