Your CPO and CRO fight because the org rewards them for competing goals. Here's the org design fix: shared metrics, aligned comp, and joint governance.
It looks like a personality conflict. It isn't. The CPO CRO conflict you keep refereeing is a structural failure hiding in plain sight.
I've watched this fight play out at a dozen companies. Different industries, different growth stages, different people in the seats. Same arguments every time.
Product says Sales is hijacking the roadmap with one-off features. Sales says Product doesn't understand what customers actually need. Customer Success sits in the middle watching churn climb.
At some point it becomes obvious: you're not dealing with difficult leaders. You're dealing with impossible incentives. And I've lived this long enough to know how it ends. Growth stalls.
Here's how most B2B SaaS companies set up their teams and metrics.
Product gets measured on roadmap delivery, adoption, and platform uptime. Success means shipping features on time and keeping the system up 24x7.
Sales gets measured on new logos. Winning means hitting quota and closing deals.
Customer Success gets measured on NPS and renewals. Success means keeping existing customers happy.
Sounds logical. Until you notice what's missing: no one cleanly owns expansion revenue and growth.
And expansion is where SaaS companies actually make money. Net-new logos are expensive. The margin, the durability, the compounding all live in the existing base. Yet the metric that matters most has no owner.
So what happens when nobody owns it? Three fights, on repeat.
Sales closes a strategic deal worth $500K. It arrives with "just a few" custom requirements.
Product pushes back because the features don't align with the roadmap. Sales escalates because the deal is at risk. The CEO sides with revenue, every time. Product loses another quarter of engineering capacity to a one-off feature that no other customer will ever use.
This is the roadmap hostage negotiation, and I've lived it more times than I care to remember. Each individual decision looks rational. The cumulative effect is a roadmap owned by whoever's holding the biggest deal.
A customer churns after 18 months. Sales says Product never delivered what was promised. Product says Sales oversold capabilities that were never on the roadmap. Customer Success says they flagged the risk six months ago and nobody listened.
Everyone's right. Nobody's accountable. The account is gone, and the postmortem produces finger-pointing instead of a fix.
An existing customer wants to expand. Sales says it's Product's job to drive the adoption that creates expansion opportunities. Product says it's Sales' job to close expansion deals.
The opportunity sits in committee until a competitor shows up and takes it. This is the Expansion Orphan problem in its purest form: the highest-margin revenue in the business, owned by no one, dying in the gap between two functions.
Sound familiar?
I used to believe the root cause was personality. It isn't. It's that we've built an org model where the success metrics compete with each other.
Product wants to say "no" to one-off features so they can build for the market. Sales wants to say "yes" to anything that closes this quarter. Customer Success wants to keep customers happy even if that means pushing features that don't scale.
All three leaders are doing exactly what they're paid to do. And all three are making each other's jobs harder.
You can't ask for collaboration while paying for competition.
So the CEO ends up as referee roughly 30% of the week, adjudicating roadmap disputes that shouldn't reach their desk. Growth plateaus, not because the leaders are weak, but because the structure won't let the company scale. It's a textbook symptom of the Linear Growth Trap: the business gets more fragile and more expensive to run as it gets bigger, because coordination drag hardens into a permanent tax.
The first time I proposed this kind of structural change, it did not go well.
The CRO didn't believe me. He heard me out, nodded politely, then said: "Brian, I appreciate the thought, but there's no way I'm tying my comp to product adoption metrics I don't control."
My own team thought I was crazy. Some were genuinely unhappy, because I was putting their compensation at risk. Tying bonuses to outcomes they didn't directly control felt unfair.
And they weren't wrong to push back. It was risky. It was uncomfortable.
But here's what I learned: if the people leading Product, Sales, and Customer Success aren't at least a little uncomfortable with a new incentive structure, you probably haven't changed the game enough for it to matter.
Once everyone got on board, that same CRO came around after seeing the early results. We went from weekly battles to a unified growth team in 90 days. Not because people suddenly became better collaborators or best friends, but because we stopped paying them to compete with each other.
After living through this enough times, here's what worked. Three moves, in order.
Stop measuring teams on independent outputs. Create at least one shared outcome metric that no single team can win alone.
The one I've seen work best is Net Revenue Retention.
NRR requires Product to build things customers actually expand on. It requires Sales to close customers who stay and grow, not just customers who sign. It requires Customer Success to keep accounts healthy enough to buy more.
We put NRR on all three leaders' scorecards, not as a nice-to-have but as a headline number driving 20% of everyone's variable comp. Roadmap conversations changed overnight.
Metrics without money behind them are just dashboards people ignore. Shared metrics comp alignment is the part most companies skip, and it's the part that does the work.
We put 15-20% of the CRO's variable comp on product adoption. We put 15-20% of the CPO's variable comp on revenue outcomes. We tied part of the CCO's comp to expansion signings, not just renewals.
Here's what happens next. The CPO starts asking Sales sharper questions about what's blocking deals. The CRO starts caring whether customers actually used what they bought. The CCO starts thinking about growth, not just NPS.
They always had the ability to influence those outcomes. They just weren't used to being accountable for them. Once you clarify what "influence" looks like versus "complete control," the resistance drops.
We replaced the "Product decides, Sales complains" dynamic with a structure where all three leaders owned prioritization together.
Restructure your Product Council:
The key shift: no new feature gets approved without a defined ROI tied to NRR, profitability, or churn prevention.
Instead of Sales "requesting" and Product "rejecting," all three teams argued about data and business impact. Not turf. Not politics. That's real Product Led Revenue governance: the roadmap becomes a shared instrument for growth instead of a hostage in a quarterly negotiation.
Your CPO and CRO fighting is not a people problem. It's an org design problem.
You built a structure that rewards leaders for different things. Expansion revenue got left in no-man's land. The CEO became the daily tiebreaker on roadmap disputes. What got designed can be redesigned, but it takes changing incentives and decision rights, not speeches and off-sites about teamwork.
Companies that fix this break through revenue plateaus faster, because Product and GTM finally row in the same direction. They waste less engineering capacity on political roadmap fights and one-off features that don't scale. They retain and expand at rates competitors can't match, because the entire org is aligned on making customers successful enough to grow.
The question isn't whether your CPO and CRO can learn to get along. It's whether you're ready to change the game they're playing.
Not sure where your alignment is breaking? Take the free Quick Test to see where your operating model is leaking leverage.
Because the org rewards them for competing outcomes. Product is measured on roadmap and adoption; Sales is measured on new bookings. When those metrics pull in opposite directions, the leaders fight, even when both are doing their jobs well. It's a structural design flaw, not a personality clash.
Net Revenue Retention. NRR can't be won by any one team alone: Product has to build expandable value, Sales has to close customers who stay, and Customer Success has to keep them healthy enough to grow. Putting NRR on all three scorecards forces genuine collaboration.
Put 15-20% of each leader's variable comp on outcomes outside their direct function: the CRO on product adoption, the CPO on revenue, the CCO on expansion signings. Metrics without money behind them get ignored. Shared comp turns influence into accountability.
It's when a large deal comes with custom requirements, Sales escalates, the CEO sides with revenue, and Product loses a quarter to one-off work that doesn't scale. Repeated across deals, it hands roadmap control to whoever holds the biggest contract. Joint governance with ROI-gated decisions is the fix.
The Quick Test reads your revenue motion against the five patterns in a few minutes. No financials required.