A finance manager is reviewing the card statement and spots two lines that look suspiciously alike: a monthly fee for a task-planning tool, and a larger fee for the office suite everyone already uses, which also contains a task-planning app. Nobody remembers choosing both. Each was approved separately, by different people, for good reasons at the time. Together they mean the business has been paying twice for the same capability, and has been doing so for as long as anyone can recall.
What this is, and what it is not
Mellorca has already looked at specialist tools bought for jobs an existing platform could handle and at several applications doing the same job. This article looks at a narrower and more persistent cause: the business has no record of what its current plans actually include. Without that record, every new purchase is made in ignorance of what is already owned, and every change to a vendor's plan goes unnoticed.
It matters because plans do not stand still. Vendors add features, move them between tiers and bundle them into higher plans. When Microsoft announced commercial price rises effective July 2026, trade coverage reported that the company linked the increases to new AI, security and management features added to its plans. Whether or not a price rise is justified, a change like that shifts what is already inside your subscription. A business that does not read the change may be buying a separate product for something it has just been given.
Why businesses tolerate paying twice
- Plans are described by marketing names, not job lists. The name of a subscription tier tells you little about what it lets you do.
- Purchases are decentralised. A team lead finds a tool, expenses it and moves on. Nobody compares it with the contract the IT provider manages.
- Documentation is long. Edition comparison tables run to dozens of rows. Few people read them end to end.
- The overlap is partial. The paid-for add-on usually does a little more than the built-in feature, so it feels justified even when the extra is never used.
- Nobody is asked. The question "do we already have this?" is rarely part of an approval step.
How the pattern shows up
You will usually find it in a handful of recognisable forms:
- Two or more tools for chat, file sharing, video calls or task lists.
- A separate e-signature, forms or survey service when the suite offers basic versions.
- An additional security or backup product that overlaps with controls already in a higher-tier plan.
- A standalone booking or scheduling service alongside a suite that includes one.
- Staff keeping files in three places because each tool has its own storage.
Microsoft's own developer documentation for Microsoft Graph lists services inside the Microsoft 365 core, among them Bookings, Planner, To Do, OneNote, SharePoint and Teams. Many owners of that suite could not say which of those they have switched on, let alone use. Google's documentation shows the same variation: it groups Workspace into Business, Education, Enterprise and Essentials editions and says Enterprise adds premium security and advanced controls, while Essentials leaves out Gmail. Which edition you hold changes what you already own.
The financial chain
- Direct duplicate fees. The overlap costs the monthly price of the redundant tool, every month, across every seat.
- Licence mismatch. Higher tiers are bought "for one feature", then used by everyone, or lower tiers are kept alongside because the right tier was never identified. See premium plans bought for basic needs.
- Data scattered across tools. The more places work lives, the more time is spent searching and reconciling.
- Training and support load. Staff must learn both tools, and the help desk must support both.
- Security surface. Every additional vendor holds some business or personal data and needs access reviews.
An illustrative cost model
The figures below are assumptions for a hypothetical South African professional-services firm with 30 staff. They are for illustration only; substitute your own invoices.
| Overlapping capability | Assumed monthly cost | Annual cost |
|---|---|---|
| Separate task and project tool (30 seats at R90) | R2 700 | R32 400 |
| Separate forms and survey service | R650 | R7 800 |
| Separate booking service | R450 | R5 400 |
| Separate e-signature plan | R1 200 | R14 400 |
| Total | R5 000 | R60 000 |
Suppose a review finds that the suite already covers half of that need adequately. The recoverable fees are about R30 000 a year. If the duplicated tools also cost each person ten minutes a week in switching and searching, 30 people lose around 260 hours a year. At an assumed internal cost of R250 an hour, that is a further R65 000 in time. The labour figure is the part owners most often overlook, and it depends entirely on the assumptions you choose, so treat it as a scenario, not a prediction.
Why it is not just a one-off tidy-up
A single clean-up helps, but the pattern returns for three reasons. First, new tools keep being proposed. Second, vendors keep changing what is in each tier, so last year's gap may be this year's included feature. Third, staff turnover means nobody who remembers the earlier decisions is left. The fix has to be a standing practice, not a project.
Mellorca's guidance on stopping payment for features the business does not need addresses the other side of this problem. Here the problem is simpler: paying a second time for something you already have.
The commercial trigger point
This becomes pressing at predictable moments:
- A vendor announces a plan restructure or a price rise.
- Someone requests a new tool in a category the business already covers.
- A switch of IT provider or a licensing review is under way.
- Annual budgets are being cut and the software line is being examined.
At each of these, an entitlement list turns an argument into a lookup.
What better looks like
The business keeps a short entitlement register: for each paid platform, the plan held, the main capabilities it includes, who administers it and when it renews. The register is not a technical document. It is a table that a manager can read in five minutes, and it answers one question: before we buy this, do we already own it?
It pairs naturally with the business application inventory described elsewhere on the site. The inventory lists what is running; the register lists what each licence permits. Together they show gaps and overlaps at a glance.
Practical steps
- List your platforms. Start with the two or three large suites: email and documents, accounting, customer records. Note the exact plan name on the latest invoice.
- Check the current comparison pages. Use the vendor's own edition comparison, not a reseller summary, and note the date you checked.
- Pull usage and licence data. The Microsoft 365 admin centre shows licences assigned and unassigned, and usage reports show which services people actually use. Google Workspace admins have comparable reports, depending on edition.
- Match every paid add-on against the register. For each overlap, ask what the add-on does that the built-in feature cannot, and whether anyone uses that extra.
- Trial the built-in option with a small group before cancelling anything. Replace in the order of least risk, and keep the old tool until data has been moved out. Our article on rationalising software without breaking the business sets out a safe sequence.
- Add one gate to approvals: any new software request must name the existing platform it was checked against.
- Re-check at each renewal and whenever a vendor announces changes.
Cautions
Do not assume the built-in version is equivalent. Included tools are often simpler, and the specialist product may genuinely earn its fee if it connects to a core system or is used heavily. Check that data can be exported before you stop using any tool. Also be careful with plan changes: moving down a tier to save money can remove features a team quietly relies on, so confirm with the people who use them.
The bottom line
Paying separately for features already included is rarely a single mistake. It is the result of buying without a list of what is owned. The waste is modest each month but constant, and it is compounded by scattered data and extra training. A one-page entitlement register, checked at every purchase and every renewal, costs very little to keep and turns a recurring leak into a decision the business makes on purpose.
Sources and further reading
- Compare Google Workspace editions - Getting started - Google Workspace Help (last verified 10 October 2026)
- Microsoft Graph overview - Microsoft Graph (last verified 10 October 2026)
- Microsoft 365 Admin Center Usage Reports Overview - Microsoft 365 admin (last verified 10 October 2026)
- Microsoft 365 Commercial Subscription Prices Set to Hike Mid 2026 -- Redmond Channel Partner (last verified 10 October 2026)
Related Mellorca reading
- Software Nobody Measured: Paying for Tools Without Knowing What They Return
- Software Bought Without Approval: The Financial and Security Cost of Shadow IT
- Software That Grew by Accident: The Price of Complexity Nobody Designed