Begin with a complete service and contract inventory, then compare actual use, resilience value and strategic importance against recurring cost and termination dates. Savings commonly come from re-procuring off-net circuits, replacing expensive access products, right-sizing transit, rationalising POPs, removing duplicates, renegotiating colocation and aligning contract renewals. Every saving should be tested against capacity, migration risk and resilience.
Build a reliable baseline
Cost reduction starts with an accurate inventory rather than a carrier invoice total. Record:
- Service and circuit reference
- Site, A-end, B-end and route purpose
- Product, capacity and current utilisation
- Underlying access or wholesale provider
- One-off and recurring charge components
- Contract start, end and notice dates
- Resilience role and operational criticality
- Known delivery or fault performance
- Replacement and migration constraints
Common opportunity areas
| Area | Questions to test |
|---|---|
| Backhaul and leased lines | Is the circuit off-net, over-specified, duplicated or replaceable with dark fibre or wavelength? |
| IP transit | Are commits, ports, burst arrangements and supplier mix aligned with actual traffic? |
| Colocation | Are racks, power, cross-connects and remote-hands charges still required? |
| POPs | Does each location still provide coverage, resilience or commercial value? |
| Contracts | Are services rolling over without market testing or notice control? |
| Architecture | Can traffic be aggregated or routes simplified without creating new concentration risk? |
Protect resilience and operational value
A circuit with low utilisation may be a critical backup. A costly POP may protect a region or provide access to a strategic carrier. Remove cost only after documenting the service’s purpose and the failure scenario it protects.
Test each proposal against:
- Capacity in normal and failure conditions
- Physical and logical diversity
- Migration and rollback plan
- Fault and maintenance impact
- Future build or customer commitments
- Operational support capability
Use contract timing intelligently
Build a contract calendar at least 12 to 18 months ahead. Group services by renewal date, geography, provider and replacement option. This creates competition before notice deadlines and allows migrations to complete before existing contracts expire.
Build a decision-ready business case
For every saving, show:
- Current annual recurring cost
- Replacement recurring cost
- One-off migration and termination cost
- Net saving by year
- Payback period
- Capacity and resilience change
- Implementation risk and owner
- Confidence level and dependencies
Control implementation
Real savings begin when the old service is ceased, not when a new quote is accepted. Track order, delivery, testing, traffic migration, billing start, old-service notice and final cease. Reconcile invoices after the change and confirm that credits and termination charges are correct.
Frequently asked questions
Common questions
Can cost be reduced without changing the network architecture?
Often, through re-procurement, contract negotiation, capacity changes and billing correction. Larger savings may require route or POP changes.
Should low-utilisation backup circuits be ceased?
Not until their resilience purpose and failure scenario have been assessed. Low use can be evidence that a backup has not been needed, not that it has no value.
Can CROSS work on a shared-savings basis?
A commercial model can be agreed for suitable assignments, normally with a defined baseline, verification method and treatment of one-off costs.
What data is needed for an initial review?
Carrier invoices, service inventory, contract dates, capacity, utilisation where available, topology purpose and known replacement constraints.
Apply this to a live site
You do not need to know the product before speaking to us.
Send us the site, project or carrier quotation and we will identify the most useful next step.