What are the cons of a pay-per-user SaaS pricing model?

Per-user or seat-based pricing has been the default SaaS move for more than a decade.
It’s simple, familiar, and easy to forecast. But as products get more collaborative,
more AI-powered, and more usage-driven, founders are starting to realize something
uncomfortable: that neat little “$X per user per month” line can quietly slow down
growth, distort product adoption, and even crush margins.

That’s exactly why Jason Lemkin and other SaaStr voices increasingly talk about
per-user pricing as a bit “dated” for many new SaaS products, especially in an AI-first world
where the real cost driver is usage, not seats.

In this deep dive, we’ll walk through the main drawbacks of a pay-per-user SaaS pricing
model, how they show up in real life, and when it might still make sense to stick with
seat-based pricing (or blend it with something smarter). Think of this as a friendly
“roast my pricing page” before your customers do it for you.

Quick refresher: What is a pay-per-user SaaS pricing model?

A pay-per-user pricing model charges a fixed subscription fee for each individual user
that has access to your software. One user = one seat = one license. If your customer adds
20 team members, they pay for 20 seats; if they only roll it out to three power users, they
pay for three.

This model is especially common in:

• Collaboration tools (chat, project management, documentation)
• CRM and sales engagement platforms
• Help desk and customer support software
• Many B2B productivity and vertical SaaS products

The big upside: it’s easy for everyone to understand. Finance teams can forecast spend,
founders can forecast MRR, and the pricing page looks clean.

But that simplicity comes with trade-offs. Let’s dig into the cons.

1. Misaligned with how customers actually get value

The biggest problem with pay-per-user pricing is that it assumes each user gets roughly
the same amount of value from your product. In reality, SaaS value is often driven by:

• Volume of transactions or data processed
• Number of API calls, messages, or workloads
• Revenue or cost savings generated through the platform
• Automations executed or tasks handled by AI agents

When you charge per seat, you’re basically saying, “Every person who logs in is equally
valuable.” That might be true for classic sales CRM seats. But for an AI-first or usage-heavy
product, one power user can drive 10–100x more consumption (and cost) than a light user,
while both are billed the same.

Result: your revenue and your cost structure stop lining up. Heavy users quietly erode your
margins, while light users feel like they’re overpaying.

2. Seat friction kills adoption and collaboration

Per-user pricing introduces a psychological tax on every new seat. Before a manager adds one
more person, they have to think, “Is this extra $20–$200/month really worth it?”

That friction shows up in a few unhealthy patterns:

• “Power user only” rollouts: Teams limit access to a handful of admins instead of rolling the product out company-wide.
• Shared logins: To dodge extra seats, people share credentials, which hurts security, auditability, and your user data.
• Shadow tools: Other team members spin up their own tools because they don’t have a seat on the “official” one.

Collaboration products suffer the most. If the whole value prop is “get everyone working
together in one place,” but your pricing makes it painful to include everyone, your model is
quietly fighting your product-led growth.

3. Per-user pricing can cap expansion revenue

Great SaaS businesses are built on net dollar retention, not just logo count. The dream is
simple: your customers grow and your revenue grows faster. But per-user pricing can hit a
hard ceiling once your customer has:

• Added all relevant team members
• Automated away some user seats with AI or workflows
• Centralized usage into a few super users

At that point, expansion slows or stallsunless you keep nudging prices up across the board.
That’s when “We’re just right-sizing pricing to the value you get” starts to sound, in the
customer’s ears, like “We’re charging more for the exact same thing.”

In contrast, usage-based or value-based pricing lets customers expand their footprint
naturally as they do more with your platform, without always tying that growth to headcount.

4. It creates ugly incentives on both sides

Pricing is more than math; it shapes behavior.

With pay-per-user pricing, customers are incentivized to:

• Limit seats to “essential” users only
• Under-report who’s using the product or share logins
• Delay adding new teams until the value is “undeniable”

Meanwhile, your sales team is incentivized to:

• Push for large seat deals up front, before value is proven
• Index on headcount rather than actual customer value or outcomes
• Focus on “how many users can we add?” instead of “how much impact are we driving?”

None of this is evil; it’s just the logic of the pricing model. But over time, that logic
can push you away from value-based conversations and toward quota-driven seat stuffing.

5. In an AI-first world, seat-based pricing breaks faster

AI is pulling the rug out from under traditional SaaS economics. You now have AI agents,
copilots, and automation systems doing the work that entire teams used to handle. That means:

• Fewer human users in the app
• More AI workloads running behind the scenes
• Cloud and model costs that scale with usage, not seats

If you keep charging per user in this environment, a weird thing happens: the more your
product delivers on its promise (“do more with fewer people”), the fewer seats you can bill.
That is… not the flywheel you want.

Even SaaStr has highlighted how AI agents can replace expensive human workflows for a
small monthly cost, which makes high-priced seat-based tools look increasingly fragile.

For AI-heavy offerings, charging per request, per workflow, or per unit of compute often
makes far more sense than pretending a “user” is the core economic unit.

6. It can punish customers with fluctuating or seasonal teams

For companies with stable headcount, per-user pricing is easy. But many modern businesses
agencies, hospitality, retail, logistics, startupshave highly dynamic teams. Seasonal hires,
rotating contractors, and temporary project squads create constant seat churn.

In a pure per-user model, those customers either:

• Over-buy seats “just in case” (resentment builds)
• Constantly add/remove seats (admin overhead + billing chaos)
• Push people to share logins (again, security and data problems)

Over time, these customers start shopping for tools that feel more flexible and aligned to
how their teams actually work. If your competitor offers usage-based or tiered pricing with
more elasticity, you suddenly look rigid and expensive.

7. Seat-based pricing can distort your product roadmap

Your pricing model doesn’t just affect sales; it also whispers in your product team’s ear.

When revenue is tied to user count, it’s tempting to prioritize features that:

• Make it easier to add more users in each account (even if the core value is elsewhere)
• Optimize admin controls and permission schemes (so IT buys more seats)
• Focus on “adoption metrics” over outcome metrics

That’s not necessarily bad, but it can pull focus away from usage depth, efficiency, or
performanceespecially for products where the real magic happens in the heavy workflows,
automations, or integrations, not in simply expanding to more humans.

When can pay-per-user pricing still work well?

To be fair, per-user pricing isn’t dead; it’s just no longer one-size-fits-all. There are
still scenarios where seat-based pricing is a great fit:

• Uniform value per user: Each user’s experience and value are roughly similar (e.g., CRM or email for sales reps).
• Strong comparison anchors: Buyers already think in “seat” terms and benchmark against tools like Salesforce or Zoom.
• Low backend cost per user: Your marginal cost for another seat is tiny and not tightly tied to usage.
• Simple go-to-market: You sell into teams where “number of users” is the cleanest, fastest way to get a deal done.

Even then, many companies add safety valves: per-user pricing with usage caps, plan tiers, or
fair-use policies that protect margins and keep high-usage customers from accidentally
becoming loss-making accounts.

Smarter alternatives: hybrid and value-based pricing

If pure per-user pricing has all these cons, what do modern SaaS companies do instead? The
trend isn’t to abandon seats entirely, but to augment them with value- or usage-based
levers.

1. Per-user + usage tiers

Charge a base price per user, but define tiers based on product usage: number of projects,
contacts, messages, workflows, or credits. This keeps pricing familiar while better aligning
heavy usage with higher spend.

2. Usage-based with a platform fee

Charge a small platform fee (for access, support, security) plus metered usage for the
value-driving actions: API calls, documents processed, AI tokens, or transactions. That
ensures you get paid fairly as customers grow without tying everything to headcount.

3. Value-based tiers

Instead of “Starter / Pro / Enterprise” based on arbitrary feature bundles, build tiers
around clear business outcomes: revenue supported, seats served, locations managed, or
tickets resolved. Customers see pricing as aligned with their success, not just with
how many humans log in.

The common thread: modern pricing models try to charge for what actually scalesusage,
complexity, or valuenot just the number of people who have an account.

Real-world experiences with pay-per-user SaaS pricing

It’s one thing to talk theory. It’s another to watch how per-user pricing plays out in
messy, real-life SaaS companies. Here are a few composite stories and patterns that come up
again and again in founder and operator conversations.

Story #1: The “shared seat” collaboration tool

A product-led startup built a fantastic internal knowledge and collaboration platform.
They launched with a straightforward $15 per user per month model. Early adopters loved
the productbut only rolled it out to small teams of “knowledge champions.”

When the startup dug into usage data, they discovered:

• Documents were being exported and shared via email or PDFs instead of adding more users.
• Admins were actively removing inactive seats each quarter to keep the bill flat.
• Several accounts had suspiciously high activity from one or two loginsclearly shared seats.

They eventually shifted to a hybrid: a modest per-user fee plus tiers based on the number
of workspaces and documents. That gave larger accounts room to bring more people into the
product without feeling like every extra collaborator was a budget negotiation.

Story #2: The AI-heavy platform with collapsing margins

Another company offered an AI assistant for customer support teams. Their pricing?
$79 per support agent per month. At first, it worked beautifully: customers compared it
to the cost of a human agent and felt they were getting a great deal.

But as adoption grew, something broke:

• Some agents were running thousands of AI-assisted replies per month.
• Others barely used the assistant at all.
• Cloud and LLM costs were tightly correlated with usage, not seats.

A handful of customers became wildly unprofitableeven though their seat counts hadn’t
changedbecause a few agents were pounding the AI features all day. The company switched
to a base platform fee plus “AI credit” bundles, and suddenly margins stabilized without
forcing them to raise per-user prices across the board.

Story #3: The seasonal workforce headache

A vertical SaaS startup selling into hospitality used per-user pricing with annual
contracts. Their customers loved the product but hated the pricing gymnastics. Hotels
ramped up staff in peak seasons and cut back in slow months, yet the SaaS bills stayed
flat based on the prior year’s seat count.

That created friction in renewals:

• Buyers demanded aggressive discounts or shorter contracts.
• Sales teams spent weeks renegotiating seat counts instead of expanding new features.
• Churn spiked among seasonal businesses that felt “locked in.”

The fix was a usage-based component tied to reservations or room nights processed,
with a lighter per-user fee. Customers finally felt like the pricing flexed with their
business, and the startup regained trust and expansion momentum.

Pattern: The pricing conversation shifts from “why so many seats?” to “look at the value”

Across these stories, one theme repeats: once companies move away from pure pay-per-user
pricing, customer conversations get healthier. Instead of arguing about how many people
really “need” a seat, both sides can focus on:

• How much work the platform is doing
• What outcomes it’s driving (revenue, time saved, tickets resolved, costs reduced)
• How to roll it out more broadly without blowing up budgets

That doesn’t mean you should never charge by seat again. But it does mean you should be
brutally honest: if the core value of your product isn’t headcount, a pure per-user SaaS
pricing model may be quietly working against you.

Bottom line: Question the default before you ship it

Pay-per-user SaaS pricing feels safe because it’s familiar. But “familiar” isn’t the same
as “best.” The cons are real: misaligned value, friction in adoption, limited expansion,
warped incentives, and serious issues for AI-heavy or usage-heavy products.

Before you ship your pricing page, ask:

• What really drives value and cost in our productheads, usage, or outcomes?
• Are we making it easier or harder to get everyone who should use the product into the product?
• Can we blend per-user with usage or value-based elements so pricing grows with impact, not just seat count?

SaaStr’s core message on pricing is simple: treat it as a growth lever, not a one-time
decision. You can start with seat-based pricing if that’s the cleanest way to get to market
but don’t stop there. Keep tuning your model until it reflects how customers truly use and
love your product, not just how many people have logins.