Should we switch to usage-based pricing for our software product?

[Emily_R]

I’m trying to decide if we should switch our SaaS product to a usage-based pricing model. Our current flat-rate subscription is simple, but we’re seeing a big gap between light users who feel overcharged and heavy users who are getting a huge bargain, which feels like leaving money on the table. I’m just not sure if the operational complexity and customer pushback would be worth it.

[Madison.R]

We did a tiny test with usage based pricing last year, and the system got messy fast. Light users felt nickel and dimed, mid tier churn ticked up, and the whole metering invoicing pile became a magnet for support tickets. We pulled back after a quarter.

[Joshua.J]

If you run a small pilot, what metric would you use to decide if it works, revenue, churn or net value per user?

[EvelynDW]

We tried a hybrid tiered approach with soft caps, heavy users did not mind, light users yelled about overage charges, and the ops team spent weeks building dashboards that never felt clean. We eventually dropped it because the admin overhead outweighed any revenue gains.

[Grace69]

From where I sit maybe the biggest win is clarity of value and gating, sometimes the problem is that customers do not see the difference between tiers. A simpler option is to offer value based add ons rather than strict usage charges.