When Your Portco Needs a CGO, Not a CRO

Every board deck with flat growth says the same thing: "we need a CRO." Half the time, it's the wrong hire.

I say this as someone who has carried the CRO title. The CRO is one of the most misdiagnosed seats in PE-backed healthcare. Boards reach for it whenever revenue disappoints, regardless of what's actually broken.

CRO vs. CGO: different jobs

A Chief Revenue Officer runs the revenue engine: pipeline discipline, forecast accuracy, sales leadership, pricing execution. You hire a CRO when the growth plan is right and the machine needs an operator.

A Chief Growth Officer designs the growth system: which markets to play in, which channels to build, how partnerships and enterprise deals fit together, how pricing architecture supports expansion, how an acquired company integrates into the commercial model. You hire a CGO when the plan itself is the problem.

One optimizes. The other architects. Hiring an optimizer when you need an architect is how you end up churning through two CROs in three years.

Five signs you need a CGO, not a CRO

1. The core sales motion works, but growth is flat. Win rates are fine. The team is solid. The number just won't move: you've saturated the segment the motion was built for. That's market selection, not sales execution.

2. Expansion and partnerships could dwarf new-logo, and nobody owns them. There's a payer partnership that could 3x the business sitting in the CEO's inbox. Enterprise deals take 18 months and die in procurement. These are system-design challenges. A CRO hired to run the existing engine will never get to them.

3. You're post-acquisition with two companies and one spreadsheet. The deal thesis said "cross-sell." Eighteen months later there are still two CRMs, two pricing books, and two sales teams with different comp plans. Integration is a growth-architecture job.

4. The market is shifting under you. Value-based care, consumerism, payer consolidation. When the ground moves, selling harder into the old model just accelerates the wrong thing. Someone has to redesign where growth comes from.

5. You've already churned through CROs. If the seat keeps failing, stop blaming the seat. Every CRO inherited a growth model that doesn't work and was asked to execute it harder.

The sequencing most boards get backwards

The instinct is to hire the CRO first because the title feels like action. The better sequence: a CGO (or fractional CGO) to d