How Many Apps Does the Average Company Use? The Real Number by Company Size
How many apps does the average company use? Ask your ops lead to name every tool the company pays for, and watch them guess. The subscription list is a start, but finance sees one set, IT sees another, and the team is quietly living in a third. “How many apps does the average company use?” sounds like a trivial number to look up. It isn't — because every dataset measures something different, and the honest range is wide: 47 apps for a tech startup, 93 for an average Okta customer, 144 for an average business in 2026, and 660 for a large enterprise. The number that matters for your company is the one you measure consistently, compared against teams of your size, with your headcount as the biggest variable.
This post gives you the current benchmarks, explains why the averages disagree by a factor of ten, and shows what the count actually costs once you pass a few hundred employees.
The short answer: 93 to 144 — and it depends who's counting
Headline averages cluster in the low three digits, and which one you see depends on the dataset. Vertice's company tech stack data, which tracks SaaS spend across its managed customers, puts the average business at 144 individual SaaS applications in Q2 2026 — up from 138 in Q1 2026 and 131 in June 2025. That's six new tools added in a single quarter, and Vertice attributes much of the growth to specialist AI point solutions landing on top of existing stacks rather than replacing them.
Okta's Businesses at Work report, built from more than 18,800 customer environments, found the average company deploying 93 apps — up 4% year over year from 89, the first real jump after the figure stalled at 89 for two straight years. Meanwhile, BetterCloud's 2025 State of SaaS survey of roughly 600 IT professionals lands on 106 apps, down from a peak of 130 in 2022 as teams consolidated.
So who's right? All of them, about different things. Okta counts apps provisioned through an identity platform — the sanctioned, SSO-connected stack. BetterCloud asks IT professionals what their company runs, which captures more of the long tail. Vertice counts what its finance-managed customers actually pay for, which catches licenses that exist outside the official catalog. None of these is “wrong”; they just sample different slices. The useful habit is to always ask how this number was counted before you compare it to yours.
The headline average is a trap. The only benchmark that tells you anything is the one sized to your headcount.
Headcount is the biggest variable
Company size moves the number more than anything else in the data. Okta's report splits its customers by employee count, and the spread is enormous: companies with 2,000 or more employees run an average of 231 apps (up 10% from 211), while smaller companies run 72 and tech startups with under 100 employees run just 47. Country matters too — the same report shows US companies averaging 105 apps while Canadian companies average 66.
Zylo's 2025 SaaS Management Index, which analyzed more than 40 million licenses, paints an even steeper ladder: small businesses with 1–500 employees run about 152 apps, mid-market companies near 275, and enterprises with 10,000 or more employees run roughly 660.
| Company size | Zylo 2025 (40M+ licenses) | Okta 2024 (18,800+ orgs) |
|---|---|---|
| Tech startup (under 100 staff) | — | 47 apps |
| Small company (under 500–2,000) | 152 apps (1–500) | 72 apps (under 2,000) |
| Mid-market | 275 apps | — |
| Large enterprise (2,000–10,000+) | 660 apps (10,000+) | 231 apps (2,000+) |
Two things follow. First, a 400-person company running 200 apps may be leaner than a flat average suggests — it's below its mid-market norm, not above it. Second, app counts scale with headcount because departments duplicate each other's choices, not because individual employees need more tools. Zylo found companies typically run 15 duplicate training tools, 11 duplicate project-management tools, and 10 duplicate collaboration tools at the same time, bought by different teams without a shared procurement process.
The count is a symptom — the switching is the cost
App sprawl isn't expensive because of license fees alone; it's expensive because each extra tool is another place information can live. The human cost shows up in switching. A widely cited Pegasystems study of office workers found people switch between applications and websites more than 1,100 times a day, perform an average of 134 copy-and-paste actions to move data between tools, and spend only 28% of active work time inside structured applications built for the task. The same study found error rates are 50% higher in unstructured tools like email, and workers juggling 30 or more applications in a shift have a 28% higher error rate than those using fewer.
Add the financial layer. Zylo's index found companies use only 49% of the licenses they provision, and the waste averages $21 million a year per organization — up from $18 million the year before, even as headline app counts fell. Consolidation cuts the number of tools without fixing over-provisioned seats inside the ones you keep.
The structural problem is ownership. CIO Dive's coverage of Productiv's sprawl research reports that line-of-business teams now manage more of the company's app inventory than IT does — 56% of app ownership — with departments typically using 40 to 60 applications each. Nearly three-quarters of IT leaders in a Zluri and Pulse survey named security as their top sprawl concern. When nobody owns the catalog, nobody owns the duplication either: the same status update gets written in Slack, a PM tool, a doc, and an email chain, and that's before we get to the cost of project updates getting lost inside Slack.
How to use the benchmark without benchmarking wrong
Measure your own stack before you cut anything. Pull the billing export, ask IT what's provisioned, and ask each team what they actually open daily — three lists, three sizes, all legitimate. Then compare against your size band, not the flat “93” or “144.”
Follow the money more than the count. Zylo's duplicate-tool finding is the practical signal: if you can name two tools that do the same job for the same team, that's a cut waiting to happen. And remember that consolidation has a ceiling. The teams you see in the data that “reduced” their count mostly killed obvious duplicates; the harder tradeoffs — retiring a tool a department loves because the company already pays for a better one — are where real savings live, and where governance, not counting, matters.
Finally, recognize what the count can't tell you. The number of apps says nothing about whether information flows between them. That's why we wrote about the real cost of tool sprawl before, and it's why the follow-up question matters more than the total: how many of those apps does a project's status actually live in? For most teams it's three to five. You can't consolidate your way to zero, but you can stop treating five places as one.
What good looks like
A team with healthy tooling doesn't have the fewest apps; it has a small, stable core that everyone agrees on — one messaging tool, one place for documents, one place for projects — with additions governed rather than ignored. The benchmark to track isn't the app count; it's the number of places a project's status lives, and how long it takes to find the latest truth on any workstream. Teams that fix this don't necessarily delete tools. They make the count irrelevant by making information flow regardless of where it was typed.
That's exactly the gap the project-limit research keeps pointing at: leaders aren't short of updates, they're short of a single view of them. Asa.Team's Project Intelligence pulls project updates out of Slack, Teams, Telegram, and WhatsApp into one timeline, so the status that used to live in five tools shows up in one view — without forcing anyone to give up the tools they already use. It applies the benchmark lesson at the coordination layer: fewer places to look, not fewer tools to argue about. See it in the interactive demo.
Frequently asked questions
How many apps does the average company use? Headline averages land between 93 and 144 depending on the dataset: Okta's 2024 report counts 93 company-wide, BetterCloud's 2025 survey finds 106, and Vertice's Q2 2026 data shows 144. By segment the range is far wider — 47 apps for a tech startup up to 660 for a large enterprise.
How many apps does the average employee use at work? Company counts are pool numbers, not per-person numbers. Per-person usage is much smaller — most knowledge workers live in a handful of daily tools — but the switching tax is heavy: office workers switch between apps more than 1,100 times a day and perform around 134 copy-and-paste actions to move data between them.
Is app sprawl getting better or worse? Both, depending on what you measure. BetterCloud's survey shows the average count falling from 130 in 2022 to 106 in 2025 as teams consolidated obvious duplicates. Vertice's spend-tracked data shows stacks growing again in 2026, to 144, driven by specialist AI tools. The two are consistent: consolidation trims the tail, then new categories grow back over it.
How many apps is too many? There's no universal ceiling, but the warning signs are structural: multiple tools in the same category for the same team, license utilization below half (Zylo's average is 49%), and no single owner for the app catalog. When status and project information are spread across five tools, count is no longer the point — findability is.
The next time someone asks how many apps the average company uses, you have the honest answer: it depends on how you count, and on how big you are. Benchmark against your own size band, watch the duplicates, and remember the number that actually hurts is the number of places a project's status can hide. Cut what you can, consolidate what you keep — and make the tools you do run share their truth with each other, so nobody has to go hunting for it.