Two years ago, during an otherwise ordinary quarterly review, our head of customer success pulled up an account screen that made the room go silent.
One of our enterprise clients—a fast-growing logistics company with over 300 employees—had exactly three paid seats on our platform. Those three seats, however, were running nearly round-the-clock automations, pinging our database hundreds of thousands of times a day, and driving about $40,000 in monthly operational value for their business.
They were paying us $147 a month.
When we looked closer, the reality was even more humiliating: the team had created a shared calendar invite containing the master login credentials. Whenever someone needed to pull a report or run a workflow, they all logged into the same master admin account.
We were furious at first. We talked about implementing IP restrictions, forcing single sign-on (SSO) locks, and adding device limits to stop password sharing. But as the frustration settled, an uncomfortable truth emerged: our customers weren’t acting maliciously. They were simply responding rationally to a broken economic model.
For two decades, the per-seat pricing model was the golden goose of B2B SaaS. Today, it is quietly strangling product adoption, misaligning incentives, and leaving massive revenue on the table. Here is why we abandoned user-based billing, what we built instead, and how shifting to a value-first pricing strategy completely transformed our Net Revenue Retention (NRR).
The Fatal Flaw of Per-Seat SaaS Pricing
The per-user subscription model was popularized by early cloud giants like Salesforce. In the early 2000s, replacing bulky on-premise licenses with a predictable monthly fee per human user sitting in a cubicle was revolutionary.
Today, that same model creates a direct conflict between your revenue goals and your user's desire to collaborate.
Traditional Per-Seat Dynamics:
More Team Members Added --> Software Bill Increases
Result: Managers restrict invites, share logins, and limit tool adoption.
When you charge per user seat, you penalize your customers for spreading your tool across their organization. Instead of encouraging organic product virality, you force team leads to become internal gatekeepers who ask: "Does Sarah in marketing really need access, or can someone just export a CSV for her once a week?"
Every time a customer decides not to invite a colleague to save $49 a month, your software becomes that much easier to churn out of when budget cuts arrive.
The AI Tsunami: Why Seat-Based Billing Cannot Survive
If product virality issues weren't enough to kill per-seat pricing, modern generative AI and workflow automation have delivered the final blow.
Consider what happens when software transitions from being a tool (which helps a human work faster) to an agent (which does the work autonomously).
- The Old Paradigm: A support team uses a SaaS platform to handle tickets. As the company grows, they hire 10 more agents and buy 10 more seats. SaaS revenue scales linearly with customer headcount.
- The New Paradigm: A company implements autonomous AI agents inside the SaaS platform. The software resolves 70% of inbound tickets without human intervention. The company downsizes their tier to 3 human supervisors.
Under a per-seat model, the SaaS vendor that just delivered 5x more operational efficiency gets rewarded with a 70% drop in software revenue.
Tying software value to human headcount in an era where software exists to reduce human headcount is an unsustainable business strategy.
What We Learned Auditing Our Churn Data
Before changing our pricing architecture, we audited 14 months of churn and downgrade surveys. The data exposed three distinct failure patterns in our seat-based model:
- The "Zombie Seat" Backlash: During economic downturns, CFOs ran software audits. Finding 20 unused seats on an annual contract generated immediate resentment, leading to aggressive downgrades or outright cancellations.
- The Collaboration Ceiling: Accounts with 1 to 3 users had an annual churn rate of 34%. Accounts with 8 or more users churned at just 4%. Per-seat pricing was directly discouraging the very behavior that prevented churn.
- Value Disconnect: Small agencies handling massive client volumes were getting enterprise-grade value for entry-tier pricing, while large corporate departments with light usage felt gouged.
Comparing Modern SaaS Pricing Frameworks
Transitioning away from pure seat-based tiers requires matching your pricing metric to how your product actually delivers value.
| Pricing Model | Best Suited For | Primary Advantage | Main Risk |
|---|---|---|---|
| Per-Seat (Legacy) | Core workspace tools where every employee actively works daily (e.g., Slack, Google Workspace). | Highly predictable MRR for both vendor and buyer. | Encourages password sharing; penalizes organizational adoption. |
| Pure Usage / Consumption | Developer infrastructure, compute, API integrations (e.g., Snowflake, Twilio, AWS). | Zero barrier to entry; scales directly with customer infrastructure. | Unpredictable monthly bills can scare enterprise procurement teams. |
| Outcome-Based | Workflow automation, AI agents, revenue-generation tools (e.g., resolving tickets, generating pipeline). | Perfect alignment between customer ROI and software cost. | Difficult to define and attribute concrete "outcomes" across complex edge cases. |
| Hybrid (Platform Fee + Value Metric) | Most B2B SaaS platforms combining a workspace with backend automation. | Predictable baseline revenue with uncapped upside as customer usage grows. | Requires clear in-app dashboards to track usage thresholds. |
The Hybrid Model: What We Built
We realized that going 100% consumption-based would introduce too much revenue volatility for our finance team and too much billing anxiety for our customers.
Instead, we designed a Hybrid Value Model:
- Unlimited Free Viewer & Collaborator Seats: We made user seats practically free. Anyone inside an organization can view dashboards, leave comments, and review reports.
- Predictable Base Platform Tiers: A fixed monthly platform fee (Starter, Growth, Scale) that covers core infrastructure, security compliance, and priority support.
- Value-Metric Billing (The Growth Engine): We identified the single metric most correlated with our customers' business success—in our case, Active Monitored Workflows. Customers buy capacity blocks for these workflows.
Our New Pricing Formula:
Total Cost = Base Platform Fee + (Active Workflow Blocks Consumed)
The psychological shift was immediate. Managers stopped rationing logins. They invited their entire engineering, product, and operations teams on day one.
Within six months, our average user count per account jumped from 3.8 to 14.2. More importantly, when those 14 people interacted with our product weekly, our software became deeply embedded across departments, cutting our gross churn in half.
How to Audit Your SaaS Pricing Metric
If you suspect your current pricing structure is holding back your product-led growth, run through these diagnostic steps:
- Identify Your "Aha!" Metric: What action inside your product directly correlates with your customer making or saving money? (e.g., emails sent, transactions processed, storage utilized, candidates screened).
- Check the Seat-to-Value Ratio: Calculate the revenue generated per active daily user across your top 10% and bottom 10% of accounts. If the difference is massive, your pricing is disconnected from reality.
- Survey Cancelled Accounts for Friction: Look for keywords like "paying for people who barely log in" or "couldn't justify the cost for the whole department."
- Run a Grandfathered Pilot: Never force existing customers into a new pricing structure overnight. Pick a cohort of 50 new inbound signups and test a value-metric model against your control group to measure conversion and expansion rates.
The era of charging companies simply for looking at a screen is coming to an end. By aligning your revenue with the tangible business value you create—rather than the number of email addresses in your database—you remove friction for your users and unlock durable, expansion-driven growth for your business.
How is your team handling the balance between predictability and usage-based expansion in your current pricing model?
Top comments (0)