So it works. You typed, the AI built, you deployed, and somewhere out there a real person is using a thing you made. That feeling is legitimate — enjoy it for a day.
Then read this. Because here's the part nobody puts in the launch tweet: building the app was maybe forty percent of the job. The other sixty percent starts now, and it has no progress bar.
First: do you actually own your app?
Not philosophically. Practically. Open a private browser window and try to log into your hosting account, your database, your domain registrar, and your payment provider. From scratch, with credentials you control.
If any of those logins live only in a browser session you're scared to close, or in the AI builder's account rather than yours — fix that today. Ownership means access. Everything else in this article assumes you have it.
While you're at it: put every credential in a password manager and turn on two-factor everywhere. Boring advice. Also the advice that would have prevented most of the horror stories we hear.
The backup question (you probably can't answer it)
Ask yourself: if your database vanished right now, what would you do?
Most founders answer "there are backups, I think." That word — think — is the problem. Backup settings pages are reassuring and often misleading: retention might be seven days, file uploads might not be covered at all, and whether a backup can actually be restored is a separate question nobody checks until the worst day of their year.
We wrote a whole piece on this — a backup that was never restored is a rumor — but the short version: restore one, into a separate environment, this week. Time it. Write the number down.
Will you notice when it breaks?
Your app will go down. Not because you did anything wrong — providers hiccup, functions time out, certificates expire. The question is whether you find out from a monitoring alert or from a customer email three days later (the second one costs more, and not just in money).
A free uptime monitor takes fifteen minutes to set up. Error tracking a little longer. If you're not sure what's worth watching, we broke it down in monitoring for non-engineers — the honest answer is: less than you fear, more than nothing.
Support: the job you didn't apply for
The first support email is a milestone. The fortieth is a Tuesday. How you handle them decides whether your app grows or eats you — and there's a real craft to doing support solo without drowning, which we covered in its own guide.
The one-sentence version: one inbox, honest response times, and written answers you can reuse. Don't promise a chat widget you can't staff.
The legal furniture
Not legal advice — we're engineers — but the pattern is consistent: apps launch without an imprint, with a privacy policy copied from a different kind of site, and with consent banners that don't actually block anything. If you sell to anyone in the EU, get the basics checked. It's an afternoon with a checklist, or a short focused conversation with a lawyer instead of an expensive open-ended one.
And the code itself?
Here's an uncomfortable truth you've maybe already sensed: you are now the maintainer of a codebase you didn't exactly write. Dependencies will age. Security advisories will land. The AI that built it won't come back on its own to patch things.
That doesn't mean you need to become an engineer. It means you need either a safe update routine — see updates without fear — or someone accountable for it. Both are fine. Pretending the problem doesn't exist is the only wrong answer.
When to get help (and when not to)
Plenty of this you can genuinely do yourself; that's half the point of this blog. Where the math flips is when real money runs through the app, when downtime costs more than a monthly plan, or when the evenings you spend worrying are worth more than what you'd pay someone to carry the pager.
We wrote a decision framework — fix it yourself or pay someone — that tries to be honest about both sides, including the cases where you don't need anyone. And if you want the full picture of your app in one pass, that's literally what our Health Check is: read-only, flat fee, and if we don't find anything material you didn't know, you don't pay.
You built something real. Now keep it alive. That part is learnable too.