KuTh Consultants (Pty) Ltd

Corporate & Business · Telecommunications & Technology

Individual allowances waste money in both directions at once

Some users never approach theirs; others exceed theirs and pay out-of-bundle. Pooling removes a cost that exists only because the allowances were separate — and six in ten tariff records here were data top-ups, not voice plans.

15.0%
quoted reduction on pooled spend
353
tariff records classified
60.6%
of records were data top-ups
10%
usage tolerance, not a cash saving

Proof context: A large multi-entity mobile estate across the major network providers

One capability, applied two ways

This engagement and the NPO Mobile mandate are two examples of the same KuTh mobile capability applied to very different estates — not two separate services.

A multi-entity corporate estate with pooling potential and an NPO data estate bought through a reseller need different answers. Both are documented in full so a reader can go to whichever resembles their own position.

The situation

Hundreds of individual allowances, managed individually

The organisation ran a large multi-entity estate mixing corporate-managed accounts, store and reseller-managed connections, data-only services, voice plans, top-up tariffs, roaming and specialist connections.

KuTh mapped the estate across the major providers, then concentrated the quantified commercial review on the largest voice account and the group account where reliable usage data existed. The published percentage describes that analysed baseline rather than every connection in the group.

The tariff estate

353 records, and what they turned out to be

Scroll table sideways →

Tariff familyCountAnalytical relevance
Data top-up214 (60.6%)The largest family by some distance — which makes data allocation, not voice, the design problem.
Voice top-up65 (18.4%)A material individual-allocation population that pooling could absorb.
Standard voice63 (17.8%)Traditional plans alongside top-up and integrated services.
Standard data10 (2.8%)Data-only connections outside the top-up family.
Machine-to-machine1 (0.3%)A specialist telemetry-type connection requiring separate treatment, not ordinary user pooling.

Six in ten tariff records were data top-ups. An optimisation aimed at voice plans would have addressed the smaller half of the estate.

Results

What was quoted, and what came with it

Scroll table sideways →

MeasureStatusResult
Pooled enterprise modelQuoted / commercially validated15.0% lower — a supplier proposal against the analysed baseline for the 352-line pooled model.
Usage toleranceIncluded commercial value10% headroom above the baseline pool before the usage band triggers price movement. Not a direct cash saving.
Spend-management platformNegotiated value addCentral visibility, reporting, policy monitoring and administration, included in the commercial design.
Device fundingNegotiated value addA funding mechanism for qualifying new and upgrade users. Existing device commitments remained the client's responsibility.
Group account architectureIdentified / designCentralised commercial treatment that uses group leverage without collapsing the separate legal liability of participating entities.

Why the 10% tolerance is not counted as a saving

It is headroom, not money. The pool can run 10% above baseline before the usage band moves the price — which protects the organisation from normal month-to-month variation immediately becoming out-of-bundle cost.

That is genuine commercial value and it is not a reduction in spend. Adding it to the 15.0% would count the same pooling benefit twice.

Commercial significance

Not a tariff-switch exercise

The larger opportunity came from reconstructing the estate, normalising usage, separating active from specialist connections, pooling predictable demand, and then putting monitoring and governance around the result.

The quoted saving therefore arrives with better visibility, more predictable cost, and an operating framework that can hold the position — which matters more than the percentage in a category where fragmentation returns within a year if nobody is watching it.

Could this be recoverable in your own operating spend?

Request a confidential category diagnostic