Scale your MVP: from prototype to product.

Yes. Lovable exports clean React/TypeScript and a Supabase backend, which we pick up and build on. Bubble can’t export, so there we plan a migration to a standard stack, but either way you end up with something you own and can scale.

We build on a sound foundation and only re-engineer the parts that genuinely need it. No vanity rewrites: the goal is a product that scales, for the least work and cost. How far we go depends on where you are heading, because a platform serving a thousand users is a very different beast to one serving a million with text, video and images. That is the question the analysis answers before anyone quotes a build.

Yes. Plenty of founders want to focus on customers and fundraising, not databases and scaling. We take the engineering off your plate, with one point of contact: the engineer actually doing the work.

Three parts. A free 30-minute call to understand what you have built and where you want to take it. Then a fixed-price analysis from €1,500: we go through the codebase, the data and the architecture, and within five working days you get a written report with the findings, a recommended target architecture and a phased delivery plan. Then a fixed price for the build, test and launch of each phase, quoted from that report. If you go ahead within 30 days, the analysis fee comes off the first phase in full. Hosting, support and ongoing changes are time and materials afterwards. You can stop after the report and take it to anyone: it is yours.

Typically two to four weeks for the first release, once the analysis is done. We phase it deliberately rather than cramming everything into release one, so you get something real in front of customers early. Apple’s review then takes roughly one to three days, so the honest promise is shipped to the App Store in a few days, not live the same day. Behind that first release sits a three to six month feature roadmap, and a higher-level view out to twelve and twenty-four months.

Because a first release that carries every feature is the most common way these projects fail. It delays revenue, it multiplies what can go wrong at launch, and it commits you to decisions before any customer has used the thing. We ship the core flow first, learn from real use, and build the rest against a roadmap that stays under review. This is how our founder delivered software in aerospace, defence and investment banking, where you do not get to launch everything at once and hope, and it works just as well for a startup.

Almost always the database, not the code. A prototype stores data in whatever shape was fastest to build, with no indexes, no constraints and every tenant’s records mixed together. It works for ten users and falls over at a few hundred. The fix is a proper schema and clear boundaries between tenants, which is a rebuild of the foundation rather than the features.

Lovable is genuinely good for getting to a working prototype, and its own documentation recommends validating with it and then building the production version. It exports clean React, TypeScript and Supabase, so the code is a real starting point rather than a dead end. What it does not give you is architecture: multi-tenancy, migrations, access control, testing and a deployment pipeline are the work that turns the export into a product.

Three signals, and one is usually enough: paying customers now depend on it, you are hitting limits the platform cannot lift, or you cannot hire someone to work on it. Cost per user climbing as you grow is the fourth. Moving before any of those is premature; moving after all four is expensive, because you migrate under pressure with customers watching.

Yes, and it is the most common thing we are asked to fix. mibi (mibihub.app) is our own proof: a field-service platform running five active tenants with thousands of records each, where every company’s data is isolated, the schema is indexed for the queries it actually runs, and adding the next tenant is configuration rather than engineering. That is the difference between a prototype and a product.