How to sell an app idea (and what buyers actually pay for)

Can you actually sell an app idea?

Rarely, and the pages that promise otherwise are usually selling something: a development service, a course, or a listing fee. A buyer of an app idea is buying a guess. They cannot check it, they cannot protect it, and they would still have to pay for all of the work that turns it into a product. The work is the expensive part.

That does not mean your idea has no value. It means the value shows up only after you attach something to it. Think of the idea as the first row of a ladder. Each rung you add makes a buyer, partner or builder more willing to talk.

Why do buyers pass on a bare idea?

Four reasons repeat, and each one tells you what to fix.

• The law does not protect it. The U.S. Copyright Office says that copyright does not protect ideas, concepts, systems or methods of doing something. A buyer who walks away from your pitch can build a version of it without breaking copyright. The guide to protecting an app idea covers what you can protect and how.
• It cannot be checked. Anyone can claim an idea is good. A buyer cannot tell the difference between your idea and fifty similar ones without evidence that people want it.
• The same idea occurs to many people. If it is obvious to you, it is probably obvious to others. A buyer would rather back the person who has already started.
• Execution is the cost. Design, engineering, hosting, support and marketing are most of the effort. The idea is a small share of it, so an idea buyer expects to pay a small share, which is close to nothing.

The useful reading of this is not “my idea is worthless”. It is “my job is to reduce the buyer’s risk”. The next section lists the cheapest ways to do that.

What can you sell instead of the idea?

Pick the rung that matches your time, skills and budget, and climb at least one before you pitch anyone. Each rung below is something a stranger can look at.

1. Evidence of the problem. Interview 5 to 10 people who have it and write down what they did the last time it happened. The guide to validating an app idea has the questions. Keep the notes; they are the first thing a serious partner asks for.
2. A one-page brief. Name the person, the problem, what exists today and the one workflow of the first version. The brief template in what to do with an app idea is a good start.
3. Market research. Show who else solves the problem and where they fall short. See the guide to app idea market research.
4. A clickable prototype. An AI coding agent can turn a clear description into a working demo in a few days. The guide to making an app prototype and the Claude Code walkthrough show how. A demo turns “imagine this” into “try this”.
5. Signs of demand. A landing page that describes the product and collects email addresses, or a small paid pilot, gives you numbers from strangers. Friends who say “nice idea” are not demand.
6. A first user who pays or commits. One paying customer, even at a low price, changes every conversation after it.

You do not need all six. Rungs 1, 2 and 4 together cost little more than time, and they are enough to start real conversations with builders.

Where can you find someone to take the idea?

The right channel depends on what you have on the ladder and on what you want back. Money, a share of the product, and credit are three different goals.

If you want money specifically, the honest paths are the third row, where a working app sells, and the first two rows, where you earn a share by doing real work. A buyer who offers to pay a fee for a bare idea, especially one who asks you to pay first for a listing, valuation or “protection package”, is the one to be careful with.

How do you pitch an app idea to a builder?

Short beats clever. A builder decides in about a minute whether to reply, so lead with the person, the problem and the proof, and ask for one small thing. Do not attach a long document to a first message. Do not ask for an NDA before saying anything useful; the guide to protecting an app idea explains why.

Subject: [One-line description of the product], looking for a builder

Hi [Name],

I saw [specific thing you saw them build or write] and thought you might be the right person for this.

The problem: [Person] has to [annoying task] and today they [what they do now]. I spoke to [number] of them and [number] described the same last-time story.

The product: [One sentence. What goes in, what comes out.]

What I have so far: [Interview notes / clickable prototype / waitlist of N signups. Only list what exists.]

What I bring: [Domain access, the first users, design, marketing, budget, time.]

What I am asking: a 20-minute call to see whether this is interesting to you. If it is not, I would still value one piece of feedback on what is missing.

Thanks,
[Your name]

Notice what the email does not do. It does not call the idea revolutionary, it does not mention a price for the idea, and it does not hide the idea behind secrecy. It shows that you did the work that is yours to do.

How are deals around an app idea structured?

When a deal happens, it almost always pays for work or for a working product, not for the bare concept. These are the usual shapes. The right one depends on who contributes what over what period of time.

Put every agreement in writing before work starts. In some places, courts have treated an idea that was pitched for sale, on the understanding that it would be paid for if used, as a possible implied contract (the California decision Desny v. Wilder is the usual reference). Outcomes depend heavily on the facts and the jurisdiction, and a written agreement is far easier to enforce than an understanding. Ask a lawyer before relying on any of it.

What if you will not build it and nobody buys it?

Then the choice is between leaving the idea in a notes app and handing it over. A builder who finds a clear, well-described idea may take it on without a payment, and you get something money cannot buy: the product exists.

On Post your build ideas you type a name, a title and the idea, and publish it, with no account and no email. Every idea gets a generated build prompt that a builder can paste into Claude Code, Cursor or Lovable. The trade-off is plain: you give up control, publishing is permanent, and there is no payment. Read how others phrase theirs on the board first; Photograph a parking sign and know if you can park here names one situation, one input and one answer. Some ideas on the board were posted by the site’s operator to seed it, so treat them as examples of how to write, not as proof that people want the product.

If you are not sure whether the idea is ready, run it through the free Idea Checker. It points out what a stranger would need to know and does not claim to judge demand.

What should you do before sharing the idea with anyone?

• Decide what is actually secret. Ideas are rarely secret. Customer lists, your own data and unreleased code can be. Share the first, guard the second.
• Write down the date and what you shared. Keep the emails. A record helps if a dispute arises.
• Never pay to be “matched” or “protected”. Real partners come from work and conversation. Be wary of anyone who charges a fee to introduce you to buyers or to “register” an idea.
• Do not promise yourself an income. Most people who post or pitch an idea receive feedback, not money. Plan on that.