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

This is the fifth article in The Post-Startup C-Suite series. I've written about the CEO who needs to transition from founder to executive. The CRO who needs to be an operator, not a strategist. The CFO who needs to say no. The CPO who needs to follow a framework instead of throwing things at walls. Each of those articles describes a role with specific accountability for a specific function.

But here's the question none of those articles answer: who makes sure all of those operators — and every other function in the MVNO — are actually operating in concert?

Who ensures the CRO's dealer channel is selling plans that the CPO designed on wholesale foundations that the CFO validated, that billing operations can reconcile, that compliance has filed for, and that customer care can support? Who catches the handoff failures between functions before they become customer-facing disasters? Who runs the operating rhythm that turns a collection of functional leaders into a functioning business?

That's the COO. The operator of operators. And in my experience, it's the most misunderstood, most misfilled, and most consequential role in the post-startup MVNO.

Why the Role Exists

Let me be direct about something: the COO role is not a given. Plenty of companies operate without one. In a startup with 10 people, the CEO is the de facto COO — they're in every meeting, they see every handoff, they catch every gap. The CEO-as-COO model works when the organization is small enough that one person can hold the entire operation in their head.

It stops working around 25-40 employees, or around the point where the MVNO has a dedicated CRO, CFO, CPO, billing operations team, customer care team, and compliance function. At that point, the CEO has a choice: continue being the COO (which means they're not being the CEO — they're not doing strategy, fundraising, board management, partnership development, or market positioning), or hire someone whose entire job is to make the operational machine work.

Most MVNOs that fail to make this transition don't fail because of bad strategy. They fail because the CEO is buried in operational firefighting, the C-suite functions are operating in silos, and nobody is connecting the dots between product, sales, finance, billing, compliance, and customer care. The plan launches but billing ops wasn't configured. The dealer channel is growing but nobody told compliance to file in the new states. The BSS got updated but nobody tested whether existing plans still rate correctly.

These aren't failures of individual functions. They're failures of operational integration. And operational integration is the COO's job.

What the COO Owns

The COO doesn't own revenue — the CRO does. The COO doesn't own the product — the CPO does. The COO doesn't own the financials — the CFO does. The COO owns the system that connects all of them.

That sounds abstract, so let me make it specific.

The Operating Cadence

The COO owns the weekly operating rhythm. Not the board meeting. Not the quarterly strategy review. The weekly cadence that forces every function to report on its commitments, surface its blockers, and coordinate its handoffs.

A functioning weekly operating review covers: subscriber growth versus forecast (CRO), plan-level margin versus model (CFO + CPO), billing operations reconciliation status and dispute pipeline (billing ops), customer care volume and resolution rates (care), compliance calendar status (compliance), and platform/vendor issues (technology). Every function reports. Every function is accountable. Every cross-functional dependency is surfaced and tracked.

The great COO runs this meeting in 60-75 minutes, holds people to specific numbers rather than narratives, and follows up on commitments that were missed. The bad COO turns it into a 2-hour information-sharing session where everyone presents slides and nobody is accountable for anything.

Cross-Functional Handoff Management

This is where the COO earns their salary. Every major operational event in an MVNO requires coordination across multiple functions. A plan launch touches product, wholesale, BSS configuration, billing operations, customer care, compliance, sales, and marketing. A new state expansion touches compliance (PUC filing), tax (jurisdiction configuration), sales (dealer recruitment), and care (agent training). A BSS platform update touches technology, billing operations, product (rating validation), and customer care.

The COO owns the launch sequence — the specific order in which things must happen, the dependencies between steps, and the validation that each step was actually completed. Not delegated and assumed done. Validated and confirmed.

When a plan launches and billing operations discovers two weeks later that the BSS wasn't configured correctly, that's not a billing ops failure. That's a COO failure — or the absence of a COO. Someone should have enforced the launch checklist that includes BSS validation by billing operations before the plan went live. That someone is the COO.

Vendor and Platform Management

The MVNO operates on a stack of third-party platforms and vendor relationships: BSS/OCS vendor, MNO or MVNA wholesale partner (at the operational level), tax engine provider, payment processor, SIM vendor, customer care platform, and dealer portal. Each of these vendors has its own SLAs, support processes, update cycles, and failure modes.

The COO owns the operational relationship with these vendors — not the commercial relationship (that's the CEO or CFO), but the day-to-day performance management. Is the BSS vendor meeting its uptime SLA? Is the tax engine updated for the latest rate changes? Is the MNO's CDR feed arriving on time and in the correct format? Is the payment processor's decline rate within acceptable thresholds?

When a vendor fails — and vendors fail — the COO coordinates the response across affected functions. A BSS outage affects activations (CRO), rating (billing ops), and customer experience (care) simultaneously. Someone needs to manage the incident across all three functions while communicating with the vendor. That's the COO.

Operational KPIs

The COO tracks metrics that span functions — the ones that fall between individual functional dashboards:

Activation-to-first-bill cycle time. How long from subscriber activation to the first successful billing event? This metric spans sales (activation), BSS (provisioning), and billing (first charge). If it's too long, revenue recognition is delayed and the subscriber experience suffers.

Plan launch readiness time. How many days from plan design completion to commercial availability? This spans product (design), BSS (configuration), billing (validation), sales (channel readiness), and care (training). The COO who compresses this from 6 weeks to 2 weeks without sacrificing quality has delivered a competitive advantage.

CDR reconciliation accuracy. What percentage of CDRs match wholesale invoice line items on first pass? This spans billing operations and the MNO/MVNA relationship. Persistent low accuracy signals either a BSS configuration issue or a wholesale billing discrepancy that needs escalation.

Cross-functional escalation frequency. How often do issues require escalation above the functional leader to get resolved? High escalation frequency means the operating system isn't working — functions can't resolve dependencies between themselves. The COO's job is to build the system that reduces escalation to the exception, not the norm.

The Great COO

The great MVNO COO has a specific operating style. It's not charismatic leadership. It's not strategic vision. It's relentless, detail-oriented execution with the authority and discipline to hold every function accountable.

They run the operating review that everybody dreads and everybody needs. The meeting starts on time. It runs on numbers, not narratives. When someone says "we're making progress on dealer recruitment," the COO asks: how many recruited, how many onboarded, how many activated, how many producing, what's the 90-day survival rate? When someone says "the plan launch is on track," the COO asks: has billing ops validated the BSS configuration? Has care been trained? Has the tax engine been updated? "On track" without specifics is not an answer.

They maintain an operational dashboard that tells the CEO the health of the business in one page. Subscriber growth trend. Margin by plan tier. Billing reconciliation status. Customer care volume and resolution rate. Compliance calendar status. Platform uptime. Cash runway. The CEO should be able to look at one document, produced by the COO, and know whether the operational machine is running or breaking.

They catch handoff failures before they become crises. The plan that launched without billing ops being briefed — the COO's checklist would have caught it. The dealer that activated 200 subscribers in a state where the MVNO hasn't filed its PUC registration — the COO's compliance integration would have flagged it. The BSS update that broke the rating engine on three plan tiers — the COO's change management process would have required pre-deployment testing.

The great COO doesn't do these things personally. They build the system that does them — the checklists, the launch sequences, the change management processes, the cross-functional review cadences. And then they enforce the system relentlessly, because a system that isn't enforced is just documentation.

They say "that's not ready" when everybody else wants to say "ship it." The CRO wants to launch the new dealer program next week because the master agent is pressuring them. The CPO wants to push the new plan live because the competitive window is closing. The CEO wants both because the board meeting is in 10 days and they need a growth story. The COO looks at the launch checklist and says: billing ops hasn't validated the BSS configuration, care hasn't been trained, and the tax engine hasn't been updated for the three new states the dealer program covers. We launch when it's ready, not when it's convenient.

That takes backbone. It makes the COO unpopular in the moment. It saves the MVNO from the customer-facing disasters that happen when you launch things that aren't operationally ready.

The Bad COO

I see two failure modes, and they're opposite ends of the spectrum.

The Meeting Facilitator

This is the COO who confuses coordination with operation. They schedule cross-functional syncs. They take notes. They distribute action items. They follow up with polite emails asking for status updates. They maintain a beautifully organized project tracker with color-coded status indicators.

And nothing actually changes.

The functions remain siloed. Handoffs continue to fail. The weekly operating review becomes an information-sharing session where everyone presents what they did last week and nobody is held accountable for what they committed to. When a cross-functional issue surfaces, the meeting facilitator COO schedules another meeting to discuss it.

The meeting facilitator isn't operating. They're administrating. They're a human project management tool with a C-suite title. The organization would get the same output from a good project manager at a third of the cost — and at least the project manager wouldn't create the illusion that someone is running the operation.

The tell: ask the meeting facilitator COO what the MVNO's plan launch readiness time is. What the CDR reconciliation accuracy rate is. What the activation-to-first-bill cycle time is. If they can't answer without checking with someone, they're not tracking operational performance — they're tracking meeting schedules.

The Bottleneck

The opposite failure mode: the COO who inserts themselves into every decision, every approval, every workflow. Nothing moves without the COO's sign-off. Every cross-functional interaction routes through them. They become the single point of dependency for the entire organization.

This COO is often genuinely competent — they insert themselves because they don't trust the functional leaders to coordinate on their own, and they're frequently right that the coordination would fail without them. But the result is an organization that moves at the speed of one person's bandwidth. The COO is in back-to-back meetings 12 hours a day, every decision takes twice as long because it's queued behind their calendar, and the functional leaders atrophy because they've never had to coordinate directly.

The bottleneck COO builds a fragile organization — one that works when they're present and collapses when they're not. A vacation, a sick day, or a resignation creates an immediate operational crisis because no one else knows how anything connects.

The tell: what happens when the COO is out of the office for a week? If the answer is "things stop moving," the COO has built a dependency, not a system.

The COO's Relationship with the C-Suite

The COO doesn't overrule the CRO, CFO, or CPO. They don't own those functions. What they do is enforce the operating system that makes all three functions accountable — to each other and to the business.

With the CRO: The COO holds the CRO accountable to pipeline numbers and dealer compliance. Not to the revenue target — that's between the CRO and the CEO. But to the operational commitments that support the revenue target: are dealers being onboarded on schedule? Are underperforming dealers being addressed? Is the dealer channel compliant with tax collection and CPNI requirements? Is the digital activation flow functioning correctly? The COO ensures the CRO's operation is actually operating, not just reporting.

With the CFO: The COO ensures operational spending aligns with the financial forecast. When billing operations needs a new reconciliation analyst, the COO validates the need, confirms budget availability with the CFO, and manages the hiring timeline. When a vendor contract is up for renewal, the COO provides the operational performance data that the CFO needs to negotiate terms. The COO and CFO are natural allies — both are systems thinkers who value discipline over enthusiasm.

With the CPO: The COO enforces the plan launch framework. Every new plan goes through the launch sequence: wholesale mapping, BSS configuration, billing ops validation, tax engine update, care training, channel readiness. The COO doesn't evaluate whether the plan is a good idea (that's CPO + CFO) — they ensure that if it launches, it launches correctly. The COO is the CPO's operational conscience.

With the CEO: The COO frees the CEO from operational firefighting. The CEO should be spending their time on strategy, fundraising, board management, and market positioning — not diagnosing why a BSS update broke the rating engine or why a dealer in Texas isn't collecting taxes. When the CEO finds themselves pulled into operational details, it means either the COO isn't doing their job or the MVNO doesn't have one.

The Consequences of Getting It Wrong

An MVNO without a functioning COO looks like this:

The CEO is the de facto COO, spending 60-70% of their time on operational coordination and firefighting instead of strategy and growth. They're in every cross-functional meeting because nobody else can make decisions that span functions. They're the escalation point for every vendor issue, every handoff failure, and every launch that didn't go as planned.

Functional silos calcify. The CRO blames product for uncompetitive plans. The CPO blames sales for not selling what they built. The CFO blames both for margin erosion nobody told them about. Billing operations blames product for plans that weren't properly configured. Customer care blames everyone for the subscriber complaints they're fielding about issues nobody warned them were coming.

Plan launches happen without operational readiness. A new plan goes live on Monday. By Wednesday, customer care is getting calls about incorrect charges because the BSS configuration didn't match the plan description. By Friday, billing operations discovers that the wholesale mapping was wrong and the MVNO has been paying the MNO at a higher rate than intended. By the following Monday, compliance discovers the plan was launched in three states where the PUC registration hasn't been completed.

This isn't hypothetical. This is what I've seen at MVNOs that have strong individual function leaders but no one connecting them.

The cost is not a single catastrophic failure. It's death by a thousand cuts — a steady accumulation of operational gaps, handoff failures, and cross-functional miscommunication that individually seem minor but collectively erode margin, subscriber experience, and organizational trust. By the time the board recognizes the problem, the operational dysfunction is embedded in the culture and takes 6-12 months to unwind.

What to Look For

The COO who works in an MVNO has a specific profile — and it's different from the CRO, CFO, or CPO profiles:

They're systems thinkers, not functional specialists. The COO doesn't need to be the best salesperson, the best financial analyst, or the best product designer. They need to understand how all three functions connect and where the dependencies are. A COO who came up through one function and can't think across functions will default to over-managing their area of expertise and under-managing everything else.

They're detail-oriented without being micromanagers. They know the difference between tracking operational KPIs (their job) and doing the functional work (not their job). They ask "what's the CDR reconciliation accuracy rate this week?" — they don't sit down and reconcile CDRs themselves.

They've managed vendor relationships at the operational level. Not negotiated contracts — managed performance. Held vendors accountable to SLAs. Coordinated incident response across affected functions. Managed platform migrations and updates without operational disruption. This is a core COO skill in the MVNO world where the entire technology stack is third-party.

They run meetings that produce outcomes, not updates. Ask them to describe their weekly operating review. If they describe a meeting where functional leaders share updates, that's a meeting facilitator. If they describe a meeting where functional leaders report against commitments, surface blockers, resolve cross-functional dependencies, and leave with specific action items and deadlines — that's an operator.

They've said "that's not ready" and made it stick. Ask for a specific example. A time they delayed a launch, halted a rollout, or pulled back a release because the operational readiness wasn't there — against pressure from sales, product, or the CEO. If they can't give you one, they've either never been tested or they fold under pressure. Either way, that's not the COO you need.

They build systems, not dependencies. Ask them what happens when they're out for a week. If the answer is "the team knows the processes and the operating rhythm continues," they've built a system. If the answer involves anything resembling "things slow down but they call me if it's urgent," they're a bottleneck.

Recommendations

Hire the COO when the CEO is spending more than 50% of their time on operational coordination. That's the signal. The CEO who is in every cross-functional meeting, fielding every vendor escalation, and managing every plan launch sequence has become the COO by default — and they're not being the CEO. That's the hiring trigger.

Define the role around operational integration, not functional management. The COO doesn't manage the CRO, CFO, or CPO — the CEO does. The COO manages the system that connects them. If the COO becomes a layer between the CEO and the functional leaders, you've added bureaucracy, not capability.

Require a weekly operating review from day one. This is the COO's primary governance mechanism. Every function reports. Every commitment is tracked. Every cross-functional dependency is surfaced. If the COO can't get this meeting running within 30 days of their start, the operating rhythm won't come later.

Track cross-functional KPIs, not just functional ones. Plan launch readiness time. Activation-to-first-bill cycle time. CDR reconciliation accuracy. Escalation frequency. These are the metrics that tell you whether the operational machine is working. Functional KPIs tell you whether individual engines are running. Cross-functional KPIs tell you whether the engines are connected.

Evaluate the COO by operational stability, not by activity. The great COO makes the organization boring — things launch on time, handoffs work, vendors perform, crises are rare. The bad COO makes the organization exciting — constant firefighting, dramatic saves, heroic efforts to fix things that should have worked the first time. If the operation feels calm and predictable, the COO is doing their job. If it feels chaotic and reactive, they're not.

Make the decision at six months. Same as the CRO and CFO. If the COO hasn't established a weekly operating cadence, built launch and change management checklists, reduced cross-functional escalation frequency, and freed the CEO from operational firefighting within six months — the role isn't working. A great COO makes their impact visible within 90 days. Six months is generous.