Status summary
Overall
Usability, onboarding, and support readiness look healthy. Security evidence and CRM reliability remain the gating items.
Distribution
Enablement
Sales enablement deck, launch email sequence, and admin setup guide are approved and translated for UK and US teams.
Reliability
Platform
Token refresh failures for stale CRM sessions still create blank pre-meeting cards for 0.6% of pilot sessions.
Checklist by owner
Operational readiness
Filter by owner when one team needs a tighter pass over their launch items.
Launch assets
- Pilot success story approved
- Admin rollout guide finalized
- Finalize in-product upgrade copy
Release engineering
- Edge build validated
- Token refresh fix in soak test
- Crash alerts routed to on-call
Security sign-off
- Browser extension permissions memo pending
- Pen test retest completed
- SOC 2 evidence appendix pending
Field readiness
- Sales manager FAQ published
- CS escalation macros updated
- Webinar dry run passed
Timeline
Final 10-day path
Jun 1
Security evidence pack due
Jun 3
Chrome Web Store submission
Jun 6
Go-to-market freeze and support training
Jun 10
General availability if criteria hold
CRM token refresh reliability
Blank summary cards still appear when the extension hits expired CRM tokens during browser wake-from-sleep flows.
Owner: Extension platform
Due: Jun 4
SOC 2 appendix for extension permissions
Enterprise security reviewers asked for explicit mapping between browser permissions and data handling controls.
Owner: Security program
Due: Jun 2
Summary quality on noisy calls
Calls with more than three speakers still show lower action-item extraction quality than clean one-on-one calls.
Owner: Applied AI
Due: Monitor through launch week
Launch criteria
Must-pass gates
| Gate | Threshold | Status |
|---|---|---|
| Crash-free sessions | Greater than or equal to 99.5% | Passing |
| Summary usefulness rating | Greater than or equal to 80% | Passing |
| Token refresh reliability | Greater than or equal to 99.5% | At risk |
| Security evidence complete | All enterprise review docs approved | At risk |
| Support readiness | Macros + runbook + training complete | Passing |
Decision note
What would trigger no-go
If token refresh reliability stays below threshold after Jun 4, or if the security appendix is still incomplete by Jun 5, postpone launch by one release train and keep the pilot cohort on the current build.