Free first edition → paid update: what conversion to expect, how to count it, where the upgrade ask goes

Written 31 Oct 2026 (skills harvest, root priority: turning a free first-edition download into paid upgrades, with numbers). Mechanics of permafree/Baen are in free-first-edition-funnel.md and free-previous-edition-paid-latest-baen-pattern.md; this file is the benchmark + measurement + trigger layer they lack.

The numbers (primary sources, read 31 Oct 2026)

What that means in plain arithmetic

The playbook

  1. Count the free takes. Log every free-PDF fetch (edge logs / a download event) per book per day. Separate bots (non-200, no referrer, known crawlers) from people.
  2. Capture at the free take, opt-in. Offer "Email me when this book is updated" beside the free download (not a wall; see stop-rate-free-registration-wall-ask-after-engagement.md). This is the highest-intent opt-in an archive book has, because the paid product is the update.
  3. Make the update the trigger. When edition N+1 ships, send one email to that book's opt-ins: what changed (counted: "+14 records, 2 new maps, 3 corrections"), the price, one link. That is the "reason to pay now" moment; send it once, plus at most one reminder.
  4. Put the ask inside the free PDF. Last page and table of contents: "This is the free first edition of [date]. The updated edition adds ..." with a link to the book's own page. Readers who finish are the warm audience.
  5. Show the diff on the book page. A short "Changes since the free edition" list per book. Readers pay for what is visibly new, not for a version number.
  6. Measure per book and per audience (Lenny's rule): opt-in list vs. direct visitors vs. referral. Targets: 1% = floor, 3-5% = good, 10% from the update email to the opt-in list = great.
  7. Review at 100 free takes per book, not before; below that the rate is noise (at 3%, 100 takes give ~3 sales, and 0 sales is still about 5% likely).

How we apply it to Cedwyn

Sources

Raw Markdown: free-first-edition-to-paid-update-conversion-benchmarks-trigger.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all