Three years into building, a founder in construction software asked his largest account a direct question: how often do you use the scheduling module? The answer was twice a year — during bid season. He had been charging $800 per seat annually for a feature that delivered its value in two sessions. Seat-based pricing was hiding a fundamental mismatch between how his product created value and how he was charging for it.
SaaS usage-based pricing isn't a trend to follow. It's a structural pricing choice with specific conditions under which it outperforms seat licensing — and specific conditions under which it creates problems. Understanding the difference before you build your pricing page is worth more than any benchmark.
What usage-based pricing actually is
Usage-based pricing ties revenue to consumption. Customers pay based on API calls, records processed, transactions completed, bids generated, or filings submitted — not for access. The more they use, the more they pay. The less they use, the less they pay.
This differs fundamentally from seat licensing (pay per user regardless of activity) and from feature-tier licensing (pay for access to capability levels). Those models charge for access. Usage-based pricing charges for outcomes.
In horizontal vertical SaaS markets — project management, communication tools, generic CRM — seat licensing makes sense because usage is daily and relatively uniform. Everyone logs into Slack. Not everyone generates the same number of construction bids in a given month, or submits the same number of compliance filings.
Where it works in vertical SaaS
Usage-based pricing fits when three conditions hold. First, usage variance across accounts is high. One customer runs 200 inspections per month; another runs 12. Seat pricing charges both the same and leaves money on the table with the first account while creating friction with the second.
Second, the product's value ties to a discrete, measurable outcome. Estimation tools create value per bid generated. Compliance platforms create value per filing. Payroll software creates value per pay run. When value is episodic and countable, usage pricing matches the revenue model to the value model.
Third, the product is used to complete a task rather than as ambient infrastructure. A scheduling tool open all day fits seat licensing. A tool used intensely during bid season and lightly the rest of the year fits usage billing — the billing mirrors how customers already think about their own business costs.
Where it creates problems
Vertical SMBs budget annually. A plumbing company owner who signs a software contract in January needs to know what they're paying in December. Usage-based pricing introduces cost unpredictability for buyers and revenue unpredictability for you. Neither is good at the early stage.
It complicates renewals. When a customer's usage grows 40% year-over-year because they're running more projects, their bill grows 40%. That's mathematically fair. It feels like a price increase in the renewal conversation. You end up defending a number you didn't choose rather than leading with the value the growth represents.
Usage-based pricing can also penalize your best accounts. The customers driving the most value from your product — and most likely to refer others — get the highest bills. Some accept this. Others resent it quietly until renewal.
The customer acquisition cost math changes too. When pricing is variable, average contract value becomes a range rather than a number, which makes unit economics harder to model for investors and harder to forecast for your own planning at the stage where planning matters most.
The hybrid model that actually works
Most successful vertical SaaS pricing strategies that incorporate usage-based elements don't use them exclusively. They use a platform fee plus usage tiers. The platform fee covers access, support, and a baseline usage allowance. Usage above that baseline is billed at a fixed per-unit rate.
This structure gives buyers what they need — a predictable floor to budget against — while giving you the upside when accounts grow. The sales conversation simplifies: you're selling a known annual commitment with usage upside, not a variable cost that requires a CFO to model scenarios before approving.
The tiers work best when set at points that match natural usage bands in your customer base. If most accounts fall below 100 transactions per month, set your platform tier there. If a second cluster runs between 100 and 500, that's your next tier. Price overages at a rate where growth feels like a natural upgrade rather than a surprise invoice.
How to decide
Three questions will tell you whether usage-based pricing fits your product.
Does your product create value continuously or episodically? If customers are in the product daily and value compounds with time, seat licensing fits. If they use it in bursts tied to business outcomes, usage billing matches the value more accurately.
Is your customer's usage predictable? Small businesses that run consistent volume month to month may add more friction than the model is worth. Project-based businesses, seasonal workflows, and transaction-driven processes are better candidates — usage already varies in ways buyers understand.
Can your sales team explain the pricing in 60 seconds? If the model requires a spreadsheet before the prospect can say yes, it adds friction at a stage where friction costs deals. The best pricing models feel obvious in a demo.
If you're an operator founder who has been on the buying side of these conversations, you already have the most useful data point available: how did this category of software pricing feel when you were the buyer? What made the number feel arbitrary? What made it feel fair? That instinct is more calibrated than any benchmark.