By motion · PLG with sales-assist

The PLG motion, where the library applies.

This library is honest about its center of gravity: it's calibrated to sales-led B2B outbound — cold email, LinkedIn, conferences, multi-thread enterprise cycles. PLG operators inherit a subset of the chapters, and most PLG founders arriving at the library come for a specific piece (first-party signals, expansion nurture, the sales-assist layer) rather than the whole stack.

This reading path is the curated subset. It also includes the bridge path for PLG companies that scale past $5-10M ARR and start layering cold outbound on the self-serve funnel — at which point most of the library starts to apply, and the segment-and-motion hubs become the natural next stop.

Before you read

If your PLG company is pre-PMF, the library will under-deliver for you. The first-party-signals chapter is useful, but the deeper sales-led chapters are written for a motion you're not running. If you're post-PMF and adding sales-assist or outbound on top of self-serve, the library applies in proportion to how much of your motion is sales-led.

What the library covers for PLG

The chapters PLG operators actually use

Self-serve plus sales-assist

Most of the Allston Labs library is calibrated to sales-led motions — cold outbound, LinkedIn, conferences, multi-thread enterprise cycles. PLG operators inherit a subset: the first-party signal work, reply handling for self-serve-to-paid handoffs, expansion nurture, and the founder-led chapter for the manual sales-assist layer most PLG companies eventually layer on the self-serve funnel.

  1. 01
    ICP — First-party signal mining

    The single most useful chapter for PLG. Product usage, demo requests, support tickets, activation milestones — the PLG operator's ICP signal is first-party by default.

  2. 02
    ICP — Closed-won deconstruction

    PLG closed-wons (self-serve users who converted to paid, or self-serve teams that expanded to a seat-license) carry the same signal as sales-led closed-wons. The differential vs closed-lost is your highest-leverage analytics surface.

  3. 03
    Replies — Nurture for expansion

    PLG expansion is a nurture motion. Trigger-based touches (usage milestone reached, team-member added, plan-limit approached) produce the 3-7x lift PLG operators expect from lifecycle marketing.

  4. 04
    Replies — Reply classification (handoff layer)

    When PLG layers a sales-assist motion on top of self-serve, the inbound reply queue mirrors the cold-outbound reply queue. The five-category classification applies; routing goes to PLG AE or customer-success instead of outbound AE.

  5. 05
    Replies — Meeting booking

    PLG-sourced meeting requests (a self-serve user asks for a demo) decay at the same speed as cold-outbound replies. Same calendar-vs-coordination tradeoff, same show-rate pattern.

  6. 06
    Sales Motion — Founder-led (the sales-assist layer)

    Most PLG companies add a manual sales-assist layer for high-ACV accounts. The founder-led chapter applies — 20-35% close rate, single-pipeline rule, time-allocation discipline.

When PLG hits the ceiling

Layering cold outbound on top of PLG

Post-PMF PLG companies expanding to enterprise

Most PLG companies that scale past $5-10M ARR add a cold-outbound lane to reach enterprise accounts that don't naturally arrive through self-serve. At that point, most of the library applies in full. The chapters below are the entry door for the PLG operator standing up that outbound lane for the first time.

  1. 01
    ICP — Segmentation architecture (PLG-to-outbound)

    PLG self-serve produces a different segment than the enterprise tier cold outbound targets. The segmentation chapter is the bridge — it formalizes the differential between the inbound and outbound cohorts.

  2. 02
    ICP — Segment-channel fit

    PLG companies typically have no sales-led infrastructure. The channel decision has to come before the infrastructure spend — confirm the enterprise segment is LinkedIn-active before standing up LinkedIn account architecture.

  3. 03
    Email infra — The full reference

    The 14-chapter substrate that determines if your new outbound lane lands or goes to spam. PLG companies frequently have strong inbound-email reputation; the outbound estate has to be separate so one doesn't contaminate the other.

  4. 04
    Sales Motion — Multi-thread engagement

    PLG sales motions inherit the self-serve single-stakeholder bias. The first outbound-sourced enterprise deals expose the multi-thread discipline gap; reading this before the first enterprise deal closes is the cheap version of learning it.

When PLG adds an outbound lane

We stand up the outbound lane for PLG companies.

When PLG hits the enterprise ceiling and you need a cold-outbound lane to reach accounts that don't arrive through self-serve, we build the infrastructure and operate the upstream. The PLG team stays focused on product and self-serve; the outbound lane runs in parallel under your entity.