Claude Templates / A-tier · High leverage

Growth & SEO

The Beta Tester Playbook

Invites, in-app feedback, NPS, beta-only gating, and the graduation flow.

BETA-TESTER-PLAYBOOK.md · 14 sections · 2,066 words · 16 KB · markdown

Structure for the first ninety days. A beta_notes table and in-app feedback widget so bug reports land somewhere you'll read them, NPS prompts timed to activation rather than signup, beta-only feature gates, and a graduation flow that converts testers instead of stranding them.

What's inside

When to use it

Pre-launch through the first 90 days.

Build these first

Auth & Onboarding

Straight from the file

When an admin posts a reply: 1. Trigger writes the row (RLS allows admin insert). 2. Edge function or DB trigger fires /api/beta-notes/notify which: - Inserts an in-app notification row (user sees a badge on /dashboard/beta-notes). - Enqueues a transactional email via the lifecycle email infra (trigger_event = 'beta_reply'). 3. The user's beta panel shows the threaded reply inline under the originating note.

Table of contents

  1. 0. Use this spec
  2. 1. Architecture
  3. 2. Schema (Supabase)
  4. 3. RLS — mirror the same shape across all three tables
  5. 4. In-app feedback widget
  6. 5. Founder-side admin dashboard
  7. 6. Reply notifications
  8. 7. Beta-only feature gating
  9. 8. Beta graduation flow
  10. 9. Lifecycle email cohort tagging
  11. 10. NPS prompts
  12. 11. Founding-tier overlay (optional)
  13. 12. Common pitfalls
  14. 13. Kickoff prompt

How to run it

Drop BETA-TESTER-PLAYBOOK.md into your repo, then tell Claude Code: “Read BETA-TESTER-PLAYBOOK.md and implement it in this codebase.” It's written for an agent to execute end to end. Search the file for angle-bracket placeholders and swap in your own project names, domains, and keys before the first run.

↓ Download the playbook

More growth & seo playbooks

← All 28 Claude templates