Prototype to product
A prototype can show that a flow works, but that alone does not prove the product is ready for real users and data. An audit checks the actual codebase; only then can we decide what to fix, what to keep and how much work is required.
Last updated: 13 September 2026 · By Lovy StudioAn MVP built with Claude, Cursor, Lovable, v0, Codex or similar tools can help test a hypothesis and collect feedback. Validation still depends on the evidence gathered: an app that opens does not by itself prove market demand or production readiness.
There is no single defect shared by every generated project. We check authorisation, secrets, validation, error handling, data, backups and monitoring to establish which risks actually exist in that codebase.
Before proposing any work we read the code and use the application. The output is a document listing what we found, ordered by actual risk. It usually takes 2–5 working days.
| Area | What we check | Why it matters |
|---|---|---|
| Security | Authentication, per-role permissions, database policies, exposed secrets, input validation | Reduces the risk of unauthorised access or operations |
| Data | Table structure, relations, indexes, migrations, backups | Late data-model changes can affect migrations and existing features |
| Reliability | Error handling, loading states, edge cases, what happens when a call fails | Helps keep the flow understandable when something fails |
| Performance | Slow queries, bundle size, images, Core Web Vitals | Can affect user experience, infrastructure cost and technical SEO signals |
| Maintainability | Duplication, types, folder structure, abandoned dependencies | Influences the time and cost of future changes |
| Going live | Environments, variables, domain, monitoring, logs | Makes problems easier to detect and diagnose |
An honest audit also says what to keep. Rewriting to personal taste burns budget and leaves the product where it was.
Price depends on the findings, the scope and the product decisions still open. The audit separates contained fixes, structural work and any parts that may need rebuilding before the main budget is committed.
| Engagement | Indicative band | What it covers |
|---|---|---|
| Audit only | €800 – €1,500 | Full review and a document with priorities, risks and effort estimates. Deducted from the quote if you go ahead |
| To production, contained scope | €3,500 – €6,500 | Security and permissions fixed, error handling, correct deployment, basic monitoring |
| To production, broad scope | €6,500 – €12,000 | Wider refactoring, revised data model, performance, minimal documentation |
| Ongoing technical ownership | from €9,000 | We become the product's technical lead: evolution, maintenance and new features |
No stage starts before you have seen and approved the previous one. The audit is also the point where you can stop: the document is yours and you can hand it to anyone.
That cannot be established without reading the project. Sometimes contained fixes are enough; in other cases changing the existing structure costs more than rebuilding part of it. The audit documents the reasons for that decision.
Because without opening the code any number would be unreliable. Two MVPs that appear to do the same thing can require very different work. The audit defines the risks and makes the subsequent quote testable.
We can audit projects started with Claude Code, Cursor, Lovable, v0, Bolt or Replit where the stack matches our experience, including Next.js, React, Supabase and Firebase. For other foundations we first confirm the technical scope.
We use AI tools during development, but review their output and directly verify permissions, data models, security and application behaviour. The tool does not replace technical accountability for the result.
Yes. It is yours and you can use it however you like, including to get competing quotes. If you go ahead with us, the audit cost is deducted from the quote for the work.
As an initial reference, after the audit a contained scope may take 2–4 weeks and a broad one 4–8. The final estimate depends on the findings, external dependencies and product decisions still open.
Next step