a vp of product walks into a monday standup with one slide. "we're moving to usage-based pricing in q1." the room nods. the cfo doesn't. the cfo knows what most rooms don't — the company is about to take a 28% revenue hit before the model stabilizes, and the recovery curve depends entirely on what they decide in the next two weeks.
per-seat pricing has been the saas default for fifteen years because it's legible. customers know what they pay. usage-based is the opposite — variable, opaque to the customer, and structurally biased toward customers paying less on average. that bias is the whole problem. it's also the whole reason the transition is worth running, when it's run correctly.
losing 30% of arr in q1 isn't a pricing model mistake. it's running the conversion as a flip when it should have been a hybrid.
the question every founder asks the wrong way
the conversation always opens the same way. founder pings finance — "should we move to usage-based?" — and waits for a yes or no. the right answer is neither.
the question isn't should we? — most b2b saas companies should, eventually, because usage-based scales with customer value in a way per-seat never will. the question is how do we run the conversion without burning the runway we'd use to fund growth on the other side.
pendo's 2024 conversion is the cautionary tale every operator references — a meaningful slice of the book moved to consumption-flavored pricing inside two quarters, and public reporting showed material revenue compression before the new model anchored. the lesson isn't don't do it. the lesson is don't do it as a flip.
the math of a flip versus a hybrid
run the arithmetic on a representative account. $30 per seat times 50 seats is $1,500 a month. predictable, anchored, the customer has been paying it for two years. they know exactly what they get.
now flip to pure usage. $0.05 per api call. the customer has been making 22,000 calls a month and assumes — correctly, because that's how customers think — that pure usage means they'll pay less on average. the first invoice lands at $1,100. they're delighted. you're down 27%.
the hybrid lands differently. $750 platform fee plus $0.05 per call over a baseline. customer pays the $750 floor plus 22,000 calls at $0.05 equals $1,850. the customer accepts it because the platform fee feels like the "old" subscription and the usage line feels like fair-use overage. you're up 23%, and you've built an expansion mechanism that scales with their consumption — every additional 1,000 calls is another $50, automatically, no sales motion required.
the difference between -27% and +23% on the same customer is not pricing strategy. it's transition design.
what to keep, what to meter, what to grandfather
the platform floor is the part most founders set too low. the temptation is to make the conversion feel friendly — "new pricing is cheaper unless you really scale up" — which is a fast way to lose the customers who were already at the right consumption band. set the floor at 70-80% of current per-seat revenue for the median account. modestly cheaper for low-usage customers, modestly more expensive for high-usage ones, with the meter doing the rest.
the metered dimension should correlate with the customer's value — api calls if you're infrastructure, records processed if you're data, messages sent if you're communications. avoid metering things the customer can't control, because they'll resent paying for something they didn't choose to consume.
the grandfathering window keeps the legacy book intact while you measure the usage curve on new customers. six months is the right length. during the window, sales motions on legacy accounts position the new pricing as an opt-in upgrade with a usage projection, not a mandate.
new customers go straight to the new pricing. no choice. the hybrid is the only offer. if you let new logos pick per-seat, the new pricing never anchors.
the metric to watch through the transition
the number that decides whether the conversion is working is net dollar movement per converted account, measured at month 3 and month 6 against the per-seat baseline. for every account that converts, the calculation is the difference between what they would have paid under per-seat and what they actually paid under hybrid, including platform and metered components.
if the median converted account is at -5 to +10% at month 3, the conversion is healthy and will compound positive as usage grows. if it's at -15% or worse, the platform floor is too low and the meter unit is too cheap. the fix is mechanical — raise the floor on the next cohort of conversions, not the ones already converted.
founders who go full-usage from full-seat report -28% revenue in q1 across the published case studies. hybrid converters report flat to +12% in the same window. the flippers spend three quarters back-pricing into a healthier model. the hybrid converters compound from month one.
how zift handles this
zift ingests stripe and your billing system every fifteen minutes and reports converted-account dollar movement against the per-seat baseline at the cohort level. on monday morning the briefing names the converted accounts that moved below the -10% line and the median dollar delta across the converted book.
if you're a finance lead at a series b team running this conversion across multiple billing entities or contract types, zift handles that too.
per-seat is the model most companies start with because it's legible. usage-based is the model most will end up with because it's leveraged. the gap between the two is a transition, not a flip — and the transition is where the revenue lives or dies.