The Cannibalization Decision Framework

The hardest call a CPO makes during the AI inflection isn't whether to ship an agent product. It's whether to keep selling the SaaS product that ships the agent product's payroll.

This chapter is the decision framework I use. Four diagnostic questions, three operating modes, and the political map that turns a strategic call into an executable plan.

The companion essay The Cannibalization Playbook carries the rhetoric. This chapter carries the operating practice.

The four diagnostic questions

Run these in order. Each one routes the decision.

Question 1: Can the legacy architecture support the successor's quality bar?

Look at the agent-native product you would ship in twelve months if your current architecture were the constraint. Can you build it on top of the legacy? Can the legacy data model, latency profile, and security posture support the successor's quality bar?

If yes, refresh becomes possible. If no, the architecture itself is forcing a sunset, regardless of the customer math.

The mistake here is wishful thinking. Engineers will tell you the architecture can be extended. They're sometimes right and often telling you what they hope. Test the answer concretely: have a senior engineer write a one-page sketch of how the successor would ship on the legacy architecture. If the sketch requires three foundational rewrites, the architecture cannot support it. Sunset.

Question 2: Is the legacy customer base the right ICP for the successor?

The successor product has a target buyer. Maybe it's the same buyer as the legacy. Maybe it's a different role, a different department, a different size of company.

If the legacy customer base is the right ICP for the successor, sunset is operationally clean (you migrate them). If the legacy customer base is the wrong ICP, sunset means losing those customers as you sunset. Then the question becomes whether you can replace them faster than you lose them.

Most companies discover the buyer for the agent product is different from the buyer for the SaaS product. The SaaS product sold to a function. The agent product sells to operations or to a different function entirely. This routes toward split rather than sunset.

Question 3: Can the company afford the gross margin trough?

Gross margin will compress from 78-82% (mature SaaS) to 58-65% (early Service-as-Software during ramp), bottoming around month 12 and recovering toward 70-75% by month 24-30.

Compute: how much cash will the company burn at the trough's bottom, given current revenue trajectory? Is that sustainable? Does the board have the patience? Does fundraising need to happen before the trough?

If the answer is no, the call cannot be sunset; you don't have the runway. The call is split (legacy revenue defends the cash position) or refresh (AI is additive, not replacement). Choose carefully and pre-sell to the board.

Question 4: Is the buyer the same person?

Same buyer means migration is feasible. Same buyer means a single relationship handles both products. Same buyer means CS and sales motion don't have to be cloned.

Different buyer means split. The two products will need different sales motions, different CS playbooks, different positioning. Trying to run both under one product team breaks one or both.

Routing to the three operating modes

Take the four answers and route.

Sunset when: architecture cannot extend (Q1 = no), customer base is right ICP (Q2 = yes), trough is affordable (Q3 = yes). The successor replaces the legacy on a published date.

Refresh when: architecture can extend (Q1 = yes), customer base is right ICP (Q2 = yes), buyer is the same (Q4 = yes), and AI is a feature improvement not a business model replacement. The legacy product evolves; positioning and pricing remain stable.

Split when: customer base is wrong ICP for successor (Q2 = no), or buyer is different (Q4 = no), or trough not affordable without the legacy revenue (Q3 = no). Two product lines under one company.

Most CPOs I work with want the answer to be refresh because it's the least disruptive. In 2026 the architecture and pricing realities of agent products are pushing more decisions toward sunset than most CPOs are comfortable with. The honest test is the four questions, not the comfort level.

The political map

Once the operating mode is set, the work is moving the coalition. Five seats.

CEO

Will support if the option-value math is clear and if the board is pre-sold. Will fight if the transition feels like CPO empire-building.

The argument that wins: walk in with the seven-decision sequence already structured. Make the option-value argument (the legacy has a known cash flow and a declining option value; the successor has higher uncertainty and much higher option value). Ask "do you want me to lead this or escalate to the board?" CEOs who hesitate are not going to back you in the trough.

CFO

Will support if the trough is bounded and modeled. Will fight if revenue becomes variable and the forecast goes from "predictable" to "depends on customer volume."

The argument that wins: model both scenarios in unit economics terms. Propose hybrid pricing for the successor (committed minimum + per-outcome overage) so there's still a forecast floor. Co-author the board narrative. The CFO has to be your closest partner.

CRO

Will fight hardest. Comp plans and renewal economics are the levers.

The argument that wins: outcome pricing is typically 1.5x-3x the SaaS price for the same customer. The CRO's quota math actually gets better, not worse. Rewrite comp in their favor for successor deals (legacy at 50% historical comp, successor at 150%). Make them the hero of the new motion. Hold the line on the 50% legacy comp; this is the lever.

CCO

Will fight if CS metrics are tied to seat-based usage. Will support if the CCO can see CS redesigned around outcome quality.

The argument that wins: CS becomes the team that owns outcome SLAs, dispute resolution, and customer migration. CS gets strategic again. Senior CS leaders get a real budget and a real mandate.

CPO (you)

Will fight yourself, because cannibalizing the product line you spent years building feels like an admission of failure.

The argument that wins yourself: the legacy was the right answer for its time. The successor is the right answer for the next time. Both can be true. Loyalty to a product is not a virtue when the world has changed.

The coalition takes 90 days to assemble. Most of the work is one-on-one conversations, not meetings. By the time the seven decisions hit a leadership meeting, the calls have been made.

The seven-decision sequence

Once the coalition is formed, the decisions come in this order. Out-of-order is the most common reason transitions fail.

1. Sunset date. Set 18-24 months out. Internal first, external later. The forcing function for everything downstream.

2. Reorg. Maintenance team owns the legacy with a clear runway. Successor team owns the agent product. Bridge engineers (5-10% of engineering) own integration points: data, auth, identity, infrastructure. Hard fences, no rotation.

3. Comp rewrite. Legacy at 50% historical comp. Successor at 150%. Renewal accelerators on legacy disappear. Migration accelerators on successor introduced.

4. Board pre-sell. 30-minute slot in the next quarterly review. Pre-read includes trough math. Establish the leading indicators that will be reported every quarter.

5. Customer migration in cohort waves. Wave 1 (months 6-9): top 20 strategic accounts, individual CPO+CRO calls. Wave 2 (months 9-12): mid-market, structured email + webinar + self-service. Wave 3 (months 12-18): long tail, public announcement, deadline-driven.

6. One number tracked. Percent of legacy revenue migrated. CEO sees it weekly. Board sees it quarterly. Every leadership conversation references it.

7. Post-sunset reorg planned. Six months before sunset, communicate transparently to the maintenance team: here are the roles that exist after sunset, here's how to interview, here's the timeline, here's the severance for those who don't transition.

What I have learned by getting this wrong

Three failures from earlier transitions, kept here so you can avoid them.

One: I waited too long to publish the sunset date internally. I thought I was protecting the legacy team by keeping the sunset informal. I was actually preserving their ambiguity, which kept them holding on, which kept the transition slow. Publishing the date is a kindness, not a threat.

Two: I let the comp plan get watered down. The first version was strong. The CRO pushed back. We compromised. The compromise meant salespeople kept selling the legacy because it still paid better in some scenarios. Three quarters of slow successor growth could be traced to that one comp decision.

Three: I tried to make the post-sunset reorg humane by being vague about it until late. Vagueness is not kindness. People want to know what their lives look like after the transition. Plan the reorg early, communicate it transparently, give people time.

What to do this week

If you suspect your product line needs the cannibalization decision, run the four diagnostic questions on a single page before Friday. Show the page to your CFO. Just the CFO. Ask them what would have to be true for the gross margin trough to be acceptable to the board.

Their answer is your next month of work.

The companies that win the AI inflection are the ones running the seven-decision sequence. The companies that lose are the ones still running the soft pivot.

---

The companion blog essay is The Cannibalization Playbook. The Cannibalization Decision Tree worksheet is at /toolkit/cannibalization-decision-tree. The CPO Coalition Map template is at /toolkit/cpo-coalition-map.