Most pricing decisions happen in a conference room with a spreadsheet and a gut feeling. Ours did too. We picked a model that felt logical, posted it on the website, and moved on to building product. That worked fine — until it didn't.
The moment it stopped working arrived not as a dramatic churn event but as a quiet, confusing conversation with a customer we'll call Company M. They were mid-market, growing fast, and exactly the profile we wanted more of. When they told us they were thinking about leaving, we assumed the product had a gap. It didn't. The problem was simpler and harder to fix: they couldn't justify what they were paying relative to what they believed they were getting.
Company M was on a plan priced around usage volume. They paid more as they used more. On paper, that's fair. In practice, it punished them for the behavior we wanted — deeper adoption.
The founder on the call said something that stuck: "Every time my team finds a new way to use you, my finance person sends me a Slack message asking why the bill went up." Growth in usage should feel like a win for both sides. For Company M, it felt like a tax.
We'd built pricing around what was easy for us to meter, not around what the customer considered valuable. Those are rarely the same thing.
After that call, we looked at accounts that had churned or contracted in the previous two quarters. The pattern was obvious in hindsight: the customers who left weren't the ones who barely used the product. They were the ones who used it enthusiastically for two months, watched the invoice climb, and pulled back.
The churn data had been telling us this for months. We just hadn't framed the question correctly. We'd been asking "who stopped using us?" when the better question was "who started using us less on purpose?"
Voluntary contraction — customers actively throttling their own usage — is a pricing problem wearing a retention costume. If you see usage dip right after an invoice lands, that's not an engagement issue. That's a price-signal issue.
We didn't lower prices. We restructured what was included and how the tiers mapped to outcomes customers actually cared about.
The old model charged for consumption. The new model grouped capabilities around the job the customer was trying to do. A team that needed a specific set of outcomes could pick the tier that matched, and their usage within that tier was predictable. No more "growth penalty." No more Slack messages from finance.
The shift wasn't dramatic from a revenue-per-customer standpoint on day one. But the behavior change was immediate. Customers in the new packaging expanded faster because trying more of the product didn't trigger a surprise on the invoice. They brought new teams in. They moved from cautious experimentation to committed adoption.
Expansion revenue improved meaningfully in the two quarters after the change. Not because we found new customers, but because existing ones stopped being afraid to go deeper.
The temptation after a win like this is to declare the problem solved. We've learned otherwise. Pricing needs revisiting regularly — not because the cost structure changes (though it does), but because customer perception of value shifts as the product matures and as their businesses evolve.
We now treat pricing reviews the way we treat product retrospectives: scheduled, structured, informed by real data. The inputs are churn interviews, contraction patterns, expansion velocity, and direct conversations with customers about what they'd pay more for. The output is not always a change. Sometimes the output is confidence that the current model still fits. That's valuable too.
A few principles we hold after going through this:
Price around the customer's unit of value, not your unit of cost. What you meter internally and what the customer considers worth paying for are different things. Close that gap.
Watch contraction more carefully than churn. A customer who cancels is obvious. A customer who quietly scales back is telling you something subtle and important. The second signal often arrives months before the first.
Make expansion feel rewarding, not punishing. If deeper adoption makes a customer nervous about their bill, your packaging is working against your growth.
Revisit before you're forced to. The best time to rethink pricing is when things are going well and you have room to experiment. The worst time is when a valuable customer is already on a call telling you they're leaving.
Pricing is not a launch-day decision you laminate and hang on the wall. It's a living negotiation between what you build and what your customers believe that's worth. The signals that tell you it's time for a change are usually already in your data — in the contraction trends, in the post-invoice usage dips, in the expansion deals that stall for reasons nobody can quite name.
Listen to the customer who pushes back. They're doing you a favor.
Be the first to comment.
0 comments
Loading comments...