How do you choose between usage-based and seat-based pricing?

Your pricing model is a bet on where value lives in your product. Seat-based pricing bets that access itself is the value; usage-based pricing bets that outcomes are. Getting this wrong doesn't just hurt revenue—it creates friction with the exact customers who would otherwise expand fastest.

Start with how your customers actually create value

The most important question isn't 'what do other SaaS companies charge for?' It's 'where does the ROI show up for my customer?' If a customer gets value every time they use the product—each API call processed, each document generated, each transaction completed—usage-based pricing aligns your revenue with their success. Every time they win, you win. That alignment is self-reinforcing: customers don't resent the bill because growth in spend tracks growth in value.

Seat-based pricing makes sense when the value is less about frequency of use and more about access, collaboration, or organizational coverage. A project management tool where ten people need to coordinate daily doesn't generate ten times the value with ten times the usage—it generates value through the coordination itself. In that case, charging per seat reflects what the customer actually cares about: who can get in the door.

A useful diagnostic: ask your best customers what they'd lose first if forced to cut usage by 50%. If they'd lose outcomes (revenue, speed, throughput), lean usage-based. If they'd lose coverage (fewer team members, less visibility), lean seat-based.

Consider your customer's budget approval process

Seat-based pricing is predictable, and predictability is a feature inside large organizations. A CFO can look at a 50-seat contract and know exactly what the next 12 months cost. That predictability lowers the psychological and procedural barrier to signing. Enterprise procurement teams are built around fixed commitments—they have frameworks for it, legal templates for it, and approval chains calibrated to it.

Usage-based pricing shifts that dynamic. Customers pay more when they succeed, but they also face variance—and finance teams are allergic to variance in operating expenses. This is why pure usage-based models often stall in enterprise deals even when the product is exceptional. The solution most companies land on is a committed minimum with usage overage: the customer buys a floor (predictability for their CFO) and pays for what they consume above it (fair for them when they grow).

If your primary buyers are individual contributors or small teams with credit cards, usage-based pricing removes friction because there's no approval needed to get started. The customer experiments, finds value, and the bill grows naturally. That's a powerful self-serve acquisition motion. But if your deal requires a VP signature, a fixed-price structure will close faster—even if usage-based would ultimately generate more revenue.

Map the risk each model places on each party

Seat-based pricing transfers expansion risk to you: if your customer adds seats slowly, your revenue grows slowly regardless of how much value they get. Usage-based pricing transfers churn risk back to the customer—if they don't use it, they don't pay, but they also don't have sunk-cost pressure keeping them engaged. Each model creates a different psychological dynamic that affects retention behavior.

One underappreciated failure mode of usage-based pricing is what happens during cost-cutting seasons. When a customer's CFO orders a 20% reduction in SaaS spend, usage-based tools are the easiest to cut because the immediate financial impact is clear and the reduction requires no renegotiation—just dialing back activity. Seat-based contracts, paradoxically, can be stickier because eliminating them requires an active cancellation decision and often a conversation. The irony is that usage-based feels more customer-friendly, but it can be less durable in a downturn.

The best-run companies treat pricing as a living decision, not a founding choice set in stone. Start by understanding the concentration of your customer base: if your top 20% of customers by revenue are heavy users with volatile usage, locking in a committed contract protects you both. If your base is wide and relatively even in consumption, pure usage-based may be both simpler and fairer.

What your pricing model signals about who you're building for

Pricing is positioning. Usage-based pricing signals 'we're confident enough in our value to only charge you when you succeed.' That's a powerful statement in a competitive market and one that resonates particularly well with technical buyers who hate paying for shelfware. It also creates a natural land-and-expand motion: a small team can start with minimal spend, prove the value internally, and grow the contract without renegotiation.

Seat-based pricing signals predictability and organizational scale. It works especially well when your product's value proposition involves changing how a team or department operates—not just what one person can do. If you're selling to HR, legal, or ops teams who measure success by adoption rates and organizational rollout, a seat model aligns with how they think about deployment success.

There's a trap founders fall into here, similar to what Paul Graham describes when founders imitate the flaws of big companies to seem more legitimate: choosing a pricing model because it feels more 'enterprise' or 'serious' rather than because it fits how customers actually extract value. A usage-based model that fits your product perfectly will outperform a seat model adopted to appear more established. Let the value mechanics of your product drive the choice, not optics.

Practical signals that tell you which model to run

Run usage-based pricing if: your product's core output is discrete and measurable (queries, transactions, minutes, tokens), customers vary dramatically in how much they use the product, heavy users naturally generate far more value than light users, and your go-to-market motion involves self-serve or developer-led adoption. In these cases, usage-based pricing rewards you fairly for the value you deliver at scale and removes friction for new customers who aren't ready to commit.

Run seat-based pricing if: your product's value is tied to team-wide adoption and coordination, usage is relatively uniform across your customer base, you're selling into enterprise procurement where predictability is required, or your product involves ongoing access to a platform rather than discrete outputs. If customers would still pay even during a month they used it lightly—because losing access itself would be disruptive—you have a seat-based product.

The hybrid committed-minimum-plus-usage model deserves serious consideration for companies that need both enterprise dealability and the ability to grow with customers. It captures the predictability advantage of seat-based contracts while preserving the upside alignment of usage-based pricing. The tradeoff is complexity in your pricing page and sales motion—but for many B2B SaaS products in the $50K–$500K ACV range, that complexity is worth it.

“They want so much to seem big that they imitate even the flaws of big companies.”

— Paul Graham, source

The one thing to do

Identify whether your customers' value comes from outcomes (usage-based) or access (seat-based), then build your pricing model around that—not around what looks most professional or what competitors charge.

Frequently asked questions

Can you switch from seat-based to usage-based pricing after launch?

Yes, but migrate carefully. Existing customers should be grandfathered or given a transition window—surprise pricing changes erode trust faster than almost anything else. New cohorts can be moved to the new model immediately while you measure whether it changes conversion or expansion rates.

Does usage-based pricing hurt predictable revenue forecasting?

It adds variance, but not necessarily unpredictability. With enough customer history, usage patterns are often quite stable. Committed minimums with overage clauses give you a revenue floor to forecast against while preserving upside from growth.

What if customers reduce usage to save money even though the product is working?

This is the key risk of usage-based pricing and a sign your pricing metric may not be aligned with the outcome customers care about. If reducing usage doesn't reduce the value they get, you've chosen the wrong unit to charge on—find the metric that rises and falls with their actual results.

Is usage-based pricing better for early-stage startups?

Often yes for self-serve products, because it removes the commitment barrier for new customers and lets early adopters start small. But if you're selling to enterprise buyers from day one, seat-based or committed contracts may close faster and give you more predictable runway.

Sources

More playbook answers · Growth Prophet home