Reference — generated from the toolkit

Source of truth: toolkit/templates/beta-agreement.md. Edit it there; this page is regenerated on build.

Beta agreement — {client} × {product}

• Client: … Product: … Beta window: {start} – {review date}
• Client sponsor: … Our owner (Commercial): …

What the client gets

Early access to {product}, a direct feedback channel into the build squad, and influence over the roadmap during the beta.

Expectations of the client

• Participation in {N} task-based feedback sessions and a CSAT/NPS pulse.
• Nominated users who will genuinely use the product.
• Timely feedback via the agreed channel (fed into the signal register).

Expectations of us

• Release cadence and support arrangements during beta (rapid-fix SLAs apply from {severity level}).
• Transparency: how the product is built (client transparency statement).

Data handling

What client data (if any) enters the beta, its classification, residency and retention; no client data is used for model training (AI usage policy).

Exit & graduation

• Beta exit criteria: CSAT/NPS thresholds {TBD}, task-completion evidence, zero open S1/S2.
• Graduation checklist: exit criteria met → GTM Readiness gate → GA terms supersede this agreement.
• Either party may end the beta with {notice period}; data handled per the data-handling section on exit.