# Plan a beta or early-access program for a new feature

A beta plan covering who to invite, what to learn, how to collect feedback, and the criteria for general release.

- Topic: Product & UX Design
- Framework: Few-Shot
- Level: Standard
- Tags: Coding, Plan, Code, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/plan-a-beta-or-early-access-program-for-a-new-feature

## Prompt

```text
Plan a beta program for a new feature.

**Feature:** [DESCRIPTION AND CURRENT MATURITY]
**What we need to learn:** [e.g. does it solve the problem, does it scale, will people pay]
**Ideal beta users:** [SEGMENTS, USE CASES]
**Candidate pool:** [CUSTOMER LIST, WAITLIST, COMMUNITY]
**Duration and capacity:** [WEEKS, HOW MANY USERS WE CAN SUPPORT]
**Known limitations:** [WHAT IS NOT DONE YET]

Include:
1. Learning goals: 3-5 specific questions the beta must answer, each linked to a measure.
2. Participant selection: criteria, mix of segments, and red flags (e.g. users who will only report bugs, accounts that cannot tolerate instability). Suggested number of participants.
3. Invitation message and a short expectations note: what is unfinished, how to give feedback, support level, whether data carries over, and whether it will be paid later.
4. Feedback system: in-product prompt, survey at key moments, interview schedule, bug-report channel, usage events to watch.
5. Weekly cadence for reviewing feedback and deciding fixes.
6. Exit criteria for general availability: quality bar, adoption or satisfaction thresholds, open bugs allowed.
7. How to close the beta: thank-you, what happens to their access and data.

Keep the plan to a page. Have legal review any beta terms or data-use language.
```

## What to fill in

- DESCRIPTION AND CURRENT MATURITY
- SEGMENTS, USE CASES
- CUSTOMER LIST, WAITLIST, COMMUNITY
- WEEKS, HOW MANY USERS WE CAN SUPPORT
- WHAT IS NOT DONE YET

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.