n o ren
Building & Strategy

Does Abandoning a Core Line Reinforce Your Position?

Adobe stopped selling the software that made it famous and told customers the only path forward was renting it.

Adobe announced in May 2013 that Creative Suite 6 would be its last boxed release. Everything after that would be Creative Cloud, a subscription, with no perpetual license available at any price. Customers who had bought Photoshop once and used it for a decade were told that arrangement no longer existed. The backlash was immediate and loud, and Adobe did not reverse the decision.

The reported financials got worse before they got better, and that was arithmetic rather than failure. A perpetual license books one large payment on the day of sale; a subscription books a small one every month. Trading the first for the second guarantees a revenue trough during the transition even if every customer eventually converts. Adobe's annual revenue fell the year after the announcement and did not clear its old peak for two more years, and the company absorbed that on purpose.

The strategic move was not the pricing change. It was removing the fallback. As long as a perpetual version existed, the sales team, the roadmap, and the customer base would all keep one foot in the old model, and the cloud products would be judged as an expensive alternative to something that still worked fine. Killing the alternative made the new product the only thing left to improve. Abandoning a core line strengthens your position when that line was the reason the organization could avoid committing, and destroys it when the line was where the customer value actually lived.

A fallback option is not neutral; it absorbs the demand that would otherwise force the new product to get good.
Model transitions carry a mandatory revenue trough — decide how long you will tolerate it before the first bad quarter arrives, not during it.
Cut a core line when it lets the organization dodge commitment, not merely because its margins are thin.

Keeping a legacy option alive as a safety net guarantees the new model gets judged against it, and the new model will lose that comparison for years.

Transitions that trade upfront revenue for recurring revenue look like decline in the reported numbers, which is exactly when boards and founders tend to reverse them.

1
List every product or plan you still sell mainly so existing customers are not forced to move, then count how many of your last ten renewals landed on one of them.
2
Ask your sales team to name the deals they closed this quarter on the legacy option, count them, and multiply by the price gap to get the revenue you are spending to avoid committing.

The mechanic here is the difference between a strategy and a preference. Adding a new model while keeping the old one is a preference, and preferences get revisited every quarter by whoever missed their number. Removing the old option converts it into a constraint, and constraints are what actually redirect engineering and sales effort. Adobe's move is usually studied as a pricing shift, but the durable lesson is that it foreclosed its own retreat.

The approach is not universal, and the exception has a clear shape. When the line you are cutting is where your customers' switching costs live — their files, their integrations, their muscle memory — removing it hands them a decision they were not otherwise going to make. Adobe survived this partly because none of that moved: same file formats, same applications, same workflows, only the payment method changed. A company whose legacy line carries the lock-in itself is cutting the rope it is hanging from.