# Launch Readiness Checklist — Quick Reference **Sage, CSO · February 23, 2026** **Use this before every major decision point through March 5** --- ## Pre-Launch Checklist (by March 4, before Meta approval) ### Blocker Items (Cannot launch without these) - [ ] **Meta App Review approved** — Awaiting March 5 estimated approval - [ ] **Kristi's content approval** — 9 items (7 emails, lead magnet, lead page) signed off - [ ] **support@getstylify.com created** — Email forwarded to Jason's inbox - [ ] **ToS v4 sections integrated** — Style Data Ownership, Auto-Publishing, Founding Member Pricing in TermsPage.jsx - [ ] **Landing page typo fixed** — $$49/mo → $49/mo (if not already done) - [ ] **Brand Vibe update deployed** — 4 new vibes, backward-compatible, tested with existing user data ### Important Items (Should do before launch if possible) - [ ] **Instagram week 1-2 content approved** — 14 posts queued, Kristi approved, ready to publish - [ ] **Support response templates drafted** — 20 scenarios, tone-matched to brand voice - [ ] **CS tracker spreadsheet created** — Ready to log first support tickets - [ ] **API risk audit completed** — No surprise deprecations from Instagram API before Meta approval - [ ] **Supabase Pro upgrade completed** (or scheduled for Day 1) — Eliminates free-tier auto-pause risk - [ ] **Founding Member governance rules documented** — Added to ToS or Help Center FAQ ### Launch Day Checklist (March 5-6, assuming Meta approval) **Day 0 (March 5 — Approval Day)** - [ ] Verify Meta approval email received - [ ] Stitch: Deploy Brand Vibe + ToS v4 updates - [ ] Stitch: Run full pre-launch QA (see next section) - [ ] Charlotte: Activate support@getstylify.com - [ ] Jason: Fix any remaining landing page issues **Day 1 (March 6 — Go Live)** - [ ] Deploy to production (Vercel + Railway) - [ ] Charlotte: Send Email 1 of nurture sequence (or launch PPC) - [ ] Pixel: Begin daily Instagram posts (using pre-approved week 1-2 content) - [ ] All: Monitor for errors (Sentry, support inbox, user feedback) - [ ] Jason: Respond to support emails within 4 hours **Days 2-7 (Week 1)** - [ ] Monitor daily: Signups, trial starts, first-post completions - [ ] Charlotte: Track support tickets (>5 per day = escalate to Jason) - [ ] Stitch: Monitor Sentry for errors, fix same-day bugs - [ ] Pixel: Continue daily Instagram posts + comment engagement **Days 8-14 (Week 2)** - [ ] Launch Founding Member acquisition campaign - [ ] Jason: Personal outreach to first 10-20 users (direct ask for FM participation) - [ ] Charlotte: Weekly CS standup report (Friday summary of tickets + patterns) - [ ] Target: 20-50 Founding Members signed up by day 14 --- ## Pre-Launch QA Checklist (Stitch) Run this before Day 1 launch: ### Core Workflow - [ ] Create account → Onboarding quiz → Voice assignment → First post generation → Copy/post to Instagram - [ ] Verify Brand Vibe update: Old user values still load correctly (backward compatibility) - [ ] Verify ToS v4: New terms display in onboarding + settings - [ ] Photo upload → Caption generation → Approval screen → Instagram preview - [ ] Manual copy/paste workflow (for Solo users without auto-publishing) ### Pro Features (assuming Meta approval) - [ ] Instagram connect → Permission grant → Auto-publishing to queue - [ ] Scheduled post → Posted at correct time - [ ] Auto-publish cancellation (user can still edit/delete) ### Mobile & Cross-Browser - [ ] Onboarding works on iOS Safari + Android Chrome (primary devices for stylists) - [ ] Caption approval screen readable on 375px viewport (iPhone SE) - [ ] Instagram preview accurate at mobile sizes ### Database - [ ] Supabase connection stable (no timeouts) - [ ] Keep-alive is running (4-hour interval) - [ ] Posts table has no data loss from Brand Vibe update ### Monitoring - [ ] Sentry is receiving errors - [ ] UptimeRobot is pinging backend - [ ] Vercel deployment successful --- ## Critical Success Metrics (Track from Day 1) ### Day 1-7 (Launch Week) - **Signups:** Target 50-100 trial starts - **Activation:** 40%+ reach first-post generation screen - **Completion:** 20%+ complete their first post (reached approval screen) - **Support:** <5 emails per day (if higher, something is wrong with onboarding) ### Day 8-14 (FM Push Week) - **FM Signups:** Target 20-50 by day 14 (out of 100 total spots) - **Email Engagement:** 40%+ open rate on Email 1-3 - **Trial-to-Paid (if any):** Even 1 conversion is a win at this stage - **Daily Active Users:** 50%+ of Day 1 signups still active (check at Day 7 + Day 14) ### Day 21 (First Report) - **Churn Rate:** <20% of early users churned (lost) - **Voice Satisfaction:** 70%+ say assigned voice "sounds like me" (in-app survey) - **Pro Features Adoption:** If Meta approved, 40%+ of Pro users scheduled at least 1 post - **Support Ticket Patterns:** Identify top 3 support questions for FAQ updates --- ## Decision Gates (Ask Jason if conditions are met) | Gate | Trigger Condition | Action | |------|-------------------|--------| | **Meta Approval Uncertainty** | If Meta hasn't approved by March 3 | Switch to Solo-only launch; start FM resubmission | | **Low FM Signup Rate** | <10 FM signups by day 10 | Double down on personal outreach (Jason calling users) | | **High Support Volume** | 15+ support tickets per day | Escalate to Phase 2 CS planning (consider dedicated agent) | | **Unexpected Churn** | >30% churn at day 7 | Debug onboarding; something is wrong with product or positioning | | **Voice Satisfaction Low** | <60% "sounds like me" feedback | Investigate archetype calibration; may need quiz update | --- ## Contingency: If Meta Approves Late (March 6-10) **Impact:** Slides entire launch by 1-3 days. Acceptable but creates pressure. **Mitigation:** - Use March 5 as "soft launch" — deploy Solo-tier, send Email 1, begin FM recruitment for "Pro waiting list" - Message: "Pro (auto-publishing) coming within 48 hours. Founding Members will get early access." - When Meta approves, deploy Pro features mid-stream (users already onboarded, conversion path warm) --- ## Contingency: If Meta Rejects Again **Impact:** CRITICAL — Entire launch delayed. Can't emphasize Pro tier. **Mitigation:** - Activate "Solo-only launch" narrative immediately (Day 1-2) - Message: "Stylify is live. Pro auto-publishing launching in Week 2 pending platform approval. Founding Members lock in Pro pricing now ($49/mo forever)." - Use Week 1 to gather user feedback on core product (caption generation, voice, onboarding) - Prepare v5 screencast (faster turnaround if new issues found) - Resubmit Meta within 7 days --- ## The 14-Day Rule **Rule:** If anything seems off (churn, support backlog, conversion drop), debug it within 24 hours. Don't wait for next session. Early-stage data is more valuable than polish. Iterate quickly based on real user behavior, not assumptions. --- ## Key Contacts | Role | Name | Contact | Responsibility | |------|------|---------|-----------------| | **Founder** | Jason | jason@ | Final decisions, personal user outreach, voice recording | | **COO** | Charlotte | charlotte@ | Go/no-go decision (content approval), support management, CS handoff | | **CTO** | Stitch | stitch@ | Deployment, monitoring, bug fixes, API risk | | **Social Media** | Pixel | pixel@ | Instagram posting, engagement, content calendar | | **Content Approval** | Kristi | kristi@ | Email, landing page, content sign-off | **Escalation path:** Support → Charlotte → Jason. Bugs → Stitch → Jason. Strategy → Sage (this audit) → Jason. --- ## Success = Three Things 1. **Meta approves by March 5** (not in your control, but plan for it) 2. **Founding Members reach 50+ by day 14** (social proof + runway) 3. **Trial completion rate >70%** (product works, onboarding is smooth) If all three happen, you've launched successfully. Everything after is iteration. --- **Print this. Reference it daily through Day 14. Update with actual numbers as you go.** *Sage, Chief Strategy Officer · Stylify*