MVNE commercial choice: revenue-share vs managed service

Operator-MVNE contracts compress years of execution risk into a few pages of pricing, KPIs and remedies. The core decision is not cosmetic: revenue-share or managed service. Each routes margin, cash timing and accountability differently. For CFOs and wholesale heads, the fulcrum is the settlement cadence connecting wholesale inputs, tenant ARPU, and dispute windows. Get that wrong and churn tax, roaming IOT drift, and provisioning backlogs consume any headline discount.

Two archetypes, one P&L: what changes structurally

Revenue-share and managed service are not two pricing labels for the same operating model. They allocate the marginal dollar differently. They also decide who funds demand volatility, who absorbs billing friction, and who can force operational change when activation, porting or interconnect performance misses plan.

Under a revenue-share structure, the MVNO or tenant pays the enablement partner a defined percentage of Net Revenue across voice, SMS and data. Tiers usually step down as the installed base grows. Reporting tends to run monthly, sometimes with 30 or 45-day true-ups through OCS mediated usage and charging records. The commercial attraction is obvious: fixed run-rate is lower during launch, and the MVNE participates in growth rather than recovering all margin through setup fees and standing charges.

Managed service reverses the emphasis. The tenant or host pays a fixed fee, often with minimum commits, for a defined operating stack: BSS/OSS, eSIM RSP including SM-DP+, HLR/AuC, SMSC/MMSC, and SBC/SIP capacity. Wholesale inputs normally pass through, with change-order pricing for new interfaces, custom rating logic, additional ranges or non-standard reporting. The economic debate then moves from headline percentage to volume commitments, indexation, pass-through markups and the scope of included operations.

The margin waterfall exposes the difference. Interconnect termination, roaming IOT, A2P/SMSC fees, MNP dips, fraud operations, platform OPEX and customer-care integration do not disappear because a contract says Net Revenue. They sit somewhere. In revenue-share, exclusions and deductions decide how much revenue is actually shared. In managed service, the same items appear as pass-throughs, event fees or change-order lines. The breakeven point can move materially with small shifts in ARPU, roaming mix or message origination profile.

Control follows risk. Revenue-share aligns upside and can make sense where the tenant wants the enablement partner to share launch uncertainty. It can also dilute roadmap control because the provider will resist bespoke work that does not lift shared revenue. Managed service buys a more explicit operating promise. Acceptance criteria, SLA remedies, change budgets and step-in rights become the centre of gravity. The tenant pays for that control through minimums and less protection against slow commercial take-up.

Contract tenor also diverges. Revenue-share tenants often accept a longer ramp, because the provider needs time to recover launch effort through volume tiers. Managed service contracts focus more sharply on acceptance gates, service credit caps, termination assistance and step-in or insource options. A CFO should treat these clauses as economic instruments, not legal residue. They determine whether a miss in provisioning or settlement creates a cash remedy or merely an operational meeting.

Commercial mechanics: where each model wins or fails

The right model depends less on negotiating posture than on traffic variance, churn profile and cash conversion. A consumer app-aligned MVNO, a travel proposition or a seasonal roaming base will rarely forecast cohorts cleanly in the first year. Revenue-share absorbs part of that uncertainty. Lower fixed cost protects early cash, and upside-aligned tiers avoid a standing-charge burden while distribution channels are still being tested.

Stable enterprise, private APN and FWA plays point in the other direction. Attach rates are easier to model. Churn is lower. Provisioning defects are more visible to account managers and end customers. Managed service terms can then create a cleaner P&L. Once the fixed fee is absorbed, incremental IMSI cost should decline with scale, assuming the contract does not bury growth in profile, lookup and support event charges.

Churn changes the answer. Revenue-share tolerates aggressive go-to-market because the MVNE carries part of the ramp risk. That can be valuable where CAC recovery is uncertain. At maturity, the same percentage can become expensive. The tenant has already paid acquisition cost, retention has stabilised, and the provider continues to take a share of revenue that may no longer correlate with incremental effort. Managed service rewards discipline later in the curve. If churn is controlled, the per-subscriber platform cost compresses and margin becomes more predictable.

KPI drafting must follow the commercial logic. For revenue-share, tier uplifts and share reductions should depend on measurable scale and retention, not only gross adds. For managed service, rebates should attach to the operational events that move revenue recognition and customer lifetime value: SIM and eSIM activation success, MNP-in lead time, GTP/IMS registration, Diameter/SIP latency, OCS availability and eSIM profile download success. Credits that do not touch those events are usually weak financial controls.

Risk transfer should be explicit. Revenue-share gives the provider a claim on upside but also creates exposure to dispute timing, reconciliation and delayed true-ups. Managed service shifts the debate to SLA penalties, change-order governance, data access and continuity. Escrow, documented build procedures, source code access for custom components and operational runbooks reduce lock-in. They also affect valuation if the tenant is a platform business that expects later funding or sale.

A practical case illustrates the point. Tier-2 MNO, CEE, ~8M subscribers moved several SMB-oriented tenants from revenue-share to managed service after ARPU compression and invoice disputes pushed DSO beyond 60 days. The original model looked attractive during acquisition. It failed when retail discounts, A2P cost movement and porting exceptions made Net Revenue reconciliation the monthly bottleneck. The managed-service rewrite added fee floors, tighter provisioning KPIs and separated wholesale pass-through invoices from platform charges. Gross margin stabilised before subscriber growth recovered.

Numbers that matter: margin model and settlement terms

RFP comparability requires an apples-to-apples parameter pack. Without it, one bidder presents a low revenue share with broad Net Revenue deductions, another presents a managed fee with profile and event charges, and the finance team cannot model cohort economics. The pack should force each respondent to price the same subscriber bands, traffic assumptions, roaming exposure, support volumes and dispute mechanics.

Separate traffic-driven from event-driven costs. Interconnect, termination, roaming and data consumption move with usage. MNP dips, HLR queries, eSIM profile operations, fraud handling and manual support events move with lifecycle activity. Blending those lines into Net Revenue deductions hides OPEX and makes churn more expensive than the model first suggests. A base with modest ARPU but high port-in and support intensity can underperform a higher-usage base if lifecycle event costs are not visible.

Revenue-share tiers (illustrative)

0–20k subs: 12–15%; 20–100k: 9–12%; 100k+: 6–9% of Net Revenue

Managed service baseline

Monthly platform fee + per-IMSI/eSIM profile + per-activation; wholesale inputs pass-through with 0–3% admin markup

Net Revenue definition

Retail excluding VAT, refunds and chargebacks; clarify inclusion or exclusion of MNP fees, A2P surcharges and fraud losses

Minimums/commitments

Revenue-share: optional minimum Net Revenue or install-base floors; managed service: monthly fee floor and annual indexation

One-off setup

HLR/IMSI ranges, SM-DP+ onboarding, OCS integration, SBC interconnect, quoted as fixed with capped time and materials

Event fees

MNP dip: $0.02–$0.05 per lookup; HLR/AuC: $0.001–$0.005 per event; eSIM profile: $0.15–$0.50 per provision

Wholesale pass-through

Roaming IOT, interconnect termination, A2P MT fees, markup 0–3% admin or none under MFN clause

Settlement cadence

Monthly invoicing; due net 30–45; dispute window 10–20 business days; audit right annual with 2–3% error threshold

SLA credits cap

Typically 10–15% of monthly fee under managed service or 1–2% Net Revenue under revenue-share

The settlement terms are often more valuable than the headline price. Monthly invoicing with net 30 may look equivalent across bids, but the cash outcome changes if one contract allows broad netting, another requires gross settlement, and a third lets the provider suspend service for aged amounts that include disputed items. Security deposits, payment assurance, audit windows and error thresholds should be modelled as working-capital variables.

For CFO review, the model should show at least three cohorts: launch volatility, base case and mature retention. Each should include ARPU, churn, gross adds, port-in ratio, roaming ratio, A2P exposure, profile downloads and support events. Sensitivity should then test a two-point movement in revenue share, a 10% traffic mix shift, a 15-day DSO extension and a one percentage point change in churn. Those four tests usually reveal whether the contract is robust or merely well presented.

Negotiation choreography and KPI instrumentation

The negotiation should start with structure, not discount. Split the RFP into a base SOW and optional growth modules. Base scope should cover the launch stack, operational responsibilities, reporting feeds, settlement files and acceptance criteria. Optional modules can include RCS Business Messaging, 5G SA data, SCEF/NEF exposure, additional roaming zones and advanced fraud operations. Each module needs pricing guardrails, delivery assumptions and a change request tariff.

Tier design should carry incentives both ways. Revenue-share can step down with volume, but the step-down should also require retention and settlement hygiene. A tenant that grows gross adds while producing high churn, chargebacks and disputes should not receive the same economics as a tenant with clean cohorts. Managed service rebates should be automatic where measurement is objective: at least 98.5% activation success, no more than two business days for MNP-in where donor conditions are normal, and at least 99.95% OCS uptime for charging availability.

Traffic quality KPIs need equal precision. SIP ASR and NER should be tracked by destination group, not only in aggregate. Diameter and GTP latency should use agreed percentiles, with exclusions defined for host-network or upstream failures. Attach success should distinguish SIM inventory faults, profile entitlement issues and core registration failures. P95 eSIM profile download time should be measured from entitlement to successful profile installation, not from email dispatch or QR code generation.

Cash risk controls are part of the operating design. Deposits or performance bonds sized to one or two months of exposure can be reasonable, but they should reduce as payment history and installed base stabilise. Gross settlement with selective netting keeps ageing visible. Cure periods should be short for non-payment but narrower for disputed lines. Set-off should not allow a tenant or provider to withhold an entire traffic invoice because of a small platform credit.

Exit mechanics should be priced before they are needed. eSIM profile migration must follow a defined SM-DP+ change procedure. Number ranges, MNP records, rating data, subscriber exports and operational documentation need delivery formats and deadlines. Data escrow should cover custom configuration as well as code where bespoke work is material. Termination assistance should have a fee cap, ideally expressed as a percentage of trailing fees with a declining glide path after the first renewal.

A second case shows the value of instrumentation. MVNE servicing 12+ tenants in EMEA raised net margin by approximately 3 percentage points after converting soft KPI targets into automatic credits linked to measured SLA breaches. The commercial change was not punitive. It clarified accountability. Tenants stopped escalating anecdotal service complaints into settlement disputes, and the provider gained a cleaner basis for defending invoices where network-side causes sat outside its control.

The closing test is simple. Pick the model that matches ARPU volatility, churn curve and cash discipline, then instrument it. The delta between a tidy headline share and a healthy P&L is usually found in the settlement schedule and KPI remedies, not in the first page of pricing.