How to sell a vibe coded app (and what to charge for it)

There’s a folder on your laptop, or a repo on your GitHub, with something in it that works. You built it for yourself, or for a challenge, or because you couldn’t sleep. And somewhere out there is a person who would happily pay to skip the fifty hours you spent getting it right.

This guide is about finding that person and making it an easy yes.

What buyers are actually paying for

Not the code. Code is cheap now, and they know it. They could open the same AI tool you did. What they can’t buy anywhere else is:

• Time. The evenings of describing, testing, rewinding and fixing that you already spent.
• Decisions already made. The layout that works, the database shape that holds up, the twenty small calls that make it feel finished.
• Proof it works. A live demo they can click beats any feature list.
• Not having to think. Clear setup instructions are worth more than an extra feature.

Keep that list in mind. Every choice below is really about one of those four things.

Three things you can sell

What you sell	What the buyer gets	Good for
A template	A polished starting point they make their own	Landing pages, dashboards, directories, portfolios, starter kits
The source code	Your whole working app to run and change as they like	Niche tools, internal tools, games, anything with clever logic
The whole thing	The app, the domain, the users and any income, handed over	Apps that already have users or revenue

Most first sales are templates. They sell more than once, and buyers are used to them. Selling the whole thing is closer to selling a small business. It’s rarer and pays more, and the buyer will (rightly) want to see the numbers.

How to price it

There’s no formula, but there are three honest anchors:

1. The hours it saves. Count the hours it would take a capable person to rebuild it, including the dead ends. Then price at a small fraction of what those hours are worth. Buyers should feel they’re getting a bargain, because they are.
2. What similar things sell for. Look at what comparable templates and starter kits go for, and position yourself against them. Cheaper if yours is simpler, more expensive if it does more and looks better.
3. The licence. One price for “use it on one project”, a higher one for “use it on as many projects as you like”, and a much higher one for “I’ll never sell this to anyone else”.

Package it like you mean it

Most sales are lost in the packaging, not the product. Before you list anything:

• A live demo with realistic sample data. Nobody buys an empty dashboard.
• Screenshots of the best three screens, on a phone as well as a laptop.
• A one-paragraph pitch that says who it’s for, not what it’s built with. “A booking page for small studios that takes deposits” beats “A Next.js app with Supabase”.
• A setup guide that a beginner could follow, start to finish, without messaging you. Have a friend try it. Fix every place they get stuck.
• A list of what’s included and what isn’t. Surprises after purchase become refund requests.
• An honest build story. Which tools you used, how long it took, and what you’d improve. Buyers trust makers who admit trade-offs.

Clean it up before you sell it

A buyer is about to read your code, possibly with their own AI looking over their shoulder. Before you list:

• Remove every API key, password and personal detail from the code and from its history. If a key was ever committed, change the key.
• Delete the dead files and experiments the AI left lying around.
• Make sure it runs from a fresh download, on a machine that isn’t yours.
• Run through our vibe coding security checklist. A template with a security hole will come back to haunt you, and a buyer who finds one will tell people.

Where to sell

You can sell anywhere you can reach buyers: your own site, template marketplaces, or directly to people who’ve seen your work. What matters most is that buyers can see the thing working and can trust the person selling it.

That’s the bet behind Vibers. Every project you post can be offered three ways: to look at only, as a free download, or as a paid download. Paid downloads sit on a real project page, with the build story, the tools, the upvotes and your other work right next to them. Payment sits in escrow until the buyer confirms they’ve got what they paid for, so neither side has to trust a stranger.

Mistakes that kill sales

• Selling something that only runs on your machine. Test it on a clean setup.
• “Built with AI” as the headline. Every listing says that now. Lead with who it’s for and what it saves.
• No support plan. Say up front what help is included, and for how long.
• Vanishing after the sale. Your second sale comes from your first buyer’s review.
• Never updating it. Tools move quickly. A template that worked with last year’s version of everything sells less every month.