Per-seat pricing looks fair on the invoice: you pay for each person who uses the tool. The catch is what the invoice doesn't show. Between annual price rises, seats you bought "to be safe," and tier upgrades you didn't plan for, a per-seat bill climbs faster than the team it's meant to track.
For a 30 to 200 person business, that gap is where real money leaks. You hire ten people and your software cost jumps by far more than ten seats' worth. This guide breaks down why per-seat pricing compounds, what it actually costs per employee in 2026, and the concrete moves that bring it back under control.
What you'll learn
- Why per-seat pricing compounds faster than headcount
- What idle seats and annual hikes really add up to
- What SaaS costs per employee in 2026
- When per-seat is fine, and when to act
- The fastest ways to bring the bill back down
What is per-seat pricing?
Per-seat (or per-user) pricing charges you a fixed amount for every named user or licence, usually billed monthly or annually. It's still the dominant way SaaS is sold: most vendors price per user, and even the newer "hybrid" plans that mix usage-based fees keep a per-seat base.
It's popular for a simple reason, it's predictable for the vendor and easy to understand at sign-up. The problem isn't the model itself. It's what happens to that model over three or four renewal cycles, once your team grows and the vendor's price doesn't sit still.
Why does per-seat pricing grow faster than your headcount?
Because three things rise at once, and they multiply rather than add: the price per seat goes up, the number of seats goes up, and the tier each seat sits on goes up. Add idle seats nobody cancels, and a bill that should track headcount quietly outruns it.
Here's the backdrop. SaaS prices have been climbing roughly 11 to 12% a year, according to Vertice's SaaS Inflation Index, close to five times the general inflation rate across G7 countries. Meanwhile Gartner puts corporate IT budget growth at around 2.8% a year. So even if your team and your tools stayed exactly the same, your software bill would still rise several times faster than the budget meant to cover it.
Now layer your own growth on top. Each of these pushes the number up:
- Seat creep. You add people, and each one needs a licence across five, ten, sometimes twenty tools. One new hire isn't one new cost, it's a new line on every per-seat contract you hold.
- Idle seats. Somewhere between 30% and 40% of SaaS licences in a typical organisation go unused, and some 2025 reports put it closer to half. These are seats for people who left, switched roles, or never logged in, still billed, still auto-renewing.
- Annual price hikes. Most contracts allow yearly increases, and vendors use them. Microsoft lifted Power BI Pro from US$9.99 to US$14 per user per month, a 40% jump on a single tool. Salesforce's top CRM tier now runs around US$500 per user per month, roughly double where it sat five years ago.
- Tier and bundle creep. You start on the mid plan, hit a feature limit, and get nudged to the higher tier, for every seat at once. AI features bundled into premium plans are the latest version of this.
None of these is dramatic on its own. Together, across a dozen tools and a few renewal cycles, they're why the bill compounds.
How per-seat costs compound: an illustrative example
A quick, made-up scenario to show the shape of it. Say a 40-person team pays for one tool at $50 per seat per month, $24,000 a year. Then the normal things happen: the team grows, a few seats sit idle, and the vendor lifts the price about 11% each year.
| Year | Seats billed | Price per seat / mo | Annual cost |
|---|---|---|---|
| 1 | 40 | $50 | $24,000 |
| 2 | 45 | $56 | $30,240 |
| 3 | 50 | $62 | $37,200 |
| 4 | 55 | $69 | $45,540 |
| 5 | 60 | $77 | $55,440 |
Headcount grew 50% over five years. The bill grew 131%, more than double, for one tool. Multiply that across a full stack and you can see why finance keeps getting surprised at renewal. (Figures are illustrative; your numbers will differ, but the divergence is the point.)
How much is per-seat SaaS really costing you per employee?
More than most teams think, and the number is rising fast. Zylo's 2025 SaaS Management Index puts average SaaS spend at about $4,830 per employee, a 21.9% jump year over year. Other indices that track contract-level data, like Vertice's, land higher still, near $9,100 per employee. The range reflects different methods, but both point the same way: up, and quickly.
The part that stings is how much of that buys nothing. If 30 to 40% of seats are idle, then a meaningful slice of your per-employee spend is paying for empty chairs. On a $250,000 annual stack, that's $75,000 to $100,000 a year going to licences no one opens.
This is also why per-seat pricing is hard to forecast. Your cost isn't really driven by how many people you employ, it's driven by seats provisioned, tiers chosen, and prices set by the vendor. Three of those four levers aren't fully in your control.
When per-seat pricing is actually fine
It's worth being fair here, because per-seat isn't always the villain. For a small, stable team using a tool everyone genuinely logs into every day, per-seat is simple and reasonable, you pay for value you use. The model works when usage is high, headcount is steady, and the tool does one job well.
It breaks down when you're scaling, when several tools overlap, or when usage is patchy across seats. That's the situation most growing mid-market businesses are actually in, which is why the bill and the headcount drift apart.
How to bring per-seat costs back under control
Start with what you can act on this quarter, then move to the structural fixes. In order of speed-to-savings:
- Reclaim idle seats first. Pull last-login data for your top tools and deactivate seats dark for 60 to 90 days. This needs no migration and returns money immediately.
- Right-size your tiers. Check whether you're paying for a premium plan to use one or two features. Downgrading is often a same-day change.
- Audit the whole stack. List every tool, its real annual cost, and actual usage so you can see overlaps and waste in one place. Our walkthrough on how to audit your SaaS stack in an afternoon covers this step by step.
- Time your renewals. Start renewal conversations 90 to 120 days early, armed with usage data, and push back on increases. Switching leverage is real even when you don't switch.
- Consolidate overlaps. Where two or three per-seat tools do one job, standardise on one and cancel the rest. For deeper context on where the money really goes, see more on the real cost of your SaaS stack.
- Question the model itself. For the workflows you depend on most, the ones where you're paying rising per-seat fees across multiple overlapping tools, it's worth asking whether renting is still the right call, or whether owning a single tool that does exactly what you need would cost less over five years.
That last point is the one most teams never reach, because per-seat pricing trains you to think in monthly increments rather than five-year totals. The math in the table above is the argument for at least asking the question.
Frequently asked questions
Is per-seat pricing the same as per-user pricing?
Yes. The terms are used interchangeably, both charge a fixed fee for each named licence or active user.
Why does my SaaS bill go up even when my team size stays the same?
Two main reasons: vendors raise prices each year (SaaS prices have risen around 11 to 12% annually per Vertice), and you may still be billed for idle seats and higher tiers you no longer need. Price and tier creep push the bill up independently of headcount.
What percentage of SaaS licences typically go unused?
Industry research consistently puts it at 30 to 40% of licences in a typical organisation, with some 2025 reports finding closer to half. Idle seats are usually the fastest waste to recover.
How much do companies spend on SaaS per employee?
Estimates vary by study. Zylo's 2025 index reports about $4,830 per employee (up nearly 22% year over year), while contract-level trackers like Vertice report figures closer to $9,100. Either way, the per-employee cost is climbing fast.
Is it cheaper to build a custom tool than to pay per-seat forever?
Sometimes. It depends on how many overlapping tools you're replacing, how stable your needs are, and the five-year total rather than the monthly fee. For high-overlap, business-critical workflows it can pay off; for a single well-used tool, per-seat is often fine. Run the five-year comparison before deciding.
See what per-seat pricing will cost you in five years
Per-seat pricing hides the real number behind a tidy monthly fee. The way to see it is to project it forward, annual price rises, seat growth, and all. Estimate your five-year SaaS spend with our calculator, it takes about 30 seconds, no email required. Once you've seen the number, you can decide what's worth keeping, cutting, or replacing with a tool you own outright.