Someone from product said the words "self-serve motion." Someone from finance nodded. There was a slide with a funnel on it, and the top of the funnel didn't have a single seller in it. And you sat there doing the math on what that means for the team you built.

Lindy sorts your inbox, drafts replies in your voice, and preps you before every meeting over iMessage. 400,000+ professionals use it. Try it free.

Try Lindy Free

Here's what nobody in that room said out loud: the shift to product-led growth doesn't just change how the company sells. It changes what enablement is for.

And most enablement teams are going to find that out the way they find out about everything else. Late. After the decision is made, after the org chart is redrawn, after someone hands them a Slack message that starts with "can you put together training on the new motion."

I don't want that to be you. So let's talk about what actually happens to your function when the product starts doing the selling, and how you get in front of it while you still have room to move.

When a company goes from sales-led to product-led, everyone braces for the obvious change. Fewer SDRs. A self-serve tier. A pricing page that does work a rep used to do.

The change that matters more is the one nobody braces for. The center of gravity of enablement moves.

In a sales-led org, enablement has one audience. The seller. Everything you build points at one person: the deck they pitch, the talk track they memorize, the certification they pass. Your whole function is organized around making a human better at selling.

In a product-led org, the product sells before the human ever shows up. A user signs up, pokes around, hits a wall or hits the "aha," and decides — mostly on their own — whether this thing is worth paying for. By the time a seller enters the picture, the buyer has already half-decided.

That single fact reshapes everything. The product is now teaching. The user is now learning without you. And the seller's job has quietly changed from opening the relationship to extending one that the product already started.

Enablement doesn't shrink in that world. It splits.

Here's the framework I want you to draw on a whiteboard before your next planning cycle.

In a sales-led motion, enablement serves one audience. In a product-led motion, enablement serves three. I call it The Three Audiences of Product-Led Enablement, and the whole reshaping of your role lives inside it.

Audience One: The Product. Your new first enablement surface isn't a deck. It's the product itself. In-app onboarding, activation flows, empty states, the moment a user gets stuck at 11pm with nobody to call. That experience is now teaching the thing a rep used to teach in a demo. Somebody has to own whether the product actually onboards a human well, and increasingly that somebody is you. This is where the leverage is, and it's also where the danger is: between 40% and 60% of free users in a typical product-led funnel never reach the activation milestone. That's not a product bug. That's an enablement gap with no enablement person assigned to it.

Audience Two: The User. The self-serving buyer who reaches the "aha" moment before any seller is involved. They don't read your sales playbook. They read your help docs, your onboarding emails, your in-app nudges, your getting-started guide. The educational layer that used to live inside a rep's head now has to live in content the user can consume alone. That's enablement work. It has just never sat in your job description before.

Audience Three: The Seller. Still here. Still mattering. Just doing a different job. The seller stops being the gatekeeper to the product and becomes a consultant on usage that's already happening. Their new core skill is reading product signals — who activated, who invited their team, who hit a usage limit, who visited the pricing page three times — and knowing what to do with each one. Gartner's research is blunt about why this shift is permanent: 75% of B2B buyers now prefer a representative-free buying experience. The rep who insists on being the front door is selling against what the buyer wants. Product-qualified leads convert at 25 to 30%, against 5 to 10% for the marketing-qualified leads your team chased for a decade. The signal is the job now.

Three audiences. One function. If you only enable the third one, you're running a sales-led playbook inside a product-led company, and the gap between those two things is where careers stall.

Here's the thing about the reshaping. It happens whether or not you lead it.

If enablement doesn't claim the product surface, product owns it. If enablement doesn't claim the user education layer, marketing or lifecycle owns it. If enablement doesn't redefine the seller's role, RevOps writes the new comp plan and hands you the training order after the fact. Your function gets carved up and distributed to whoever moved first, and you're left with the smallest, most reactive slice: train the reps on a motion three other teams already designed.

This is the Mandate Gap showing up in its highest-stakes form. The transition to product-led growth is the single biggest change-management event a revenue org will run this decade — it rewires roles, comp, the funnel, and rep identity all at once. And McKinsey is direct that it "cannot be achieved as a side project," that building the integrated motion takes at least a year. A year-long, function-redefining change, and in most orgs nobody owns the human side of it.

The data on what happens when nobody owns it is ugly. Only 27% of companies that attempt a product-led transition report sustained year-over-year expansion. Insight Partners names the number one reason these efforts stall, and it isn't the product. It's cross-functional misalignment. Nobody owned the change, so the change owned everybody.

That number — 27% — is your argument for moving now. The other 73% didn't fail because their product wasn't ready. They failed because the organization wasn't.

This is the moment enablement's scope actually expands, if you reach for it. Not by asking permission. By building influence through the value you deliver before the org chart catches up to it.

Let me get practical. You don't reorganize a team around three audiences in a quarter. You start signaling the shift before the transition forces it. Here's the sequence.

Map your function against the three audiences. Take everything your team produces this week and sort it: product, user, or seller. If 90% of it lands in the seller column, you've just found your blind spot. That imbalance is the gap a reorg will eventually expose — better you find it than your VP.

Plant a flag on the product surface. Go find whoever owns in-app onboarding and activation today. It's probably a product manager doing it part-time with no enablement instinct. Offer to co-own the activation experience. You don't need a title change to start treating the product as an enablement surface. You need one working relationship and one shipped improvement.

Reskill the seller before the comp plan does it for you. The gatekeeper-to-consultant shift is a real reskill, and it's an onboarding problem in disguise — you're moving an experienced rep into what is functionally a new role. Build the signal-reading curriculum now. Teach reps to read product behavior and consult on it. The team that already knows how to do this when the motion flips is the team that survives the flip.

There's a part of this that no framework captures, and if you skip it the whole reshaping fails.

Your sellers are doing math too. When leadership says "the product is going to do more of the selling," your reps hear "I'm being automated out." And a frightened rep completes your certification and then quietly slow-walks the change on the floor. You cannot train your way past a threatened paycheck.

This is the part of the transition that belongs to enablement and to no one else, because you're the only function in the room with the reps every single week. RevOps owns the comp number. You own the conversation about it. There's a difference, and the difference is the whole job.

Here are two conversations to have early on…

The Identity Conversation: reframe the role out loud. Not "the product is replacing you." It's "you're moving from chasing cold leads to consulting on warm usage — the higher-leverage half of the job." That conversation happens in coaching, one rep at a time, and it is the most important enablement you'll deliver all year.

The Proof Conversation: stand up a small pilot pod, find the one rep who's winning under the new motion, and let peer proof do what a top-down mandate never can. Manager belief is the multiplier that decides whether any of this transfers. Get one manager and one rep visibly winning, and the floor follows.

The companies that survive a product-led transition don't do it because their product was better. They do it because somebody owned the fear in the room. That somebody is you.

Most enablement teams will read a piece like this, nod, and wait for the transition to formalize before they act. That's the mistake. By the time it's formalized, the reshaping is done and you weren't in the room.

The window to lead this is open in exactly the moment that feels too early. While it's still a slide with a funnel on it. While "self-serve motion" is still a phrase and not a comp plan. That's when you claim the three audiences. That's when you plant the flag on the product surface. That's when you have the money conversation before fear sets in.

Product-led growth is going to reshape your team. That part isn't up to you.

Whether you lead the reshaping or get reshaped by it — that part is entirely up to you.

So my question to you is this.

If your company announced a full product-led pivot tomorrow morning, would your enablement team be the one designing the transition, or the one waiting for the training order? Be honest about which one. And if it's the second one, what's the one flag you could plant this week to change the answer?

Hit reply and tell me. I read every one.

Until next time my friends…
❤️, Enablement

Key Concepts from This Issue

The Three Audiences of Product-Led Enablement
The Three Audiences of Product-Led Enablement is a framework developed by Ryan Parker in Love, Enablement that describes how a company's transition to product-led growth splits the enablement function from serving one audience into serving three. It consists of three audiences: the Product (the in-app experience as the first enablement surface), the User (the self-serving buyer who reaches activation before a seller is involved), and the Seller (recast from gatekeeper to signal-reading consultant). It solves the problem of enablement teams running a sales-led playbook — one focused only on the seller — inside a company that has become product-led.

Key Data Points

Related Analysis

If You're Asking...

How does product-led growth change the role of sales enablement?
According to Ryan Parker's Three Audiences of Product-Led Enablement framework in Love, Enablement, a product-led transition splits enablement from serving one audience (the seller) into serving three: the product as a teaching surface, the self-serving user, and the seller recast as a signal-reading consultant. Enablement doesn't shrink in a product-led org — it splits, and teams that only keep enabling sellers are running a sales-led playbook inside a product-led company.

How do you keep sales reps from quitting during a shift to product-led growth?
Love, Enablement's Three Conversations practice says enablement must own the Money, Identity, and Proof conversations with reps before the motion flips, because reps hear "the product will sell itself" as "I'm being automated out." MongoDB deliberately overpaid reps through their transition rather than risk losing the team, proving the comp-and-identity conversation is the retention lever, not the training.

Why do most product-led growth transitions fail?
Only 27% of companies attempting a product-led transition report sustained year-over-year expansion, and Insight Partners names cross-functional misalignment — not product quality — as the number one reason these efforts stall. Ryan Parker argues in Love, Enablement that the transition fails as an unowned organizational-change problem, which is precisely the gap enablement is built to close.