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

By Moe Ameen, founder of BILT · Published · Updated

The Beta Tester Playbook structures an app's first 90 days. Claude Code adds beta_notes, replies and NPS tables with matching row-level security, an is_beta flag separate from plan, a floating feedback widget with page context on every signed-in page, a founder dashboard to reply and resolve, a BetaGate component for beta-only features, NPS prompts, and a graduation flow with a 30-day notice email.

Key takeaways

  • Feedback lands in your own tables through an in-app widget.
  • Beta status is a flag, separate from plan or tier.
  • BetaGate hides beta-only features from everyone else.
  • Graduation sends a 30-day notice before testers move to paid.

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 does the Beta Tester Playbook build?

It builds the feedback loop between testers and founder: widget, user-facing feedback board, /admin/beta dashboard, reply notifications and an NPS rollup.

Testers are also tagged into lifecycle email cohorts.

When should you run a structured beta?

Run it from pre-launch through the first 90 days, while you still talk to every user.

Decide early whether bring-your-own API keys are tied to beta or sold separately; the file asks for that decision.

What do you need first?

You need Auth & Onboarding (a profiles table with a role column), a Supabase Storage bucket for screenshots and Email Infrastructure trigger hooks.

A founding-tier overlay is optional.

What's inside

What does the playbook give you?

When to use it

Pre-launch through the first 90 days.

Build these first

Auth & Onboarding

Straight from the file

What does the writing look like?

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

Which sections does the file cover?

  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 do you 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

Who is this for, and who should skip it?

Best for

  • Apps in private or public beta
  • Founders who reply to every bug report personally
  • Products planning a founding-member offer at graduation

Not ideal for

  • Apps past beta with established support
  • Teams already using a hosted feedback tool
  • Products without user accounts
  • Builders who won't adapt paths: the file points to a reference app you won't have

What else do people ask?

What does the Beta Tester Playbook ask for up front?

The Beta Tester Playbook asks whether you have a profiles table with a role column, the Storage bucket name for screenshots, whether email infrastructure is wired, and whether you run a founding tier with a price and cutoff date. If profiles or email aren't in place, it says to run the Auth & Onboarding or Email Infrastructure playbook first.

Does it assume Supabase?

Yes. The Beta Tester Playbook writes its schema as Supabase SQL, gates rows with RLS helpers using auth.uid() and stores screenshots in a Supabase Storage bucket. The UI is React components and app-router routes, so another stack means translating those parts yourself.

Can I skip the founding-tier part?

Yes, the Beta Tester Playbook marks the founding-tier overlay optional. If you use it, founding membership stays separate from is_beta, and bring-your-own API keys are gated on profiles.is_founding rather than is_beta.

What is in the Beta Tester Playbook download?

The Beta Tester Playbook is a markdown file of about 2,100 words. It has SQL for the profiles.is_beta flag and the beta_notes, beta_note_replies and beta_nps_scores tables with RLS, the BetaGate component, a table of six lifecycle email triggers and eight common pitfalls.

Should graduating a tester turn is_beta off?

No. The Beta Tester Playbook removes the gate at the feature level and keeps is_beta forever, because the flag drives cohort analytics, founding-member perks and future invitations. Flipping it off throws that history away.

How do we know this?

This page is based on the playbook file itself, BETA-TESTER-PLAYBOOK.md, which Moe Ameen wrote from the Kompozy codebase (called BKE in the file). We read the file on November 4, 2026; the facts here come from it, not from independent testing in other codebases.

More growth & seo playbooks

← All 28 Claude templates