The PLG Sales Motion Reboot — 60-Min Training

Direct Answer

The PLG sales motion is not "sales-led plus a free trial." It's a fundamentally different operating model where the product is the top-of-funnel, the demo, and the proof-of-value all at once — and your AEs only enter the conversation when a Product Qualified Lead (PQL) has already self-selected through usage signals.

This 60-minute training rewires AEs and sales managers around five operating rules: (1) define the PQL by behavior, not firmographics; (2) respect the "don't ruin the magic" rule — never reach out before the user has had their aha moment; (3) segment ruthlessly into self-serve, sales-assisted, and sales-led tiers using ACV potential and account complexity; (4) treat expansion as the primary revenue motion, not new-logo; and (5) arm reps with usage data, not pitch decks.

Run this as a live 60-min working session — no slides on rep monologues, every block ends in a written artifact your team uses Monday morning.

Section 1 — Frame the Reboot (5 min)

Open by killing the dominant misconception. PLG is not a marketing tactic and it is not "self-serve." As Wes Bush argues in *Product-Led Growth* (2019), PLG is a go-to-market strategy where the product itself drives acquisition, conversion, and expansion — sales exists to compress time-to-value on accounts the product can't close alone.

Kyle Poyar at OpenView frames it bluntly: "The product is your best SDR."

Sales managers, say this out loud to the room:

"From today forward, we do not chase logos. We chase usage. If the product hasn't earned a conversation, we don't have one."

Then ask each AE to name one deal in the last 90 days where they engaged too early — before the user activated — and what it cost them. Write the deals on the whiteboard. This is the baseline.

Section 2 — Define the PQL with Precision (15 min)

A Product Qualified Lead is a user or account that has demonstrated buying intent through product behavior, not form fills. Elena Verna's working definition: "A PQL is a user whose in-product behavior predicts they'll convert to paid at materially higher rates than a random signup."

Walk the room through the PQL signal taxonomy. Have AEs build their own scorecard live:

• Activation signals (table stakes) — user completed the core "aha" action (e.g., invited a teammate, connected a data source, ran their first workflow). No activation, no PQL. Period.
• Depth signals — 3+ active users from the same email domain, 5+ sessions in 14 days, or API calls above the free tier ceiling. Depth proves the use case is real, not a kicked tire.
• Account-fit signals — domain matches ICP (employee count, industry, tech stack via Clearbit/ZoomInfo enrichment), billing email is corporate not gmail, and the workspace name reads like a real company.
• Intent signals — user hit a paywall, viewed the pricing page from inside the app, invited a user with a "VP" or "Director" title, or asked a question in-app that maps to a paid feature.

Tomasz Tunguz's rule of thumb at Theory Ventures: a PQL should convert to paid at 5-10x the rate of a marketing qualified lead. If your PQL definition isn't producing that lift, it's too loose — tighten the activation bar.

End the block with each AE writing their personal PQL scorecard (4-6 signals, weighted) on a notecard. These get reconciled into a single team definition in Section 6.

Section 3 — The PLG-to-Sales Handoff Trigger (10 min)

This is where most PLG sales orgs bleed pipeline. The handoff is not "PQL fires, AE calls within 5 minutes." That ruins the magic. The handoff is a trigger criterion plus a permission-to-reach-out moment.

Teach the three-gate handoff:

1. Gate 1 — PQL fires in your CRM/CDP (Pocus, Endgame, Common Room, or homegrown).
2. Gate 2 — Permission moment — user took an action that *invites* contact: hit a paywall, requested a quote, invited 3+ teammates, or crossed a usage threshold that implies team/enterprise need.
3. Gate 3 — Account context check — AE spends 5 minutes in the product workspace (read-only) to see *what the user is actually trying to do* before reaching out.

Verbatim outreach script (use this — do not improvise):

**"Hey [Name] — saw you and two teammates have been running [specific workflow] this week. I noticed you hit the [free tier ceiling]. I'm not going to pitch you — I'm the AE for your account and I wanted to make sure you know there's a [team plan / feature] that removes that limit.

Want me to turn it on for a week so you can keep going, no commitment?"**

Notice what this script does NOT do: it doesn't ask for a meeting, doesn't pitch features, doesn't reference a deck. It offers to remove friction the user is already feeling. That is the entire PLG sales playbook in one paragraph.

Section 4 — Segment Ruthlessly: Self-Serve vs Sales-Assisted vs Sales-Led (10 min)

Bob Moesta's JTBD lens applies directly: different jobs require different motions. Build the segmentation table on the whiteboard:

• Self-serve — <$10K ACV potential, <50 employees, individual buyer. AE never touches. PLG nurture only. Product and lifecycle marketing own this.
• Sales-assisted PLG — $25K-$100K ACV, 50-500 employees, team-level adoption. AE engages only after PQL + permission moment. Goal: compress activation-to-paid from 90 days to 30. Quota: ~$1.2M-$1.8M.
• Sales-led PLG — $100K-$500K+ ACV, 500+ employees, multi-team or security/procurement gate. AE engages earlier, but the product still leads — start every call with a workspace screen-share, not a deck.

Jason Lemkin's SaaStr observation: the worst thing you can do is run sales-led plays on a sales-assisted segment. You burn the user's trust and the CAC math collapses. Have each AE re-segment their top 20 accounts using these tiers. Anything mis-tiered gets re-routed today.

Section 5 — Expansion Is the Game; "Don't Ruin the Magic" (15 min)

In a mature PLG motion, 60-80% of net new ARR comes from expansion, not new logos. Kyle Poyar's OpenView benchmarks consistently show PLG leaders posting 130-150% net dollar retention — that's where the model pays for itself.

Reframe the AE role: you are an account-growth engineer, not a hunter. Three expansion plays to drill:

• Seat expansion — monitor weekly active user growth inside paying accounts. When WAU grows 30%+ MoM, trigger a "right-size your plan" conversation with the billing owner. Script: *"Your team's grown from 8 to 14 active users. Want me to move you to the team tier — it's cheaper per seat at your volume."*
• Feature expansion — watch for paid users hitting limits on adjacent features (API calls, integrations, SSO requests). These are pre-qualified upsell triggers.
• Multi-team expansion — when a second email domain or department starts a workspace inside an existing account, that's a land-and-expand signal. Loop in the customer's exec sponsor.

Now the "don't ruin the magic" rule, said plainly:

"If the user is succeeding without us, we shut up and let them succeed. Sales contact before the aha moment lowers conversion. Always."

Operationally that means: no outbound to users who haven't activated. No "checking in" emails. No drip sequences that interrupt onboarding. The product's job is to deliver the aha; the AE's job is to show up *after* it lands, with value, not friction.

Section 6 — Artifacts and Commitments (5 min)

Close the hour with three written artifacts the team commits to before leaving:

• The team PQL scorecard — reconciled from Section 2 notecards into one weighted definition. Posted in #sales-ops by EOD.
• The handoff SLA — PQL fires → AE acknowledges in CRM within 4 business hours, but does not contact the user until the permission moment. Manager audits weekly.
• The "magic-preserving" pledge — every AE signs off: no outbound to non-activated users, no "just checking in" emails, no calendar links before the user asks. Violations get reviewed in 1:1s.

End with Jason Lemkin's line: "In PLG, your job as a rep is to be useful, not present." Adjourn.

FAQ

Q: How is a PQL different from an MQL? A: An MQL is a marketing-attributed lead — usually a form fill, content download, or webinar attendee. A PQL is a usage-attributed lead — the user has *demonstrated* fit through behavior inside your product. PQLs convert at 5-10x MQL rates because the qualification signal is behavioral, not declared.

Q: What if our product doesn't have a free tier? A: Then you don't have a PLG motion — you have a sales-led motion with a trial. That's fine, but don't pretend the playbooks are the same. PLG requires unrestricted self-serve access to the core value loop. If you gate that, you lose the activation signal that makes PQLs work.

Q: How fast should AEs reach out after a PQL fires? A: Acknowledge the PQL in CRM within 4 hours. Reach out to the user only after the permission moment (paywall, quote request, team invite, usage ceiling). Speed-to-lead matters less than context-of-lead in PLG.

Q: Won't AEs miss quota if we restrict outbound? A: Restructure quota around expansion plus PQL conversion, not raw new-logo outbound. PLG-mature orgs typically run 60-80% of ARR from expansion. If your comp plan still rewards cold outbound on non-activated users, the comp plan is the bug — not the rep behavior.

Q: Who owns the PQL definition — product, marketing, or sales? A: Joint ownership, single accountable owner. RevOps usually holds the pen, with product, marketing, and sales each having a veto. Re-tune the definition quarterly based on conversion lift vs. MQL baseline.

Sources

1. Wes Bush — *Product-Led Growth: How to Build a Product That Sells Itself* (2019). The foundational PLG text; defines the PLG framework and the "you must, you should, you can" trigger model.
2. Kyle Poyar — *Growth Unhinged* (OpenView Partners newsletter). Ongoing PQL definitions, sales-assisted PLG benchmarks, and NDR data across 100+ PLG companies.
3. Elena Verna — *Elena's Growth Scoop* (Substack). Operating definitions of PQLs, PQAs (Product Qualified Accounts), and growth loops.
4. Bob Moesta — *Demand-Side Sales 101* (2020). Jobs-to-be-Done framing for matching sales motions to buyer jobs across PLG segments.
5. Jason Lemkin — SaaStr (saastr.com). Practical writeups on PLG-plus-sales hybrid motions and segmentation pitfalls at $25K-$500K ACV.
6. Tomasz Tunguz — *Theory Ventures* blog (tomtunguz.com). PQL conversion benchmarks and PLG-to-enterprise transition data.
7. OpenView Partners — *2023 Product Benchmarks Report*. NDR, activation rates, and PQL-to-paid conversion across the PLG cohort.
8. Pocus / Endgame / Common Room — vendor documentation on PQL scoring architecture and PLG-to-sales handoff tooling.