# Vibe Code Rescue Checklist
**A printable, scannable checklist for founders who shipped fast and now need the app to hold.**
You proved the idea. Customers are here. This checklist shows what to check before the next hundred of them arrive. Score each item Yes, Partly, or No, then bring your answers to a free systems audit.
## Who it is for
* Founders who shipped a vibe coded or AI built app and now have real customers depending on it.
* Operators whose internal tool quietly became the system of record.
* Teams that can add features but cannot say with confidence that secrets, backups, and access are solid.
* Leaders deciding whether to reinforce what they have or start over.
## How to use it
1. Work through each section below.
2. Mark every item Yes, Partly, or No. Be honest. Partly and not sure both count as Partly.
3. Note the weakest sections. Those are your first fixes.
4. Bring your answers to a [free systems audit](https://www.causeofakind.com/free-systems-audit?utm_source=vibe_checklist&utm_campaign=body_link). We use them so the thirty minutes go to what to fix, not discovery.
## Secrets and access
* Secrets (database passwords, payment keys, email keys, AI keys) live in environment settings, not in the code.
* No secret reaches the browser or a public file.
* A logged in user can only see and change their own data, even if they edit a link or an ID.
* Regular users cannot reach admin pages by guessing a URL.
## Data and backups
* The database is backed up automatically on a schedule you did not invent by hand each week.
* You have restored a backup at least once and know it works.
* You know what you would lose if the live database disappeared tonight.
## Environments and releases
* There is a staging copy of the app where changes are tried before customers see them.
* Shipping a change follows written steps someone new on the team could repeat.
* Releases are boring. They are not a nervous afternoon.
## Monitoring and tests
* Error tracking or uptime alerts tell you when something breaks before a customer does.
* Someone on the team actually receives those alerts.
* Payments, signups, and anything that touches personal data have automated tests that run before each release.
## Ownership and readability
* The code lives in a repository you control.
* You can export all of your data if you had to leave the current host tomorrow.
* A new engineer could read the code and make a safe change without fear of breaking something unrelated.
* The hardest files are known. You could name the three places nobody wants to touch.
## Rescue vs rebuild signals
Grounded in how we decide on real audits. See [Rescue or Rebuild: How to Decide What to Do With a Vibe Coded App](https://www.causeofakind.com/blog/rescue-or-rebuild-how-to-decide-what-to-do-with-a-vibe-coded-app).
**Keep and reinforce when:**
* The core data model matches how the business actually works.
* The pain is concentrated in a few areas (login, payments, one overloaded page).
* It runs on mainstream tools a good engineer already knows.
* Customers are mostly happy with what the product does. Complaints are about speed and bugs.
**Consider a rebuild only when:**
* The data model is wrong at the root and every feature fights it.
* The platform cannot grow with you and there is no way through the limits.
* You cannot get your code or your data out.
* Security cannot be patched piece by piece at a cost that makes sense.
Most vibe coded apps can be rescued. Rebuild only when platform, ownership, or security cannot be patched.
## What your answers mean
**Ready.** Most items are Yes. Secrets, access, and backups are solid. Keep the habits that got you here and focus on the product.
**Working but fragile.** The app does its job, and a few gaps could turn into a bad week. Fix the No answers first, starting with secrets, access, and backups.
**At risk.** The app proved the idea, which is a real win. It now needs reinforcement before it carries more customers. This is the most common place we see founders, and the most fixable.
Want a numbered score out of 100? Use the [production readiness scorecard](https://www.causeofakind.com/production-readiness-scorecard?utm_source=vibe_checklist&utm_campaign=scorecard). Ten questions, a few minutes, same ground.
## Book a free systems audit
The checklist tells you where to look. A systems audit tells you what we would fix first and in what order. Thirty minutes with Mike and Justin, free, whether you work with us or not.
Prefer a scored pass first? [Open the production readiness scorecard](https://www.causeofakind.com/production-readiness-scorecard?utm_source=vibe_checklist&utm_campaign=scorecard).
## Related reading
* [What We Find When We Open the Hood on an AI Built App](https://www.causeofakind.com/blog/what-we-find-when-we-open-the-hood-on-an-ai-built-app). Six findings from systems audits of AI built apps.
* [Rescue or Rebuild: How to Decide What to Do With a Vibe Coded App](https://www.causeofakind.com/blog/rescue-or-rebuild-how-to-decide-what-to-do-with-a-vibe-coded-app). When to keep reinforcing and when a rebuild is justified.
* [Is Your AI Built App Actually Ready for the World? A Production Readiness Field Guide](https://www.causeofakind.com/blog/is-your-ai-built-app-actually-ready-for-the-world-a-production-readiness-field-guide). The longer field guide behind the scorecard.
* [Production Readiness Scorecard](https://www.causeofakind.com/production-readiness-scorecard). Ten questions and a numbered score.
* [Free 30 Minute Systems Audit](https://www.causeofakind.com/free-systems-audit). Bring this checklist and leave with the two or three things to fix first.
We help cool people build great products.
Canonical URL: https://www.causeofakind.com/vibe-code-rescue-checklist