Four Tools, One Job: The Real Cost of Departments Buying Their Own Software

The tolerated pain

Marketing signed up for a project board in March because the agency recommended it. Operations found a different one in June because marketing's did not suit shift planning. Finance already had a third inside the accounting package, and the sales manager keeps a fourth on a personal card because "it is just R250 a month". Nobody decided to pay for four tools that solve one need. Each purchase was reasonable in isolation, small enough to avoid a conversation and quick enough to solve a real Tuesday-afternoon problem.

The result is a business paying several times for the same capability, with information scattered across products that do not speak to each other. This article looks at the cost of that pattern. It is different from not knowing what you subscribe to, covered in unknown software subscriptions and their invisible recurring cost. Here the subscriptions may be perfectly visible on the bank statement. The problem is that they overlap, and that the overlap splits the data.

Why overlap happens in otherwise well-run businesses

Departments buy tools to remove their own friction, not to optimise the company. Almost every tool today can be bought online with a card in ten minutes, so the purchase never reaches a procurement desk. A team lead with a problem and a monthly budget line can solve it before lunch.

Speed beats coordination. Asking IT or finance for approval takes a week. A free trial takes five minutes.
Each team describes the need differently. Sales calls it "pipeline tracking", operations calls it "job scheduling" and support calls it "ticketing". They are variations of the same underlying need: a shared list of work with owners, stages and due dates.
Nobody owns the whole map. Without one person looking across departments, overlap is invisible until a contract renews.
Existing platforms are under-used. The business already pays for a suite with a perfectly adequate feature, but only one person knows it is there.
Switching feels harder than adding. Moving a team off a tool means data export and retraining. Adding another tool is easier in the short term.

Microsoft's documentation on Defender for Cloud Apps lists "Shadow IT discovery" and visibility into cloud app usage as core capabilities of that product. The fact that large vendors build whole products to find out which applications people are using shows how common unmanaged adoption is. A smaller business does not need that tooling to start, but it does need to ask the same question.

Operational symptoms

two or more departments tracking the same kind of work, such as tasks, customers or approvals, in different products;
staff asking "which one are we using for this?" at the start of every new project;
customer details stored in a CRM, a quoting tool, a mailing platform and a support desk, with no agreement on which is correct;
exports and copy-paste between tools just to produce one management report;
renewals arriving from vendors the finance team has never heard of;
onboarding checklists that list six logins for a new starter, and offboarding that misses two of them.

How the pain becomes money

The visible cost is the subscription itself. The larger costs are usually the ones around it.

Duplicated subscriptions: paying for several licences of overlapping tools, often at monthly retail pricing because nobody negotiated a combined deal.
Dual data entry: staff re-keying the same facts into more than one product. That labour is paid for every month.
Disconnected data: a customer is updated in one tool and stays wrong in another, causing wrong quotes, missed follow-ups and duplicate contact. The wider problem is described in business systems that do not talk to each other.
Training and support time: each tool needs its own onboarding, its own admin and someone who "knows how it works".
Security and access exposure: every extra tool is another place where a former employee may still have a login, another vendor holding business or customer information, and another thing to include in a POPIA review.
Lost purchasing leverage: several small contracts rarely earn the discount one larger contract would.

An illustrative cost model

This example is illustrative. All figures are assumptions for a hypothetical business with 45 employees in Johannesburg.

Assumption	Value
Overlapping tools covering the same need	4 tools, 3 of them redundant
Average monthly cost of each redundant tool	R3,200
Staff who re-key data between tools	8
Hours per person per week re-keying or reconciling	1.5
Loaded hourly cost	R200
Working weeks per year	46
Admin time on separate logins, renewals and support	3 hours a week at R300

Redundant subscriptions: 3 × R3,200 × 12 = R115,200
Re-keying and reconciling: 8 × 1.5 × R200 × 46 = R110,400
Administration: 3 × R300 × 46 = R41,400
Illustrative total: about R267,000 a year

The subscriptions are less than half of the total. That ratio is typical of the pattern: the invoice is the small part. Your own figures will differ, and some re-keying will remain even after consolidation, but the exercise is useful because it shows where to look first.

Why the pain is tolerated

Each tool is cheap, so nobody feels the total. The people who use a tool are usually happy with it. The costs that matter, such as inconsistent data and duplicated effort, are spread across several teams so no single manager sees them. The invoices are small and arrive on different dates and on different cards. There is also a quiet fear: consolidating means telling a team that the tool they chose is going away.

When it becomes commercially urgent

a customer receives two different answers because two teams' tools disagree;
a data-protection request or incident shows nobody knows which tools hold customer information;
annual renewals cluster and the total finally appears in one budget meeting;
the business plans a CRM, ERP or finance system change and finds half its process lives in side tools;
a key employee leaves and the team discovers they alone administered a critical tool.

What better looks like

The aim is not a single product for everything. It is a deliberate choice for each business need, with a named owner and a clear answer about where the data lives.

Build the inventory. Combine bank and card statements, accounts-payable records and a staff survey. Capture the tool, the need it meets, the cost, the owner and the data held.
Group by need, not by product. Put all tools that handle tasks together, all that handle customer records together, and so on. Overlap becomes obvious.
Choose a system of record. For each need, decide which tool holds the authoritative data, as explained in how to decide which system owns which data.
Check what the existing platforms already do. Often the suite you already pay for covers the need; see expensive tools for tasks the existing platform already handles.
Set a simple purchasing rule. Any new tool needs a named owner, an answer to what it replaces and a check of what data it will hold. The questions in before you buy another tool, ask these questions work well as a one-page form.
Retire in stages. Export data, move the team, keep a read-only copy for a defined period and cancel on the renewal date.

Access control belongs in the same exercise. Microsoft's application management overview describes managing the applications an organisation uses and who can reach them, which is the discipline a small business needs in simpler form: know the list, know the owner, know who has a login.

Practical next actions

Pull the last three months of card and bank statements and list every software charge.
Ask each department head: "which tools does your team pay for, and what for?"
Group the list by business need and mark the overlaps.
Pick one overlap with the highest combined cost and the least data risk, and retire one tool.
Diarise every renewal date so decisions are made before the charge, not after.
Adopt a one-page rule for new tool requests.

Bottom line

Duplicated tools are rarely a purchasing failure. They are the natural result of capable teams solving their own problems without a shared picture. The subscription cost is real, but the larger bill is paid in re-keying, disagreement between records and the time spent managing logins and renewals. A shared inventory, a named owner for each business need and a short buying rule remove most of the waste without taking tools away from the people who depend on them.

Sources and further reading

Overview - Microsoft Defender for Cloud Apps (last verified 10 October 2026)
What is application management? - Microsoft Entra ID (last verified 10 October 2026)
Overview of the Microsoft Entra application gallery - Microsoft Entra ID (last verified 10 October 2026)