Executive Summary
Readiness: 7.2/10 — Product is fundamentally sound and ready to launch, but 8 priority issues must be resolved before the first founding members onboard.
Blockers (3): Brand Vibe onboarding update, Supabase database upgrade, ToS integration. All three are blocking but all three have implementation packages or clear paths. None require architectural rework.
Important (7): Landing page typo, tooltip QA fixes, mobile inbox re-sync convention, API risk audit, dashboard reskin planning, retention automation, and referral program go/no-go. Important to launch quality but most can ship post-launch with minimal user impact.
First-Run Experience: 7-step onboarding is polished, 2-minute approval loop works end-to-end, and all core features are functional. No show-stoppers from a user perspective.
🔴 Blockers — Must Fix Before Day 1
These will cause founding members to churn or prevent product use. Fix these before Meta approval lands.
🔴 BLOCKER
Brand Vibe Onboarding — 4 Old Options Need Replacement
The 14-day free trial starts the moment a new user signs up, so onboarding timing is critical. The onboarding flow's Brand Vibe step has 4 outdated options (Luxury, Creative, Warm, Expert) that don't match current positioning and voice archetypes. New options (Polished, Bold, Laid-Back, Fun) are documented with backward-compatible aliases and voice calibration vectors.
Impact: New users complete onboarding with misaligned voice archetypes. They then approve posts that don't sound like them, creating immediate churn risk on Day 1 of the trial.
Status: Implementation package ready in inbox (`2026-02-23_brand-vibe-update-stitch.md`).
Action: Stitch — implement brand vibe replacement package. Estimated: 45 minutes. Do this before any founding members onboard.
🔴 BLOCKER
Supabase Database — Free Tier Auto-Pause Risk
Supabase free tier auto-pauses projects after 7 days of inactivity. The project `etsacubwnujenvbpekwm` received an inactivity warning and is currently kept alive by a
setInterval health check running every 4 hours. This is a bandaid, not a solution.
Impact: Once founding members start posting, the keep-alive becomes fragile. If the health check fails (network hiccup, deployment interruption, anything), the database auto-pauses and the app goes down. Supabase Pro upgrade is required before accepting any paying users.
Status: Upgrade path exists; cost is $25/month. Planned for ~March 1, but should happen immediately after Meta approval.
Action: Jason — upgrade Supabase to Pro tier the moment Meta approval lands. Remove the
setInterval keep-alive from server.js once upgraded. Estimated cost: $25/mo ongoing.
🔴 BLOCKER
ToS v4 Sections Not Integrated Into TermsPage.jsx
Three new ToS sections have been drafted, panel-hardened, and approved (Section 15: Style Data & Style Profile Ownership; Section 16: Automated Content Publishing; Section 17: Founding Member Program). They exist as markdown in
business/strategy/Stylify_Terms_of_Service_Update_Draft.md but are not yet integrated into the frontend TermsPage.jsx component.
Impact: Users see outdated ToS on the Terms page. Founding members have no written agreement covering auto-publishing or the locked-in pricing promise. Legally vulnerable.
Status: Implementation is straightforward HTML integration; estimated 30-45 minutes.
Action: Stitch — integrate 3 new ToS sections from draft markdown into
frontend/src/components/TermsPage.jsx. Verify "Style Data" terminology is consistent across all legal copy (not "Voice Data"). Do this immediately after brand vibe update.
🟡 Important — Should Fix Before Day 1, Low-Cost Fixes
Product works without these, but the first-run experience is degraded. All are low-cost fixes (15-45 min each).
🟡 IMPORTANT
Landing Page Typo — Double Dollar Sign
The landing page displays "$$49/mo" instead of "$49/mo" in
LandingPage.jsx. This is the highest-traffic page and the first thing prospective users see.
Impact: Credibility hit on first impression. Small but visible error signals lack of polish.
Action: Stitch — find and fix the double `$` in
frontend/src/components/LandingPage.jsx. Estimated: 2 minutes.
🟡 IMPORTANT
InfoTooltip QA Issues — 3 Critical Bugs Identified
Full QA testing on all 17 InfoTooltips identified 3 blocking issues: (1) Strategy page loads Content Calendar instead of strategy sections, making tooltips 1-7 untestable (state routing gap); (2) Tooltip #8 (Instagram Connect) popup overflows the right viewport edge at 375px mobile; (3) Tooltips 11-16 not rendered in mobile accordion Settings layout.
Impact: New mobile users on iPhone 6-8 width (375px) can't see Instagram Connect help. Settings mobile users can't access 6 of 17 tooltips. Strategy page has no in-context help. Test account:
charlotte-qa@test.com / Testing123!. QA report in shared-docs/inbox/archive/2026-02-21_infotooltip-qa-results.md.
Action: Stitch — fix 3 issues from QA report (linked in session context). Estimated: 2 hours total. Priority order: mobile viewport overflow, Settings accordion rendering, strategy page routing.
🟡 IMPORTANT
API Risk Audit Not Yet Done
Before accepting real users, all API integrations (Instagram Graph API, Claude Haiku, GPT-4o-mini, Resend, Kit, Stripe) should be evaluated for failure modes, rate limits, deprecation risk, and fallback strategies. A comprehensive audit task exists in the inbox but has not been completed.
Impact: Unknown unknowns. If an API changes or depreciates mid-launch, we discover it when founding members complain, not beforehand.
Action: Stitch — run API risk audit before Meta approval (inbox task from 02-22). Estimated: 2-3 hours. Document findings and fallback strategies.
🟡 IMPORTANT
Retention Automation Not Built
4-tier inactivity email sequence (Days 7/14/21/28), monthly recap emails, and Solo→Pro upsell at 20+ posts have been designed with Kit email sequences and tags, but the application-side implementation is not done. Inactivity detection and email triggers exist at the backend (Kit lifecycle tags), but the full email sequence is not yet live.
Impact: Founding members who go silent after first week will not receive any re-engagement outreach. Churn will accumulate silently.
Status: Task brief in inbox. This is a "Day 1 post-launch" priority, not pre-launch.
Action: Stitch — build retention automation in Week 1 post-launch. Not blocking, but should be live by Day 8 (when first inactivity windows close). Estimated: 4-6 hours.
🟡 IMPORTANT
Referral Program — Jason's Go/No-Go Decision Needed
Referral program design is complete (3-for-1 incentive, qualified referrals, auto-rewards via Stripe coupon). Implementation brief is ready, but the decision to build and launch with founding members (vs. defer to Month 1 post-launch) is pending. Jason's decision on 6 questions in the referral program brief.
Impact: If build decision is yes, Stitch needs 1-2 days to implement (DB + API + UI + Stripe integration). If defer, the feature ships Month 1 instead. Either is viable; the decision just needs to be made to unblock Stitch's roadmap.
Action: Jason — review referral brief in inbox and make go/no-go decision. If go, Stitch builds during Week 1 post-launch. If no-go, defer to Month 1.
🟡 IMPORTANT
Dashboard Reskin — Plan Exists, Not Started
A visual reskin of the dashboard (colors, layout, typography refinement) has been planned but not implemented. The current dashboard is functionally correct but visually dated compared to the 5-phase homepage redesign that just completed.
Impact: Founding members' primary workspace doesn't match the visual polish of the rest of the app. Small credibility hit, but not a blocker.
Status: Not blocking. Can ship post-launch (Week 2-3) without impact to core workflows.
Action: Stitch — defer dashboard reskin to Week 2-3 post-launch. Core functionality is solid; visual refinement is not critical for Day 1 founding member experience.
🟡 IMPORTANT
Stitch CLAUDE.md Update — Session Process Separation
Charlotte's CLAUDE.md has been updated to reflect separated opening/closing session processes (Charlotte owns ops/conflict checks/marketing audit; Stitch owns git/code impact flags). Stitch's CLAUDE.md has not been updated yet. This is an operational consistency issue, not a product issue, but it affects how sessions are run.
Action: Stitch — update your CLAUDE.md with the new session process separation. Inbox task in
2026-02-23_workflow-principles-stitch.md. Estimated: 15 minutes.
🟢 Post-Launch — Can Wait, Won't Impact Founding Members
These improve the product but don't affect Day 1 founding member experience. Build these in Week 1-2 post-launch or Month 1.
🟢 POST-LAUNCH
Demo Video Pipeline — Build Starts Post-Meta-Approval
Phase 1 (scripts + voice prep) is complete. Phase 2 (Stitch builds the automation pipeline) starts after Meta approval. 3 scripts approved: "2-Minute Proof," "How Stylify Works," "Your Voice, Your Posts." ElevenLabs voice cloning + Playwright + ffmpeg stack defined.
Timeline: Week 1-2 post-launch. Not blocking; demo videos are a lead magnet, not a core product feature.
🟢 POST-LAUNCH
Salon Tier Phase 2-3 — Approval Workflows & Brand Controls
Salon tier Phase 1 (sub-account model, owner dashboard, invite system, billing) is complete. Phase 2 (approval workflows) and Phase 3 (brand controls, leaderboards) are future phases. Not blocking for founding member launch (all founding members are Solo/Pro).
Timeline: Month 2-3 post-launch, after validating Phase 1 with real salon owners.
🟢 POST-LAUNCH
Photo Enhancement (Pro Differentiator) — Not Yet Built
AI photo enhancement toggle is in the Pro tier spec but not yet implemented. Current Pro feature is scheduled auto-publishing + multi-platform publishing. Photo enhancement is on the roadmap.
Timeline: Month 1-2 post-launch (second-highest Pro differentiator after auto-publishing).
🟢 POST-LAUNCH
Multi-Platform Publishing (Facebook/TikTok) — Phased Rollout
Currently Pro auto-publishing is Instagram-only. Facebook and TikTok are planned as sequential additions (Facebook first, because Instagram/Facebook share Meta API infrastructure).
Timeline: Month 1-3 post-launch. Start with Meta (Facebook), then add TikTok.
🟢 POST-LAUNCH
Help Center Search Optimization
Help Center has 40+ questions + 5 user guides + 17 InfoTooltips deployed and functional. Search works. Not a gap, but search ranking and content discoverability could be improved.
Timeline: Month 1+, based on support ticket patterns.
🟢 POST-LAUNCH
Analytics Interpretation (AI-Powered Insights Recommendations)
Decision gate: 50+ users with 30+ published posts each + reliable statistical patterns + support tickets showing demand. Not ready for founding member launch; requires post-launch data collection.
Timeline: Month 3+ post-launch (deferred; gated feature).
🟢 POST-LAUNCH
Trademark ITU Filing
Decision made to defer to pre-launch (actually pre-public-launch, not pre-founding-launch). TESS search clear. Risk low after reframing (SaaS, not beauty). $500 filing cost.
Timeline: 2-4 weeks before public launch (Month 2-3).
1. Core Flow Integrity — End-to-End Analysis
Does the product work end-to-end for a new founding member on Day 1?
Onboarding Flow (7 Steps)
Content Creation → Approval → Publish (2-Minute Loop)
Verdict: Core loop is 100% functional. Brand Vibe fix (blocker #1) is the only onboarding issue.
Post-Launch Metrics & Retention Triggers
Verdict: All tracking is in place. Retention emails require manual Kit setup but the plumbing is there.
2. Infrastructure Readiness
Database (Supabase PostgreSQL)
| Component | Status | Notes |
|---|---|---|
| Schema migrations (017 total) | ✓ Complete | All migrations through 017 (daily_suggestions) are defined and runnable |
| Free tier auto-pause risk | ✗ BLOCKER | Keep-alive workaround in place; Pro upgrade required before production users |
| Backup strategy | ⚠ Partial | Free tier has no daily backups. Supabase Pro ($25/mo) includes daily snapshots. |
| Query performance | ✓ Acceptable | No identified N+1 queries or slow indexes. Frontend pagination on large datasets (calendar, progress page) is client-side. |
Backend (Node.js + Express on Railway)
| Component | Status | Notes |
|---|---|---|
| Deployment | ✓ Live | Railway deploys from git main branch automatically. Backend running on :3000 |
| Rate limiting (100 gens/24hr) | ✓ Implemented | Invisible abuse protection; friendly 429 toast message |
| Error handling | ⚠ Needs audit | API risk audit not yet completed. Some failure modes (Claude API down, Instagram Graph API rate limit) may not be handled gracefully. |
| Cron jobs (scheduling, trial reminders, churn detection) | ✓ Running | setInterval-based (not true cron). 60-sec interval for post scheduling, 4-hr health check, 24-hr churn detection |
Frontend (React 19 + Vite on Vercel)
| Component | Status | Notes |
|---|---|---|
| Build pipeline | ✓ Tested | npx vite build is the verification method. Vercel deploys automatically from git main. |
| Mobile responsiveness | ⚠ Mostly ready | 3 tooltip overflow issues at 375px (identified in QA). Core UI responsive; icons/buttons scale correctly. |
| Skeleton loading states | ✓ Polished | All 5 major pages have content-shaped skeletons (Settings, StrategyPage, InstagramConnect, InstagramPerformanceCard, InsightsCard). Shared CSS foundation in App.css. |
| Performance (Lighthouse) | ⚠ Not measured | No recent Lighthouse scores. Need to baseline performance and identify any critical issues before launch. |
API Integrations
Critical: API risk audit (inbox task, high priority) must be completed before Meta approval lands.
3. First-Run Experience — What a New Founding Member Sees
Day 1: Landing Page → Signup → Onboarding (15-20 min)
Day 1: First Post (2-5 min)
Estimated time to first publish: 7-10 minutes (signup + onboarding + first post). Zero blockers on the happy path.
Day 1-3: Help & Questions
Verdict: First-run experience is strong. Brand vibe fix and landing page typo are the only visible credibility issues. Core workflow is smooth.
4. Edge Cases & Failure Modes
Instagram API Failures
| Scenario | Expected Behavior | Status |
|---|---|---|
| Instagram Graph API rate limit hit | Toast message; queue post for retry; user can publish manually later or try again | ⚠ Not audited |
| User revokes Instagram permission | Graceful degradation; user sees "Connect Instagram" button; all other features work (Solo: captions still generate; Pro: can copy/paste manually) | ✓ Working |
| Business account becomes Personal | Next publish attempt fails; user sees "Switch to Business Account" callout | ⚠ Not audited |
| Instagram disconnects during trial | Pro auto-publish feature disabled; Solo features unaffected | ✓ Working |
AI Generation Failures
| Scenario | Expected Behavior | Status |
|---|---|---|
| Claude Haiku times out (> 30 sec) | Fallback to GPT-4o-mini immediately | ⚠ Needs audit |
| GPT-4o-mini rate limit hit | Error toast; no generation; user can retry or edit manually | ⚠ Needs audit |
| Both models unavailable | Error toast; user gets blank caption editor; can write manually | ⚠ Needs audit |
Database & Auth Failures
Billing & Stripe Failures
5. Missing Features — Does Founding Members Expect These?
Expect & Delivered
- ✓ Caption generation with voice matching — Core feature; works perfectly
- ✓ Instagram auto-publishing (Pro) — Live and tested on 02-23
- ✓ Scheduled publishing (Pro) — Application-side cron; queue system works
- ✓ Batch content planning — ContentCalendar component; create/edit 7-30 posts at once
- ✓ Voice archetype selection — 8 archetypes available to all tiers; onboarding quiz assigns correctly
- ✓ Help Center & in-app support — 40+ questions, 5 guides, 17 tooltips, email support endpoint
Expect But Not Delivered
- ⚠ Multi-platform publishing (Facebook, TikTok) — Currently Instagram-only. Planned for Month 1-3 post-launch. Founding members understand this.
- ⚠ Photo enhancement (Pro) — Spec exists; not yet built. Planned for Month 1-2. Currently founders get analyzed-feedback-only (no enhancement).
- ⚠ Analytics dashboard (Pro) — Insights card shows per-post + aggregated metrics (Instagram data). Further insights recommendations gated to Month 3.
Don't Expect
- ○ Competitor monitoring — Not a feature
- ○ DM automation — Not a feature; messaging is manual
- ○ Hashtag research tools — Config includes 5-hashtag sets; no dynamic research
- ○ Content templates — Stylify generates from scratch per voice; not a template tool
Verdict: All table-stakes features are built. Phased features (multi-platform, photo enhancement) are roadmapped and communicated. No surprises that would cause churn.
Critical Issue: Supabase Auto-Pause Risk
The Supabase free tier will auto-pause the project after 7 days of inactivity. Once founding members start posting, the project becomes active and the keep-alive workaround becomes fragile. A single network hiccup or deployment interruption could cause the database to pause and the entire app to go down.
This is not acceptable for a production SaaS. Supabase Pro upgrade ($25/month) is mandatory before the first paying user.
Immediate action required: Jason must upgrade Supabase to Pro tier the moment Meta approval lands. This should be done before sending invites to founding members.
Launch Readiness Scoring
3
Blockers (Must Fix)
7
Important (Should Fix)
8
Post-Launch (Can Wait)
Overall Readiness by Category
| Category | Readiness | Risk Level |
|---|---|---|
| Core Product (Onboarding → First Post) | 8.5/10 | Medium (Brand vibe update needed) |
| Infrastructure (Database, Backend, Frontend) | 7/10 | High (Supabase upgrade critical) |
| First-Run Experience (UI/UX Polish) | 8/10 | Medium (3 tooltip issues, 1 typo) |
| Reliability (Error Handling, Fallbacks) | 6.5/10 | High (API audit not done) |
| Feature Completeness (Expected vs. Delivered) | 8/10 | Low (phased features are documented) |
| Overall Product Readiness | 7.2/10 | Medium-High |
Summary: The product is fundamentally sound and ready for founding member launch. Core features work end-to-end. However, three critical pre-launch fixes are required (brand vibe, ToS integration, Supabase upgrade) and seven important fixes would significantly improve quality. All fixes are low-cost and implementable within 1-2 days.
Recommendations & Launch Timeline
Immediate Actions (Before Meta Approval)
- Brand Vibe Onboarding Update — Stitch, 45 min. Fix the outdated vibe options now, before any tests or demos use the wrong ones.
- ToS v4 Integration — Stitch, 30-45 min. Integrate 3 new sections (Style Data ownership, Auto-Publishing, Founding Member Program) into TermsPage.jsx.
- API Risk Audit — Stitch, 2-3 hours. Document all API failure modes, rate limits, and fallback strategies. Critical for launch confidence.
- Fix 3 InfoTooltip QA Issues — Stitch, 2 hours. Mobile overflow, Settings rendering, strategy routing. Test with Charlotte-QA account.
- Landing Page Typo — Stitch, 2 min. Fix $$49/mo → $49/mo in LandingPage.jsx.
The Day Meta Approval Lands (~March 5)
- Jason: Upgrade Supabase to Pro — Immediate. This is the prerequisite for accepting paying users. Remove the keep-alive script once upgraded.
- Jason: Review Meta approval details — Confirm all 3 permissions (basic, content_publish, manage_insights) are approved. If any are rejected, re-submit immediately.
- Stitch: Deploy all fixes — Push any pending commits (brand vibe, tooltips, typo, ToS). Verify on production.
- Charlotte: Enable Pixel's Task Scheduler jobs — Once ready, enable the 4 batch scripts (Morning/Afternoon/Evening/Weekly) on the HP laptop. Pixel will now handle all day-to-day social media operations.
- Jason: Send founding member invites — Batch 1: First 20-30 founding members. Send direct email invites with unique signup links (no public launch yet). Cap founding spots at 100 total per agreement.
Week 1 Post-Launch (March 6-12)
- Monitor founding member onboarding — Track signup → first post time, help ticket volume, churn. Setup Supabase analytic events if not already configured.
- Stitch: Build retention automation — Days 7/14/21/28 inactivity emails, monthly recap, Solo→Pro upsell. Kit sequences should fire automatically by Day 8.
- Stitch (Optional): Referral engine — If Jason approved, build during Week 1. Otherwise defer to Month 1.
- Stitch: Dashboard reskin — Lower priority; can ship Week 2 if Week 1 is smooth.
- Pixel: Execute content strategy — Post 2-3x daily to @GetStylify (Instagram + synced platforms). Monitor engagement. Respond to DMs.
Month 1 Post-Launch (March 13-April 5)
- Stitch: Build demo video pipeline — Phase 2: Automate "2-Minute Proof," "How Stylify Works," "Your Voice, Your Posts" videos. ElevenLabs voice cloning + Playwright + ffmpeg.
- Stitch: Multi-platform publishing (Facebook) — Add Facebook/Instagram cross-posting via Meta Graph API.
- Analysis: Founding member metrics — NPS survey, retention curves, feature usage patterns. Identify top drivers of activation and churn.
Month 2+ Post-Launch
- Stitch: Photo enhancement — Build AI photo enhancement toggle (Pro differentiator #2).
- Stitch: TikTok publishing — Add TikTok as third platform.
- Decision gate reviews — Evaluate Hook Optimization, Analytics Interpretation, Trademark filing triggers.
- Salon tier Phase 2-3 — Approval workflows, brand controls. Only if Phase 1 validates with early salon customers.
Key Assumptions & Uncertainties
Assumption 1: Meta App Review will approve within 10 business days (~March 5).
Why: Meta dashboard estimated "most submissions reviewed within 10 days." Previous submissions (v3, rejected) took 4 days. Resubmission (v4) was sent 02-23 early morning, so estimate March 4-5 as approval date.
Uncertainty: If Meta rejects again (unlikely given improvements), resubmission delays launch by 10+ more days. Have a contingency: what if you launch with Solo-only (no Pro) while waiting for approval?
Why: Meta dashboard estimated "most submissions reviewed within 10 days." Previous submissions (v3, rejected) took 4 days. Resubmission (v4) was sent 02-23 early morning, so estimate March 4-5 as approval date.
Uncertainty: If Meta rejects again (unlikely given improvements), resubmission delays launch by 10+ more days. Have a contingency: what if you launch with Solo-only (no Pro) while waiting for approval?
Assumption 2: API integrations (Claude, Instagram Graph, Resend, Stripe) will remain stable through launch.
Why: All APIs have been tested; fallback to GPT-4o-mini is in place for Claude failures.
Uncertainty: API risk audit not yet done. Claude may have rate limit increases; Instagram Graph API may deprecate the endpoint we use; Stripe may introduce new compliance requirements. Audit required.
Why: All APIs have been tested; fallback to GPT-4o-mini is in place for Claude failures.
Uncertainty: API risk audit not yet done. Claude may have rate limit increases; Instagram Graph API may deprecate the endpoint we use; Stripe may introduce new compliance requirements. Audit required.
Assumption 3: Founding member cohort will be 50-100 stylists willing to adopt a new product with phased features.
Why: Email list has 500+ subscribers; lead magnet is ready; early customer interviews showed strong product-market fit signals.
Uncertainty: Actual signup-to-paid conversion rate is unknown. Budget 5-10% (25-50 paying from 500 email list) as conservative baseline. First 100 founding members may take 2-8 weeks to acquire.
Why: Email list has 500+ subscribers; lead magnet is ready; early customer interviews showed strong product-market fit signals.
Uncertainty: Actual signup-to-paid conversion rate is unknown. Budget 5-10% (25-50 paying from 500 email list) as conservative baseline. First 100 founding members may take 2-8 weeks to acquire.
Assumption 4: Solo and Pro tiers will work equally well at launch; phased features (photo enhancement, multi-platform) won't cause churn.
Why: Core value (caption generation) ships on Day 1 for both. Auto-publishing (Pro) is a massive leap but is clearly marketed. Stylists expect iteration.
Uncertainty: Pro users may expect photo enhancement immediately; if they don't see it, they might churn. Mitigation: in onboarding, show a "Coming Month 1" roadmap card on the dashboard.
Why: Core value (caption generation) ships on Day 1 for both. Auto-publishing (Pro) is a massive leap but is clearly marketed. Stylists expect iteration.
Uncertainty: Pro users may expect photo enhancement immediately; if they don't see it, they might churn. Mitigation: in onboarding, show a "Coming Month 1" roadmap card on the dashboard.
Assumption 5: The 2-minute approval loop will remain the competitive moat.
Why: No competing tool ships this lean. Stylists are time-constrained and approval-fatigued.
Uncertainty: If founding members want approval workflows (manager/stylist split), the 2-minute loop may break for Salon tier. Mitigation: Salon tier is Phase 1 only (no approval workflows yet), so this is deferred risk.
Why: No competing tool ships this lean. Stylists are time-constrained and approval-fatigued.
Uncertainty: If founding members want approval workflows (manager/stylist split), the 2-minute loop may break for Salon tier. Mitigation: Salon tier is Phase 1 only (no approval workflows yet), so this is deferred risk.
Final Verdict
Ready to launch with high-priority fixes.
Stylify is fundamentally production-ready. The core product (onboarding → content creation → approval → publish) works end-to-end. Infrastructure is stable except for one critical upgrade (Supabase Pro). First-run experience is smooth except for minor polish issues.
The three blockers are all fixable in 2-3 hours:
- Brand Vibe update: Swap 4 onboarding options. 45 min.
- ToS integration: Copy 3 new sections into TermsPage. 30-45 min.
- Supabase upgrade: Click "Upgrade to Pro" in Supabase dashboard + remove keep-alive script. 5 min (Jason only).
The seven important fixes improve quality but don't block launch: landing page typo, tooltip QA issues, API audit, retention automation (deferred to Week 1), referral program decision, dashboard reskin (Week 2), and session process documentation.
Go-live recommendation: Fix the 3 blockers before sending founding member invites (March 5-6). Launch with the first 20-30 founding members immediately post-Meta-approval. Build the 7 important items in Week 1-2 post-launch while monitoring real user behavior.
Bottom line: You have a credible product with real differentiation (voice authenticity + 2-minute loop). The founding member launch will succeed if you focus on brand vibe + ToS + Supabase upgrade before Day 1. The polish issues can ship in parallel during Week 1 without impacting the core experience.