Reprice to De-risk: We Raised the Price and Won More
We raised price, won more, and closed faster, because the risk was never the price. It was a per-seat model that bet revenue on the customer's headcount.
Forwarded to you? I am Heath. I build go-to-market systems and put AI to work in sales, the right way, then I write down exactly what I built, what broke, and what it moved. One story per week, receipts only. This one is about the pricing model that was quietly betting on your customers' headcount.
| 1 | Per-seat looks stable until it isn't. When revenue is a function of seat count, every contraction at a customer is a contraction in your revenue. One lever, and it points down. |
| 2 | Half the active base never paid. Nearly half of active users sat on the free plan, using the product every week, living free forever. |
| 3 | The fix was the model, not the paywall. Chasing free users into a wall does not hold. We repriced to value first, and the conversion followed. |
| 4 | Repricing raised the deal. Average deal size climbed 30% after the repackage, and the PLG motion cut unmonetized active users from over 40% to under 15%. |
The reflex: raise the price and brace for fewer deals
Every operator staring at soft revenue reaches for the same lever. Raise the price. And they brace for the tradeoff everyone accepts as physics: raise price, win fewer deals, close them slower. The whole conversation lives inside the number.
I ran a version of that thinking. At a company I was at, the commercial business leaned on a pure per-seat license model. That sounds stable until you see what it exposes you to. When revenue is a function of seat count, every contraction at a customer is a contraction in your revenue, with no other lever. A team shrinks, your ARR shrinks with it. You are not pricing the value, you are renting chairs. And underneath it, nearly half our active users sat on the free plan, using the product every week, never paying.
The block was never the price. It was the model. The number could go up or down and it would not change the fact that revenue was bolted to headcount and half the base had no reason to convert. Tuning the price on that model is rearranging furniture on a fault line.
The AE feels this as "the deal shrinks on the next reorg." The CSM feels it as "the renewal drops the moment the team drops." The marketer feels it as "the plan is priced by the count." Same model every time: charge for the seats, not the thing the seats were supposed to proxy.
The reframe: reprice to de-risk, price the value not the chairs
A per-seat license is not a pricing model. It is a bet on your customer's org chart. The move is not to raise the number and hope. It is to take the loud, comfortable metric and drill down to the quiet thing it was hiding: your revenue was never yours to grow.
If your revenue moves one-for-one with your customers' seat counts, you do not have a pricing model, you have a beta on their headcount.
Same move, other seats. An AE discounts the per-seat number to win the deal, then watches the account contract on the next reorg with nothing to hold it. A CSM renews a contract that shrinks the instant the team shrinks, with no other lever to pull. A marketer prices the plan by seats on the page and packages the product as a row of chairs instead of the value it delivers. The comfortable metric is never the thing you should be charging for. The value underneath it is.
How the best teams frame it
I am not the first person to argue that seats are the wrong meter. The operators who have run pricing at scale mostly agree on where the leverage is, and it is not the number on the page. It is what the number is attached to.
SOURCE
Kyle Poyar / OpenView, "Usage-Based Pricing: The Next Evolution in Software Pricing"
What it argues. Usage-based pricing, done right, is value-based pricing: the meter matches how the customer actually extracts value. Companies that make the shift grow faster and retain better, because revenue expands with adoption instead of headcount.
My take. Agree, with a caveat. The point is not the meter itself. It is untying revenue from seat count. Value can be metered a dozen ways. The move is refusing to let a customer's org chart be the ceiling on your growth.
SOURCE
Elena Verna, "The DNA of a Great Pricing Page"
What it argues. The pricing page is where monetization lives or dies. The free-to-paid boundary has to make the moment to pay obvious and tied to value the user already feels, not an arbitrary wall dropped in front of them.
My take. Extend. The boundary is downstream of the model. We redesigned the free-to-paid line, but only after we fixed what we were charging for. A great pricing page on a seat model is still pricing chairs beautifully.
SOURCE
Ant Murphy, "5 Different PLG Pricing and Monetization Strategies"
What it argues. There is no single PLG pricing model. The strategies split on what you meter and when you gate, and picking the wrong value metric quietly caps expansion no matter how good the funnel looks on top of it.
My take. Agree hard. The value metric is the whole decision. Seats were the wrong metric for us, so every downstream tweak to the funnel was furniture on the wrong model. Fix the metric first, then the conversion work has something to stand on.
Nobody who has actually repriced thinks the number is the hard part. The value metric is the moat.
The method: Solve, Stack, Split
SOLVE THE CRUX
What is the real problem, framed as work and not a headcount?
The problem is not "we need to raise the price." It is "revenue is tied to seats, not value." So the first work is analysis: where across the base does revenue track chairs instead of the value delivered, and where does a weekly-active user sit on free with no reason to pay. For the AE that is the deal that shrinks on the next reorg, for the CSM the renewal with one lever, for the marketer the plan priced by the count.
STACK THE CONTEXT
What tech and signals turn the base into a decision you can package around?
Not a shopping trip. The usage and revenue data lives in Snowflake. Looker runs the pricing and packaging analysis, seats versus value across the whole base. Amplitude surfaces the free-plan active users and the free-to-paid boundary. Deepline matches ICP to packaging so the tier fits who actually buys. It all lands in Salesforce, where deal size and the per-account contract get repackaged.
SPLIT · CUT THE DRAG
What low-judgment work goes to the system?
Read the base, model the impact, match the tier to the buyer. Pull the free actives, quantify where revenue tracks seats instead of value, and test the usage-and-revenue impact of a repackage before it ships. This is the mechanical work that never got done by hand because it was slow, and AI does it cleanly and every week.
SPLIT · KEEP THE JUDGMENT
What stays human?
The price. What the value metric is, where the free-to-paid line sits, and what a customer will actually pay for. The system reads and models. The operator decides what to charge for and what it is worth. That call is judgment, and getting it wrong is expensive, so it stays with a person and a weekly review of what the repackage moved.
The workflow: the board that runs it
Solve, Stack, Split is the shape. Here is the actual board, lane by lane: what the agents run, what stays human, and the tool at each step. Once it is wired, the read and the model refresh without anyone kicking it off.
The receipt
At a company I was at, a growth-stage SaaS business running on a pure per-seat license with a large free base, this is the exact build I ran. Read the base, redesign the model, then move the free-to-paid line.
We did not win by raising the number and hoping. We changed what the number was attached to. Tie revenue to value and a customer can reorganize without the contract falling apart, and the account can grow on something other than headcount. The deal got easier to say yes to, not harder.
Both of my receipts are commercial. Drop your own workflow in. A CSM turns the same build into a renewal that survives a reorg, the contract priced on value the customer still gets even when the team shrinks. A marketer turns it into a pricing page that sells the outcome, not a row of seats, so the plan reads as value instead of a headcount bill.
WHAT I LEARNED
1. Raising the price was never the risk. A model with one lever was the risk.
2. Per-seat means your revenue is a beta on your customer's headcount. They reorg, you shrink.
3. Fix the model before the paywall. Chasing free users into a wall does not hold on its own.
4. Value-based packaging de-risks the base and, done right, makes the deal easier to say yes to.
Run this one this week
Do not reprice the whole book. Pick one account and ask one question: does this contract grow when the customer gets more value, or only when they add seats. If it is seats, you found the risk. Then do the small version. Pull your free weekly-active users, find the one usage signal that separates a buyer from a tourist, and draw a single line where that value has a reason to convert. That is the repackage in miniature, and it tells you whether the full move is worth a quarter before you spend one.
Two builds that sit next to this one:
- The Expansion Score — "Expansion is not re-selling your champion. It is finding the untapped team next door." Land-and-expand off value, not headcount, is where the repackage pays out.
- The ICP Playbook — "A firmographic filter is not an ICP; it is a list." Match the tier to who actually buys, and the packaging fits the buyer instead of a seat band.
This is one build from the Build Log. Every week I take one sales or revenue problem, run it through the loop, and show the receipts. If someone forwarded this, the subscribe button is right below. Keep building. Heath.
You bought the signal. You never built the motion.
Everyone can capture intent now. The pipeline leaks in the gap between knowing and acting. What I got wrong, and what I am asking Adam Robinson on air.
The Seventh Analyst: The Agent That Reads the Other Six
Anyone can stand up six AI analysts. The one that makes the system compound is the seventh, the meta-analyst that reads the others' audit trails and turns every miss into a rule the next run enforces.
The Governance File: How a Pipeline Stops Repeating Its Worst Week
When you automate, your failures go silent. This build turned every past break into an enforced gate, so a fixed bug stays fixed and nothing broken ships confidently again.