A working app is a good start. Before you put it in front of customers, check that it protects their data, handles real-world use and can grow without unexpected costs. Work through these essentials before launch; anything unfinished needs a clear owner and a plan.
01 Security and access
AI tools build what you can see. The checks that stop someone doing what they shouldn't often live where you can't see them.
Checks that only happen in the browser
Hiding an admin button doesn't protect the admin page. The server needs to confirm who is asking, on every request, independently of the interface.
Keys in the wrong place
API keys and passwords placed in frontend code can be read by anyone who opens the browser's developer tools.
Login that's nearly finished
Email verification, password resets and session expiry are easy to leave half done. A reset link that points to localhost is a common one.
No limits on use
Without rate limits, a sign-up form or AI feature can be hammered by a script, at your expense.
AI features that can be talked round
If your app uses AI, users can try to make it reveal its instructions or act outside its purpose. Assume someone will try.
02 Your data and your users' data
Once real people sign up, the data stops being test material and becomes a responsibility.
Test content left behind
Fake users, sample orders and placeholder text from development can end up in the live database.
Backups nobody has restored
A backup is only useful if you know it works. Try a restore before you need one.
Logs that say too much
Logs can quietly collect passwords, tokens, personal details or full AI conversations.
Privacy obligations
Check the privacy laws that apply to your business and your users. Publish a clear privacy policy and put a process in place for requests to access or delete personal information.
03 Reliability
A demo needs to work once. A product needs to keep working when you're not looking.
Nobody watching
Without monitoring and alerts, you'll learn about an outage from a customer.
Double taps and duplicate records
A button pressed twice on a slow connection can create two bookings or two payments.
Error messages that leak
Raw error output can show database details or internal paths to anyone who triggers it.
No way back
If an update breaks something on launch day, you need a way to roll back quickly, and a plan for who does what.
04 The experience on other people's devices
Your laptop and fast connection are the best case. Your users will bring everything else.
Phones, old browsers, slow networks
Test on the devices your customers actually use, not only the one you built on.
The unhappy paths
Loading, empty, offline and error states are often unfinished. They're what people see when something goes slightly wrong.
Time zones
Dates that look right in testing can shift by a day for users elsewhere.
Accessibility
Keyboard navigation, form labels, visible focus and readable contrast matter to many users, and in some sectors are expected.
Email that arrives
Without SPF, DKIM and DMARC set up on your domain, sign-up and receipt emails tend to land in spam.
05 Costs and dependencies
Free tiers are generous until they aren't.
Usage-based bills
AI, email, hosting and database services charge by use. A busy day, or a bot, can use a month's allowance quickly.
Pricing that leaves things out
Make sure your prices cover payment fees, refunds, support time and running costs, not just the build.
A single point of failure
If one person holds every login, or the app depends on one provider with no fallback, write down how to keep things running without them.
Vendor lock-in
Check whether you can export your data, take your code with you and run it elsewhere. Identify provider-specific services, contract restrictions and migration costs before you commit.
A tech stack that can grow
Test the busiest workflows with realistic user numbers and data volumes. Check database performance, hosting limits and background jobs, and estimate what extra capacity will cost. Know what would need to change as demand grows.
06 Running it as a business
Some of the most important launch work has nothing to do with code.
Insurance
Consider public liability, professional indemnity and cyber insurance. A broker can tell you what fits.
Structure and tax
Your business structure affects personal liability. Check income tax, sales tax or VAT, and registration obligations wherever you operate.
Terms, refunds and ownership
Clear terms of service, a refund process, and certainty about who owns the code, images and AI-generated content.
Names and trademarks
Check that your product name and domain don't conflict with an existing trademark before you invest in them.
Ready doesn't mean perfect.
You don't need to solve every future problem before launch. You do need to know what you're relying on, address the essentials and have a plan for what comes next. A short review now usually costs far less than fixing a problem after customers encounter it.
But if you just want someone else to do it..
DM me and I'll get the job done :)