# Beta Testing

> When to activate: beta testing, beta program, beta users, closed beta, open beta, beta feedback, early access, beta-to-GA, launch criteria, beta metrics

- Skill: `mattakushi432/beta-testing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mattakushi432/beta-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mattakushi432/beta-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Mattakushi432 (https://skillmd.com/u/mattakushi432)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mattakushi432/beta-testing

---


# Beta Testing

## Beta Program Design

### Program Objectives (define before recruiting)
- [ ] Validate product-market fit assumptions
- [ ] Identify critical bugs before GA launch
- [ ] Gather qualitative feedback on UX and value
- [ ] Build an advocate cohort for launch
- [ ] Stress-test infrastructure at realistic load

### Closed vs Open Beta
| | Closed Beta | Open Beta |
|-|-------------|-----------|
| Access | Invite-only | Anyone can join |
| Size | 20–200 users | 200–10,000+ |
| Feedback quality | High (engaged participants) | Lower (noisy) |
| Bug discovery | Deep issues | Volume/scale issues |
| NDA required | Often | Rarely |
| Best for | Complex products, enterprise | Consumer apps, simple tools |

### Beta Timeline Template
```
Week 1-2:   Recruit and onboard participants
Week 2-6:   Active beta period (collect feedback)
Week 5:     Mid-beta survey + triage session
Week 6-7:   Final survey + exit interviews
Week 7-8:   Bug fixes + GA preparation
Week 8:     Beta-to-GA graduation
```

## Participant Recruitment

### Ideal Beta Participant Profile
- Uses similar tools today (has context to compare)
- Represents target ICP (not edge case users)
- Willing to provide structured feedback (not just passively use)
- Has the actual use case — not just curious about the product
- Time-available: can commit 1–2 hours/week for duration

### Recruitment Channels
1. **Waitlist**: Best source — already interested, shown initiative
2. **Existing customers**: Use for feedback on new features to their workflow
3. **Partner networks**: Good for B2B / vertical-specific beta
4. **Community**: Discord, Slack, Reddit — self-selected enthusiasts
5. **Sales pipeline**: Prospects who are evaluating — beta can accelerate deal

### Screening Questions
```
1. What tool do you currently use for [use case]?
2. How often do you encounter [problem]? (Daily / Weekly / Monthly / Rarely)
3. What would you do differently if [problem] was solved?
4. How much time can you commit per week to beta feedback?
5. Are you comfortable providing candid feedback including negatives?
```

Accept participants scoring: use case match + time commitment + candid feedback intent.

## Beta Agreement Template

```
Beta Participation Agreement

By joining [Product] Beta, you agree to:

1. Confidentiality: Keep beta features and pricing confidential 
   until GA launch on or after [date].

2. Feedback: Provide structured feedback via [method] at least 
   [X] times per [week/month].

3. Bug reporting: Report issues via [channel] within [X] business days 
   of discovery.

4. No redistribution: Do not share access credentials with others.

5. Data: You understand beta data may be reset before GA launch.

In exchange, [Company] will:
- Provide [early access / discount / named acknowledgment / other]
- Prioritize your feedback in product decisions
- Give you advance notice of GA launch
```

## Feedback Collection Methods

### In-App Feedback (continuous)
- Thumbs up/down on key flows with comment prompt
- NPS survey at natural pause point (after first key action)
- Bug report button accessible from every screen
- Session recording consent for UX analysis

### Structured Survey (mid-beta, week 3–4)
```
1. How satisfied are you with [product] overall? (1–10)
2. What is working well? (open text)
3. What is most frustrating? (open text)
4. How does this compare to your current solution? 
   (Much worse / Worse / Same / Better / Much better)
5. How likely are you to use this after GA launch? (1–10)
6. What would make you more likely to use it? (open text)
```

### Exit Interview (final week, 30 min)
- Walk through their actual workflow
- "Show me how you use it" (observation beats self-report)
- "What almost made you stop using the beta?"
- "Who else on your team would benefit from this?"
- "Would you pay for this? What would you pay?"

## Bug Triage Workflow

### Severity Classification
| Severity | Definition | Response SLA |
|----------|-----------|-------------|
| P0 Critical | Data loss, complete blocker | Fix within 24h |
| P1 High | Major feature broken | Fix within 3 days |
| P2 Medium | Degraded experience, workaround exists | Fix before GA |
| P3 Low | Polish issue, minor annoyance | Post-GA backlog |

### Bug Report Template
```
**Summary**: [One line description]
**Severity**: P0 / P1 / P2 / P3
**Steps to reproduce**:
1. 
2. 
3. 
**Expected**: [What should happen]
**Actual**: [What happened]
**Environment**: [Browser, OS, screen size, plan]
**Frequency**: Always / Sometimes / Once
**Attachment**: [Screenshot / video if applicable]
```

## Beta-to-GA Graduation Criteria

### Required Before GA Launch
- [ ] P0 and P1 bugs resolved (zero open P0s)
- [ ] Beta NPS ≥ 30 (or established baseline)
- [ ] At least 3 "would definitely use / recommend" quotes for marketing
- [ ] Core funnel completion rate ≥ target threshold
- [ ] Infrastructure load test passed at 10× beta traffic
- [ ] Documentation and help content complete
- [ ] Pricing finalized and payment flow tested
- [ ] CS team trained on common beta issues

### Optional (nice to have)
- [ ] At least 2 case studies / testimonials secured
- [ ] PR / launch partners lined up
- [ ] Waitlist of ≥ X users for launch momentum

## Beta Community Management

### Communication Cadence
| Channel | Frequency | Content |
|---------|-----------|---------|
| Email update | Bi-weekly | What shipped, what's coming, ask for specific feedback |
| Slack/Discord | Daily monitoring | Answer questions, acknowledge bugs |
| Group call | Monthly | Demo new features, Q&A, recognition |
| 1:1 interviews | 2–3 per week | Deep feedback from power users |

### Recognition Practices
- Name participants in release notes ("Thanks to our beta community")
- Send swag or gift cards at program end
- Offer lifetime discount or extended trial as graduation gift
- Build "founding member" badge or designation into product

## Beta Program Metrics

| Metric | Definition | Target |
|--------|-----------|--------|
| Activation rate | % who log in after first week | > 70% |
| Weekly engagement | % active in any given week | > 50% |
| Feedback submission rate | % who submit structured feedback | > 60% |
| Bug reports per active user | Volume of issue discovery | Track trend |
| Net Promoter Score | NPS from mid-beta survey | ≥ 30 |
| Intent to use post-GA | % saying "definitely will use" | > 50% |