You have an idea. It feels good. Now you have to decide whether to spend the next three weekends on it, or let it go. That decision is the whole game, and most of us make it on a feeling.
This checklist is a way to slow that feeling down for about twenty minutes and pressure-test it. It has three lenses: real demand, a defensible edge, and an honesty test against your own wishful thinking. It is opinion with criteria, not a crystal ball. Nothing here predicts success. It just stops you from building the obviously wrong thing before you have written a line of code.
Copy the questions, answer them for your idea, and you will end with a clearer go, revise, or shelve.
The Real Cost Of Building The Wrong Thing
The cost is not the money. For most software ideas the money is small. The cost is the weeks, and worse, the momentum. Every abandoned project makes the next one harder to start, because a quiet part of you starts expecting to abandon it too.
So the goal of a build decision is not to guarantee a win. It is to make sure that if the thing fails, it fails because of something you could not have known, not something you refused to look at up front. This checklist is about looking.
Grab a blank note. Write your idea in one plain sentence: who it is for and what it does for them. If you cannot, that is your first signal.
Lens 1 — Demand: Is Anyone Actually Asking For This?
Demand means someone already feels the pain and is doing something clumsy about it today. Not "would this be cool." Answer these:
- Who specifically has this problem? Name a real group you could point at, not "small businesses" or "people." If you cannot name ten of them you could message this week, the audience is a guess.
- What are they doing right now instead? A spreadsheet, a manual workaround, a competitor, duct tape. If the honest answer is "nothing," they may not feel the pain enough to pay attention.
- Have you heard anyone complain about this unprompted? In a forum, a group chat, a support thread. Your own annoyance counts as one data point, not proof.
- Would they switch? Even a good solution loses to an okay habit. Is the pain big enough that someone would change what they do?
- Can you reach them? A real channel: a subreddit, a newsletter, a community you are already in. An idea with demand but no reachable audience is a marketing problem you have not solved.
If most of these are honest yeses, demand is plausible. If you are inventing the customer in your head, mark this lens as a no.
Lens 2 — Edge: What Makes This Hard To Copy Or Worth Choosing?
Edge is why a person picks you, and why they keep picking you after a bigger team notices the space. It does not have to be a patent. It usually is not. Ask:
- What is your unfair starting point? A community you already have, deep knowledge of the problem, a distribution channel, a dataset, taste. Something you have that a stranger would need months to build.
- Why you and not the incumbent? If a well-funded tool could add this as a checkbox feature next quarter, your edge is speed and focus, which is real but temporary. Know that.
- What gets stronger the longer you run it? Content that compounds, a network that gets more useful with each user, a reputation, proprietary data. If nothing compounds, you are on a treadmill.
- Is "worth choosing" enough here? Sometimes the edge is simply being the one person who cares enough to make a nicer, more honest version. That is a legitimate edge in crowded, low-love categories.
A weak edge is not an automatic no. Plenty of good small businesses run on focus and care. But be honest about which kind of edge you have, because it changes how you build and how fast you need to move.
Lens 3 — The Honesty Test: Are You Excited By The Idea Or By The Fantasy?
This is the lens people skip, and it is the one that quietly sinks projects. You are not testing the idea here. You are testing yourself.
- Would you still want to build it if no one ever congratulated you for it? If the appeal is the launch tweet, the "founder" label, or imagining the exit, you are excited by the fantasy, not the work.
- Do you like the actual daily task? Support emails, bug reports, marketing the same thing for the hundredth time. That is the job. The idea is one percent of it.
- What would have to be true for this to fail, and does that feel likely? Say it out loud. If you find yourself arguing with your own doubts instead of noting them, you are protecting the fantasy.
- Are you the right person for this, or the available one? Sometimes we build a thing because it is the idea we have, not the one we are suited to. That is fine to admit.
- Is this a business or a feature? Honest answer. A feature can still be worth building for yourself or as a wedge, but naming it stops you from expecting business-sized results.
The point is not to talk yourself out of everything. Grounded optimism means you can be genuinely excited and still willing to be wrong. Both at once.
Scoring It: Green-Light, Revise, Or Shelve
Give each lens a plain rating: strong, mixed, or weak. Then read them together, not as a total.
| Pattern across the three lenses | What it usually means | Move |
|---|---|---|
| Demand strong, edge at least mixed, honesty test clean | Worth a real, time-boxed attempt | Green-light |
| One lens weak but fixable (e.g. edge unclear, demand real) | The idea might be right, the shape is wrong | Revise and rerun |
| Demand weak, or honesty test fails | You are building for yourself or the fantasy | Shelve |
Revise looks like narrowing the audience, changing the wedge, or cutting scope until one lens gets stronger. Then run the checklist again. Two or three loops is normal and healthy.
Shelve is a real, respectable outcome. Honest optimism includes the willingness to say no to a mediocre idea so you have room for a better one. Write one line on why you shelved it and keep the note. Ideas come back, and future-you will want the reasoning.
No score here promises anything. A green light means the idea has cleared the obvious traps, so the remaining risk is the interesting kind you can only learn by building.
In Plain English
What this is: a twenty-minute, reusable checklist to decide whether an idea is worth your weekends, built on demand, edge, and self-honesty.
Who it helps: founders, indie hackers, and side-project builders who are tired of half-finished repos.
When to use it: before you build, and again whenever an idea shifts shape.
What to do next: run all three lenses, score them, and act on the pattern. If it is a green light, do not admire the plan any longer than it takes to start.
You've Got A Green Light — What To Do Next
A passing idea deserves a fast, small first swing, not a six-month roadmap. Keep the momentum: our honest weekend build playbook walks through shipping a first version in a couple of days, and the Now Go Build It starter stack covers the tools worth reaching for so you spend your time on the idea, not the setup.
If you want to see how other people run this decision in practice, the Builders & Makers hub and the pillar on people quietly building a better future collect real builders and the honest, dated tools they use. The Directory is where we curate more of them.
Download the checklist — grab the reusable "is this worth building?" template, keep it in your notes, and rerun it on every idea before it eats your calendar.