Guide: Cursor or Claude Code
Built with Cursor or Claude Code? Make it production-ready
AI coding tools write a lot of code quickly, but nobody has necessarily reviewed it. Before real users, add tests around the money and data paths, review access rules and secrets, set up deploys and monitoring, and make the codebase understandable. We review it and bring it up to production standard.

Look at this first
Look for missing tests around payments and permissions, and for code that no one on your team can explain.
The review
What we check before real users arrive
Who can see what
Access rules on the database and every endpoint, tested across accounts.
Secrets and keys
Nothing sensitive in the repo or the browser, and keys you can rotate.
Sign-in and accounts
Sessions, password reset, roles and what happens when an account is deleted.
Every check in the review
Data and backups
A separate production database, backups you have restored once, and migrations you can read.
Payments
Webhooks verified, failures handled, plans and refunds tested end to end.
Load and cost
Slow queries, uncapped AI or API spend and what happens at ten times the traffic.
Failure and visibility
Error tracking, logs, uptime alerts and a way to roll back.
Documentation
A short document that explains how it works and how to run it.
The four weeks
From review to live

Week 1
Scope and design
We agree the smallest version worth shipping. Bring a mock-up and we build from it; start without one and we design it with you.

Week 2
Core build
The main loop works end to end on a real backend, and you see it on your own phone.

Week 3
Integrate and harden
Payments, notifications, analytics and the edge cases that decide whether users stay.

Week 4
Ship
Store submission, monitoring and documentation. Then it is in people’s hands.
FAQ
Cursor or Claude Code to production: questions
Can I launch a AI-built app to real customers?
Often you can launch a prototype, but before real customers and real money are involved the app needs a security and data review, backups, error tracking, a separate production environment and a tested payment flow. We review what exists, fix what matters and tell you plainly what is already fine.
Do I have to rewrite my AI-built app?
Usually not. We read the code first and give you a written verdict on what to keep, what to fix and what to replace. A rewrite is a last resort, and we say so when it is the right call.
How long does it take to take it to production?
It depends on what the review finds. Most reviews take a few days, and we give you a plan with timings before any fixing starts.
Will I understand my app afterwards?
We document how it works and how to run it, so you or any developer can carry on.
