Your app works. Now make it ready for paying customers.

What a working demo does not test

A demo proves the path you clicked through. Real customers, bots and payment providers test everything else. These are the gaps we check first, because they are the ones that cost money or trust when they fail.

• Data access rules: whether one signed-in user can read or change another user's records.
• Secrets: API keys or admin keys that ended up in browser code or in the repository.
• Backups: whether one exists, and whether anyone has restored it.
• Payments: whether payment webhooks are verified, so a repeated event cannot charge or upgrade twice.
• Cost and abuse: whether anyone can call your AI features without limits and run up your bill.
• Errors: whether you hear about a failure before a customer emails you.

What the teardown gives you

One page, written for the person who decides. It covers your app as it runs today, not a generic checklist.

• Each issue found, ranked: fix before launch, fix soon, or can wait.
• Where the app should be hosted, including a UK region if your customers or contracts require it.
• What the fix involves, with an indicative fixed price and timeline.
• The teardown fee is credited toward the fix if you go ahead.

What we need from you

Read-only access is enough. We ask for nothing that can change your live app.

• The live URL and a test account, or permission to create one.
• Read access to the code: GitHub, GitLab, or an export from Replit, Lovable or Bolt.
• If your data rules live in a dashboard such as Supabase or Firebase, a read-only view or an export of those rules.
• Ten minutes on what the app must do for its first paying customers.

If you go ahead with the fix

The fix is a separate piece of work at a fixed price, agreed in writing before it starts. It closes the gaps in your plan and leaves you in control. It can include:

• Hosting in an account you own, with automatic deploys and a staging copy for testing changes.
• The data access and secret gaps closed, with tests that show they stay closed.
• Daily backups and a restore that has actually been run.
• Error alerts and uptime checks that reach you before your customers notice.
• A repository and runbook your AI coding tool can keep working from.

Who does the review

Urbano, a senior engineer based in Poland, one hour ahead of the UK. He builds and runs his own production apps with AI coding agents every day, so the review comes from someone who ships this way. You talk directly to the person who does the work.