Part of the series: The Post-Startup C-Suite

This is the fourth article in The Post-Startup C-Suite series, following pieces on the CEO, the CRO, and the CFO. If those three articles were about the people who lead the company, sell the product, and protect the margin, this one is about the person who designs the thing the CRO and CFO are both fighting over.

And in most MVNOs, that person is doing it wrong.

The Constrained Design Space

Here's the fundamental thing that separates MVNO product from every other kind of product management: you don't control your own platform.

A SaaS CPO can dream up a feature, spec it, build it, ship it. The design space is limited only by engineering capacity and market demand. An MVNO CPO is building commercial offers — rate plans, add-ons, bundles, promotional packages — on top of someone else's network, someone else's wholesale rate card, and someone else's provisioning system.

Every plan you launch has to map to a specific wholesale SKU that the MNO or MVNA actually offers. It has to configure correctly in the BSS. It has to calculate taxes and regulatory fees by jurisdiction. It has to produce margin at realistic subscriber usage levels — not the average usage you assumed, but the 80th-percentile usage that determines whether the plan is actually profitable for the heaviest 20% of subscribers on it.

The CPO who doesn't internalize these constraints will design products that are commercially attractive and operationally impossible. Beautiful plans that can't be billed correctly. Competitive prices that lose money on every activation. Promotional offers that create reconciliation nightmares because nobody checked whether the BSS could rate them properly.

MVNO product management is not a creative exercise. It's an engineering discipline with commercial objectives — and the engineering runs through wholesale economics, BSS configuration, billing operations, and regulatory compliance. Skip any of those and you're not launching a product. You're launching a problem.

What a Product Development Framework Actually Looks Like

The disciplined CPO follows a sequence. Every step has a deliverable. Every step has a gate. Skip a step and you're launching a product you can't support, can't bill correctly, or can't make money on.

Step 1: Market Opportunity. What customer need does this plan address? What competitive gap does it fill? What subscriber segment is it targeting? This is the only step that looks like traditional product management — and it's the step most wall-throwing CPOs stop at.

Step 2: Wholesale Feasibility. Can the MNO or MVNA actually support this plan structure? Which wholesale base plan SKU would underpin it? What's the per-line cost at the MVNO's current volume tier? What QoS tier, data allotment, and throttle/deprioritization threshold does the wholesale plan provide? If the answer is "I'm not sure" or "I'll figure that out later," the process stops here until the answer is specific.

Step 3: Margin Modeling. What's the gross margin at average usage? At 80th-percentile usage? At maximum realistic usage? What's the breakeven usage point? What's the margin after dealer commission for dealer-acquired subscribers? What's the margin after regulatory fees and taxes in high-tax jurisdictions? The CFO should co-own this step — and if they haven't signed off, the plan doesn't advance.

Step 4: BSS Configuration and QA. Can the BSS actually rate this plan correctly? Has the plan been configured in staging and tested with simulated subscriber activity? Does the rating behavior match the plan description? Do the taxes calculate correctly? Does the plan interact properly with existing plans (upgrades, downgrades, migrations)? Billing operations should validate this step — not product, not engineering, billing operations, because they're the ones who will reconcile it every month.

Step 5: Operational Readiness. Is the billing operations team prepared to reconcile this plan against wholesale invoices? Is customer care trained on the plan's terms, limitations, and common questions? Are dealer materials and training updated? Is the plan's tax treatment (inclusive vs. exclusive) documented and communicated?

Step 6: Launch with Defined KPIs. Launch with explicit success criteria: target subscriber volume at 30/60/90 days, actual margin versus modeled margin, churn rate on the plan versus portfolio average, and a defined review date. If the plan doesn't meet minimum thresholds at the 90-day review, it gets redesigned or retired. Not "monitored." Not "given more time." Redesigned or retired.

That's six steps. None of them are complicated. All of them are skipped routinely.

The Product Requirements Document Nobody Writes

The PRD for an MVNO plan launch isn't a user story. It isn't a feature spec. It isn't a one-page brief that says "we need a $35 unlimited plan to compete with Carrier X."

It's a commercial and operational specification that documents everything required to launch, operate, and evaluate the plan. At minimum:

The wholesale base plan SKU and per-line cost at current volume tier. The customer-facing plan price, data allotment, speed tier, and all inclusions. The margin model at average, 80th-percentile, and maximum usage — signed off by the CFO. The breakeven usage point. The BSS configuration requirements and QA test results. The tax and regulatory fee treatment (inclusive vs. exclusive, jurisdiction-specific calculations confirmed). The distribution channel availability and commission impact by channel. The competitive positioning rationale — why this plan, why now, why at this price. The success and failure criteria with a defined 90-day review date.

A CPO who launches a plan without this document is gambling with the company's margin. They might win the bet. They might not. But they won't know which one it is until the CFO discovers the answer in a quarterly financial review — months after the damage has compounded across thousands of subscribers.

The Wall-Thrower

Now let me describe the CPO I keep encountering — the one who treats product as a creative exercise rather than an engineering discipline.

The wall-thrower launches plans based on competitive reaction. "Competitor X just dropped to $30 unlimited — we need one too." No wholesale feasibility check. No margin model. No BSS testing beyond confirming it activated in staging. The plan goes live because the competitive pressure feels urgent and the process feels slow.

The wall-thrower launches plans based on marketing intuition. "Customers want more data." "The market is moving to unlimited." "We need a family plan." All potentially true — but none of these statements constitute a business case. "Customers want more data" doesn't tell you which wholesale SKU to use, what the margin looks like at real usage levels, or whether the BSS can rate a shared family data pool correctly.

The wall-thrower launches plans based on CEO pressure. "We need something new this quarter." So the CPO designs a plan in a week, gets it into the BSS in two weeks, and launches it in three. No PRD. No CFO sign-off. No billing operations review. And six months later, the CFO discovers it's losing money on every dealer-acquired subscriber because nobody modeled the residual commission impact against a wholesale cost that was $3 higher than assumed.

Here's what the wall-thrower's portfolio looks like after 18 months:

Twelve active plan tiers. Should be four or five. Six add-on packs. Should be one or two. Three legacy promotional plans that can't be retired because subscribers are still on them and nobody built a migration path. A BSS configuration so complex that billing operations spends 15 hours a month auditing plan-level rating accuracy. And a margin profile that varies by 20 points across the portfolio because nobody validated the wholesale mapping before launch.

That's not a product portfolio. That's a mess. And cleaning it up — sunsetting plans, migrating subscribers, renegotiating wholesale SKU assignments, reconfiguring the BSS — takes 6-9 months of work that shouldn't have been necessary if the plans were built correctly in the first place.

The Downstream Damage

When the CPO doesn't follow the framework, every other function in the MVNO pays the price.

Billing operations inherits plans they can't reconcile. The wholesale mapping was never documented, so the reconciliation analyst doesn't know which MNO invoice line items correspond to which customer-facing plans. Discrepancies that should take minutes to investigate take hours. Disputes that should be filed within the 30-day contractual window get missed because nobody can untangle the rate plan architecture.

Finance inherits margin surprises. The CFO built the financial model on the assumption that blended gross margin is 38%. Twelve months of undisciplined plan launches later, actual blended margin is 29% — and nobody can explain the 9-point gap without a plan-by-plan forensic analysis that takes weeks.

Customer care inherits subscriber confusion. When the portfolio has 12 plan tiers with overlapping data allotments and unclear differentiation, subscribers can't understand what they're paying for, agents can't explain the differences, and plan change requests become a top-3 call driver. Every unnecessary customer care contact costs $3-$8. Multiply that by thousands of confused subscribers per month.

Sales inherits a product they can't sell cleanly. The CRO needs a simple story for dealers: here are our plans, here's how they're different, here's why a customer should choose each one. When the portfolio is a patchwork of overlapping tiers, legacy promotions, and add-on packs that even the product team can't explain coherently, the dealer sells whatever is easiest — which is usually the cheapest plan, regardless of margin.

Regulatory and tax compliance inherits plans where the tax treatment was never defined. Is this plan tax-inclusive or tax-exclusive? What happens when a subscriber on a promotional rate transitions to the standard rate — does the tax calculation change? Nobody documented it because the wall-thrower didn't include tax treatment in the launch process. Now the tax engine is producing incorrect calculations on a plan with 8,000 subscribers, and the liability has been accumulating for months.

Accountability and Consequences

The CPO's accountability is plan-level profitability. Not subscriber growth on a plan. Not competitive positioning. Not "we launched six new plans this quarter." Profitability.

Every plan in the portfolio should have a quarterly P&L review: actual margin versus modeled margin, actual usage distribution versus the assumptions in the original margin model, actual channel mix versus projected, and actual churn on the plan versus portfolio average. Plans that fall below 25% gross margin at 80th-percentile usage get redesigned or retired. Plans that were never modeled in the first place get modeled now — and if the retroactive analysis shows they're unprofitable, they get retired immediately.

The CPO who cannot produce a plan-level P&L for every active plan in the portfolio is not managing a product suite. They're managing a menu — and menus don't have accountability.

The consequence of the wall-throwing approach is always the same: a painful portfolio rationalization project that the next CPO (or an external advisor) has to execute. Sunsetting plans. Migrating subscribers who don't want to move. Reconfiguring the BSS. Rebuilding the wholesale mapping documentation from scratch. Admitting to the board that half the product launches in the last 18 months were mistakes that created operational overhead and margin erosion across the entire business.

That cleanup costs 6-9 months and $100K-$300K in direct and indirect costs. The framework that would have prevented it costs nothing — just discipline.

What to Look For

The CPO who works in an MVNO has a specific profile:

They've built rate plans on a wholesale foundation. Not designed consumer products. Not managed a SaaS feature backlog. Built wireless rate plans that had to map to specific wholesale SKUs, configure in a BSS, and produce margin at real-world usage levels. This is a non-negotiable prerequisite.

They speak wholesale economics fluently. Per-line access fees, QoS tiers, deprioritization thresholds, volume tier pricing, overage mechanics. If they can't have a technical conversation about the wholesale rate card, they can't design plans that work on it.

They use a product development framework — and refuse to skip steps. Ask them about a time they said no to a plan launch. If they've never killed a plan that couldn't be margin-modeled or BSS-validated, they've never operated with discipline.

They can produce a PRD. Give them a scenario in the interview — a new plan concept — and ask them to outline the PRD. If they start with "the customer value proposition" and never mention wholesale cost, BSS configuration, or margin modeling, they're a consumer product manager, not an MVNO CPO.

They own plan-level P&Ls. They don't just launch plans. They monitor, evaluate, and retire them. They treat the portfolio as a living system that requires ongoing management, not a collection of launches that accumulate over time.

Recommendations

Require a PRD for every plan launch. No exceptions. No "we'll document it after launch." The PRD — including wholesale mapping, margin model, BSS configuration requirements, and tax treatment — is a launch prerequisite. The CPO who pushes back on this requirement is telling you they don't want accountability.

Require CFO sign-off on the margin model. The CPO and CFO must co-own plan economics. Product designs the plan. Finance validates the math. Neither has unilateral authority. This is the single most important governance mechanism in MVNO product management.

Conduct quarterly plan-level P&L reviews. Actual margin versus modeled. Actual usage versus assumed. Actual channel mix versus projected. Every plan. Every quarter. Plans below threshold get action plans or retirement dates.

Cap the active plan portfolio. Three to five core tiers. One to two add-ons. That's it. Every additional plan beyond this cap requires a documented justification that includes the operational cost of portfolio complexity — billing operations hours, customer care impact, BSS configuration maintenance. Force the CPO to account for the downstream cost of every plan they add.

Make the decision at six months. If the CPO has not established a product development framework, produced PRDs for existing plans, and initiated a portfolio rationalization within six months, the role is not working. The wall-thrower doesn't become disciplined with more time — they just throw more things at more walls.