One Owner, Many Carriers: Building a Defensible Business Case for Difficult-Site Connectivity

Executive summary

The problem. Most multi-site estates have a list of "difficult" sites: transport hubs, shopping centres, forecourts and other locations where the standard connectivity offer does not reach. These sites are usually handled as exceptions. They are priced separately, delivered by different suppliers and governed, if at all, by different contracts.

The shift. Estates keep growing into concessions and managed locations. The exception list grows with them, and so does the share of trading that depends on it.

The cost of inaction. When nobody owns the fault, every outage becomes a negotiation between suppliers. Delayed openings, failed transactions and extra contracts all land on your budget.

The recommendation. Treat the difficult site as a governance problem, not a technical oddity. Put specialist carriers behind one accountable owner, one SLA and one transparent cost model.

In practice. Evolve describes an engagement that starts with a rapid audit of sites, carriers, risks and PCI scope, then moves through blueprint, pilot and phased rollout. This paper gives you a clear standard to test any supplier against, including Evolve.

1. The market has changed

Difficult sites used to be rare. For a growing multi-site brand they are now a standing part of the estate. Each one carries three risks that rarely appear in the original business case: access delay, landlord or venue dependency, and a supply chain with more than one party.

2. Why the usual approach no longer holds

The common model is a primary provider for standard sites plus ad hoc arrangements elsewhere. The result is a contract set that looks tidy in procurement and fragments in operation. Three symptoms to check in your own estate:

• Different SLAs for sites that trade the same hours.
• Separate escalation routes, so a fault has no single owner.
• Pricing that moves when a site is classed as "non-standard".

This is the vendor behaviour your own role exists to catch: value overstated, cost hidden in the exception clauses.

3. The hidden cost is growing

The cost of a difficult site rarely sits in one line of the budget. It tends to show up in four places:

1. Trading time lost to delayed go-live.
2. Transaction and customer-experience loss during outages.
3. Management time across multiple suppliers and contracts.
4. Uplifts and variations on non-standard sites.

Building these into your own baseline is the first step towards a business case that holds up under scrutiny.

4. A new operating model: one owner, many carriers

Reliability at hard-to-reach sites depends on two things: choosing the carrier that is right for the location, and having one party accountable end to end. Neither works alone. A specialist carrier without an owner leaves you managing the gaps. An owner without carrier choice forces one network onto every site.

Evolve's stated model combines carrier partner relationships, including partners that specialise in particular location types such as airports, train stations and shopping centres, with in-house project management and network support. This is Evolve's own description and should be read as a company claim.

What "one owner" should mean in the contract:

• One SLA across all sites, with no lower tier for difficult locations.
• One escalation route, with the owner responsible for carrier performance.
• Transparent site-by-site cost, with exceptions priced up front.
• Change control and an audit trail.

5. The measurable value

Evolve states the following. Each is a company claim, not independent proof:

• Proactive monitoring, with 86% of support calls outbound.
• Dedicated account management and SLA-driven reporting.
• Blueprint-led onboarding, with programmes delivered at pace, for example 600+ sites in three months, with change control and audit trails.

Ask any supplier for the same evidence, and ask for references. Lack of reference clients and supplier size are fair questions, and Evolve should be tested on both.

6. A 90-day roadmap

Days 0 to 30: map. Audit sites, carriers, contracts and risks (including PCI scope). Stakeholders: procurement, IT, operations. Success metric: complete exception list with contract and cost per site.

Days 31 to 60: decide. Compare suppliers against the one-owner standard. Agree one SLA standard. Pilot at a limited set of sites. Stakeholders: procurement, finance, IT. Success metric: pilot success criteria agreed before start.

Days 61 to 90: roll out. Phased rollout under change control, with quarterly review dates set. Stakeholders: operations, supplier owner. Success metric: uptime and fault-ownership reporting from day one.