NPO Mobile Data & Telecommunications Optimisation · Data Sheet
NPO Mobile Financial Results
Quantified savings architecture, package mix, usage evidence, result status and implementation boundary for a reseller-supplied mobile-data estate.
1 · Result classification
Five results, including one that limits the others
Scroll table sideways →
| Result | Classification | Interpretation |
|---|---|---|
| 30.7% reduction | Modelled / commercially priced | Direct-network equivalent packages against the quantified reseller baseline. |
| 40.8% reduction | Modelled / commercially priced | Usage-led package mix, using lower and higher bundles according to observed consumption. |
| 10.1 percentage points | Analytical uplift | The additional reduction attributable to right-sizing, beyond the supplier and pricing change. |
| Signed migration documents | Contract / implementation evidence | Supports that the solution moved beyond a theoretical quote into an implementation process. |
| Transition disruption | Implementation evidence | Prevents the modelled saving from being described as fully realised without clean post-migration billing evidence. |
3 · Savings architecture
Two scenarios against the reseller baseline
Scroll table sideways →
| Scenario | Cost index | Reduction | What changes |
|---|---|---|---|
| Existing reseller baseline | 100.0 | — | Existing package mix and reseller commercial route. |
| Direct carrier, equivalent packages | 69.3 | 30.7% | Supplier route and pricing change; package sizing broadly preserved. |
| Direct carrier, usage right-sized | 59.2 | 40.8% | Supplier route changes, plus lower and higher bundles selected from usage evidence. |
The 84-connection baseline is the denominator for both models. A later implementation snapshot records 92 connections and a revised package population — that changed estate must not be retrofitted into the earlier calculation.
4 · Usage mismatch
Why one package size produced two opposite losses
Scroll table sideways →
| Evidence point | What it shows | Commercial implication |
|---|---|---|
| 88.1% of baseline on 2GB | Package concentration was far greater than usage uniformity. | A common standard was administratively simple and economically blunt. |
| Very low-use lines present | Some connections recorded little or no use across several periods. | Lower tiers or controlled top-up SIMs could cut fixed recurring cost. |
| High-use outliers present | Some lines repeatedly exceeded the nominal allowance. | A pure downgrade strategy would create avoidable top-up cost and user disruption. |
| Usage history available per line | Demand could be analysed before package assignment. | Right-sizing could be evidence-led, rather than based on title, seniority or default package. |
5 · The right-sized estate
The range widened in both directions
Scroll table sideways →
| Tier | Quantity in model | Purpose |
|---|---|---|
| Controlled / top-up SIM | 20 | Very low or intermittent use; load value only when required. |
| 500MB | 21 | Low-use lines materially below the former standard bundle. |
| 1GB | 19 | Moderate users below the former 2GB default. |
| 2GB | 15 | Users whose observed demand supported the former baseline level. |
| 3GB | 11 | Users requiring more than the former common allowance. |
| 5GB | 1 | Higher-use line. |
| 10GB | 1 | High-use line. |
| 20GB | 2 | Very high-use or router-type demand. |
The model expanded the range materially below the old 2GB floor while retaining larger tiers for high-use connections. Right-sizing is not a downgrade exercise — 15 users stayed at 2GB and 15 moved above it.
6 · Non-price value
From monthly invoice to managed category
The operating model added a central portal carrying balances, usage history, user profiles and expenditure visibility, together with top-up control, package changes, SIM replacement, invoice access, alerts and capped usage.
That is what keeps a right-sized estate right-sized. Package assignment based on observed demand drifts as quickly as demand does, and without a mechanism to see it and change it, the estate returns to a single default package within a year or two.