Launch
Public Launch Checklist
This checklist separates the working SlotNest product from the integrations, security, and operating details still required for a dependable public launch.
Working now
Core product
- Customer discovery and multi-service booking
- Customer, business, staff, and administrator accounts
- Business services, staff photos, shifts, hours, and calendars
- Appointments, clients, reviews, coupons, and inventory
- Unique referral links, attributed bookings, and completion-based rewards
- Booking availability and staff-shift validation
- Resend email confirmations and secure password recovery
- Twilio-ready SMS outbox and scheduled reminder processor
- Customer and business-owner email verification
- Administrator email two-step verification
- Separate administrator recovery and per-account session controls
- Durable abuse limits for sensitive public actions
- Security headers, request tracing, and administrator-visible server errors
- File-signature validation for uploaded photos
- Verified database-export and public smoke-test commands
- Verified isolated database restoration and encrypted-backup tooling
- Authenticated end-to-end booking and account acceptance suite
- Stripe live credentials and signed platform and Connect webhooks
- Customer and business Android apps with shared SlotNest accounts
- Verified customer, business, and administrator public domains
- Cloudflare deployment and shared database architecture
Priority one
Required before processing money
- 1. Complete live payment acceptanceStripe cards, deposits, policy fees, partial refunds, receipts, disputes, and payouts have passed end-to-end sandbox testing. Live credentials and signed webhooks are active. Complete each business's Connect onboarding and a controlled production transaction before accepting customer payments broadly.
- 2. Deliver real notificationsFinish SMS and push delivery for appointment reminders, review requests, cancellations, and staff shift reminders. The SMS delivery pipeline is ready; production Twilio credentials and sender registration remain.
- 3. Protect account accessPassword recovery, customer and business email verification, administrator two-step verification, session controls, and durable request limits are live.
Integrations
Connections still to complete
- 4. Finish calendar providersPrepare Google OAuth for production verification and build real sync for Outlook, Apple Calendar, Square, Calendly, and supported booking systems.
- 5. Publish the native mobile appsThe customer and business apps, secure native sessions, booking flows, dashboards, reminders, and internal Android builds are ready. Complete real-device Android and iPhone acceptance testing, production push credentials, and approved store or testing-channel distribution.
Infrastructure
Scale and protect the platform
- 6. Move media to object storageStore business, service, coupon, review, and staff photos in Cloudflare R2 or equivalent storage, with image optimization and unused-file cleanup.
- 7. Add production protectionDurable rate limits, security headers, request tracing, administrator-visible server errors, encrypted-backup tooling, and an isolated restore rehearsal are ready. CAPTCHA, external alerts, automated off-site retention, and a final security review remain.
- 8. Keep deployment migrations guardedThe migration process now audits, reports status, and applies each new migration before deployment. Keep that check in every release procedure.
Operations
Finalize the public business
- 9. Complete support and legal detailsSupport email, legal drafts, operating policies, retention procedures, and administrator-managed public company details are ready. The real operating name and address still need to be entered and counsel must review the legal drafts before broad launch.
- 10. Finish provider identity polishOwner and staff photos are supported. Existing businesses should review every bookable staff profile and upload any missing photo before launch.