If you're delivering a solution that relies on cellular connectivity, that connectivity probably shows up in your accounts as a small line in cost of goods — a few percent of deployment cost and the price of SIMs and data.
But that number is a poor guide to what connectivity is actually doing in your business; the support load it drives, the deployment timelines it shapes, the margin it protects or erodes, the deals it enables or prevents.
None of that sits in the line where connectivity is booked. Instead, it's distributed across the business, in places nobody's actively measuring. Which means connectivity decisions are being made on a number that doesn't reflect the full picture.
What follows is a practical look at both sides:
Cellular connectivity behaves like a system. It touches provisioning, support, deployment speed, customer retention, margin stability, and pricing confidence.
It's involved in almost every commercial decision a provider can make, from quoting a new deal to deciding whether to renew a supplier agreement. It's part of the operating model, whether a business treats it that way or not.
But often, it gets booked like a component; a cost line, a margin assumption, or a pass-through to suppliers. Something you buy, mark up, and move past. And the accounts don't see the system, they just see the component.
Knowing the difference between cellular as a system or component is where both the hidden cost and the hidden value sit.
When the system is managed well, the line item can understate the value the business is actually getting. When it's managed casually, the line item can understate the cost the business is actually carrying.
Connectivity as a component:
Priced, passed through, largely unmanaged.
Connectivity as a system:
Vsible, controlled, commercially governed.
The shift from one to the other is what changes the numbers.
When cellular connectivity is managed as a component, costs show up in places the P&L doesn't connect back to it. The line item stays small, but the business still pays — it just pays somewhere else:
Every connectivity issue a customer raises has to be owned, investigated, diagnosed, and resolved.
At low volumes, this gets absorbed into general support and nobody thinks much about it. As the estate grows, the time spent on connectivity issues becomes a meaningful chunk of what the support function is doing — but it's rarely traced back to the connectivity line that originally priced the deal.
The support itself isn't the problem; support is expected. What makes it costly is when it's unpredictable and untraceable — when the business is carrying the load without being able to attribute or anticipate it.
Providers running fragmented connectivity across multiple suppliers especially can't often see the load accumulating, can't forecast where it'll land next, and can't price future deals to account for it. The support function grows, the margin compresses, and the connectivity line in the P&L looks the same as it always did.
Pull the last quarter's support tickets and tag which ones were cellular connectivity-related. Then look at whether the time spent on those tickets is reflected in how you priced the deployments they came from.
If there's a gap — and there usually is — that's the cost you're carrying that the P&L won’t connect cellular to.
Cellular connectivity isn't usually the most complex part of a rollout, but it is often the part that holds things up. Waiting for SIMs to arrive. Waiting for activations to process. Waiting for a supplier to confirm coverage in a specific region. Waiting for an unusual APN configuration to be approved.
Individually, these delays are small, but at scale, they stack. For project-based providers, they show up as quarters that come in under plan. For recurring-revenue providers, they show up as delayed ramps on new contracts.
Either way, the cost is revenue that arrived later than it should have — which doesn't appear in the connectivity line because it's not a cost at all. It's a timing gap between when a deal was signed and when it actually started earning.
Look at your last ten deployments and measure the gap between contract signature and first revenue. Then look at what caused the delays. If cellular connectivity provisioning is showing up as a recurring factor, you've got a deployment friction cost that's invisible in the accounts but real in the cash flow.
Every connectivity contract is priced on assumptions: usage patterns, support load, supplier costs, FX on international elements, the rate at which devices are active versus dormant. None of those assumptions stay still. Usage may drift upward as customers do more with the service. Support load can accumulate. Supplier costs can move. The commercial model that looked good at sale starts looking a lot thinner a year in.
One reason this drift can go unnoticed is structural. When connectivity is sourced from multiple suppliers, there's no single view of usage or cost across the estate. Ownership is diffuse — nobody's actively watching any given deployment's margin because the data lives in different places and platforms. Nothing in that kind of operating model is designed to catch the drift.
Pick five deployments that have been live for more than two years. Rebuild the original margin model with current usage data and current supplier costs. The gap between what you modelled and what you're actually running is your margin drift — and it's almost always larger than people expect when they first do the exercise.
This is the hardest cost to see because it's invisible by definition. But it’s worth noting that when connectivity is hard to price with confidence — complex regions, unusual usage profiles, heavy support requirements, suppliers you haven't worked with before — the most common response isn't to get it wrong — it's to price conservatively, scope it down, or not pursue the deal at all.
Providers at scale often have this pattern. There's a backlog of opportunities that were passed on or priced defensively because the connectivity story was too hard to tell with confidence. That's a commercial loss that can go under the radar.
Ask your commercial team how many deals in the last year were priced higher than they should've been, scoped smaller than they could've been, or dropped from the pipeline — because of uncertainty about connectivity.
These four costs usually add up to something much larger than the connectivity line will show. None of them are inherent to cellular connectivity as a technology; they come from managing it as a component with fragmented supplier relationships, limited visibility, and no defined ownership of the commercials over time.
The good news? All these costs are structural, which means they're addressable.
In fact, the same dynamics that create these costs also create the upside when connectivity is managed differently:
When cellular connectivity is managed as a system, the value shows up in the same places the costs were accumulating:
Customers barely notice connectivity when it works. But when it doesn't, they notice nothing else. Every dropped session, slow reconnect, or unexplained downtime is a moment where the whole service is being judged on something that sits underneath it.
Providers who manage connectivity directly — who can see what's happening across the estate and act on it without escalating to suppliers — reduce the failure points that can erode customer trust over time.
Providers who pass connectivity through, or leave it to the customer, inherit someone else's performance, which means inheriting someone else's visibility gaps and response times. The retention difference shows up in renewal rates, NPS scores, and the churn conversations that go well — not the connectivity line.
Your team can see a connectivity issue developing before the customer notices, diagnose it without calling a supplier, and resolve it without waiting. Connectivity stops being a source of erosion and starts being one of the reasons customers stay using your service.
Deployment speed is one of the few things providers can compete on that customers actively buy on. A service that's up and running in three weeks beats one that takes three months, even if the underlying capability is identical. And the thing that most often separates the two is how smoothly connectivity comes online — whether SIMs are ready when devices arrive, whether activations work first time, whether coverage is confirmed before anyone's on site.
Providers who've made connectivity predictable can quote aggressive timelines with confidence and win deals on that basis. Providers who haven't end up padding timelines, losing competitive deals, or missing commitments they made in the proposal.
Provisioning works the same way for every device, regardless of which underlying network it's on. Your deployment timeline doesn't depend on which supplier picks up the phone first. Your commercial team can quote delivery dates they actually believe in.
Margin on deployments usually moves in small steps: usage patterns shifting, supplier costs edging up, support load accumulating. Each movement is small, but added up across a portfolio of deployments over several years, they're the difference between a service line that can hold its margin and one that's leaking.
Providers who can see usage, cost, and health across the estate in one place can manage that drift actively — spotting issues early, renegotiating before problems compound, and keeping the margin they modelled at sale.
You can pull up any deployment and see its current margin against its original model. Drift is caught in months rather than years. When you renegotiate with a supplier or restructure a contract, you're doing it from data rather than instinct.
When connectivity is hard to price with confidence, the usual response is to pad the number or walk away from the deal. That's expensive — it costs deals and it costs margin on the deals it wins.
When connectivity is managed as a system, the commercial team can pursue deals that competitors either overprice or walk away from. Complex regions. Unusual usage profiles. Customers with non-standard requirements. High-support verticals. These are the deals where connectivity uncertainty pushes providers into conservative pricing or a polite decline — and they're also the deals where margins are usually best for the providers who can handle them.
Your commercial team doesn't have to build a new cost model from scratch for every unusual deal. The data is already there — usage benchmarks, supplier costs, support load by deployment type. Quoting a complex deal feels the same as quoting a simple one.
Because building it yourself is genuinely hard.
Treating connectivity as a system means having visibility, control, and commercial governance across your entire estate as a single thing.
It means provisioning that works the same way regardless of which network a device ends up on. It means diagnostics you can act on without waiting for a supplier. It means a commercial model you can track and adjust over the life of a deployment, not just at the point of sale.
Getting there by stitching together multiple operator relationships, normalising their behaviour, building internal tooling, and maintaining it all as the estate grows is possible — but it's a significant engineering and operational programme.
Most providers who try it end up somewhere in the middle: carrying the commercial and operational consequences of connectivity, without having enough control to manage them properly.
Which is why the more practical route is to work with a connectivity platform that has already done the integration work — one that consolidates multiple operators and carrier platforms into a single managed estate, with the provisioning, diagnostics, and commercial tooling built in. Rather than building and maintaining the system yourself, you inherit one that's already operational.
The important thing to look for is whether the platform is designed for providers who are building a connectivity practice into their service — or for buyers who just need SIMs in bulk.
A platform designed for practice-building gives you the commercial model to price connectivity into your service with confidence, the operational tools to manage it as the estate grows, and the visibility to keep margins healthy over the life of each deployment. It treats your growth as the thing it's optimised for, because your practice succeeding is how the platform succeeds.
That's a different relationship from buying connectivity as a commodity input, where the tooling is built for procurement rather than for running a business on top of it.
One response to all of this is to sidestep it entirely by passing it through (or leaving it to the customer). If it's someone else's system, it's someone else's problem. The appeal is obvious — less complexity, less risk, less surface area to manage.
But passing connectivity through doesn't remove the dynamics described above. It pushes them into parts of the business that are harder to control: the support function still carries the load without being able to resolve it, the deployment team still waits on a third party's timeline, the commercial team still can't quote confidently because the underlying capability isn't theirs to manage. The complexity doesn't disappear, it just relocates.
The providers who've stopped treating connectivity as a component aren't the ones with the most complex setups. They're the ones who decided that if connectivity is going to be part of how well the solution runs, it's worth running deliberately — and found a platform that lets them do it without having to build the infrastructure themselves.
The connectivity line in the P&L doesn't necessarily get smaller when you make this shift. But the business around it gets substantially stronger. The support load becomes visible and manageable. Deployments get predictable. Margins stabilise. The pipeline broadens because the commercial team can price with confidence in places competitors can't.
The commercial case for managing connectivity as a system isn't that it avoids problems — problems can still happen. It's that the problems become ones the business can do something about, rather than ones it absorbs across places nobody's watching.
And the practical case is that you don't have to build the system yourself. The integration work, the operator relationships, the platform — it already exists. The question is whether you're using it.
If you're wondering where the cost and value of connectivity actually sit in your business — beyond the line item — we can help you work through:
_white.svg)
