Launching PLG Inside a 25-Year-Old B2B Company

58 percent of B2B SaaS companies ran a PLG motion (OpenView 2022 Product Benchmarks, via ProductLed). OpenView's 2023 benchmarks found PLG companies grew about 50 percent year over year, against 21 percent for sales-led, while spending 39 percent less on sales and marketing.

That is a structural reordering of who wins in B2B revenue. But the harder question in front of most revenue leaders is how you get there when you already have 25 years of infrastructure, a loyal customer base, a PE firm on the cap table, and 80 percent of revenue baked into a motion built for a completely different era.

That is the real conversation, and we had it live inside our community with a CRO running exactly that transition at a 25-year-old low-code platform with enterprise logos like AT&T, Google, Southwest, and Farmers Insurance. A real, established business navigating one of the hardest transitions in B2B: building an entirely new front door while protecting the house you already built.

The door you built no longer fits the people trying to walk through it

The diagnosis was uncomfortable and specific. The addressable market for the original product was shrinking. The people who knew how to build on the platform had learned a proprietary language. That group was loyal and deeply embedded, and it was also aging and shrinking. Younger builders and newer teams expected something that looked and felt like Replit or Lovable. They were never going to learn a dated interface to discover value that a natural language prompt could surface in 60 seconds.

The conclusion: the current front door was actively losing the next generation of the market before the first conversation happened.

That shows up in market data too. Menlo Ventures reports AI-native startups reach product-market fit 2.4x faster than traditional software companies. Products where AI is the architecture are being funded, adopted, and scaled faster than the previous category leaders. Buyers expect it. Companies without a credible answer lose shortlist consideration before the first demo gets booked.

When did you last honestly audit whether your front door matches what today's buyer expects to find?

The innovator's dilemma, lived in real time

Clayton Christensen wrote The Innovator's Dilemma in 1997. In 2026 it is a weekly operational reality for revenue leaders at established companies. The specific tension: how do you build an AI-native product motion inside a company designed for something else, without blowing up the revenue that funds the whole operation?

Fence off the new thing completely

The new product team operates as a separate business unit, with its own brand, its own ICP, its own content strategy, and a CRM built on the product itself. Engineers, marketers, and a small sales team of four in an 80 percent PLG motion, all dedicated. No double duty on the core business. That was a deliberate decision. Without the fence, the gravitational pull of the existing business kills the new initiative before it finds product-market fit.

Intercom made the same call at larger scale. The company renamed itself Fin, betting the business on its AI customer agent. Intercom CEO Eoghan McCabe said (company-stated, early 2026) Fin reached about $100 million ARR, growing about 350 percent year over year. Getting there required intentionally cannibalizing roughly 60 million of core business revenue. They absorbed that pain deliberately, because the alternative was a slow fade.

Ship before you are ready

The new product launched with less than two months of public availability at the time of our conversation, thousands of active users, and a clear list of features still to build. The framing was blunt: the market is moving too quickly for a long beta. Ship, get feedback, iterate. Two quarters to product-market fit or bust. That is startup thinking applied to an enterprise product built on 25 years of infrastructure, and it requires cultural rewiring alongside the product decision.

The culture problem is harder than the product problem

This is the part that does not make it into case studies. Engineers who had been building the core platform for years came onto the new team with a pace and a pride shaped by a different kind of company. Revenue leaders needed startup urgency. The team brought craftsmanship. Neither orientation is wrong. They are different definitions of urgency, and the gap between them is where initiatives stall.

Google's version is instructive. When ChatGPT launched in late 2022, Google had better AI research than any competitor and no product team wired to turn it into a consumer surface fast. The pivot happened when leadership locked arms on the existential framing and made decisions at a pace the culture had not previously operated at. Eighteen months later the narrative had flipped.

The common thread: organizations that made the transition made it because leadership named the threat clearly and moved with urgency.

Barbell clarity

Roughly 60 percent of revenue came from 20 percent of customers, the enterprise and strategic tier. That barbell has to stay intact while the new motion builds. What they learned: do not migrate enterprise customers onto an unproven platform, do not let the core business absorb the new team's focus, and do not run a single unified motion across two completely different ICP profiles. Separate the metrics, separate the teams, and be honest with the board about which side is in a learning phase.

Four decisions that separate the builders from the planners

Decision 1: Name the existential case before you build the business case

The companies successfully launching new motions inside legacy businesses share one thing: leadership said out loud, clearly and without diplomatic softening, that the current trajectory is a slow decline. The version that changes behavior is harder to say: we are watching our addressable market shrink, and if we do not open a new front door, we become a zombie.

Zombie is the honest frame. A business that is not dead but has stopped growing because the market moved past it. You still have revenue. You still have customers. You have no path to new logos. You are running out the clock. The business case follows from the existential case.

Decision 2: Separate the metrics before you separate the teams

The most common failure mode in dual-motion companies is treating the new initiative as a cost center inside the old reporting structure. Enterprise quota attainment, traditional MQL volume, and historical bookings velocity are the wrong scorecards for a PLG motion 60 days into market.

Define separate success metrics before launch: activation within the first session, free-to-paid conversion at 30 days, time to value, net revenue retention from PLG accounts. These numbers will look terrible at first. That is expected. Separating them prevents terrible early PLG metrics from getting averaged into the overall revenue report and triggering the wrong governance response.

Decision 3: Solve the wartime versus peacetime mismatch early

Ben Horowitz's framing of peacetime versus wartime leadership maps directly onto running a legacy motion and a startup motion at once. People who thrived in the 2021 and 2022 era learned behaviors and expectations that do not transfer to a market where you are building before product-market fit, moving before consensus, and measuring by experiments shipped. Retrofitting that inside a mature company means being deliberate about who works on the new initiative and what norms govern that team. The fence matters for culture as much as it matters for headcount.

Decision 4: Pick your cannibalization stance before the first customer crosses over

Intercom's move worked because the decision was explicit and made in advance. The alternative, letting customers migrate opportunistically while maintaining two product commitments and two pricing structures, creates internal chaos and customer confusion at the same time.

Before your first enterprise customer expresses interest in the new product, know your answer to three questions. Is this an and where they keep both? A migration path where they move over time? Or a replacement where you are actively steering them off the old product? Each has different implications for pricing, contract structure, and how you talk to your base. Organizations that do not answer this in advance find out the hard way that customers will answer it for them, usually in ways that damage both sides.

The close

Above roughly 10 million in ARR, the question stops being whether a motion works and becomes how you run multiple motions simultaneously without letting them cannibalize each other. The companies that get that right capture the PLG economics. The ones that do not end up with unreadable pipeline data and resource allocation that serves neither side.

If your legacy motion is plateauing and nobody in the room has named the existential case out loud, that is the work. Everything else is a planning exercise.