top of page

A Holistic Approach to Mobility Expense Management: Why One Report Is Never Enough

Akira Oyama
Aug 23
6 min read

Mobility expense management is often approached as a reporting exercise.


Review the monthly bill. Identify large cost increases. Find unused lines. Check roaming. Analyze plans. Produce a savings report.


Each of these activities is useful. But each answers a different question.


The problem arises when one report is expected to provide the complete picture.


A month-over-month cost report can tell you what changed, but it may completely miss waste that has remained unchanged for months. An audit can identify individual exceptions but may not reveal whether the overall plan structure is inefficient. A usage analysis can identify underutilized plans but may not explain why this month's invoice changed.


Effective mobility expense management therefore requires a more holistic approach: looking at the same environment through multiple analytical lenses and connecting the findings.


Three Different Questions

Consider three common types of mobility analysis:


Analytical Lens Primary Question

Cost Variance What changed?

Audit/Exception Analysis What appears unnecessary, incorrect, or unusual?

Usage & Plan Optimization Are we buying the right services and plans?


None is inherently better than the others.


The value comes from using them together.


Real-world examples illustrate why.


Case 1: The Line With No Cost Variance — and Six Months of No Usage

Suppose a mobile hotspot costs approximately $105 per month.


Last month: $105.


This month: $105.


A cost variance report appropriately concludes:

No material month-over-month change.

If the organization focuses primarily on cost changes, there is little reason for this line to receive additional attention.


Now add another analytical lens.

A six-month usage audit finds:

No recorded usage for six consecutive months.

Suddenly, the interpretation is very different.


The monthly bill did not change because the problem itself did not change. The organization has simply continued paying approximately $100 every month for an apparently unused device.


In a larger mobility environment, many similar lines can quietly accumulate.


In one anonymized analysis, 15 active lines had recorded no usage for six consecutive months, representing more than $800 in monthly recurring charges.


Most of those lines showed little or no month-over-month cost movement.


That leads to an important principle:


Some of the Most Expensive Problems Do Not Create Variances

Traditional variance analysis is naturally attracted to movement.


A line increases $500.


Roaming increases $2,000.


A new charge appears.


Those events deserve investigation.


But persistent waste often behaves differently.


It may appear as:

  • An unused hotspot billed every month

  • A tablet assigned to a former use case

  • An unnecessary feature that has existed for years

  • A device with little or no usage

  • A legacy plan that is still being billed exactly as designed


Nothing "changed."


And that is precisely why the expense can survive unnoticed.


A mature mobility expense program should therefore monitor both change and persistence.


Case 2: A $3 Cost Increase That Hides Much More Than $3

Now consider a smartphone line.


Its total monthly cost changes from approximately:


$130 → $134


Net increase:


About $3


On the surface, this looks insignificant.


But looking only at the net change can be misleading because multiple billing components may offset one another.


When the same line is examined through several analytical lenses, additional activity appears.


An audit identifies an optional recurring cloud-storage feature costing approximately $6 per month that comparable users on the same plan generally do not have.


A roaming analysis separately identifies approximately $58 of international activity during the current period.


At the same time, other billing components decreased or credits were applied.


The result is only a small net increase.


So:


Net cost movement: +$3


does not mean:


Only $3 worth of activity deserves attention.


This illustrates another important limitation of high-level variance reporting.


Netting Can Hide Actionable Activity

Invoices contain many moving pieces:

  • Recurring charges

  • Discounts

  • Credits

  • Equipment charges

  • Roaming

  • Taxes and surcharges

  • One-time adjustments

  • Feature charges


Several significant changes can occur simultaneously while producing almost no change in the final bill.


For that reason, mobility analysis should not stop at:

How much did this line increase?

It should also ask:

What changed underneath the total?

And then:

Does any of that activity require action?

Case 3: Correct Billing Does Not Necessarily Mean Optimal Billing

Auditing introduces another important question:


Was the organization billed correctly?


But even a perfectly accurate invoice can still be inefficient.


That requires a different analytical lens.


Consider an anonymized plan analysis that found:

  • Several unlimited-data device lines with zero recorded data usage

  • Multiple limited-data smartphone plans with zero data usage

  • Other devices consuming only a fraction of their available service

  • Different plan structures serving similar populations


There may be nothing technically incorrect about any of these charges.


The carrier may be billing exactly according to contract.

The question is different:

Should these lines be on these plans at all?

This is where expense management shifts from audit to optimization.


An audit asks:

Are we paying something we should not be paying?

Optimization asks:

Even if everything is correct, are we buying the right thing?

That distinction matters.


Organizations can have highly accurate invoices and still overspend because of poor plan alignment, unnecessary services, outdated configurations, or historical decisions that no longer reflect current usage.


From Reports to Analytical Lenses

Rather than treating these reports as separate deliverables, I prefer to think of them as interconnected analytical lenses.


Lens 1 — Cost Movement

What changed?


Examples:

  • Large monthly increases or decreases

  • New billing items

  • Disappearing credits

  • New roaming charges

  • Line additions or removals

  • Changes in recurring plan charges


Lens 2 — Audit and Exceptions

What deserves investigation?


Examples:

  • Zero-usage lines

  • Unexpected features

  • Recurring-charge variances

  • Abnormal roaming activity

  • Duplicate or inconsistent charges

  • Contract or pricing exceptions


This lens finds conditions that may exist even when costs remain stable.


Lens 3 — Usage and Optimization

Is the environment structurally efficient?


Examples:

  • Plans misaligned with usage

  • Underutilized devices

  • Excessive allowances

  • Legacy plans

  • Opportunities to consolidate plan structures

  • High cost per line or cost per unit of usage


This lens looks beyond billing accuracy and asks whether the environment itself should be redesigned.


The Real Opportunity Is Connecting the Lenses

The biggest opportunity is not creating more reports.


Most organizations already have plenty of reports.


The opportunity is to connect the findings.


Instead of three independent observations:


Variance report: No meaningful monthly cost change.

Usage report: Zero usage for six months.

Inventory report: Active mobile hotspot.


A connected analytical process produces:

Active mobile hotspot with approximately $100 in recurring monthly charges has recorded no usage for six consecutive months. Monthly cost is unchanged, so the line would not normally appear in variance analysis. Review business need and consider suspension or disconnect.

That is much closer to a decision.


The objective of mobility analytics should ultimately be to move from: Data → Reports


to: Data → Multiple Analytical Lenses → Connected Findings → Prioritized Action


Where Automation and AI Can Help

This is also where automation and AI can significantly improve mobility expense management.


Automation can continuously perform tasks such as:

  • Comparing current and prior invoices

  • Tracking multi-month usage

  • Benchmarking recurring charges across similar plans

  • Identifying unusual features

  • Measuring roaming patterns

  • Evaluating plan utilization

  • Connecting inventory, billing, usage, and employee information


AI can add another layer by helping interpret relationships between those findings.


For example:

This line would not normally be investigated because monthly cost did not change. However, six consecutive months of zero usage combined with a recurring charge of approximately $100 indicates a potential annualized cost avoidance opportunity of approximately $1,200 if the service is no longer required.

Or:

Total cost increased only slightly this month, but the line generated meaningful international roaming charges and contains a recurring feature not typically present on comparable lines. Review both the travel activity and feature requirement.

The value isn't simply having AI summarize a spreadsheet.


The value is using technology to connect signals that would otherwise remain scattered across different reports.


A More Holistic Mobility Management Cycle

A strong mobility expense management program can operate as a continuous cycle:


Observe

What changed?

Audit

What looks wrong, unnecessary, or unusual?

Optimize

Is the service, plan, or configuration still appropriate?

Act

Correct, disconnect, suspend, optimize, negotiate, or monitor.

Measure

Did the action produce the expected result?


Then repeat.


Each cycle creates additional historical information that makes future analysis better.


Over time, the organization moves away from simply explaining invoices and toward continuously improving the mobility environment.


One Report Rarely Tells the Whole Story

There is nothing wrong with cost reports, audit reports, usage reports, or optimization reports individually.


The mistake is assuming that any one of them represents the complete answer.


A cost report might say:

Nothing changed.


An audit might say:

This line has not been used for six months.


An optimization analysis might say:

The plan structure itself should be reconsidered.


All three statements can simultaneously be correct.


The strongest mobility expense programs therefore do more than generate reports.


They connect cost, usage, inventory, contracts, plans, employee information, and historical patterns to understand not only what happened, but also why it matters and what should be done next.


That is the difference between reporting on mobility expenses and actively managing them.


 
 
 

Comments


bottom of page