Most connectivity projects do not fail because radio is hard. They fail because somebody approved a business case before the connectivity due diligence process was done properly. Coverage looked fine on a slide, commercials looked acceptable in a headline number, and the operational detail was left for later. Later is usually where cost, delay and reputational damage show up.
That pattern repeats across MVNO launches, private 5G and LTE deployments, IoT estates, EV charging networks, camera programmes, automated vehicle platforms and any business that depends on mobile connectivity to make money or keep services running. If connectivity is central to the proposition, due diligence is not a procurement step. It is a go or no-go discipline.
What the connectivity due diligence process is really for
A good connectivity due diligence process is there to answer one simple question: can this service work commercially and operationally in the real world, not just in a proposal deck? That means pressure-testing network fit, device behaviour, commercial terms, support models, compliance, and scaling assumptions before contracts are signed and before the wrong architecture becomes expensive to unwind.
In practice, the work sits between strategy and execution. It translates ambition into constraints. It also exposes whether stakeholders are aligned on what they are actually building. A consumer MVNO, a mission-critical private network for a port, and an IoT deployment for remote assets may all use mobile technology, but their tolerances for latency, resilience, security, roaming, battery performance and field support are completely different.
This is why generic checklists tend to disappoint. The right process depends on the use case, regulatory environment, device estate, geography and commercial model. It also depends on how much risk the business can absorb if assumptions prove wrong.
Start with the service model, not the SIM
A common mistake is to begin with suppliers, tariffs or coverage maps. The better starting point is the service model. What are you trying to deliver, to whom, at what margin, with what service levels, and across which operational footprint?
For an MVNO, that may mean understanding target segment economics, acquisition channels, expected usage profiles, roaming needs, digital onboarding flows and customer support implications. For a private 5G network, it may be about asset density, mobility patterns, interference environment, indoor versus outdoor requirements and integration with existing IT and OT systems. For IoT and connected devices, it often comes down to data profile, sleep behaviour, provisioning workflows, remote management and failure handling at scale.
If this is not clear at the start, every later decision becomes noisy. Suppliers fill the gaps with their own assumptions, and those assumptions usually favour their product rather than your outcome.
The key stages in a connectivity due diligence process
The sequence matters because weak foundations distort everything that follows. The first stage is use-case definition and business case validation. That means identifying the operational need, expected revenue or efficiency gain, service criticality and non-negotiables. If the business case only works under ideal network conditions or unrealistic support costs, it is not ready.
The second stage is technical fit. This covers radio access options, coverage reality, indoor penetration, resilience requirements, SIM or eSIM strategy, device compatibility, firmware behaviour, provisioning, OTA update paths, policy control, traffic routing and management tooling. The point is not technical perfection. The point is to confirm that the architecture can support the actual service, at the expected scale, with acceptable complexity.
The third stage is commercial and contractual assessment. Headline rates tell you very little on their own. You need to understand minimum commitments, traffic pools, roaming terms, liability positions, service credits, implementation fees, change control, termination mechanics and what happens when growth is slower or faster than forecast. A cheap deal can become a very expensive one if it traps the business in the wrong support model or blocks future migration.
The fourth stage is operational readiness. This is where many projects come unstuck. Who owns incident management? How are SIM lifecycles handled? What is the fraud posture? How are support tickets triaged? Can the business reconcile usage, billing and inventory? How are devices replaced in the field? If this work is ignored, teams end up improvising after launch.
The fifth stage is risk and governance. Security, compliance, data handling, lawful intercept obligations where relevant, resilience planning, supplier dependency and escalation paths all belong here. This is particularly important for public sector, defence-adjacent, transport, utilities and safety-related deployments where failure carries wider consequences than a missed KPI.
Where buyers most often get it wrong
The first error is trusting coverage claims without field validation. Predicted coverage and usable service are not the same thing. Signal levels, congestion, handover behaviour, building materials and antenna placement all affect outcomes. In private networks, site design assumptions can be equally misleading if they are not checked against the physical environment and device reality.
The second is separating commercial and technical work. They are interdependent. A contract that looks sensible may rely on traffic assumptions that devices will not follow in the field. Equally, a technically elegant solution may destroy margin once support, roaming, integration and compliance costs are included.
The third is underestimating operational complexity. A pilot with fifty devices can hide problems that become painful at five thousand. Provisioning errors, firmware inconsistencies, poor stock control, weak customer support workflows and bad exception handling are manageable in small numbers, then suddenly not manageable at all.
The fourth is accepting vendor-led architecture too early. Vendors are useful, but their incentives are not neutral. They tend to optimise for product fit and deal closure. Your job is to optimise for long-term service viability.
What a strong diligence outcome looks like
A proper diligence exercise should leave decision-makers with a clear view of viability, not more jargon. It should identify what will work, what will not, what can be phased, what needs redesign, and which risks are acceptable versus unacceptable.
It should also produce decision-grade evidence. That may include coverage test results, device certification status, traffic modelling, operational workflow design, supplier comparison, commercial sensitivity analysis and a realistic launch plan. If the output cannot support an investment decision or a contract negotiation, the exercise has not gone far enough.
For senior teams, the real value is clarity. Sometimes the right answer is to proceed quickly because the fundamentals are sound. Sometimes it is to narrow the scope, change supplier strategy or redesign the proposition before more money is committed. Occasionally, the right answer is not to launch at all. That is still a good result if it prevents a larger failure.
Why the connectivity due diligence process changes by sector
The phrase connectivity due diligence process sounds universal, but the weighting changes sharply by sector. In EV charging, uptime, payment flows, remote diagnostics and field maintenance can matter more than headline data rates. In automated vehicles and micromobility, mobility continuity, handover behaviour and latency tolerance move up the list. In agritech, rural coverage reality, power management and ruggedised hardware tend to dominate. In an enterprise private network, integration with business systems, security policy and site-specific radio performance can outweigh almost everything else.
That is why operator-grade judgement matters. Experience helps you spot where a project is likely to break before it gets there. It also helps distinguish a genuine requirement from a fashionable one. Not every deployment needs private 5G. Not every connected device programme needs a complex eSIM strategy on day one. But some absolutely do, and missing that early can be costly.
Execution matters more than paperwork
A final point that often gets overlooked: due diligence is not a report-writing exercise. It is part of delivery. The best work informs negotiation strategy, implementation planning, supplier management and launch sequencing. It creates leverage because you know where the commercial pressure points are and where technical compromise is safe or dangerous.
That is also why businesses often bring in specialist support at this stage. Not for theory, but for informed challenge. Someone who has seen MVNOs, private networks and connected device programmes succeed and fail can test assumptions much faster than a generalist team working from first principles.
Christian Borrman’s approach has always been grounded in that reality: bespoke, operator-level due diligence shaped around the commercial model, technical architecture and operational burden of the specific service, not a recycled framework.
If your connectivity proposition matters to revenue, service continuity or investment confidence, treat diligence as part of the build, not an admin task before procurement. The earlier you find the weak points, the cheaper they are to fix.
