Run a beta customer recruitment and success plan

Description

You need 10-20 real customers on a beta in 4 weeks and your CS team is fully booked. This builds the recruitment spec, screening criteria, success metrics, and communication cadence so beta customers feel supported and give you the signal you need without consuming all your bandwidth.

You are a beta program manager designing the beta for {{feature_name}}. Target: {{customer_count}} beta customers, duration {{duration}}.

## Step 1 — Ideal beta customer profile
Criteria (must have 4 of 5):
- Active user (logged in past 30 days)
- Pain point match (uses workaround feature Y or has stated Z need)
- Engagement willingness (responded to past NPS, feature requests)
- Feedback quality track record (wrote past Intercom/Zendesk feedback)
- Not a top-10 ARR account (avoid blast radius)

## Step 2 — Recruitment
- In-app banner for matching segment
- Personalized email to 30 candidates
- Screening questionnaire (5 Q, takes 3 min)
- Opt-in confirmation with beta agreement

## Step 3 — Success metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| Activation | 80% use feature within 48h of access | Product analytics |
| Weekly engagement | 70% return in week 2 | Product analytics |
| NPS on feature | ≥8/10 | In-app survey at day 14 |
| Qualitative feedback | 60% respond to at least 2 of 3 weekly check-ins | Survey/1:1 |
| Bug signal | Top 3 bugs surfaced and triaged by week 2 | Support |

## Step 4 — Communication cadence
- Kickoff email with what to expect
- Weekly check-in email with 1 question
- Slack channel for real-time feedback
- 30-min 1:1 at day 14 with 5-10 willing customers

## Step 5 — Exit plan
- Graduate to GA: pricing continuity commitment, thank-you credit
- Beta rollback: clear communication, data preservation

## Output
1. ICP criteria list
2. Recruitment plan with candidate counts
3. Success metric dashboard
4. Exit/graduate plan

Customize This Prompt