Jake Friedberg

Is usage-based pricing becoming the norm for AI tools?

by

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.

1.5K views

Add a comment

Replies

Best
Casey Gaskins

I think hybrid pricing is probably where a lot of AI tools are heading. Pure monthly SaaS feels clean, but AI changes the math because every prompt, generation, video, image, or deep research task can have a real cost behind it.

I’m building Traction, and we’ve been thinking about this too. Some parts of the product should feel like normal subscription value: planning, leads, follow-up, visibility, analytics, business context, etc. But heavier AI media generation probably needs credits or usage limits because the cost structure is different.

The hard part is making it feel fair instead of annoying. Users hate feeling nickel-and-dimed, but founders also cannot pretend compute is free. My instinct is: base plan for the core platform, included monthly credits for heavier AI features, then optional credit packs for people who need more volume.

Will Towle

Running into this exact tension with Sharpread. Every analysis costs real money in Anthropic API calls plus EDGAR data fetches, so pure flat-rate SaaS feels like a race to the bottom on margin.

We landed on a hybrid: a fixed number of analyses per tier rather than pure usage billing. Users get 20 analyses for $5, which is simple to understand and predictable for them, while we can model our costs reliably on the back end.

The thing I have noticed: usage-based pricing creates anxiety for users who are not sure what they will be charged at the end of the month. A fixed credit model gives them the same flexibility without the open-ended cost fear. Conversions felt cleaner once we moved away from anything that looked like a meter running.

The real architectural pain is metering and enforcement, not the pricing model itself. That work is the same whether you charge per use or bundle credits into tiers.

Sebastian Galvis

wow, great conversation happening here ---- from my perspective (working in the VC industry with a lot of founders):

Im starting to see some great SaaS companies moving to "consumption" pricing with a small SaaS fee - depending also in what kind of problem are they solving and how painful/hard is to switch, there are a lot of sectors that are being "commoditized" today

If I wanted to start changing the model, I would begin talking to my clients and understanding their needs at least three months before renewal

Atul Yadav

usage-based is not really a pricing question, it is a forecasting question your buyer has to answer. the moment a finance team cannot predict next month's bill within a tight band, the tool moves from line-item to procurement review, and the sales cycle doubles. the hybrid that works is a flat platform fee that covers predictable workload plus metered overage on the genuinely variable bit, usually long-context or agentic loops. one thing worth instrumenting before you change pricing: cost per successful outcome, not cost per token. token bills go up when your prompts get worse, and you do not want to charge customers for your own regressions.

First
Previous
•••
456