Predictable spend forecasting
2 min read
215M+
IoT connections
180
Countries
330M+
Customers
The Opportunity
Spend moved for operational reasons; visibility landed after close
On Vodafone's IoT platform, spikes came from rollouts, misconfigured devices, roaming, firmware shifts, and fleet usage, not one-off bugs. After billing closed you could explain what happened; you still could not reliably forecast the bill, set guardrails early, or catch drift in time to act.
That gap hurt in three ways:
- Bill shock eroded trust, and finance slowed expansion sign-offs.
- Ops burned time on spikes without clean attribution or a fast path to root cause.
- When setup and docs were hard to use, automations never shipped and good controls stayed slideware.
The Solution
Plain-language forecasts, caps with a next step, operator-first alerts, docs that matched the API
Forecasting answered "What will we likely spend this period?" in language finance teams use. Breakdowns followed how teams already group fleets and sites; weak signals were labelled clearly instead of presented as exact.
Caps mirrored real ownership: warn before a hard stop, show "what next" when a threshold is crossed, and keep a simple log of who changed what. Anomalies stayed short and clear, with links to the slices teams already use to investigate.
Developer docs used the same words as the UI (quota, threshold, alert), with quickstarts and copy-paste examples so integrations shipped with fewer round-trips.
The Impact
Less rear-view billing, more steering while the period is open
Teams shifted from "what happened last month" to what's coming, where caps apply, and what changed. Finance could plan earlier, ops could act before close, and programme owners could grow fleets with fewer invoice surprises.
Clearer signals and shared vocabulary trimmed escalation noise and sped fixes, often before the billing period ended.
“Gagan's design approach is grounded in close attention to users and what the business needed.”
More success stories
View all
Ready to take the next step?
Choose the right plan for your team.