What Does It Cost to Finish and Maintain a Vibe-Coded App?

There is no reliable price from the tool name alone

Two apps built in Lovable or Replit can have very different needs. One may need a callback corrected. Another may need permissions redesigned, billing completed, test coverage added, and data migrated. The platform is useful context, but it is not an estimate.

A useful quote starts with an agreed outcome and evidence from the existing implementation. If someone estimates from the number of screens alone, ask how they accounted for the data model, integrations, failure cases, and release responsibilities.

Separate the work into four decisions

1. Assessment. Establish what works, which issues matter, and what the next milestone requires. Agree the review's scope and price before it starts. Do not assume a consultation includes a complete code or security audit.
2. Focused fixes. Resolve a defined problem with acceptance criteria. For example, a user can reset a password and return to the intended account without gaining access to another account.
3. Launch preparation. Address the agreed release blockers, test important journeys, configure the deployment, and document recovery. New product features belong in a separate scope if they are not required for launch.
4. Maintenance. Agree the work and availability after release. This can include bug fixes, updates, release support, and small improvements. It should identify what is covered and what becomes a new project.

A partial or full rebuild is another option to evaluate, not an automatic fifth phase. It needs a comparison against repairing the current app, including the cost of moving data and preserving working behavior.

What increases the remaining work?

• Permissions and account structure. An app for one operator is different from a product where every organization must have isolated records and several staff roles.
• Payments and integrations. Recurring billing, retries, reconciliation, and failures across external services add work beyond a successful demo.
• Existing customers and data. Changes to a live app require more care than changes to an unused prototype, especially when migrations need to preserve records and access.
• Missing tests and unclear code. Reproducing behavior and adding checks takes time when nobody can show what is supposed to happen.
• Operating requirements. Availability expectations, sensitive data, expected load, and store submission can change the scope.

These are reasons to ask better questions, not reasons to pad every proposal. An unused internal tool with one simple workflow may not need the same infrastructure as a customer-facing subscription business.

Code and Trust's published pricing

Our published fixed-price builds are from $15,000, and monthly retainers are from $1,750/month. Most large builds are fixed-price, with a monthly retainer after launch. These are general commercial floors, not a quote for finishing your app or a promise that every bug fix is a full build.

The app's assessment, repair, and launch scope must be priced for the work involved. We do not publish a universal AI-app cleanup package or a separate assessment fee here. For the broader model, see our custom software development cost guide.

Keep maintenance separate from hosting

Hosting keeps the application available on infrastructure. Maintenance is the engineering work to keep its behavior reliable as dependencies, integrations, and requirements change. A builder subscription may cover platform features while leaving your particular business workflows for you to maintain.

Post-launch support and maintenance are scoped per engagement. Before signing a support agreement, ask about:

• The monthly scope or capacity, and how competing requests are prioritized.
• Response expectations, availability, and the route for reporting an urgent issue.
• Responsibility for monitoring, backups, dependency updates, and releases.
• What counts as a bug fix, an improvement, or a separately estimated feature.
• Third-party costs such as hosting, database usage, AI calls, email, and payment processing.

A monthly fee does not mean unlimited development or continuous incident coverage unless those terms are actually agreed. Compare the responsibilities and deliverables, not only the headline price.

How to compare proposals

Give each developer the same demo, issue list, account roles, and target milestone. Ask them to describe what they will keep, change, and test. A useful proposal states its assumptions, exclusions, acceptance criteria, and the access needed to do the work.

Ask for the migration and handover plan if a rebuild is proposed. Confirm how code, documentation, and operating accounts will be delivered and who can maintain the result. A lower quote with no testing or handover is not necessarily less expensive to operate.

Start with the next milestone

Pick a concrete outcome: safely invite a pilot customer, accept a subscription payment, or transfer maintenance to a developer. Use our security checklist to identify launch questions, or the Lovable production guide if that is your platform.

Then talk with Code and Trust about app cleanup and support. Bring the existing app and the outcome you need; the scope should follow the evidence.