turn these notes into a launch plan for the mobile beta
six weeks, 200 customers, no broad announcement yet
The beta can launch in six weeks to 200 existing customers if scope freezes this Friday and week four is reserved for reliability rather than feature work.1
Ship the core capture, sync, and review loop; defer team sharing and custom exports.
Admit customers in three cohorts so reliability failures remain diagnosable.
Treat week-five retention and crash-free sessions as the launch decision, not the calendar.
Scope
In beta
Deferred
Reason
Capture and offline queue
Team sharing
Not required to test individual value
Cross-device sync
Custom exports
Adds format and support surface
Review and edit
Public templates
Discovery can follow workflow validation
Account recovery
Organization administration
Cohort is existing individual users
Milestones
Week
Outcome
Owner
Exit gate
1
Scope and analytics frozen
Product
Events and acceptance criteria reviewed
2
Core workflow feature-complete
Mobile
Happy path passes on supported devices
3
Internal dogfood with 20 users
Product + Support
No unresolved data-loss defect
4
Reliability and recovery hardening
Mobile + Platform
99.5% crash-free sessions
5
Cohort one: 50 customers
Growth + Support
At least 35 complete the core loop
6
Cohorts two and three: 150 customers
Growth
Launch gates remain green
Launch gates
Gate
Go
Hold
Source
Crash-free sessions
at least 99.5%
below 99.0%
mobile telemetry
Sync success
at least 99.7%
any confirmed data loss
sync audit
Week-one core-loop retention
at least 45%
below 35%
product events
Support load
below 0.3 tickets per user
above 0.5
support tags
Values between go and hold require an explicit product and engineering decision; they do not silently pass.2
Cohort design
Start with 50 active desktop customers who already use the core workflow weekly. Add 75 customers after 72 stable hours, then the final 75 after another 72 hours. Keep platform, device, and account-age mix visible so one healthy segment does not hide another.3
Risks
Risk
Early signal
Mitigation
Owner
Silent sync loss
server and device counts diverge
reconciliation job and recovery queue
Platform
Notification fatigue
opt-out exceeds 15%
default to digest, not per-event alerts
Product
Support overload
ticket rate exceeds 0.3 per user
pause next cohort and publish known issues
Support
Scope reopens
new beta blocker after Friday
require launch-lead approval and a displaced item
Product
First-day runbook
Confirm telemetry, support routing, rollback owner, and cohort membership before invites send.
Release to 10 internal accounts, then 10 customers, before the remainder of cohort one.
Review crash, sync, and support dashboards at 30 minutes, 2 hours, and end of day.
Pause invitations immediately for confirmed data loss or account lockout.