What if the disadvantages of being an incumbent have quietly inverted into an unfair advantage - and the questions are whether the company you scaled can recognize it and can hold a problem that does not fit any seat at the table? Recognition is something you bring; holding the problem is the work I do alongside CEOs - for the bounded window the inversion opens, making the moves the scaling org can not make from inside its own gravity.
The Pattern
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 is what scaling looks like.
This is not the first time an exogenous change has reshaped what scaling rewarded. Mobile reshaped the desktop-first companies that had scaled before it. Cloud reshaped the on-prem incumbents that came before SaaS. Regulatory regime changes have done it repeatedly: HIPAA and the follow-on waves in healthcare; PSD2 and MiCA in finance; FERPA and the state privacy laws in education; the AI laws emerging now. Customer-expectations resets do it too, more quietly. In each case the underlying arc holds: the shift arrives, the existing competitive position erodes, the team tries the functional moves it knows how to make, the gap widens. I’ve been inside this pattern through six platform shifts in different seats - CEO, CPTO, CPO, and CTO. The shape of the impact was always the same: the company that should be moving but was not.
So, in response, when a successful software company tried to find new PMF, what I saw was that the effort always got valued from inside the scaling lens - wrong patience, wrong metrics, wrong people - and always lost. The pattern was so consistent (thanks to Christensen naming it) it got treated as a near-law of incumbency: success makes the next thing structurally unfindable. From the inside, the pattern held because the people who could see the next thing were the people the scaling org could not fund or promote: the discovery-aptitude, the patience for unstable signals, the willingness to throw the work away. The scaling lens valued the opposite. So the new thing got valued from inside the wrong reference frame and lost - not because the people inside the company couldn’t see it, but because the company they were inside couldn’t carry it. The conditions that made it a near-law are dissolving.
The Inversion
I see two GenAI effects changing 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 not test cheap, can not adapt cheap - are dissolving in parallel.
This is not just an analytical stance - the building I’m doing at the infra level (DXOS, plugin-bramble, Phoenix-flavored regeneration) is showing me what’s possible when both cost-curves collapse together. What’s distinctive about the GenAI moment, from where I’m sitting, is that the inversion mechanism - cost-to-test and cost-to-adapt collapsing together - is unusually sharp.
The Asset
Meanwhile, what I see your company sitting on - and what GenAI-native startups do not have - is the asset it’s 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
- Facts and assumptions about the market, customers, and company embedded in the existing software
Here’s what I’ve found makes the asset hard to see from inside the company: it’s not systematically written down anywhere. The CRM holds names and stages, not the texture of how customers actually behave when they hit the edges of the product. Sales calls leave the salesperson smarter and the company exactly as smart as it was before. Support tickets compress the situation that produced them into a category code. The texture lives in Slack threads, internal emails, the dialogue between an SDR and an AE the day after a hard customer call - and in the heads of the people who’ve been there long enough to remember the patterns. None of that shows up on any balance sheet. Which is precisely why it’s worth what it’s worth: a competitor can’t buy it, can’t replicate it, and can’t see what they’re missing until they need it and find they can’t get it.
From where I sit, the shift in what’s durable (e.g. 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 is not the asset. What changed is what it’s worth, and whether the company you scaled is built to see the value.
What It Takes
What I see from inside a company you would recognize: the Head of [the new thing] hire is six to nine months in and the strategic clarity hasn’t arrived. Win-rates are declining in segments that used to be safe. Existing customers are happy but new logos are getting harder. The product roadmap has gotten longer, not shorter. Engineering and product are both shipping but cumulative momentum has stalled. Board conversations have started shifting from “growth strategy” to “market response.” None of these are emergencies on their own. Together they’re the shape of the moment I keep seeing before it can be named.
The window is open. In my experience, the first condition is something you bring to the room - by the time we’re talking, the threat is already recognized enough to be a question worth asking. Most companies don’t see the threat until it’s too late. Once the threat is recognized, engagement runs through you - the CEO - and reaches into different parts of the company depending on the move. The minimal moves necessary to create the right conditions are the ones I run alongside you and the relevant parts of the org:
- Reframe what the scaling lens hides. The unfair advantage isn’t visible from inside the scaling lens that built the company. What’s visible is the threat - the GenAI-native startup with the disturbing demos. What’s not visible is the asymmetry of customer knowledge, valued at zero on every balance sheet, that the threat can’t replicate. I help your team make this visible to your leadership - what specifically lives in your Slack threads, in your support tickets, in the heads of your SMEs - so the conversation can shift from defense-against-threat to use-what-you-have.
- Configure isolated discovery alongside scaling. Most discovery attempts against sufficiently novel opportunities collapse back into the scaling org’s gravity. The metrics, cadence, and aptitudes that scale a company are wrong for discovery work - and an effort that isn’t isolated from them won’t survive contact. Isolation here is more than reporting lines: it’s separate funding, separate metrics, separate hiring, separate cadence, and an explicit charter not to be valued by the scaling org’s standards. I help you design that configuration so that the work survives the gravity of the scaling org.
- Run discovery alongside the scaling org. Discovery in an at-scale org requires different attitudes, different aptitudes, different cadence than the work that scaled the company, as well as insight into what is already true in the scaling org. The work is closer to what the founders did before any of the scaling rewards kicked in - and most of those skills have left the building. I bring the discovery-aptitude in and teach by doing - alongside the team, not in a separate room - so the muscle gets built back into the company.
- Lower the switching cost for users. 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. I operationalize that - helping your org turn the customer-knowledge asset into a switching-cost-reduction based on what’s already true with the current products, so the move feels to your customer like an upgrade, not a migration.
The Window
The investors 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, and 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 per 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.
What I’ve seen is that lack of intent is not 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 the next shape is not an engineering problem, is not a product problem, is not an executive problem, is not 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 is not whether you have it - you do. The question is whether the company you built can create the conditions to solve a problem that does not fit any seat at the table you already have. This is the work that gets done inside the window, or does not, in companies that don’t yet realize the window has opened for them. The companies that recognize it early get to run the experiment with their own asset; the companies that recognize it late watch their asset get bought by the labs powering the next wave of competitors. The math does not permit a wait-and-see strategy.