Loading...
Test cannibalization before approving a new offer. Separate new demand from displaced sales and decide which customer migrations are worth the cost.
A new offer can hit its growth target while making the business worse. Customers move from an existing offer to the new one, the launch team records a win, and the original business absorbs the lost contribution. Before approving expansion, decide how much of that movement is acceptable and what the business gains in return.
That is the purpose of a cannibalization test. It makes an explicit strategic choice out of demand shifting between your own offers. The aim is not to eliminate overlap. It is to establish which customer migrations create value, which merely move revenue, and which undermine the reason for launching.
Imagine a hypothetical business considering a lower-priced, self-service version of an existing managed service. Marketing sees a more accessible offer. Sales sees an easier entry point. Finance sees a possible reduction in revenue from customers who already pay for the managed service. Each view matters, but none settles the decision alone.
The wrong comparison assumes that every existing customer stays and every existing sale continues without the launch. That protects an imaginary version of the business. Some customers might leave anyway. Some prospects might never buy the managed service. Others might purchase it later if the cheaper offer does not exist.
Build a credible no-launch alternative using available renewal behavior, lost-sale reasons, customer needs, and commercial constraints. Treat it as an estimate, not a fact. The decision is whether the new offer improves on that alternative over the same period, with uncertainty visible on both sides.
New-offer revenue is not the same as new demand for the business. Separate the paths customers could take before combining them into a launch forecast. The distinction should follow customer behavior across offers and channels, not whichever team receives credit for the transaction.
| Customer path | Strategic interpretation | What to investigate |
|---|---|---|
| Would not otherwise buy from the business | Potentially additional demand | Whether access, price, or service needs explain the new purchase |
| Would otherwise buy the existing offer | Demand displaced within the business | Contribution lost and costs genuinely avoided after switching |
| Would otherwise leave the business | Potentially retained demand | Whether the new offer addresses the actual reason for leaving |
| Would otherwise buy later | Demand brought forward | Whether later sales weaken after the initial launch period |
These are hypotheses about what customers would otherwise do, not labels that a transaction record can prove. Interviews can explain purchase reasoning. Controlled comparisons, where feasible, can help estimate behavioral effects. A customer's stated enthusiasm alone does not establish that the purchase is additional.
Ask finance to compare contribution under the launch and no-launch alternatives using consistent cost definitions and a common time horizon. Include the new offer's revenue, the contribution displaced from existing offers, costs actually avoided, and costs introduced by the change. Keep one-time transition costs visible alongside recurring economics.
A customer moving to self-service does not automatically remove the cost of the managed service. Specialist capacity may remain committed. Existing contracts may keep costs in place. A lower price may also attract buyers who need more assistance than the offer includes. Distinguish an assumed saving from a cost that can actually leave the business.
Revenue cannibalization can still be acceptable. A business might deliberately trade revenue for a more sustainable service model, retain customers it would otherwise lose, or create a credible route into a different market. State that rationale separately. Do not hide a weak near-term case inside an untested claim about future customer value.
The useful question is whether the recommendation holds under plausible levels of switching. If it works only when almost every buyer is new to the business, that dependence belongs in the approval discussion. It should not surface as an explanation after the launch disappoints.
Return to the hypothetical self-service launch. Leadership could approve broad access, restrict the initial offer to a distinct customer need, or defer it until the service economics change. These are different strategies, not merely different campaign settings. An agency partner needs to know which one it is being asked to execute.
Do not let separate teams approve only their own side of the exchange. Marketing can own acquisition quality, sales can own commercial fit, operations can own service feasibility, and finance can test the economics. Final approval must cover the combined business effect.
A forecast may assume existing customers cannot access the lower-priced offer. Check whether that restriction is enforceable, understandable, and commercially defensible. Customers may use another channel, renegotiate an existing agreement, or ask why equivalent needs receive different treatment. A restriction that exists only in the launch brief cannot protect the strategy.
Where practical, test limited access against a suitable comparison group before widening availability. Choose a comparison that can reveal movement across the old and new offers, rather than measuring only conversion into the new one. Account for channel spillover and differences between groups before attributing a change to the launch.
Run observation long enough to address the relevant purchase or renewal cycle. An early conversion lift cannot settle whether customers merely bought sooner. If a clean comparison is unavailable, use a bounded rollout with explicit uncertainty and limited exposure. Do not present a forecast or a before-and-after change as causal proof.
Strategic memory should preserve why migration was approved, not just whether the new offer met its target. Retain the no-launch alternative, expected customer movements, accepted losses, cost assumptions, and evidence needed for wider access. That context lets a later review distinguish an intended transition from an unexpected erosion of value.
Review results across the affected offers together. Otherwise, the new offer can appear successful while the existing offer is treated as a separate turnaround problem. If the business intentionally accepted a loss in one place, evaluate the exchange it approved. If the expected offset never arrives, revisit the decision rather than redefining success.
Autostrat is an AI-native strategy agency delivering finished strategy work. For agency teams and in-house leaders, decision-ready clarity means connecting audience choices, commercial economics, and execution constraints before approving growth. Bring the proposed offer and the existing business into the same brief. Decide what should be replaced before asking execution teams to scale it.
Book a 30-minute demo. Bring a live question and watch the answer get built.