Получайте работу, а не только ответ.

Show 6 unchanged lines

1. 77 - Prove that new users complete the core workflow without support.
2. 88
3. 99 ## Week 1: Lock Core & Stress Test
4. 10-- **Focus:** Freeze features, push release candidate, run load and failure drills.
5. 11-- **Owners:** Engineering & Product
6. 12-- **One metric:** Critical bug count (target: 0 by Wednesday)
7. 10+- Freeze features and push the final release candidate by Monday.
8. 11+- Run load and failure drills across production infrastructure.
9. 12+- **Owner:** Engineering & Product | **Metric:** Critical bugs (target: 0 by Wednesday)
10. 1313
11. 1414 ## Week 2: Warm the Funnel
12. 15-- **Focus:** Send launch teasers, onboard early access users, finalize support playbooks.
13. 16-- **Owners:** Growth & Customer Ops
14. 17-- **One metric:** Waitlist-to-beta conversion rate (target: 30%)
15. 15+- Send launch teasers and onboard the early access cohort.
16. 16+- Finalize support playbooks and prepare customer onboarding guides.
17. 17+- **Owner:** Growth & Customer Ops | **Metric:** Waitlist-to-beta conversion (target: 30%)
18. 1818
19. 1919 ## Week 3: Final Polish & Go Live
20. 20-- **Focus:** Dry-run launch day messages, monitor pre-launch traffic, flip the switch on 28 October.
21. 21-- **Owners:** All hands (Founder leads comms, Engineering on standby)
22. 22-- **One metric:** First 48-hour activation rate (target: 40%)
23. 20+- Dry-run launch messages and monitor pre-launch traffic patterns.
24. 21+- **Owner:** All hands (Founder leads comms) | **Metric:** First 48-hour activation rate (target: 40%)
25. 22+- **Rollback trigger:** Revert to the previous stable release if uptime drops below 99% or activation falls under 25% in the first 24 hours.