For years, the moves that built your company were the right moves. Scaling rewarded code, operations, and the slow accumulation of contracts: with users about how the product behaves, with buyers about how the business runs, with the team about what counts as winning. Your company learned to see the signals that drove scale - and over time, stopped registering much else, because those were the only signals worth seeing. Tacit knowledge stayed in people’s heads because nobody needed it written down. Discovery skills atrophied because they weren’t relevant to the work. None of this was a mistake. It’s what scaling looks like.

So when a successful software company tried to find new PMF, the effort always got valued from inside the scaling lens - wrong patience, wrong metrics, wrong people - and always lost. Christensen named this the innovator’s dilemma, and the pattern has been so consistent it’s been treated as a near-law of incumbency: success makes the next thing structurally unfindable. The conditions that made it a near-law are dissolving.

Two GenAI effects change the equation. The competitive threat arrives faster and lands harder - that’s the side of the story everyone’s telling. But the same forces flip the position of the company that scaled:

  • The cost to test a new direction collapses to startup-speed through agentic coding.
  • The cost to adapt existing systems once a direction is proven appears set to collapse too. Phoenix Architecture and approaches like it are on the horizon: regenerate legacy from spec rather than maintain it, and the cost of structural change inside a scaled company moves toward startup-cheap.

The two structural disadvantages that made established companies slow - can’t test cheap, can’t adapt cheap - are dissolving in parallel.

Meanwhile, the asset GenAI-native startups don’t have is the one your company has been quietly accumulating across its lifetime:

  • Customer interaction history.
  • Buyer feedback.
  • What sales has learned about objection patterns.
  • What customer success has learned about where the product breaks down in real workflows.
  • What account management knows about how the contract differs from the use.
  • What the SMEs in the company carry in their heads but no spec has ever captured.

The shift in what’s durable - code regenerates in a weekend, customer knowledge takes the lifetime of a company - favors the side that’s been building it the whole time. The asset has been on your books, valued at zero, the whole time. What changed isn’t the asset. What changed is what it’s worth, and whether the company you scaled is built to see the value.

The window is open. Whether you can use it comes down to five conditions:

  • Recognizing the threat. Most companies don’t, until it’s late.
  • Seeing the possibility. The unfair advantage isn’t visible from inside the scaling lens that built the company.
  • Running discovery isolated, alongside scaling. Most attempts collapse back into the scaling org’s gravity. The metrics, patience, and aptitudes that scale a company are wrong for discovery work - and an effort that isn’t isolated from them won’t survive contact.
  • Doing discovery. Different attitudes, different aptitudes, different cadence than the work that scaled the company.
  • Switching users to what’s next. You don’t have to make customers switch to your new thing; you already own the relationship before any switch. The unique move available to you is to lower the switching cost, using everything the company already knows about your customers’ workflows, contracts, and dependencies. A GenAI-native startup can’t do this. They pay full switching cost. Done well, the move feels to your customer like an upgrade, not a migration.

The VCs I talk to are watching what happens when this transition isn’t made: the zombies in their portfolios. Companies that can’t grow, can’t be acquired, can’t be wound up cleanly. Their last realized asset turns out not to be the code, the brand, or the customer list. It’s the Slack archives, the support ticket histories, the internal emails, the Jira boards, the source code repurposed as training corpus rather than working system. AI labs are paying $10,000 to $100,000 a company for them, because public web text doesn’t capture how work actually gets done, and the next generation of agentic systems needs that operational dialogue to train inside. The asset that sat at zero on every balance sheet has a market price the moment the company dies. And the buyers are the labs powering the next set of competitors. It’s the same asset class your company has been quietly accumulating - and far more of it than appears on any balance sheet, including yours.

Lack of intent isn’t what makes a zombie. Engineering tried. Product tried. GTM tried. Each tried from inside their function’s frame, and the problem doesn’t shrink to fit any of them. Finding new PMF isn’t an engineering problem, isn’t a product problem, isn’t an executive problem, isn’t a GTM problem. There is no seat at the table shaped exactly for this problem. The CEO’s is the closest, and even that seat has its own gravity.

The window is open. The advantage is yours. The question isn’t whether you have it - you do. The question is whether the company you built can create the conditions to solve a problem that doesn’t fit any seat at the table you already have.