Before public launch — a structured beta program surfaces critical issues without destroying your reputation.
You are a senior {{role}} brought in to help {{target_user}} complete a Design a Beta Testing Program. # Context Original working context: - Step 1: My product: {{describe}}. Launch timeline: {{weeks_away}}. What I most need to learn from beta: {{describe}}. How many beta users I want: {{number}}. - Step 2: Define the ideal beta user profile: Who should beta test — early adopters, existing customers, target ICP, or a mix? What makes someone a 'good' beta tester vs a 'bad' one? - Step 3: Design the beta onboarding: How beta users are recruited (email, LinkedIn, community, existing waitlist), what they receive (access, onboarding doc, expectations), and how to set up for success in the first session. - Step 4: Build the feedback collection system: Daily/weekly feedback format, bug reporting template, NPS trigger, and what questions to ask at the end of beta. - Step 5: Design the beta-to-launch decision criteria: What feedback signals tell me I'm ready to launch? What signals tell me I need another round of iteration? # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before public launch — a structured beta program surfaces critical issues without destroying your reputation.
The difference between beta testing and testing your friends is structure and selection. You want beta users who are in your target market, motivated to give honest feedback, and willing to use the product under real conditions — not people who'll say 'it's great!' to be kind.
Validate this business idea rigorously. Assess market size, competition, feasibility, and risk. Give an honest recommendation — do not flatter.
Conduct a structured competitor analysis. Map each competitor's strengths, weaknesses, positioning, pricing, and target customer. Identify the market gaps your business can own.
Write the complete narrative for a 10-slide pitch deck. For each slide, write the title, the key message (one sentence), and the talking points (3-5 bullets).
Recommend a pricing strategy with full rationale. Provide 3 pricing options (low/mid/premium tier) and explain what each achieves. Recommend one as optimal for the stated goal.