Launching an MVNO is hard. Operating one is harder. But the hardest part — the part nobody warns you about — is building the executive team that can take the business from post-launch survival to sustainable, profitable growth.

I've spent two decades in wireless, and I've worked with enough MVNOs to know that the difference between the ones that scale and the ones that stall almost always comes down to six roles: the CEO, the CRO, the CFO, the CPO, the COO, and the CTO. Not whether you have them — whether you have the right people in them.

Today I'm launching The Post-Startup C-Suite — a six-part series that defines what each of these roles actually requires in an MVNO, what the right person looks like, what the wrong person costs you, and how to tell the difference before it's too late.

The Series

Part 1: The CEO — The CEO Who Built the MVNO Is Not Always the CEO Who Can Run It.
The skills that build an MVNO from zero are not the same skills that scale it from 10,000 to 100,000 subscribers. This piece covers the hardest transition in the business — from founder who does everything to executive who builds the team and holds them accountable. The good CEO who lets go and leads. The bad CEO in three failure modes: the founder who won't stop founding, the absentee strategist, and the one who can't make the hard call.

Part 2: The CRO — Your MVNO Doesn't Need a Sales Leader. It Needs a Revenue Operator.
The CRO who can build a beautiful strategy deck but can't tell you which dealers are producing and which aren't on a Tuesday afternoon isn't operating — they're narrating. This piece defines the dual-channel operator the MVNO actually needs, what a "roadmappable" sales strategy looks like, and why the wrong CRO hire costs 12-18 months of growth that didn't happen.

Part 3: The CFO — The CFO Your MVNO Actually Needs Is the One Who Says No.
The CFO who approves every plan launch and every commission restructuring without running the margin model isn't managing the finances — they're observing them. This piece covers the three scenarios where the CFO's "no" protects the business, why some MVNOs are better served by a finance analyst and an accountant than a CFO who won't push back, and the CFO-CRO and CFO-CPO dynamics that determine whether the MVNO grows profitably or bleeds.

Part 4: The CPO — Your Head of Product Is Costing You a Small Fortune — And They Don't Even Know It.
The MVNO CPO is building products on a constrained design space — someone else's network, someone else's rate card, someone else's provisioning system. This piece defines the product development framework that every MVNO plan launch should follow, the Product Requirements Document nobody writes, and what happens when the "wall-thrower" CPO refuses to use the tools at their disposal.

Part 5: The COO — The Operator of Operators.
Who makes sure the CRO's dealer channel is selling plans the CPO designed on wholesale foundations the CFO validated, that billing ops can reconcile and compliance has filed for? The COO. This piece covers the operating cadence, cross-functional handoff management, and the two failure modes — the meeting facilitator who confuses coordination with operation, and the bottleneck who builds a dependency instead of a system.

Part 6: The CTO — Your BSS Is Not a Technology Problem. It's an Operations Problem with a Technology Solution.
The MVNO CTO doesn't build software. They own the technology stack that makes every other function possible — BSS, provisioning, payment processing, dealer portal, tax engine, CDR pipeline, and every integration between them. This piece covers why most MVNO CTO hires fail because they come from software development rather than telecom operations, what the CTO actually owns versus what they delegate, and why the CTO who falls in love with the platform instead of the business outcomes it serves becomes the most expensive bottleneck in the organization.

Why This Series

Every one of these articles comes from the same observation: the post-startup MVNO doesn't fail because the market opportunity is weak or the technology doesn't work. It fails because the executive team can't operate.

The CEO who can't let go of the work they love. The CRO who strategizes but doesn't execute. The CFO who documents but doesn't challenge. The CPO who launches but doesn't validate. The COO who coordinates but doesn't enforce. The CTO who builds but doesn't integrate. Each one, individually, creates drag. Together, they create an organization that burns cash, bleeds margin, and wonders why growth isn't materializing.

The right people in these six seats — operators who are disciplined, accountable, and willing to do the unglamorous work — change everything. That's what this series is about.

A note before we begin: these articles are direct, and not every take will land comfortably. The observations in this series are my own — shaped by two decades of experience across the wireless industry. They're not aimed at any specific company or individual. They're patterns I've seen repeat often enough to write about, in the hope that the next operator can learn from what I've watched others get right and get wrong.