A plan that books a price increase across the whole book from the day it is announced will report a shortfall even if every customer accepts it. On annual contracts repriced at renewal, the increase arrives one renewal at a time, starting with the first renewal the notice period allows.
Suppose $20 million of annual contracts renews in equal monthly cohorts on the first of each month, with revenue recognized evenly over each contract year, and assume no discounts, quantity changes or churn. Notice of a 7 percent increase goes out on January 1, and the contracts require 45 days’ notice before a new price applies at renewal. The January and February cohorts renew at the old price for another year. March carries the new price for ten months of the year, April for nine, December for one. Revenue in the calendar year of the notice picks up about $535,000, roughly 38 percent of the $1.4 million that a plan repricing the whole book on January 1 would show, and monthly revenue carries the full increase only from February 1 of the next year, 13 months after the notice. The $865,000 gap against that plan is timing alone.
Real books depart from the illustration’s even spread in two ways that ChartMogul’s billing report makes visible. The report draws on 2024 billing data from more than 2,500 SaaS companies that use ChartMogul; it is observational and says nothing about price changes, so I use it only for how books are shaped. Among companies that offer both monthly and annual plans, the median share of ARR billed annually was 47 percent at $3 million to $8 million of ARR and 28 percent at $15 million to $30 million. Monthly plans can carry a new price once the notice runs out, so the mix alone changes how fast an increase shows up.
The same data show the first quarter as the strongest for winning customers, which the report links to budgets that open or expire at fiscal year boundaries. If a company’s annual contracts were mostly signed in January and February and keep those anniversaries, a January 1 notice misses the months in which most of its contract value renews. That step is my inference: the report measures new business, not renewal dates.
Revenue cannot tell a board in the first year whether customers accepted the increase, because the calendar explains most of the shortfall. Renewal cohorts can, starting with the first one the notice reaches: how many contracts came due, how many renewed at the new price, how many renewed at a negotiated price below it, and how many left, each with its contract value.
The negotiated group is the easiest to lose. ChartMogul’s report counted only discounts shown against a base plan, because some companies write the concession into a custom price for each customer. The same blind spot applies here: a board pack that looks for the increase in a discount field will miss concessions written into a custom price, while comparing each renewal’s new price with its old price plus the announced 7 percent catches them.
Cohort counts have a weakness of their own: they cannot prove acceptance any better than revenue can. A customer who leaves at the first renewal after an increase might have left at the old price, and a company’s own renewals come with no control group. The counts are still the earliest reading available, and the same renewal months a year earlier give a rough baseline for how many contracts usually leave or negotiate. The difference from that baseline is a reading of acceptance; it says nothing about what the increase caused.
I would build the plan by renewal month with the notice period counted, and put the four counts and their contract values in the monthly board pack beside revenue, starting with the first cohort the notice reaches. If the next pricing review falls before the book has fully repriced, those counts are the evidence it will have.