A structured playbook for running a closed beta that produces clear learning, retained design partners, and an unambiguous decision on whether to proceed to general availability. Most betas fail not because the product is wrong, but because the program is run informally: recruitment is opportunistic, success criteria are implicit, communication is sporadic, and exit gates are never defined. This skill replaces all of that with concrete templates and decision rules.
A good closed beta runs 4-8 weeks, recruits 10-30 participants from three concentric cohorts ("friends, family, fanatics"), publishes a weekly cadence the team commits to, and exits on pre-agreed criteria rather than the calendar. The outputs are a beta program plan, a recruitment script, a weekly cadence template, and an exit memo that either greenlights GA, extends the beta, or kills the feature.
launch-playbook/ and a progressive rollout instead).Before building the beta plan, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
create-prd/).assets/beta-program-plan.md and get PM, Eng and sponsor sign-off before recruiting. Gates set afterwards drift toward whatever the beta happened to show.assets/recruitment-script.md. Defaults [RECOMMENDED], to adjust for your context:assets/weekly-cadence-template.md).assets/exit-memo.md: Greenlight, Extend, Pivot or Kill, against the gates as written.Done when the exit memo records each gate's result against its pre-agreed threshold and a decision signed by the same people who signed the gates.
Framework tables, troubleshooting and success criteria: references/beta-framework.md.
Mistake: The cohort is 30 employees and 5 advisor friends, with no Fanatics cold-recruited from the ICP.
Why it happens: Friends say yes within two days, and cold recruiting is slow.
Instead: Sequence Friends, then Family, then Fanatics, and keep Fanatics at 30% of the cohort or more. Screen them for active pain in the problem area.
Mistake: The outreach email opens "We're launching an exciting new AI assistant, want to try it?"
Why it happens: The team is proud of what it built and leads with it.
Instead: Name the participant's problem in the first paragraph, then the ask (hours per week, duration) and the payoff. Target people who described this pain in discovery, starting from assets/recruitment-script.md.
Mistake: The largest beta customer asks for a custom export format, and engineering builds it in week 3 for that customer alone.
Why it happens: The participant is a paying account, and keeping them happy feels like protecting the beta.
Instead: Log the request in the customer-feedback-triage/ queue with the rest of the beta input. Commit to it for v1.1 only if the broader signal supports it, and track sales-promised customizations separately.
Nine more, each with a bad and a good example: references/red-flags.md.
| File | Purpose |
|---|---|
assets/beta-program-plan.md | Plan template: gates, cohort sizing, timeline |
assets/recruitment-script.md | Outreach templates for the three cohorts, screening questions |
assets/weekly-cadence-template.md | Monday digest, office hours, review, Friday snapshot |
assets/exit-memo.md | Exit decision memo (Greenlight / Extend / Pivot / Kill) |
examples/shared-dashboards-closed-beta.md | Worked beta |
references/beta-framework.md -- Full framework (cohort, Kano, success gates, cadence, exit gates), the 8-step workflow, troubleshooting matrix, and success criteria. Read this when building the plan, setting gates, running the cadence, or diagnosing problems.references/beta-program-guide.md -- Practical reference guide: why betas fail, cohort sequencing, Kano deep dive, exit-gate worked examples, common failure modes. Read this for narrative depth and worked examples.references/red-flags.md -- Bad-vs-good examples for the beta plan, recruitment script, cadence, and exit memo. Read this to review beta artifacts before opening recruitment.In Scope:
launch-playbook/Out of Scope:
launch-playbook/)discovery/brainstorm-experiments/)launch-playbook/)Important Caveats:
delivery-manager/).| Integration | Direction | What Flows |
|---|---|---|
create-prd/ | Receives from | PRD defines the hypothesis and headline outcome that beta gates measure |
discovery/identify-assumptions/ | Receives from | Riskiest assumptions become the beta's primary learning goals |
discovery/brainstorm-experiments/ | Complementary | Beta is one experiment type; brainstorm-experiments covers smaller/faster alternatives |
daci-framework/ | Uses | DACI driver owns the exit-gate decision |
launch-playbook/ | Feeds into | Greenlit beta hands testimonials, case studies, and known issues to launch |
release-notes/ | Feeds into | Beta release notes preview the GA changelog |
summarize-meeting/ | Complementary | Office hours and 1:1 notes become structured weekly summaries |
senior-pm/ | Reports to | Exec sponsor receives the exit memo and signs the GA decision |