For founders with a working prototype
You built the prototype. Now make it a product you own.
Lovable, Bolt, Replit, Bubble and FlutterFlow put a working prototype in front of users fast. Then the same walls appear. A Production Readiness Review tells you in writing, in one week, what to keep, what to fix and what it will cost.
From $2,000, one week, credited in full if you build with us. We will not tell you to rebuild when a refactor will do.
The walls
Five things that break when a prototype meets real users.
Logins and permissions
Everyone can see everything, or nobody can reset a password. Roles, invitations and access rules were never designed, only added.
A data model nobody designed
Tables grew one feature at a time. Reports are slow, records duplicate, and every new feature breaks an old one.
Secrets in the browser
API keys and database rules that anyone can read in the page source. The most common finding in AI-built apps, and the most expensive one to discover late.
Hosting you do not control
The app lives in the tool's account, not yours. Moving it, scaling it or passing a customer's security questionnaire depends on someone else.
Nobody to call
When it breaks at 2am, or a customer asks how their data is protected, there is no engineer who knows the code.
Refactor or rebuild
The honest answer is usually the smaller one.
Most quotes say "rebuild from scratch", because a rebuild is the bigger invoice. The review exists to find out which one you actually need.
Refactor
Keep the product, the users and most of the screens. Replace the parts that are fragile: access rules, the data model, secrets, hosting. Usually weeks, not months.
Rebuild
When the data model is wrong for what the product has become, or the tool will not let you take the code with you. Then the prototype becomes the specification, which is still worth a great deal.
The Production Readiness Review
What you get, in writing.
Written by Gaurav Sharma, who leads every build here, with our senior technical lead.
- What is soundThe parts of the prototype that should stay, so nobody rebuilds them out of habit.
- What is fragileAccess rules, data model, secrets and hosting, each with how serious it is and what happens if it is left.
- Refactor or rebuildA verdict and the reason for it, not a menu.
- The rules that touch your dataUK GDPR, the FCA, CQC, the NHS DSPT, FERPA or others, named for your product, with what each adds.
- A cost range and a timelineWith the assumptions written down, measured against our published prices.
- A plan any competent team can followOurs or someone else's. You keep the review either way.
Price and time
From $2,000. One week.
Fixed before we start, so the number does not move once we have looked.
- PriceFrom $2,000, quoted and invoiced in USD
- TimeOne week from access to the code or project
- CreditCredited in full against a build with us, on any track
- We needRead access or an export, a 45-minute walkthrough with you, and a list of who uses it today
- You keepThe written review and the plan, whatever you decide
If you build with us
The review becomes the scope.
Proof slice
The riskiest fix first, working, so you can see the approach before committing to the rest.
Trial release
Your existing users on the new foundations, with accounts and data moved across.
Commercial release
Ready for paying customers, security questionnaires and growth. Three ways to pay, published in advance.
Before anything else
Export your code today, whatever you decide.
Ten minutes now saves weeks later, and nobody can hold your product hostage.
- Lovable and Bolt. Connect a GitHub repository in your own name and push the project to it.
- Replit. Connect GitHub, or download the project, and keep a copy outside Replit.
- FlutterFlow. Download the code if your plan allows it, and keep the Firebase or Supabase project in your own account.
- Bubble and Softr. They do not export code. Export your data, and write down your workflows and settings while you still remember why they are there.
- Every tool. Make sure the database, the domain and the app store accounts are in your name, not a freelancer's.
Questions prototype founders ask
Straight answers.
Do I have to rebuild?
Usually not. Most prototypes need a refactor: keep the product and the users, replace the fragile parts. A rebuild is the right answer when the data model is wrong for what the product has become, or when the tool will not let you take the code with you. The review says which, and why.
Will you look at a Bubble or FlutterFlow app?
Yes. We review apps built in Lovable, Bolt, Replit, Bubble, FlutterFlow, Softr and similar tools. Whether to stay on the tool for now is one of the questions the review answers. Sometimes staying for another six months is the right call.
What happens to my existing users and data?
They are the reason the prototype matters, so the plan keeps them. The review covers how accounts and data move across, what has to be cleaned first, and what users will notice, if anything.
Which regulations touch my data?
It depends on what you hold and where your users are: UK GDPR for personal data, the FCA for payments, CQC and the NHS DSPT for care and health, FERPA and COPPA for US schools. The review names the ones that apply and what each adds to cost and time.
Is the review a sales pitch for a rebuild?
No. If a refactor is enough, the review says so, and the plan is written so that any competent team can carry it out, with us or without us. The fee is credited in full only if you choose to build with us.
What if I am not ready to pay for a review?
If another team has already quoted you, send the quote for a written second opinion at no charge. If you are still deciding whether to build at all, start with the readiness check.
Find out what your prototype needs before anyone quotes for a rebuild.
Email a link to the app or the export. Gaurav replies within one working day with a fixed price and a start date.
Prefer to talk first? Book a 30-minute call.