Should usage-based pricing work for heavy SaaS users?

[RileyS]

I’m trying to decide whether to switch our SaaS product to a usage-based billing system, but I’m worried it might actually discourage our heavier users from adopting new features. We see clear spikes in value when they use certain modules, but I’m not sure if charging per action aligns with how they perceive their monthly budget.

[Oliver.M]

We tried a 3 month pilot with per action pricing. Heavy users lit up when specific modules were in play, but the monthly bill went all over the map. Forecasts got noisy because spend tracked actions rather than a steady budget. We kept a base plan and added a tiered per action, yet adoption of new features actually slowed until we added caps and simpler quarterly budgeting. A few power users churned, others stayed but watched the invoices closely.

[Sophia.G]

In a different squad we ran a six week test of usage-based billing with a hard monthly cap and some credits. Early on we saw about 12% fewer feature trials among the top users, and support tickets around bill shocks spiked. After we introduced usage credits and a blended price bucket, numbers stabilized but retention didn't clearly improve. It felt like the budget signal outweighed the perceived value for the pulse users.

[Tyler30]

Is the real problem maybe not pricing at all but how we surface value and onboard heavy users? I keep wondering if we assume price drives behavior when the bigger friction is discovery and ROI communication.

[EthanNH]

We kept the old pricing alongside optional usage add-ons. Feedback was mixed: some heavy users liked paying for what they used, others felt nickel-and-dimed. We tracked module activation and ROI signals, and found adoption didn't move much until we paired it with in-app nudges and a clearer ROI story.