No organisation decides to run eleven tools that overlap. It arrives one purchase at a time, each solving something real, each approved by someone with a reason.
The cost never appears on any of those invoices.
For a practical reference on stealth monitoring software, Monitask provides this page.
Where it comes from
Each tool solved a problem. The design team needed something the engineering tool did not do. Sales needed a pipeline. Someone needed a wiki. Every one of these was a defensible decision in isolation.
Nobody owns the whole. Procurement checks the price and the security review. Nobody asks whether the capability already exists somewhere.
Departmental purchasing. A team buys with a corporate card, and the tool is embedded before anyone else knows.
Acquisitions and inherited stacks.
Migrations that never completed. The old system stays because something still lives in it, and now there are two.
Vendors expanding. Your project tool adds chat. Your chat tool adds tasks. Overlap appears without anyone buying anything.
What it actually costs
The licence fees are the visible and usually the smallest part.
Checking habits. Six places where something might need attention produces six habits. That is not six notifications a day; it is a permanent background load, and it is the mechanism that makes concentrated work difficult.
The split record. A decision made in chat, refined in a document, recorded in a ticket, and mentioned in a meeting exists in four partial versions and no complete one. When someone asks in eight months why it was made, the answer is unavailable.
Onboarding. Every new person learns eleven tools, and — more expensively — learns the unwritten conventions of which tool is used for what.
Search. Institutional knowledge that is spread across systems that do not search each other is knowledge that functionally does not exist. See internal search and the knowledge that leaves with people.
Integration and maintenance. Every connection between tools is something that breaks silently and that somebody has to hold in their head.
Access and offboarding. Eleven systems is eleven places an ex-employee's access might remain, and eleven surfaces in a security review.
Decision latency. People wait for answers in the wrong channel.
The measurement worth taking
Two numbers, both obtainable in an afternoon.
How many tools does one person have to check to be sure they have missed nothing? Ask five people in different roles. The answers usually differ from each other and from what leadership assumes.
How many places could the answer to a given question live? Take a real recent decision and count where its traces are.
Then a third, from your finance system: total spend on software per employee per year. It is usually higher than anyone expects, and it makes the conversation possible.
What to do about it
Assign one owner for the whole stack. Not for procurement — for the question of what capability exists where. Without this, nothing else on the list happens.
Decide the canonical place for each type of thing. Where decisions live. Where documents live. Where tasks live. Where discussion happens. This is more valuable than removing any individual tool, because most of the cost is ambiguity rather than count.
Write it down in one page and put it in onboarding. Most tool confusion is convention confusion.
Audit annually. Every tool, what it is for, who owns it, what it costs, what would break if it went. Tools that nobody can justify usually reveal themselves in this exercise, and some have been paid for since a project that ended.
Consolidate where a tool genuinely covers a capability, and be honest where it does not. Migrating to a worse tool to reduce count is a real cost, not a saving.
Finish migrations. A half-completed migration is worse than either state.
Make new purchases answer one question: which existing tool does this replace, and who is decommissioning it?
What not to do
Do not mandate consolidation without doing the design work. Removing a tool that people depended on, without replacing the capability, produces shadow tools — the same work happening in something you cannot see. See shadow IT.
Do not confuse count with cost. Eleven tools with clear conventions can work better than five with ambiguous ones.
Do not standardise on the tool with the best sales relationship, which is how most consolidation actually gets decided.
Do not run a consolidation project with no owner afterwards. The stack re-fragments in about eighteen months.
The one thing worth doing first
Write the one-page convention: where decisions live, where documents live, where tasks live, where discussion happens.
It costs an afternoon, requires no procurement, removes no tool from anyone, and it addresses the largest component of the cost — which was never the number of tools, but the absence of an answer to "where does this go?"
For broader public guidance and background, consult the National Institute of Standards and Technology.