Blog
The app per employee problem
The app per employee problem is the steady rise in the number of separate SaaS applications each worker touches, and it inflates spend because overlapping tools renew on their own clocks with nobody owning the total. Count the real app load across your portfolio, retire the duplicates before each renewal, and the audit itself becomes the evidence that wins a better deal.
Key takeaways
- The app per employee problem is SaaS sprawl measured per head: more tools per worker than any single owner tracks or needs.
- Industry surveys put large enterprises well past one hundred SaaS applications, with heavy overlap across collaboration, project, and analytics tools.
- Duplicate capability is the costliest form of sprawl because two tools do one job and each renews on its own clock.
- A portfolio level app audit turns sprawl into leverage: consolidate first, then negotiate the survivors on a smaller, cleaner base.
What is the app per employee problem?
The app per employee problem is the quiet growth in how many separate SaaS applications each worker uses, to the point where no single owner can name the full list or defend it. A finance manager logs into an accounting suite, a planning tool, two analytics products, a collaboration platform, a project tracker, and a handful of point tools, and most of those arrived through different buyers in different years. The cost is not one big line, it is dozens of medium lines that never get reviewed together, and that is exactly why the total keeps climbing.
It is a portfolio problem disguised as a series of small renewals. Each tool looks reasonable on its own. The damage shows up only when you divide total SaaS spend by headcount and watch that number rise year over year while productivity does not move with it. Naming the problem at the portfolio level is the first step, because a cost you never total is a cost you never negotiate.
How many apps does the average employee really use?
More than most leaders expect, and the count rises every year. Published SaaS management surveys through 2025 and into 2026 put large enterprises well past one hundred distinct applications in the portfolio, with mid market companies commonly running several dozen. The per employee figure varies by role, but knowledge workers routinely touch ten or more sanctioned tools plus whatever shadow SaaS they expensed without telling procurement. These figures are indicative and depend on how an organisation counts a tool, but the direction is consistent across every credible source.
The growth has a mechanism. Teams adopt a tool to solve one task, the task gets solved, and the tool stays. The next team picks a different product for an overlapping task, because the first tool was never offered to them, and now two products cover the same ground. Multiply that across departments over five years and the per head app load doubles without anyone deciding it should.
Why does app sprawl cost more than the licence fees suggest?
Because the licence is only the visible part. Every additional application carries an administration cost, an identity and security surface, an integration burden, and a renewal that someone has to manage. The hidden tax is duplicate capability: two project tools, three places to store files, four analytics products that each ingest the same data. You pay full rate for each, and the overlap means you are buying the same job more than once.
The four shapes of sprawl
Sprawl is not one thing. Naming the shape tells you the reclaim move.
| Shape of sprawl | How it shows up | The reclaim move |
|---|---|---|
| Duplicate tools | Two products covering one job, each on its own renewal date | Consolidate to one and route the saved spend into the deal you keep |
| Shadow SaaS | Expensed subscriptions never visible to procurement | Surface them through expense and single sign on data, then fold them into the portfolio |
| Edition overshoot | Premium tiers bought for teams that use only the basics | Right size the edition to adopted features before the renewal locks the count |
| Orphaned seats | Licences assigned to leavers and dormant accounts | Reclaim inactive seats so the uplift never lands on waste |
How do you measure your real app load?
You build one list from three sources and reconcile them. Pull the single sign on directory for every application users actually authenticate into, pull the expense system for subscriptions bought outside procurement, and pull the contract register for what you are committed to. The overlap between those three is your sanctioned portfolio. The gaps are the problem: tools in single sign on that no contract owner knows about, and contracts for tools nobody logs into. The reconciled list, divided by headcount, is the app per employee number you manage from here.
Do this before any individual renewal, not during one. A vendor proposal arrives anchored on last year's quantity and tier, and if you only look at that one tool you negotiate inside the vendor's frame. Looking across the portfolio first lets you spot the duplicate that makes this renewal optional, which is a far stronger position than haggling a discount on a tool you could retire.
How does the audit become renewal leverage?
Consolidation creates a real alternative, and a real alternative is the only thing that moves price. When you can show that two tools overlap, the renewal of the weaker one becomes a genuine decision rather than a formality. That is leverage you can use two ways: retire the tool and remove the spend entirely, or keep it and trade the credible threat of removal for a better rate, a tier right size, and contract protections on the survivor. Either path beats renewing both on autopilot.
The 2026 backdrop sharpens the point. Published analyses put AI driven renewal asks at 20 to 37 percent against a historical 3 to 9 percent annual uplift, and about 60 percent of vendors mask increases rather than state them plainly. Every duplicate tool you carry into that environment is an aggressive uplift applied to capability you already own elsewhere. Cutting the app load before renewal season removes the surface those increases would otherwise multiply.
What is the move before your next renewal cycle?
Total the portfolio first. Reconcile single sign on, expense, and contract data into one app per employee number, sort the four shapes of sprawl, and decide which tools are candidates to retire before their renewal dates arrive. Then bring that evidence to each negotiation so the base is clean before you ever discuss a rate. The full sequence, from portfolio audit to signature, sits in the SaaS Renewal Playbook, and the discovery method runs alongside it in our wider buyer side work.
Cut the sprawl before you renew.
Read the SaaS Renewal Playbook for the full portfolio method, see how to start by discovering shadow SaaS spend, and reclaim the waste by cutting shelfware before the renewal. When you are ready to act, our SaaS portfolio review team runs it with you.
Download guide →Published market figures reflect 2026 SaaS pricing analyses and are labelled indicative where appropriate.