A second opinion · No client, no brief · Note 01
A customer ports their number out. Their insurance stops. Their storage disappears. Their points vanish.
The operator calls this retention. Ending the add-on when the contract ends is meant to make leaving painful, so fewer people leave.
There are two problems with that.
The first is timing. The penalty only takes effect once the customer has already gone. For it to change anyone's mind it has to be known in advance, and mostly it isn't.
The largest test of a pure forfeiture rule ever run is not in telecoms. It is in American company pensions, where leaving a job too early costs you your employer's contributions — real money, on average 40% of the balance. Vanguard studied 4.7 million people leaving jobs across roughly 1,500 plans between 2010 and 2022. The effect on whether people quit was zero. Separation rates did not move around vesting dates.
The reason is in the same study. Only 33% of participants could correctly identify their own vesting schedule.
You cannot scare someone with a punishment they have never heard of.
That transfers directly. A customer who has never read the clause voiding their insurance at port-out is not held by it. They find out afterwards — at which point it is not a retention device, it is a grievance.
And there is no evidence for it either. No operator, in any industry, has ever published a measured retention result for a forfeiture rule. It is defended in public with assertion — loss aversion, breakage, "a natural reason to contact members" — and with accounting and legal rationale. Not with measurement.
That is a claim about the public record, not about what sits in anyone's internal decks. Operators may well have measured this. None of them has shown the working.
The second problem is that we have been running two decisions on one axis, and the word hiding them is bundle.
We talk as if products must either live together or live apart. But selling them together and killing them together are completely different decisions, and only one of them earns anything.
Sell it together. Don't kill it together.
| Sold and priced together | Sold and priced apart | |
|---|---|---|
| Terminates together | Most operator practice today | Rare, incoherent |
| Survives independently | The evidence-supported design | Classic separate product |
Selling the add-on together with the main product creates value. The UK's FCA measured this twice. In a 2013 controlled experiment, 65% of people who were offered an add-on during the main purchase accepted the first offer. Only 17% did so when they had to shop for it separately. Selling at the same time also increased the price paid by 15%.
In 2018, the FCA studied what happened after it required a pause between buying a car and buying GAP insurance. Add-on sales fell by 19.8%. Separate sales increased only from about 6% of the market to 9%. Most of the lost add-on sales did not move to another seller; they disappeared.
My conclusion is simple: selling together works. Ending together is another decision. I could not find a published measurement showing that this second decision creates value.
Here is where most articles on this subject quietly cheat, and where I nearly did.
The case against fusion has two halves. One half has telecom evidence behind it. The other half has none at all.
The figures usually quoted here — 42% of cancelling customers returning within twelve months, a second subscription lasting 98.7% as long as the first — are from streaming and newspapers. They are real measurements. They are not measurements of mobile.
And mobile is exactly the category where that distinction has already bitten. Ofcom found the bundling effect in fixed broadband and not in mobile, in the same dataset, the same year, from the same respondents. If the effect does not even survive the move from fixed to mobile, it is not safe to move a number from Netflix to a SIM.
The rule I am using
Mechanisms transfer. Magnitudes don't.
Vanguard is a pension study, and I have used it — but only for a mechanism: a rule you have never read cannot deter you. That reasoning holds wherever people are unaware of a penalty, and the 33% is evidence for the mechanism, not a number I have put into a model.
Netflix's 42% is a magnitude. Magnitudes belong to the category that produced them. Streaming has no number portability, no SIM, no contract, and a content calendar that pulls people back on its own schedule. None of that is true of a mobile plan.
Nor is the direction obvious. Porting out might make returning harder — more friction, a new contract, a device commitment. Or easier, because you keep your number and never have to re-register it with your bank, your contacts and every service that texts you a code. Nobody has measured which, in either direction.
So this note is not going to tell you the answer. It is going to tell you the threshold you would have to clear, and how to find out whether you clear it.
Start from the thing you are defending. Fusion is not free to keep — it costs you whatever a preserved relationship would have earned. So the question is not "does fusion work?" but "how much would it have to be worth?"
That number is smaller than it feels, and it comes apart in five steps. The calculator below runs them on your own numbers.
Your business
Observed range 0.8–3.5 pp, telecom. The 1.6 default is Grzybowski's mobile figure — the most generous well-identified estimate that exists. Ofcom found no significant mobile effect at all, so zero is a defensible setting.
No published figure. How fast ex-customers drop the add-on once the mobile line is gone. Above 100% means an average life under a year.
What you would have to find
So unfusing pays if more than
9.6%of your leavers keep paying for the add-on. That is the whole test. Nothing else has to be true.
How long before you would know
Your base produces 417 leavers a month.
You need about 371 to measure the keep-rate to ±3 points.
About 1 month.
Only two numbers here come from outside your own business: the fusion benefit, measured in mobile telecom, and the churn of the surviving pool, which nobody has measured. No streaming figures are used anywhere in this calculation.
The keep-rate is unusually cheap to measure, for a reason that is easy to miss: under fusion it is zero by construction. The add-on is terminated, so nobody can keep it. There is no counterfactual to build and no control group to run. You unfuse, and you count.
That is why it reads in weeks rather than a year. Measuring a difference between two arms needs roughly four times the sample of measuring one number, and the return rate is defined over twelve months, so most of it has not happened yet when you want to decide.
One note on how confident you need to be
Those sample sizes assume a textbook 95% confidence and 80% power. This decision does not deserve that bar.
Not deleting an account costs nothing, changes nothing operationally, and can be reversed next week. The asymmetry is severe: being wrong towards preservation means you keep some dormant accounts alive. Being wrong towards fusion means you have been destroying the return option permanently, at scale, for years.
You do not need publication-grade confidence to stop deleting accounts.
I found one strong argument for fusion, but it is not a retention argument.
If customers can keep an insurance product after leaving, the people who choose to keep it may be more likely to make a claim. Several studies show this effect. In the United States, claims under health insurance continued after employment were 46% higher than claims for current employees. In group life insurance, mortality was 18% higher among people who chose additional cover. This made actual costs 9.7% higher than they would have been with a random group. The FCA also found a 52% claims ratio for travel insurance sold as an add-on, compared with 42% for separately purchased insurance.
For insurance products, simply allowing the policy to continue at the same price may therefore be a poor design.
However, automatic termination is not the only solution. It removes the higher insurance risk, but it also removes all future revenue from the customer. The more direct solution is to set a new price and assess the risk again for customers who want to continue.
This problem does not apply in the same way to products without insurance claims and with low additional cost: cloud storage, content, software, data allowances or loyalty balances. For these products, a customer who continues after leaving mobile is mainly an additional source of revenue.
The interesting part is not the answer. It is how we got there.
Three numbers would settle this, and none of them is public.
One number, two billing cycles, no control group. It would be the first published anywhere, and it would make this whole note redundant — which is the point.
What share of customers who port out later come back. No operator discloses it, no regulator tracks it, and no analyst house publishes it. Until someone does, every quantified claim about the value of preservation in mobile — including the ones I would like to make — is borrowed from another industry.
The only place the adverse-selection objection can be settled rather than bounded.
If you have run any of this, I would rather see your number than keep reasoning around the absence of one.
Grzybowski, Liang & Zulehner, Bundling and Consumer Churn, Review of Network Economics 20(1), 2021 · Prince & Greenstein, Does Service Bundling Reduce Churn?, JEMS 23(4), 2014 · Ofcom, Pricing and Consumer Engagement, 2025 · Vanguard, Does 401(k) vesting help retain workers?, 2025 · FCA MS14/1, General Insurance Add-Ons Market Study and its experimental report, 2014 · FCA EP18/1, GAP insurance intervention evaluation, 2018 · Kumar, Bhagwat & Zhang, Regaining "Lost" Customers, Journal of Marketing 79(4), 2015 · CRS, Health Insurance Continuation Coverage Under COBRA · Harris, Yelowitz, Talbert & Davis, Adverse selection in the group life insurance market, Economic Inquiry 61(4), 2023 · Antenna, Premium SVOD 2025 Year in Review and Thomas, Blattberg & Fox, Recapturing Lost Customers, JMR 41(1), 2004 — both cited above only as out-of-category reference points, not as inputs.
Send me the context and what you're trying to understand.
No calendar. No discovery call.