A weak wholesale agreement can turn a credible MVNO proposition into a margin problem before the first customer is connected. This MNO negotiation strategy guide is for leaders who need more than a rate card: they need a host-network relationship, technical design and commercial model that will still work when volumes rise, customer behaviour changes and the business asks for more.
The central mistake is treating an MNO negotiation as a procurement exercise. It is a business-model negotiation. The network operator is assessing risk, operational effort, channel conflict, expected volumes and whether your team can deliver what it says. You should be assessing far more than headline unit pricing: the constraints that will shape your product, cash flow, customer experience and ability to differentiate.
Start with an investable case, not a pricing request
An MNO can spot an unprepared opportunity quickly. A vague request for “the best wholesale rates” signals that the buyer has not decided who the customer is, what the offer needs to do or how demand will be generated. That creates risk for the operator, and risk is priced into the deal.
Before approaching the market, define the proposition in operational terms. Is this a consumer SIM business, an enterprise mobility offer, an IoT deployment, a public-sector connectivity programme, or a connected-vehicle service? Each creates a different traffic pattern, support burden, fraud profile and commercial logic. An EV charging estate with low-bandwidth telemetry is not negotiated like a data-heavy consumer proposition. A private-network extension with managed devices carries different dependencies again.
Your business case should show realistic subscriber or connection forecasts, expected usage by service type, acquisition routes, retention assumptions and gross-margin logic. Do not inflate volumes to gain attention. Operators will test the numbers against your funding, route to market and team capability. If the forecast later collapses, minimum commitments and credit exposure will remain.
The stronger position is to show a credible base case, a growth case and the operational milestones that make each one possible. This allows you to ask for commercial flexibility tied to evidence rather than making promises you cannot keep.
The MNO negotiation strategy guide: know what drives value
Headline price matters, but it rarely determines whether an MVNO succeeds. A lower domestic data rate can be overtaken by expensive out-of-bundle charging, restrictive fair-use rules, poor roaming economics or a costly change-control process. The agreement must be read as a connected system.
The commercial discussion should cover domestic voice, SMS and data, but also the charging model behind them. Clarify whether data is rounded per session, whether there are minimum charges, what happens after allowances are exhausted and how usage records are rated. Small billing mechanics become material when multiplied across a customer base.
Minimum monthly commitments deserve particular scrutiny. They can be sensible where the MNO is investing in integrations, operational support or bespoke product capability. They become dangerous when they are based on optimistic timing rather than proven customer demand. Seek a ramp that reflects the launch plan, with clear triggers for volume steps and practical remedies if activation is delayed by an issue outside your control.
Credit terms are equally strategic. A fast-growing connectivity business can look profitable on paper while consuming cash through prepaid wholesale charges, deposits and delayed customer collections. Model the working-capital requirement at launch and at scale. If the numbers do not work, the answer is not simply to negotiate harder; it may mean changing the proposition, funding plan or customer payment structure.
Build a full cost view
A proper comparison includes one-off implementation fees, platform charges, SIM and eSIM costs, support fees, number management, porting, roaming, fraud controls, reporting, testing, change requests and exit costs. Ask what is included, what is chargeable and who owns the cost when a fault crosses organisational boundaries.
For IoT and connected-device programmes, look beyond standard airtime. Consider long-life device behaviour, low-usage connections, permanent roaming restrictions, steering policies, IP addressing, private APN requirements, SMS routing, suspension rules and lifecycle management. A commercial schedule designed for handsets may be wholly unsuitable for thousands of deployed devices that cannot be physically accessed easily.
Negotiate the operating model alongside the contract
Many otherwise sound deals fail after signature because the parties never agreed how the service will be run. Commercial teams may agree a launch date while technical, provisioning, care and finance teams are working to different assumptions.
Define the service boundary. Who supplies the core platform, manages the SIM or eSIM profile, provisions customers, handles number porting, monitors fraud, answers first-line queries and owns incident communication? Where does the MNO’s responsibility end, and where does yours begin? Ambiguity creates slow fixes, frustrated customers and avoidable cost.
Service levels need practical measures, not decorative percentages. Ask how availability is calculated, what exclusions apply, how severity is classified and what escalation route operates outside office hours. For a mission-critical fleet, agricultural monitoring estate or security application, response and restoration times may matter more than a generic monthly availability figure.
Data access is another frequent blind spot. You need enough timely information to manage usage, investigate faults, reconcile invoices and support customers. Specify the reports, APIs or portals required, their cadence, retention periods and ownership. If your proposition depends on automated controls, verify that the relevant actions can be executed programmatically rather than through a manual support queue.
Treat technical capability as a commercial variable
The MNO’s network footprint and technology roadmap influence what you can sell. Coverage should be assessed against the actual customer geography, not a national marketing claim. Test indoor environments, rural routes, ports, depots, event venues or other locations that define the use case.
Be precise about required capabilities. These may include eSIM support, multi-IMSI, private APNs, static IP addresses, voice over LTE, 5G access, SMS APIs, device-management integration or wholesale roaming. Do not accept a broad assurance that a feature is “available”. Establish whether it is available to your specific wholesale model, what the implementation lead time is, what it costs and whether it is supported at the scale you expect.
Roadmap commitments should be handled carefully. An MNO may have every intention of introducing a feature, but internal priorities change. Where a future capability is fundamental to your offer, agree decision points, dependencies and a meaningful remedy if it does not arrive. In some cases, the right decision is to delay the proposition rather than launch on an assumption.
Create leverage without damaging the relationship
Competitive tension is useful. Running a disciplined process with more than one credible MNO or wholesale partner improves your information and reduces dependency. It also reveals material differences in culture, speed and willingness to solve problems.
That does not mean using every conversation as a threat. The goal is a workable long-term relationship, particularly where the MNO will be supporting non-standard requirements. Be direct about your decision criteria and make commitments only when they are within your control. A network operator is more likely to invest effort when it sees a prepared partner with a credible route to revenue.
Your leverage is strongest when it is based on substance: a differentiated customer segment, committed distribution, technology that creates usage, funded deployment, experienced delivery leadership or a proposition the MNO cannot easily replicate through its own channels. Price pressure alone is rarely a durable negotiating position.
Protect the business when circumstances change
The agreement should anticipate the problems most teams hope will not happen: delayed launch, poor provisioning, a platform migration, a security incident, a network sunset, disputed invoices or an MNO change in strategic direction.
Pay particular attention to exclusivity, term length, termination rights and migration support. Exclusivity can be justified where the MNO is providing meaningful investment or a genuinely unique capability. Otherwise, it may leave you exposed if performance or commercial alignment deteriorates. A long initial term can secure certainty, but it can also lock in a pricing structure that no longer reflects your scale.
Exit provisions are not pessimism. They are operational discipline. Establish how customers, numbers, SIM inventories, eSIM credentials, usage records and service configurations can be transferred if necessary. Migration is never effortless, but a deal that ignores it gives the other party too much control.
Enter negotiations with the right team
The best MNO negotiations bring commercial, technical, operational and legal expertise into the room early. A lawyer can protect wording, but cannot decide whether a charging event, API limitation or roaming restriction will undermine the offer. A sales lead can articulate demand, but may not see a provisioning dependency that adds six months to launch.
This is where specialist operator-side experience earns its place. Christian Borrman’s work across MVNO launches, private mobile networks and connected-device programmes is built around connecting the commercial promise to the technical and operational reality before that gap becomes expensive.
Do not aim to win a rate-card argument. Aim to leave with an agreement that supports the customer proposition you intend to run, the cash profile you can fund and the operational standard your market expects. That is the negotiation outcome worth protecting.
