How to sell an app: a step by step guide

Decide what you are selling

An app sale is not one thing. A buyer might want the domain, the code, the users, the revenue, the brand, or simply the time it would take to build something similar. Before you list, decide which of those you can actually hand over, because the answer shapes your price, your listing and your handover.

Write the list down. For most vibe coded apps it looks like this:

• The domain name and its DNS settings
• The source code and the repository it lives in
• The hosting project and its deployment settings
• The database and the data in it, with user data handled carefully
• Third party accounts and services the app depends on
• The brand, the logo and the written content
• Existing customers and their billing
• Documentation, prompts and any build notes you kept

Next to each item, mark whether it is included, excluded or negotiable. Anything you leave off the list becomes a surprise later, and surprises cost you the deal.

Check that you are free to sell it

You can only sell what you own. If you built the app for a client, with a partner, or with code, images or content you do not hold the rights to, you cannot sell it alone. Sort that out first, in writing.

Read the terms of the tools you used. Some app builders let you export your code and move it to hosting you control. Others tie a project to their platform. If the app can only run inside the builder that made it, say so plainly in your listing, because it changes what the buyer is really getting.

Check the small print on dependencies too: template and font licences, API terms and any account that is personal to you. Some accounts cannot be transferred and the buyer will need to create their own. Finally, read your own privacy policy. If it does not allow user data to move to a new owner, fix that before you sell.

Put the app on its own custom domain

Every listing on Vibe Classifieds is one app on its own custom domain. That is not paperwork. A domain is a real identity you can prove you control, and it is the thing a buyer takes over. An app that lives on a shared subdomain belongs to a host's account, which makes ownership harder to show and harder to transfer.

If your app is not on a custom domain yet, register one, point it at the app, and let it settle for a few days before you list. Pick a domain you are happy to sell, and avoid changing it once the listing is public. The FAQ explains why the board works this way.

Get the app into a state you would want to buy

Buyers judge an app in the first few minutes. They will sign up, click around and look for rough edges. A little cleanup before you list pays for itself.

• Fix visible bugs and test the sign up, the main workflow and any payment flow end to end.
• Remove dead pages, placeholder text and broken links.
• Write a one page handover note: what the app does, how it is deployed, which settings it needs (names only, never the secret values), and where the data lives.
• List every recurring cost: domain, hosting, database, model usage, email and any subscription.
• Make sure no secret keys sit in the code or its history. If one ever did, rotate it.
• Note the known issues. An honest list builds more trust than a clean one that a buyer later finds incomplete.

Work out your price

Pricing a small app is a judgement, not a calculation, and there is no standard that fits every project. Revenue and how stable it is matter most, followed by growth, age, running costs, how much the app depends on you and how easily it can be handed over. Our valuation guide walks through each factor and shows how to build an asking price step by step.

Decide two numbers before you list: the lowest price you would accept, and the asking price you will publish. The gap between them is your room to negotiate. If you would rather trade, set the listing type to Swap and describe what you would take. If you just want the app to go to a good home, use Free.

Write a listing buyers can trust

A good listing answers the first ten questions a buyer would ask, so the first message they send is about the deal rather than the basics. Include:

• One plain sentence on what the app does and who it is for
• Current usage: users, traffic or customers, with the period you are describing
• Revenue, if there is any, labelled as self-reported
• The stack and where it runs
• What is included in the sale and what is not
• Monthly running costs
• How much time it takes to keep running each week
• Why you are selling
• Your asking price, or what you want in a swap

Only publish numbers you can back up with a dashboard export or analytics access, because a serious buyer will ask. Mention the weak spots yourself. They will find them anyway, and an honest seller is easier to trust.

Create the listing on Vibe Classifieds

Posting is free and takes a few minutes. Here is the sequence.

1. Open the post page and paste your app's URL. The site reads the public page and suggests a title, description and other fields. It never guesses your price, revenue or user numbers, so those are yours to fill in.
2. Review every suggested field and rewrite anything that is thin or wrong.
3. Choose the type (For sale, Swap or Free) and a category: SaaS, AI tool, Developer tool, Marketplace, Directory, Productivity, Game or Other.
4. Create a free account when asked. The listing is saved as private.
5. Prove you control the domain with a meta tag, a DNS TXT record or a text file at /.well-known/vibeclassifieds.txt. A listing that is not verified within 14 days is deleted.
6. Once the check passes, the listing goes public with the green Verified ownership badge.

A public listing lasts 45 days and renews in one click. The site periodically re-checks each listing and hides any whose domain stops loading, so keep the app online while it is listed. For more on the process, see sell vibe coded apps and where to sell my app.

Talk to buyers

Buyers message you privately inside the site. No email addresses are shown and there are no public comments. Reply quickly and specifically. Ask what they plan to do with the app, how they have run similar projects and how they expect to pay. A buyer with a clear plan is usually a better partner than one with the highest first offer.

Share sensitive material in stages. Public facts first, then analytics and revenue evidence once the buyer is serious, and never any logins before the money is secured. Be cautious with anyone who rushes you, pushes to leave the site early, asks for access to your accounts, or sends an unusual overpayment story. For a larger sale, consider a short confidentiality agreement and a conversation with a lawyer. This guide is general information, not legal advice.

Close the sale safely

The site never handles the money. Buyer and seller agree the price and arrange payment between themselves, and for any meaningful amount we recommend an escrow service. In outline: both sides sign the terms, the buyer pays into escrow, the seller hands over the assets, the buyer confirms everything works, and escrow releases the funds. Neither side has to trust the other with the full risk.

Put the agreement in writing. It should cover:

• The price and how it is paid
• The exact list of assets being transferred
• Dates for each step of the handover
• How long you will provide support after the sale
• What happens to existing customers and their billing
• Whether you may build something similar afterwards
• Who pays any transfer or escrow fees

The handover itself has a right order and plenty of small traps. Follow the app and domain handover checklist so nothing is missed. When the sale completes, take the listing down.

Selling an app built with Lovable, Bolt or a similar builder

Plenty of vibe coded apps start inside an AI app builder, and that is fine. The board does not care which tool you used. A buyer cares whether the app works and whether they can really take it over.

Expect questions like these, and answer them in the listing: Can the code be exported to a repository the buyer owns? Does the app depend on the builder's own hosting, database or sign in? Do plan credits or subscriptions stop when the project moves? Which account does the project live in today? Check the builder's current terms for how projects can be exported or transferred, and plan the move to accounts the buyer controls before you agree a date. An app that runs cleanly outside the builder is easier to sell than one that does not.

Mistakes that slow down or kill a sale

• Listing before the domain and the basics are in order
• Writing a vague listing with no numbers, no stack and no reason for selling
• Overstating revenue or users, which ends the conversation the moment a buyer asks for proof
• Pricing on the hours you spent instead of what the app gives a buyer
• Sharing logins early or moving the conversation off the site too soon
• Releasing the domain or code before payment is secured
• Letting the app break while it is listed
• Forgetting to remove the listing after the sale

Selling an app is a handoff, not a performance. Be clear about what you are offering, be honest about its limits, and let the right buyer find it.

Frequently asked questions