RevTune
SolutionsFeaturesPricingAboutBlogContact
Sign InGet Started

End of dispatch · Ready to tune pricing?

Connect your billing stack and get answers in minutes.

Stripe, Paddle, LemonSqueezy, or Chargebee. Read-only access. No credit card to get started.

Start Free
RevTune

A Monday-morning readout from your billing data — labeled by what the evidence actually supports.

Built for SaaS founders
Questions? support@revtune.io

Product

  • Solutions
  • Features
  • Pricing
  • How it works
  • Dashboard

Resources

  • About
  • Contact
  • Blog
  • Security
  • Changelog

Follow

  • X / Twitter
  • GitHub
  • Instagram

Vol. 1 · No. 47 · The Pricing Desk · 2026

No placeholder docs, no dead ends — every link in this dispatch goes somewhere real.

© 2026 RevTune. All rights reserved.

PrivacyTerms·Set in Fraunces & JetBrains Mono.
All issues
Nº 06·Pricing Strategy

The case for usage-based pricing in 2026

Seat-based pricing made sense in the SaaS 1.0 era. AI changed the unit economics overnight. Here's how to price for a world where the work is done by tokens, not chairs.

MK

Meriç Karpat

Founder, RevTune

March 28, 2026·6 min read

Seat-based pricing was a brilliant invention for its time. In 2010, "more users" was a clean proxy for "more value." Salesforce taught the entire industry to count chairs, and an entire generation of SaaS pricing pages copied the pattern.

Then AI happened.

The unit economics broke

The moment your product starts using LLM tokens, the seat-based model collapses. A single user can drive 100x more cost than another single user. A "free trial" can rack up triple-digit inference bills overnight. Suddenly the customer who looked profitable yesterday is bleeding you dry today.

You can't price that with seats. You have to price it with usage.

What usage actually means

The trap is to think "usage = API calls." That's the cheapest possible interpretation, and it's the one that pisses customers off. Nobody wants to watch a meter while they work.

Better unit metrics:

  • Outcomes — successful runs, completed jobs, generated artifacts
  • Throughput — messages processed, records analyzed, documents indexed
  • Stored state — projects, workspaces, environments, datasets

Pick the one that scales linearly with your customer's value, not your infra cost. If they don't feel ripped off when the bill arrives, you picked the right unit.

The hybrid that actually works

The cleanest model I've seen for AI products is base seat + pooled usage. A small monthly fee gives access to the workspace. Heavy usage gets billed against a pooled allowance shared across the team.

It's predictable for finance. It scales with value. And it doesn't punish exploration — small experiments stay free, real work pays for itself.

The Journal

New issues, in your inbox.

One pricing essay every other week. No filler, no spam, unsubscribe anytime.

Requests go to a real inbox until self-serve subscriptions ship.

All issues