Launch Finalizer
Last-mile beta launch checklist for moving fast without losing trust · Srazzu
ASAP FINISH MODE
Ship the controlled beta, then improve from real usage.
The project is now best finished by validating the core revenue loop: customer message arrives, Srazzu prioritizes it, founder replies/follows up, beta user gives feedback.
Leads
Conversations
Feedback
Tasks
Alerts
Hot leads
LAUNCH ACTIONS
Do these before inviting beta users
The test conversation button requires ADMIN role and creates Web Chat records only. It does not call paid services.
MUST-PASS LINKS
BETA TESTER PROGRESS
Who completed the mission?
FINAL FEATURE TRUTH TABLE
Widget messages flow into Inbox, Leads and Events.
Production webhook is connected and messages are logged.
Homepage, Contact and Beta forms capture leads and send notifications.
Public feedback and admin feedback triage are active.
Test checkout and billing portal routes are connected.
Health checks, Sentry test endpoint and system status are available.
Prioritizes hot leads, churn risk and support issues from live data.
Use wa.me links, prepared replies and follow-up logging before Meta approval.
Draft replies, quality checks and workspace memory support agent workflows.
Templates, segments, dry-run and automation foundation exist; sending should remain controlled.
Backend scaffold exists; Meta app, phone number and webhook verification are pending.
Browser demo is available now; Twilio/live telephony should wait until revenue validates demand.
Keep postponed because SMS has real country-dependent cost.
Current hub is a demo/static concept; live APIs should be monetized as an add-on.
Social Hub is strategic but API approvals should not block beta.