Is usage-based pricing becoming the norm for AI tools?
Hey everyone,
I've built my product around traditional SaaS pricing (monthly tiers), but I’m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market.
That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It’s something I’m starting to seriously think about for my own product.
In particular, AI usage has real COGs (every prompt costs money), and I’m seeing more platforms experimenting with usage-based models, or hybrids like “SaaS base + usage + overage.”
For those of you building AI or compute-intensive tools:
Are you sticking with SaaS pricing?
Have you considered switching to usage-based or hybrid models?
Is it helping or hurting conversions?
Would love to hear what others are doing and whether you're seeing buyer preferences shift, too.
Replies
Usage-based is becoming the norm, but it's a double-edged sword.
The upside: it feels fair to users, especially for AI tools where value varies wildly by use case. A heavy user paying more than a casual one makes intuitive sense.
The downside we're wrestling with at Hello Aria: usage anxiety. When people are metered, they start self-censoring "is this query worth it?" That friction kills the natural, conversational habits that make AI assistants actually useful.
Our current bet: flat subscription with a generous limit. You can do almost everything without thinking about tokens. Once you hit the limit, upgrade. No surprise bills, no usage anxiety.
For pure B2B API tools, usage-based is probably right. For consumer AI assistants trying to build habits, flat wins.
hot take but the whole pricing model debate is a distraction. inference costs are dropping so fast that whatever you pick today will be wrong in 6 months. just pick the simplest thing your customers understand rn and revisit when costs halve again. ive seen founders spend more engineering hours on metering and billing infrastructure than on their actual product