A warehouse with patchy Wi‑Fi, an automated vehicle trial that loses connection at the wrong moment, or a port estate trying to coordinate cameras, handhelds and sensors can all make private 5G look like an obvious answer. The difficult part is not buying radio equipment. A private 5G consultant earns their place by establishing whether 5G is genuinely the answer, what it must achieve commercially, and how to deploy it without creating a costly, isolated technology project.
Private networks sit at the meeting point of radio engineering, IT architecture, security, operations, procurement and business change. Decisions made early – on spectrum, coverage, devices, integration and operating model – shape the cost and usefulness of the network for years. That is why generic strategy work and supplier-led design sessions are rarely enough.
Start with the operational problem, not the radio
Private 5G is often discussed in terms of speed, low latency and dedicated capacity. Those are capabilities, not a business case. The starting point should be a specific operational constraint that is expensive, unsafe, slow or impossible to solve using the current connectivity estate.
For a logistics operator, that may mean maintaining reliable connectivity across a large yard where Wi‑Fi roaming fails and public coverage is inconsistent. For a manufacturer, it may involve supporting machine vision, AGVs and production telemetry without compromising network segregation. A local authority may be assessing connectivity for public safety, environmental monitoring or transport infrastructure. An event organiser may need temporary, managed connectivity for payment systems, production crews and operational teams.
The same technology can be appropriate in each case, but the design will not be the same. A credible plan defines the users, locations, applications, traffic profiles, service levels and failure consequences before it specifies a network. It also asks an uncomfortable but valuable question: could upgraded Wi‑Fi, public 5G, fibre, LTE or a mixed approach do the job at lower cost and lower operational burden?
That is not a reason to avoid private 5G. It is how to make the case defensible.
What a private 5G consultant should actually do
The best advisory work reduces ambiguity before ambiguity turns into spend. It should not stop at a slide deck describing an attractive future state. A private 5G consultant needs to work through the decisions that suppliers may treat as assumptions and internal teams may not yet have the time or specialist knowledge to resolve.
Build a business case that survives scrutiny
A strong business case joins technical performance to measurable outcomes. It might quantify reduced downtime, fewer manual interventions, improved asset utilisation, safer operations, faster turnarounds or avoided cabling costs. It should separate direct network costs from the costs of devices, integration, site works, cyber controls, support and application change.
This is where many proposals become optimistic. A radio access network may be only one part of the investment. If the intended value relies on automated vehicles, AI cameras or connected field equipment, the programme must account for device certification, SIM or eSIM lifecycle management, application integration, data handling and support processes. The network is an enabler, not the finished service.
There should also be a view of what happens at scale. A pilot can be funded from an innovation budget. A multi-site deployment needs a repeatable commercial model, procurement route, installation method and operational ownership. If those are unclear, a pilot may prove a technology but still fail to become a viable programme.
Make spectrum and architecture decisions with intent
Spectrum is central to private cellular, yet it is often raised late in the process. Available bands, licensing terms, geography, interference risk and power limits affect coverage, capacity, equipment choice and deployment timing. The right answer differs between a single industrial site, a large rural estate, a campus, a temporary event and a mobility corridor.
Architecture choices matter just as much. Organisations need to decide where the core network sits, how it connects to existing IT and operational technology environments, how users authenticate, where data is processed, and what remains available when the wider network is unavailable. An edge-hosted application may have a genuine latency or resilience requirement. In other cases, a more centralised design will be simpler to manage and less costly.
Private 5G does not remove the need for disciplined security. It changes the security model. Segmentation, identity management, device posture, remote access, auditability and incident response must be designed across the whole service. Security teams need more than reassurance that cellular authentication is strong. They need clarity on interfaces, responsibilities and operating procedures.
Challenge suppliers without slowing the programme
There are excellent vendors in private 5G, but every vendor has a preferred architecture and a product set to sell. That is normal. The client still needs an independent view of what is essential, what is optional and what has been deferred rather than solved.
A useful consultant translates requirements into an evaluation process that compares suppliers on more than headline radio performance. Device support, integration capability, deployment experience, commercial terms, management tooling, support model, upgrade path and accountability all deserve scrutiny. So does interoperability. A design that works only with one supplier’s tightly controlled ecosystem can be sensible for a contained use case, but it introduces a different kind of dependency.
The aim is not to run an endless procurement exercise. It is to give decision-makers enough evidence to select a partner confidently, negotiate from an informed position and avoid discovering critical limitations after contracts are signed.
The work after the pilot matters most
Private network programmes commonly lose momentum after a successful demonstration. The pilot proves that a camera connects, a vehicle roams or a sensor reports data. It may not prove that the solution can be installed repeatedly, supported at two o’clock in the morning, expanded to new sites or owned by a business-as-usual team.
The transition from trial to service requires operational design. Who provisions SIMs and devices? How are faults triaged between the network provider, IT team, application supplier and device manufacturer? What monitoring is needed, and who responds to alarms? How will configuration changes be controlled? Which performance measures prove that the network is delivering the intended outcome?
These questions are particularly important for organisations operating connected fleets, EV charging and monitoring estates, automated vehicles or distributed IoT deployments. Connectivity failures are rarely experienced as a simple network issue. They surface as missed journeys, unavailable chargers, delayed goods, poor customer experience or an operational safety concern. Clear workflows and ownership reduce that exposure.
There is also a practical choice between building internal capability and relying on managed services. Neither is automatically right. Large enterprises with established network and security functions may want deeper internal control. A specialist operator or growing business may get better results from a managed model, provided service boundaries and escalation routes are explicit. The decision should reflect the criticality of the operation, not an abstract preference for ownership.
When private LTE may be the better answer
Not every private cellular requirement needs 5G on day one. Private LTE remains a sensible option for many voice, data, telemetry and mobility use cases. Device availability can be stronger, implementation can be less complex, and the performance may comfortably meet the real requirement.
A phased approach can be commercially intelligent: establish coverage, mobility and operational processes with LTE, then introduce 5G where higher capacity, advanced device support or specific application needs justify it. Conversely, where the programme depends on modern 5G device capabilities or a long-term platform for demanding industrial use cases, designing only for LTE may create an avoidable migration problem.
The point is not to advocate one standard over another. It is to align the technology roadmap with the business roadmap, device lifecycle and investment horizon.
Signs you need specialist intervention
External expertise is especially valuable when a programme has stalled between concept and deployment, when supplier proposals are difficult to compare, or when senior stakeholders disagree on what the network is supposed to deliver. It is equally relevant when an organisation has inherited a pilot with no route to scale, or when the technical design is advancing faster than the commercial case.
Christian Borrman’s approach is built around this execution gap: bringing operator-grade commercial and technical judgement to the decisions that determine whether a connectivity programme launches, scales and remains useful. That can mean shaping the initial feasibility work, recovering a troubled project, supporting MNO or supplier negotiations, or putting the operational model in place before rollout.
The most valuable question to ask is not, “Do we need private 5G?” Ask which operational result is worth funding, what evidence is needed to support it, and who will be accountable for delivering it once the equipment is live. Get those answers right, and the network becomes a working part of the business rather than another impressive pilot left on the shelf.
