The £6M Thread Pull

The brief

A narrow, well-defined job: a handful of STM circuits that were expensive to run, to be migrated onto newer links with more bandwidth. Someone else had scoped it. It was routine delivery work.

What I noticed

The first few circuits didn’t look like a local problem. They looked structural. So I kept pulling the thread and ended up auditing Vodafone’s entire third-party link inventory, not just the circuits I’d been handed. Three kinds of waste came out of it:

• Duplicate links: the same route paid for twice.
• Links with a cheaper or higher-bandwidth alternative already available.
• Dead links still being billed: the service long gone, the invoice still running.

Making the case

Nobody formally approved the wider scope. The numbers made the case. The one thing I was deliberate about was framing: I presented the saving as operating expenditure, not capital, meaning recurring cost coming off the P&L every year. That is what got senior management’s attention.

Managing the risk

Switching off a circuit that turns out to be carrying live traffic means a national network outage. So nothing was decommissioned on a single source of truth. Every link was checked three ways:

1. traffic monitoring over a period,
2. the CRAMER inventory records,
3. direct confirmation from the service owner.

Every migration had a rollback plan, and we used them. Some changes were rolled back for migration faults, design errors or engineer error, then run again.

Result

• Over £6M of recurring third-party operating cost removed across the programme.
• Thousands of circuits audited, delivered with a team of 9 over three years.
• A related redesign of the cease process cut 30 days of duplicate billing per circuit and made the process 50% more efficient. That saving is part of the £6M, not added to it.

I was handed a migration. The real job was finding out what we were paying for.