September 13, 2026
PRODUCT-LED GROWTH: LET FIRST VALUE CREATE THE NEXT USER

Lessons 79.1 through 79.3 borrowed audiences — partners, marketplaces, advocates. Product-led growth removes the borrowing: the product experience itself is the distribution route. A qualified stranger tries something small, gets real value in minutes, and the result naturally points to a deeper use, a return visit, or an invite.
The vocabulary, in plain language
- Product-led growth (PLG): acquisition driven by the product experience rather than by sales conversations or advertising — try, win, return, invite.
- Activation: the moment a newcomer completes the smallest meaningful win — not signup, not a tour, but a done job.
- First value: that win, stated from the user's side: "I produced a cited paragraph," "I booked the slot," "I cleaned the list."
- Collaboration: working with others inside the product — shared packets, comments, co-edits — which deepens use and spreads it.
- Template: a pre-built starting shape that removes blank-page dread and encodes good method.
- Shareable output (shareable): a result designed to travel — a linkable brief, exportable checklist, public page — carrying proof back to new users.
- Free tool: a narrow utility that completes one job fully, for free, with no account maze.
- Upgrade path (upgrade): the honest bridge from free value to paid depth — more sources, more seats, more history — taken because the free win proved the method.
The mental model: taste before the menu. The kitchen sends one perfect bite to the table. Nobody explains the supply chain. The bite proves the chef, and the menu becomes an easy yes.
Experience before sales
Traditional software asks for trust, then delivers value: demo call, proposal, purchase, onboarding, maybe a win in week six. Product-led reverses the sequence: value first, commitment second. The newcomer touches the work within minutes, with minimal friction — no sales call to see a sample, no credit card to run one check.
Two shapes carry most PLG wins:
Sample, template, or utility that completes one job. A source-linked sample report the visitor can read without login. A filing-check template they can copy with one click and run on their own company. A free headline-tester, availability-checker, or citation-formatter that solves a ten-minute pain fully. Each ends with a natural pointer to the fuller product: "this sample took one source — the Desk runs twelve and keeps the archive."
Collaboration or shareable that multiplies the win. The saved brief becomes a link a colleague can open. The template becomes a team packet with comments. The local shop's free "what fits in a small apartment" planner becomes a shared shortlist the couple revisits. The object travels (Lesson 79.3), and every view is a qualified arrival who already saw proof.
None of this means "free forever." That confusion sinks many builders. A free tool earns attention; a freemium tier sustains light use; a paid offer captures ongoing value. Those are pricing and packaging choices — and they belong to Part XV, the canonical home for monetization. This lesson designs only the distribution loop: arrival to first value to return or invite. Keep the price page out of the activation path until the win has landed.
Design the first-value loop
A loop has six beats. Write each as a concrete sentence for your product, not a slogan.
1. Arrival. Where the qualified stranger comes from — a marketplace listing (79.2), a partner template (79.1), a forwarded brief (79.3), a search page (76.2). Name the doorway; different doorways need different first screens.
2. Input. The smallest thing you ask for — a company name, a photo, a date, one paragraph. Every extra field before value is a toll booth. Prefill, default, and example-fill aggressively.
3. Result. The visible win in under ten minutes: a cited paragraph, a booked slot, a cleaned list, a side-by-side comparison. Show it, do not describe it.
4. Object. The saved, named, shareable thing — the brief page, the care card, the shortlist — with a stable link and a filled example beside the blank. If it cannot be saved and reopened, it cannot compound.
5. Return. The reason to come back: saved work waiting, a weekly update on the same job, a follow-up step ("add two more sources"), a scheduled event. A loop without return is a demo, not growth.
6. Invite or deeper action. The earned next step: share with a collaborator where collaboration helps, try the fuller template, join the Tuesday note (78.1). Asked after value, in context, once — never as a signup-wall ambush.
Measure the loop the way Appendix 79.A teaches: arrivals, first-value completions, returns, invites sent and accepted. If arrivals are high and activations low, simplify input. If activations are high and returns low, strengthen the saved object and the return cue.
Exercise: draw the loop on one page
Create FIRST-VALUE-LOOP.md. One arriving user, one input, one result — no branching diagrams.
# FIRST-VALUE-LOOP.md — [Product]
## Arrival (qualified doorway)
- Source route + newcomer intent: ___
## Input (smallest ask)
- Fields requested + example-filled default: ___ / time to enter: ___
## Result (first value <10 min)
- Visible win, user words: ___
## Object (saved + shareable)
- Object name + link type: ___ / blank + filled example: ___
## Return (reason to come back)
- Cue + timing: ___ (saved work / weekly update / next step)
## Invite / deeper action (earned, once)
- Ask + why it helps now: ___
## What we defer to Part XV
- Free vs freemium vs paid note (one line, no pricing here): ___
Worked mini-example — Research Desk: arrival from the partner newsletter's sample brief; input is one company ticker plus one question, prefilled with an example; result is a one-page cited brief in under eight minutes; object is a saved, linkable brief with blank template beside it; return is "your brief updates when the next filing lands — plus Tuesday's check"; invite is "add a colleague to mark claims" offered only after the brief is saved. Pricing appears nowhere in the loop — the win sells the next step.
Finish line: a FIRST-VALUE-LOOP.md with arrival, input, result, object, return, and invite each specified, timed under ten minutes to first value, with monetization explicitly deferred.
Verify quickly: watch a stranger run the loop without help. If they stall, note exactly where — input, result, or save — and shrink that step before adding any feature. One observed stall beats ten opinions.
Common failure mode: the tour trap — a six-screen product tour, a required onboarding call, and a gated sample that teaches navigation instead of delivering value. Tours explain; loops prove. Prove first.
Check your understanding
1. Why does product-led growth put experience before sales, and what does that change about the first ten minutes? 2. What distinguishes a free tool in this lesson from a freemium or paid decision in Part XV? 3. How do the saved object and return cue turn a one-time demo into a loop?
Next
You now hold four borrowed and self-propelling routes — partners, marketplaces, referrals, product loops — beside the audience, paid, search, social, and email engines from earlier classes. Lesson 79.5 closes Part XIV by turning the shelf of routes into a portfolio: one compounder, one test, one direct relationship, and ninety days of testable action.
ARTICLE DISCUSSION
JOIN THE
CONVERSATION.
Got a question, a take, or a better way to do this? Log in and leave a comment.
