Design a product cannibalization guardrail

Cannibalization Is Inevitable — Cannibalization Without a Model Is Unforgivable

Every new product or tier cannibalizes something — the question is whether the new revenue and retention flows exceed the lost premium revenue. Reforge's pricing and activation research documents the pattern: teams launch new products without modeling downgrade flows, then panic when premium ARR dips, even when net impact is strongly positive. Amplitude's North Star framework recommends defining net revenue impact (new + retained − downgraded) as the north star for any tier change, not gross new revenue alone.

How the Design a product cannibalization guardrail Prompt Works

The prompt forces a four-flow model (new, down, up, retain) with explicit monthly volumes and revenue impact per flow, then sets a net-positive threshold and sensitivity tables so the launch decision survives a 2x downgrade scenario. The retained-ARR flow (premium customers who would have churned but stay on new) is the usually-missing piece — cannibalization models that ignore it underestimate net benefit.

When to Use It

• You are launching a lower-priced tier.
• You are releasing a free or self-serve plan below an existing tier.
• A new product will serve a subset of premium-customer needs.
• Revenue leadership is blocking a launch over cannibalization fear.
• A board is asking for the economics of a planned portfolio expansion.

Common Pitfalls

• Modeling only downgrade flow. If you count losses but not net-new or retained customers, every launch looks negative on paper.
• No sensitivity on downgrade rate. Launch decisions that break if downgrade is 2x expected are one data release from disaster.
• No kill criteria. Without a pre-committed stop rule, cannibalization debates will drag on for quarters.

Sources

• The Activation Metric — Reforge
• The North Star Framework — Amplitude
• Retention, Engagement & Growth: The Silent Killer — Reforge
• The Product Strategy Stack — Reforge