The cost review that changed the decision
A telecom cost review where the useful finding was not a saving. It showed that the obvious plan to cut the bill would save nothing at all.
Outcome at a glance
The team dropped a cost-cutting plan that would have taken real effort for no saving, and put that effort where it could change the numbers.
Context
A cloud phone system pays a telecom vendor for the calls and messages its customers make. That vendor bill is one of the biggest costs of running the product.
Problem
The plan on the table was simple: reduce usage-based costs to lower the monthly bill. It sounded right. Nobody had checked whether the contract made it possible.
My role
I ran the review of the vendor costs and the contract terms behind them.
Approach
- I broke the bill down by cost type, instead of looking at the total.
- I read the contract terms that sit behind each line, not just the invoice.
- I tested the plan against those terms before estimating any saving.
What I found
The contract included a minimum-spend commitment. Below that level, the business pays the same amount whether it uses less or not. Cutting usage would have lowered activity on paper and saved nothing in cash.
Outcome
The finding changed what the team decided to do. The team did not spend effort on a cut that could not pay off, and focused on the options that could actually change the cost.
Specific amounts and contract terms are confidential and are not shown here.
What I learned
Check the constraint before you calculate the saving. The most valuable analysis sometimes proves that the obvious plan will not work.