Decide if the idea is worth building
At this point, you have a problem, a starting customer, a market map, and a first product direction. Now you need to decide whether the idea is strong enough to keep going.
Not every good idea is a good product. Not every painful problem is a good business. And not every "people would use this" idea has a believable path to revenue.
By the end, you should have:
- a simple viability score
- the biggest risks
- what still needs validation
- whether the idea is worth building now
- whether to keep shaping, pause, or move forward
1. Check the pain
Start with the obvious question: is the problem painful enough?
A problem can be real and still not urgent. People might complain about it, bookmark solutions, or say "this is interesting" without ever changing their workflow or paying for something new.
You're looking for signs that the pain already costs them something: time, money, missed revenue, mistakes, customer trust, team confusion, or mental energy they are tired of spending.
If the pain is mild, the product needs a very easy path to adoption. If the pain is expensive or frequent, you have more room to ask people to change behavior.
2. Check the customer
A viable product needs a customer you can actually understand and reach.
If the customer is still "small businesses," "busy professionals," or "teams that want to be more productive," you are not ready yet. That is too broad to build for, write for, price for, or validate with.
Your starting customer should be specific enough that you can name real people, find where they spend time, and explain why this problem matters to them now.
A great idea with an unreachable customer is not a starting point. It is homework.
3. Check the alternative
Your customer is already doing something today.
They might be using another product, a spreadsheet, a manual process, an internal tool, an agency, or ChatGPT. Your app needs to be meaningfully better than that alternative, not just newer or nicer-looking.
This does not mean you need to beat every competitor on every feature. Please do not try. That is how tiny products become bloated and sad.
It means you need a clear reason someone would switch, try, or pay attention.
| Weak reason | Stronger reason |
|---|---|
| It has a better UI | It removes a painful manual workflow they deal with every week |
| It uses AI | It helps them get to the answer faster without reading 200 tickets |
| It is cheaper | It gives early-stage teams the workflow they need without enterprise pricing |
| It has more features | It solves one specific job better for one specific customer |
The alternative does not need to be terrible. It just needs to leave enough pain behind.
4. Check the path to payment
A product can solve a real problem and still be hard to monetize.
The person feeling the pain might not control the budget. The customer might love the idea but expect it to be free. The market might be used to low-cost tools, or the problem might be annoying but not expensive enough to justify another subscription.
You do not need final pricing yet, but you do need a believable reason someone would pay.
Ask whether the product helps the customer:
- save time
- make money
- reduce risk
- improve conversion
- retain customers
- avoid mistakes
- replace another tool or workflow
- make their team more efficient
If you can't connect the product to one of those, pricing will probably get weird later.
5. Check your edge
You do not need a giant moat on day one, but you do need a reason this should be you.
That reason could be customer insight, founder-market fit, distribution, speed, taste, workflow knowledge, access to a niche, or a point of view the market is missing.
"Because I can build it with AI" is not enough anymore. A lot of people can.
Your edge is the part AI cannot give you by default: judgment, customer context, taste, distribution, or a sharper understanding of the problem.
If you have none of those yet, that does not mean quit. It means go get closer to the customer before you keep building.
6. Make the call
Viability is not about proving the idea will definitely work. You cannot know that yet.
It is about deciding whether the idea is strong enough to keep shaping, test demand, and maybe build a first version.
Viability scorecard
Pain
- Strong signal: People already spend time, money, or effort solving it.
- Weak signal: People say it is interesting but do nothing.
Customer clarity
- Strong signal: You can name and find real people who match.
- Weak signal: The audience is still broad or vague.
Market gap
- Strong signal: Existing options leave a clear frustration behind.
- Weak signal: The gap is mostly a missing feature nobody asked for.
Path to payment
- Strong signal: The problem connects to money, time, risk, or efficiency.
- Weak signal: The value is nice-to-have or hard to price.
Edge
- Strong signal: You understand the customer, workflow, or distribution better than most.
- Weak signal: You are mostly building because the tool made it possible.
You are not looking for perfect. You are looking for enough signal to justify the next step.
Prompt
This prompt is not here to hype you up. It's here to pressure-test the idea before you build too much.
Viability check
Take all of my notes and organize them into a viability check for my app idea.
Please structure it into:
1. Core problem
2. Starting customer
3. Current alternative or workaround
4. Market gap
5. Path to payment
6. My possible edge
7. Biggest risks
8. Assumptions I still need to validate
9. Overall viability score
10. Recommendation: move forward, keep shaping, or pause
Then score the idea from 1–5 on:
- pain level
- customer clarity
- reachability
- market gap
- willingness to pay
- differentiation
- founder edge
Please be direct.
Flag:
- where I'm being too optimistic
- where the pain seems weak
- where the customer is still too vague
- where the gap is not meaningful enough
- where the path to payment is unclear
- where I need more evidence before building
- what I should validate next
If this idea does not seem strong enough yet, tell me.
Before you move on
| Check | What to look for |
|---|---|
| The pain is too soft | If people are not already spending time, money, or effort on the problem, it may not be urgent enough. |
| The customer is still vague | A broad audience makes product, copy, pricing, and distribution harder. |
| The gap is just a feature | A missing feature only matters if customers actually care about it. |
| The payment path is unclear | "People would use this" is not the same as "people would pay for this." |
| You have no real edge yet | If your only edge is "I can build it with AI," get closer to the customer before you build. |
| You're forcing the idea | Some ideas need more shaping. Some should stay in the notes app. That is not failure, that is taste. |