Cursor App Launch Readiness Checklist

1. Grep for TODO, FIXME, and placeholder. Every hit is either work to finish or a comment to delete before strangers read your source maps.
2. Search git history for secrets, not just the working tree. A key that was ever committed is compromised — rotate it, do not just delete the line.
3. Delete dead routes and orphaned components. Assistants generate scaffolding you never wired up; unused code is untested surface and noise.
4. Strip debug output from the production build. A console.log with user data in it is a privacy problem, not just clutter.
5. Read your tests before trusting them. Generated tests can pass while asserting nothing — confirm each one checks real behavior, then run the suite green.
6. Build and run the production bundle locally. The dev server forgives things the production build will not — test what you will actually ship.
7. Document every env var and set them in the deploy host. An accurate .env.example, and a deploy that boots with only what is documented.
8. Make one real purchase on production. Real card, refund yourself, and watch the webhook fire in the payment dashboard.
9. Fail a payment and check the webhook path too. Declines and webhook retries should be handled, logged, and visible to you.
10. Run the auth loop and hit protected routes logged out. Including the password-reset email arriving at an outside address.
11. Check empty and error states. New account, no data, failed fetches — no blank panels, no stack traces.
12. Visit a bad URL and hard-refresh deep routes. A branded 404, and no SPA blank-outs on refresh.
13. Test at 375px wide. No horizontal scroll, readable text, thumb-friendly targets.
14. Set titles, meta descriptions, and the OG preview per page. Then check the actual preview card by pasting the link into a chat.
15. Publish refund, contact, and privacy pages that match reality. A monitored inbox and policies you will honor.
16. Scan your copy for unprovable claims. Cut guarantees and invented metrics before launch, not after a complaint.
17. Tag the release and rehearse the rollback. One command to revert, a tested database backup, and a one-page runbook naming who watches errors and payments on launch day.

Checkboxes are for this visit only — nothing is stored, tracked, or sent anywhere.

7-day money-back guarantee

Everstead Labs offers a 7-day money-back guarantee on founding beta software purchases and paid launch-readiness audits. If it is not useful, contact us within 7 days of purchase and we'll refund you. The product provides launch-readiness signals and practical fix guidance; it does not guarantee revenue, legal compliance, security, app-store approval, or launch success.