Finding an Idea That Sells

Let me show you your notebook two weeks from now. Ten ideas are written down, and nine of them are crossed out. The remaining one has a circle around it, and next to it is written: "Found people already spending money and time on this problem. Community reaction confirmed. Competitors' pain points confirmed."

That state is this course's destination. Not a vague "I want to try something", but one idea with evidence attached. The most expensive mistake in founding is spending a long time building something nobody wants, and this course stops that mistake before it is made.

And it is fine if you have zero ideas right now. This course is designed to start empty-handed. In fact, empty hands are often an advantage. With no attachment, you look at the evidence more honestly.

Let's break a common myth first. Good ideas come not from a genius's flash of insight but from concrete problems. The person who waits for the flash never starts, while the person who hunts for problems starts this week.

The typical shape of a real case goes like this. Someone wanted to travel every weekend but had nowhere to leave their dog, repeating the same searching and favor-asking every time. One day it hits them: "I can't be the only one." The idea of a weekend pet-sitting marketplace was not invented that way. It was discovered.

Discoveries like this are hiding in your daily life too. The first part of this course is the work of drawing them out systematically.

There are four wells for finding problems. First, inconveniences you personally ran into this week. Second, tedious tasks that repeat in your work or hobbies. Third, things people frequently ask or request of you. Fourth, things you would gladly pay someone else to do for you.

Open your notes app now and draw ten items up from those four wells. One rule: do not judge. Even if you think "this is too trivial", write it down anyway. Evaluation is a later step's job. Right now, quantity is everything.

The mistake beginner founders make most is building something for everyone. Something for everyone is, in the end, something nobody desperately wants. So we go in the exact opposite direction. We start by drawing one single, very specific customer.

Pick one candidate from your list that pulls at you, and write four things about one person who has that problem. Who they are (age, job, situation), in what moment they meet this problem, why the problem hurts, and how they are coping right now. That last item matters most. Your real competitor is not another service, it is the spreadsheet, the group chat, and the "just putting up with it" your customer uses today.

Now we leave the desk and go into the field. The first field is the Community. Open it with Try it now below and observe three things. Which builds attract reviews and comments, what the top-ranked results have in common, and what shows up in "is there anything like this?" request posts.

The purpose of observing is not chasing trends but collecting evidence of demand. If people are reacting to topics that touch your candidates, that is a piece of evidence. Record the temperature of the reactions too. A passing "nice" and "where can I try this?" carry different weight.

The second field is the Funding Market. This is the place with records of actual money moving, not just reactions. Open the Funding Market with Try it now below, pick one campaign that gathered backing, and dissect it. What problem does it touch, what does it promise on the first screen, how are the early bird passes designed, what comments do backers leave?

The purpose is not copying but pattern reading. Once you discover the skeleton that successful campaigns share, you can lay your own idea on top of that skeleton.

The third piece of research is the competition. The Studio has not only web pages and apps but a build type called question. You ask what you want to research and it produces an organized answer. Press Try it now below and an example question is pre-filled: asking what customers complain about most in existing meal-plan subscription services.

Run it as is, then swap in your own candidate and ask again. The complaints of competitors' users are a gold mine for a founder. Complaints are the gaps in existing products, and gaps are exactly where you dig in.

The evidence is in, so now we narrow. Apply three criteria to your ten candidates. First, is the problem vivid? Do three faces of people who have it come to mind? Second, are there traces of demand? Did you find evidence in the Community, the Funding Market, and the competitive research? Third, can you build an MVP within a month? Is it small enough to build one core flow in the Studio?

Cross out any candidate that fails any of the three. Usually only two or three of the ten survive, and that is normal. If nothing survives, go back to the wells and draw up more. That back-and-forth is not waste, it is training.

Turn a surviving candidate into a one-page plan, the one-pager. Four boxes are enough. Problem (who hurts, and in what moment), customer (who is that one person), solution (what you will build and how it solves things), revenue (how the money comes in).

Press Try it now below and an example is pre-filled in the Studio: a prompt asking for a one-pager for a weekend pet-sitting marketplace. Run it, get familiar with what a finished one-pager looks like, then make one for your own candidate the same way.

Before it is a document to show others, a one-pager is a tool for finding the holes in your own thinking. If one of the four boxes will not fill, that box is exactly what you research next.

An eye for cutting matters as much as an eye for narrowing. If you see the following signs, let that idea go without regret. It takes more than three sentences to explain. You cannot name who would pay for it. You search and search and find no trace of demand. You catch yourself saying "once people are educated, they'll feel the need."

That last sign is especially dangerous. Educating a market into demand is a job even large corporations struggle with. A solo founder should float their boat on a stream of demand that already exists. Leave digging new channels for a later opportunity.

This is the finish line of the course. Time to bring everything you learned and draw a circle around one idea of your own. Complete the mission below, and when you are done, open the reveal to check the criteria.

There is no need to rush. If you cannot finish today, continue tomorrow. What matters is one principle: never draw the circle without evidence.

If you drew the circle, it is time to step out of solitary conviction. Post your one-pager to the Community. And show it to three people you know who actually have the problem. Every reaction is material for the next stage.

How you ask matters. Ask "would you buy this?" and most people politely answer "sure." Ask about the past instead. "How are you solving this problem right now?" "Have you spent money or time on this recently?" Past behavior is far more honest than future promises.

Let's recap. You started from an annoyance list, gathered evidence in the Community, the Funding Market, and competitive research, narrowed ten down to one, made a one-pager, and even got feedback. An idea chosen on evidence rather than hunch, that is this course's harvest.

The next course is "MVP Deep Build: Planning Is Half". You finally turn the circled idea into a working product. Be sure to bring your one-pager. That single page becomes the backbone of your Deep Build prompt.