What makes a pivot impossible

A pivot needs three things at once. Enough runway to survive the transition, a team willing to abandon work they are proud of, and few enough commitments that changing direction does not breach them. Losing any one of the three closes the door.

Runway is the usual constraint. Pivots take longer than founders expect, and a company with four months left cannot afford a six month change. This is why the pivot decision is really a runway decision made a year earlier.

The sunk cost problem

The hardest part is rarely technical. It is that a pivot requires discarding work that people spent years on. Teams protect what they built, and the more impressive the thing built, the harder it is to walk away from.

This is why pivots often happen too late. By the time the argument is settled the runway that would have funded the change has been spent continuing the thing everyone already agreed was not working.

When changing course is no longer available

If you cannot pivot, you can still transfer. Selling the assets to someone who can make the change is a version of the pivot happening without you, and it recovers value that a slow wind down destroys.

This is genuinely attractive to some buyers. A mature codebase, a real user base and clear evidence about what does not work is a strong starting position for an operator with the runway you lacked.

Common questions

How much runway do I need to pivot?

Plan for twelve months and expect the transition to take longer than the optimistic estimate. Below six months, selling usually recovers more value than attempting the change.

Can I sell mid pivot?

Yes, though be clear about what is finished and what is not. Buyers price a half migrated codebase carefully, so document the state honestly.

Do buyers care why we could not pivot?

They care about what constrained you, because contractual lock in transfers to them and a runway problem does not.

Related reading