Glossary
Tool sprawl
The expensive part is not the licences. It is that nothing is authoritative any more.
Definition
Tool sprawl is the accumulation of overlapping software across an organisation to the point where no single tool is the system of record for a given kind of work. Symptoms include the same information maintained in several places, licences nobody uses, decisions recorded where the people affected will not find them, and staff who cannot say which tool is authoritative.
- Apps per company, 2025
- 101 average (Okta)
- Main cost
- Fragmented context, not licences
- Distinct from
- Shadow IT
How much software a company actually runs
Okta's Businesses at Work 2025 report, drawn from its own customer base, put the average number of applications per organisation at 101, the first time the figure crossed one hundred, after sitting below ninety from 2019 through 2023. That is the identity-provider view, so it counts anything anyone signed into, which is exactly the population that matters here.
The number is a symptom rather than the disease. Ninety of those applications can coexist happily. Sprawl is what happens in the small subset that overlap: three places to write a document, two places to track a task, four places a decision could plausibly have been recorded.
What it actually costs
Licence spend is the easiest cost to measure and rarely the largest.
Context fragmentation
The requirement is in one tool, the discussion in another, the task in a third, the file in a fourth. Reconstructing what was decided becomes archaeology, and the reconstruction is done by the most expensive people in the company.
Duplicate maintenance
The same roadmap kept in two systems drifts within a fortnight. Whichever copy someone reads is now a coin flip.
Per-seat multiplication
Each overlapping tool charges per person, so cost scales with headcount times tool count rather than with work done.
Onboarding tax
A new hire must learn not just the tools but the unwritten convention about which one is authoritative for what. That convention is rarely written down, because it is not a decision anyone made.
Commonly confused with
| Term | What it means | The difference |
|---|---|---|
| Shadow IT | Software procured without IT approval | A cause of sprawl, not the same thing. Fully approved tools sprawl too. |
| SaaS sprawl | Unmanaged growth in subscription count and spend | Framed around procurement and cost. Tool sprawl is framed around overlapping function. |
| Technical debt | Accumulated shortcuts in a codebase | Lives in the product. Tool sprawl lives in how the company works. |
| Integration debt | Growing web of connections between systems | Often the attempted cure for sprawl, and a cost centre of its own. |
The two ways out, honestly stated
Consolidation means moving work into fewer products, which lowers the bill and restores a single system of record, at the cost of losing whatever the specialist tools were genuinely better at. Integration means keeping the tools and connecting them, which preserves capability but adds a maintenance surface and never quite makes any one place authoritative.
Polaris takes the consolidation position for tasks, docs and team chat, and the integration position for everything else: Slack, Notion, Linear, GitHub, Gmail, Google Calendar, Google Drive, Figma, HubSpot, Stripe, Supabase, WhatsApp and Instagram are in the connection catalog, so a team can move the system of record without abandoning the tools around it.
Related terms
All-in-one workspace
One data model behind documents, tasks and conversation, instead of three products and a pile of integrations.
Per-seat pricing
The bill tracks headcount, which is only a proxy for value received.
Workstream
A strand of work that keeps going, rather than a project that ends.
Replacing the stack you already pay for
Every plan here says which of your tools has an importer, which has a connector, and which has neither.
Tool stack cost for a 25-person team
The size where paying monthly instead of annually costs $1,650 a year on its own.
Every tool a Polaris worker can be given
One catalog, one credential per tool per organisation, authorized by an owner and used by every worker who carries it.
Questions people ask
+How do I know if my team has tool sprawl?
Ask five colleagues where a given decision from last quarter is recorded and see whether the answers agree. Disagreement is the diagnostic. Counting subscriptions measures spend; that question measures whether anything is authoritative.
+Is consolidating always the right answer?
No. Specialist tools exist because general ones handle some jobs badly, and forcing a design team out of Figma or an engineering team off a workflow engine they depend on trades one problem for a worse one. The tools worth consolidating are the overlapping ones, not the good ones.
+Does AI make tool sprawl better or worse?
Worse before better, on current evidence. Most teams have added AI subscriptions on top of their existing stack rather than replacing anything, which increases both the bill and the number of places where work happens without leaving a shared record.
Related
All-in-one workspace
One data model behind documents, tasks and conversation, instead of three products and a pile of integrations.
Per-seat pricing
The bill tracks headcount, which is only a proxy for value received.
Usage-based pricing
The bill follows consumption, which cuts both ways for buyer and vendor.
Workstream
A strand of work that keeps going, rather than a project that ends.
Replacing the stack you already pay for
Every plan here says which of your tools has an importer, which has a connector, and which has neither.
Tool stack cost for a 25-person team
The size where paying monthly instead of annually costs $1,650 a year on its own.
The cost of AI subscriptions for a team
Five figures a year at fifty people, and no shared record of what any of it produced.