There's a debate raging across SaaS right now: is per-seat subscription pricing dead, and is usage-based (consumption) pricing the future? Vendors are switching. Founders are agonising. Advisors are writing threads. And almost everyone is asking the wrong question.
The pricing model matters far less than one thing underneath it that nobody's debating: who controls the billing. Because the winning SaaS in 2026 isn't the one that picked subscriptions or consumption. It's the one that can charge either way — and switch between them — without asking a vendor's permission. Here's why that's the real battleground, and how to be on the right side of it.
For two decades, per-seat subscription pricing was simply how SaaS worked. It was predictable for buyers, predictable for sellers, and it fit software whose marginal cost of one more user was essentially zero.
AI broke that. When your product runs on a language model that charges you per token, every action a user takes has a real, metered cost. A flat per-seat price on top of variable per-token costs means your heaviest, most engaged users can cost more to serve than they pay. So vendors are moving to consumption pricing — charging for what's actually used — because their own costs are now usage-based. It's not a philosophy; it's their margin.
That's the whole reason the debate is loud: the underlying economics of software genuinely changed, and the old default genuinely stopped fitting a large class of products.
The trap is treating this as a winner-take-all argument. It isn't. Each model fits a different shape of product and customer.
Subscription pricing wins when value is steady and predictable, buyers want a stable budget line, and usage doesn't vary wildly between customers. Predictability is itself a feature — finance departments love a fixed number, and steady recurring revenue is easier to run a business on.
Consumption pricing wins when value scales with usage, costs scale with usage, and customers vary enormously in how much they use. It aligns price with value — light users pay little and aren't subsidising heavy ones — and it protects your margin when serving a customer has a real marginal cost.
And the best answer is often both at once: a subscription base for predictable access plus metered charges for heavy usage, or tiered plans with usage allowances and overage. Hybrid models are increasingly the norm precisely because real products have both a predictable component and a variable one.
Which means the strategic requirement isn't "pick the right model." It's "be able to run whichever model — or combination — fits, and change it as you learn." Your first pricing guess is almost always wrong. The ability to iterate is worth more than the initial choice.
Here's where it gets real. To charge consumption or hybrid pricing, you need to meter — track what each customer uses, in units that map to value, accurately enough to bill on. And to change your model, you need to control that metering and the billing logic on top of it.
Now ask where your billing actually lives. For most SaaS, it lives inside a payment processor or a subscription-management vendor. And that means:
The pricing models you can offer are the ones your vendor supports. Want a hybrid base-plus-usage plan with per-feature entitlements? Only if the vendor built it. Your pricing creativity is capped by someone else's roadmap.
Changing your model is a migration, not a decision. Moving from per-seat to usage-based should be a strategic choice you make in an afternoon. If your billing is rented, it's a painful re-platforming that can take months — so you don't do it, even when you should.
The vendor takes a cut of every transaction — and, more quietly, owns the data about who's about to churn and who's a heavy user, the exact data you need to price well.
So the vendors loudly switching their pricing to consumption are, in the same breath, a warning: the entity that controls the billing gets to change the deal. If that entity is your vendor, the deal that changes is yours.
There's a second piece that decides whether any pricing model actually works, and it's the least-discussed part of the whole subject: entitlement.
Billing answers "did they pay, and how much?" Entitlement answers "so what can they access right now?" — and keeps that answer correct as subscriptions upgrade, downgrade, lapse and renew. A customer moves from Pro to Basic: their access has to shrink, automatically, immediately. A card fails and they lapse: the paid features have to switch off, cleanly, without a human involved. They buy an add-on: it unlocks at once.
Get entitlement wrong and every pricing model leaks. You give paid features to people who cancelled, or you lock out people who paid — both quietly fatal. The reason this matters to the pricing debate is that fancy pricing is worthless without airtight entitlement behind it. A hybrid usage-and-tier model with sloppy entitlement is just a sophisticated way to lose money in two directions at once.
Stop optimising the pricing-model choice and start optimising for pricing control. Concretely, the SaaS that wins the next few years can:
Notice that none of those is a pricing model. They're all capabilities — and they all come from owning the billing layer rather than renting it.
This is a core reason self-hosted, source-available platforms are gaining ground. VBWD ships subscription billing, tiered plans, invoicing and tax as core — and, critically, automatic entitlement that changes a user's access level with their subscription status, so the "what can they access now" question stays correct on its own. Because it's your deployment and your source, the pricing logic is yours to shape: run per-seat today, add usage-based metering when a product line needs it, go hybrid when that fits — without waiting on a vendor or migrating platforms. Its central LLM connection even lets you point AI features at a hosted or local model, so you control the cost side of consumption pricing too, not just the charge side. You keep the margin, you keep the churn data, and it's free for commercial use below a defined revenue threshold.
The honest caveat is the standing one: owning your billing means running the platform, which is real work and not right for a tiny project happy with an off-the-shelf checkout. But if your software is your business, billing isn't a feature you bolt on — it's the mechanism by which the business exists, and renting it means renting the ability to decide how you make money.
Subscription or consumption? Wrong question. The right one is: when the model needs to change — and it will — can you change it, or does someone else decide? Own the meter, and the pricing debate stops being something that happens to you and becomes a lever you get to pull.
VBWD is a self-hosted, source-available platform for building subscription products, marketplaces, and AI-powered apps. Explore it further: