---
title: "Freelancers: selling vibe-coded apps to clients"
description: "What services to sell, how to price them, who owns the code and accounts, and which contract clauses to include: a freelancer's guide to vibe coding."
url: "https://vibe-code.blog/en/freelance-vibe-coding"
lang: "en"
author: "Thierry Gustin"
published: "2026-10-22"
updated: "2026-11-21"
---

# Freelancers: selling vibe-coded apps to clients

> **Key takeaways** — Freelancers can sell vibe-coded apps as long as they sell an outcome (a working, secure tool handed over cleanly), not hours of prompting. The offers that hold up: prototypes, MVPs, internal tools and rescuing existing vibe-coded apps. The contract must settle three points AI makes fuzzy: who owns the code and accounts, who pays for credits, and who processes personal data.

Freelance vibe coding means selling AI-built applications to clients who have neither the time nor the inclination to build them themselves. The market is real, but it doesn't pay for prompts: it pays for a tool that works, doesn't leak data and that the client can take back the day you part ways. Here's what to sell, how to price it and what to put in the contract.

## Why would a client pay for an app they could generate themselves?

Because generating an app and delivering an app are two different jobs. The client isn't buying access to Lovable or Cursor. They're buying:

- **translating their need** into a clear specification;
- **the final 20%**: bugs, edge cases, access rules, deployment;
- **security**: a protected database, keys kept out of the front end, payments verified server-side;
- **peace of mind**: someone to call when it breaks.

Demand for that last point is already visible. In September 2025, 404 Media, picked up by Gizmodo, described freelancers and firms specialising in fixing vibe-coded software. A Fiverr seller, Hamid Siddiqi, said he works regularly with 15 to 20 clients on problems such as inconsistent interfaces and poorly optimised code. Swatantra Sohni, founder of the VibeCodeFixers platform, said the tools are better suited to prototyping than to production software.

## The 5 services that sell

| Service | For whom | Deliverable | Main risk |
| --- | --- | --- | --- |
| Clickable prototype | Agency, founder, salesperson | An online demo to win buy-in | Client mistakes it for a finished product |
| MVP | Non-technical founder | App with login, database, payments | Security and payments |
| Internal tool | Small business, operations team | Replaces a spreadsheet or overpriced software | Access rules, personal data |
| Custom brochure site | Tradesperson, freelancer | A few fast, readable pages | Maintenance and legal pages |
| Vibe-coded app rescue | Client who started alone | Audit, fixes, production launch | Technical debt hidden at quote time |

Each line has its own detailed article: [building a SaaS from idea to first customer](https://vibe-code.blog/en/build-saas-vibe-coding), [replacing a spreadsheet with an internal app](https://vibe-code.blog/en/internal-tools-vibe-coding), [building a small business website with AI](https://vibe-code.blog/en/ai-small-business-website), and rescuing an app that got out of hand in our guide to technical debt. For demos at a first meeting, see also showing a working prototype at the first meeting.

## How should you price it?

Charge a fixed fee per deliverable, not for time spent. Vibe coding shortens code generation, not understanding the need or testing. If you bill by the hour, you're penalised for your own efficiency.

A quote structure that holds up:

1. **Discovery** (fixed fee): workshops, written spec, paper mock-up. Deliverable: an approved document. Our guide to [writing a PRD your AI builder understands](https://vibe-code.blog/en/prd-for-ai-builders) can serve as a template.
2. **Build** (fixed fee): the app as specified, tested.
3. **Launch** (fixed fee): domain, hosting, backups, security checks.
4. **Maintenance** (monthly retainer): fixes, small changes, monitoring.
5. **Change requests** (separate quote): anything outside the spec.

> **Credits are a separate line** — Vibe coding tools charge by usage. Lovable's documentation states that invited collaborators use credits from the project owner's workspace. Put in writing who pays for the subscription and credits, and whose name the account is in.

## Who owns the code and the app?

That's the question your clients will ask, and AI complicates it.

### What the tools' terms say

Lovable's terms state that "as between us, you own your Customer Data" (which includes projects) and that "you also own any AI Output generated for you through the Services", subject to third-party rights in the underlying models and data. They also warn that "AI Output may be similar or identical to content generated for other users". Read the terms of whichever tool you use; they vary.

### What copyright law says

AI-generated code isn't necessarily protected by copyright. In the US, the Copyright Office concluded on January 29, 2025 that AI outputs are protectable only where a human author has determined sufficient expressive elements, and that the mere provision of prompts isn't enough. We'll cover this in depth in who owns AI-generated code.

In practice, your contract should include an **assignment of rights** over what you created (spec, design, code, content) and state that some generated parts may not be protectable. Don't promise an exclusivity nobody can guarantee.

## Accounts: the real delivery issue

Code is only part of the app. The other part is accounts: the vibe coding tool, database, hosting, domain, Stripe, email. If everything is in your name, your client is locked in, and you're responsible for everything.

The simple rule: **the client owns the accounts, you're invited in.**

- **Domain and hosting**: in the client's name, with their payment method.
- **Code**: a GitHub repository in the client's name. According to Lovable's documentation, GitHub sync creates a private-by-default repository under the account or organisation you choose, and if you disconnect, the repository stays on GitHub with its full history. See [Git for vibe coders](https://vibe-code.blog/en/git-for-vibe-coders).
- **Stripe**: the client's account, never yours. Revenue and tax responsibility are theirs.
- **Database**: a project created in the client's organisation.

## Personal data: you're a processor

As soon as the app handles data about people (customers, employees, users), your client is the data controller and you, with access to that data, are a processor under GDPR (which applies in the EU and, as UK GDPR, in the UK). Article 28 of the GDPR requires processing by a processor to be "governed by a contract or other legal act". That contract must, among other things, state that you act on the client's documented instructions, keep the data secure, don't bring in another processor without authorisation, and delete or return the data at the end of the engagement.

The vibe coding tool, host and database provider are themselves sub-processors: list them in the contract. Our article on GDPR and your vibe-coded app covers compliance in detail.

## Clauses to include in your contract

- **Scope**: the approved spec is attached; everything else is a change request.
- **Ownership**: assignment of rights over deliverables on full payment, with a note on AI-generated parts.
- **Accounts**: list of accounts, whose name, who pays.
- **Credits and subscriptions**: paid by the client, or recharged with a cap.
- **Security**: checks performed before delivery (for example RLS enabled, no secret keys in the front end), with our [pre-launch security checklist](https://vibe-code.blog/en/vibe-coding-security) attached.
- **Warranty**: how long you'll fix bugs after delivery.
- **Maintenance**: what the retainer covers, response time.
- **Personal data**: GDPR Article 28 clauses.
- **Exit**: how the client gets everything back if the relationship ends.

## The delivery process in 6 steps

1. **Spec approved in writing**, with a mock-up.
2. **Build** inside accounts in the client's name.
3. **Testing** with one account per role, plus an "attacker" account that tries to reach other users' data. See [testing AI-generated code](https://vibe-code.blog/en/testing-ai-generated-code).
4. **Security review**: database, keys, payments. See [the Supabase RLS mistake](https://vibe-code.blog/en/supabase-rls-security).
5. **Launch** and backup.
6. **Handover**: a one-page document with access, architecture, predictable monthly costs and what to do if something breaks.

## Picking your freelance tool

Your tool must let you export code and work inside the client's accounts. [Lovable](https://lovable.dev/) and [Bolt](https://bolt.new/) suit prototypes and MVPs thanks to GitHub sync. [Cursor](https://cursor.com/) and [Claude Code](https://www.anthropic.com/claude-code) suit clients who already have a repository or mandated hosting. To compare, read our [guide to the best vibe coding tools](https://vibe-code.blog/en/best-vibe-coding-tools), and for more project ideas to pitch, our [25 real use cases](https://vibe-code.blog/en/vibe-coding-use-cases).

## Frequently asked questions

## Frequently asked questions

### Can you freelance in vibe coding without being a developer?

Yes for prototypes, websites and simple internal tools, as long as you've mastered basic security: database access rules, API keys out of the front end, payments verified server-side. For apps handling sensitive data or money, have a developer review the work or partner with one. Your professional liability is on the line.

### How much should I charge for a vibe-coded app?

Charge per deliverable, separating discovery, build, launch and maintenance. The price should reflect value to the client (the software it replaces, the time saved) and your responsibility, not generation time. List tool subscriptions and credits separately, paid by the client.

### Should I tell clients the app was built with AI?

Yes. It's more honest, and it matters legally: some generated code may not be protected by copyright, and the tools' terms apply. Present it as a method that shortens timelines, and stress what you add on top: specification, security, testing and a clean handover.

### Who should pay for the Lovable or Cursor subscription?

Ideally the client, in a workspace in their name where you're invited. On Lovable, collaborators use the workspace owner's credits. If you use your own subscription during the build, plan to transfer the project and GitHub repository to the client at delivery.

### What if the client already started their app alone with AI?

Offer a fixed-fee audit first: database security, exposed keys, payments, code structure. You'll then know whether the app can be fixed or whether it's better to restart from a clean spec. It's a market in its own right, as the vibe-code "fixers" described by 404 Media show.

## Sources

- [After AI led to layoffs, coders are being hired to fix vibe-coded screwups — Gizmodo](https://gizmodo.com/after-ai-led-to-layoffs-coders-are-being-hired-to-fix-vibe-coded-screwups-2000657915)
- [The Software Engineers Paid To Fix Vibe Coded Messes — 404 Media](https://www.404media.co/the-software-engineers-paid-to-fix-vibe-coded-messes/)
- [Terms of Service — Lovable](https://lovable.dev/terms)
- [Copyright Office Releases Part 2 of Artificial Intelligence Report — U.S. Copyright Office](https://www.copyright.gov/newsnet/2025/1060.html)
- [GitHub integration — Lovable Documentation](https://docs.lovable.dev/integrations/github)
- [Collaboration — Lovable Documentation](https://docs.lovable.dev/features/collaboration)
- [Regulation (EU) 2016/679 (GDPR) — EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj)

— Thierry Gustin, Formateur en intelligence artificielle (GustinAI) · November 21, 2026
