Build and Manage Beta Programs

Beta Program Builder Agent structures and runs a full beta testing program: a three-phase framework (closed alpha, limited beta, open beta) with participant counts and durations, a recruitment strategy and ideal-participant profile, a multi-channel feedback collection system with structured templates, a communication cadence and community-platform setup, success-metric tracking, and a go/no-go launch-readiness framework.

Use it when planning or running a beta program from scratch - sizing and sequencing alpha and beta phases, defining a recruitment profile and channels, standing up an in-app feedback widget with bug and feature-feedback templates, setting a weekly, bi-weekly, or monthly communication cadence, or deciding whether a product is ready to launch against explicit go/no-go criteria. It is not a bug-tracking or product-analytics tool itself - it defines the program structure, templates, and metrics, not the underlying systems that store bugs or usage data.

Input is the product stage and target participant scale. Output is program design artifacts: three phase definitions in YAML - closed alpha at 10-25 participants over 2-4 weeks requiring an NDA and daily usage; limited beta at 50-200 participants over 4-8 weeks requiring structured feedback and weekly surveys; open beta at 500-5000+ participants over 4-12 weeks focused on scale and market validation; an ideal-participant profile and a six-channel recruitment list covering existing customers, waitlists, community forums, partner networks, events, and referrals; an in-app feedback widget config with trigger conditions and required/optional fields, plus bug-report and feature-feedback markdown templates; a weekly, bi-weekly, and monthly communication schedule and a six-channel community platform layout with moderation response-time rules; a Python beta_metrics dictionary tracking participation, quality, and engagement KPIs; a final program-evaluation and product-readiness survey; and a YAML go/no-go framework requiring zero critical bugs, fewer than three high-severity bugs, satisfaction above 4.0/5.0, and over 80% core-feature adoption, with no-go triggers for data-loss bugs, security vulnerabilities, or a broken core workflow.

Feedback collection is designed around an in-app widget (JavaScript config) and a community platform with dedicated channels for announcements, discussion, bug reports, feature requests, and support:

go_criteria:
  critical_bugs: 0
  high_severity_bugs: <3
  user_satisfaction: >4.0/5.0
  core_feature_adoption: >80%
  performance_benchmarks: met
  documentation_complete: true
  support_processes_tested: true

Product managers and QA leads running a pre-launch beta who need the structure end to end - phase sizing, participant recruitment, feedback templates, communication cadence, KPI tracking, and an explicit go/no-go decision - rather than assembling each piece separately.