Save this part
The short version
- Describe the customer and outcome in one sentence before discussing features.
- Use human needs as a lens for motivation-not as proof of demand.
- Name the single emotion most likely to make someone act.
- Score pain, frequency, alternatives, willingness to pay, and emotional pull separately.
- Look for behaviour, complaints, searches, reviews, and spending before writing code.
This framework does not predict whether a startup will succeed. It answers a narrower and more useful question before you build: does a specific group care enough about this problem or outcome to take action?
Prefer the 60-second version?Watch the original startup idea and human-needs reel↗Step 01
Write the idea in one sentence
Do not begin with technology, features, or a pitch. Name what you are building, who it is for, and the outcome they want.
I am building ____________________ for ____________________ so they can ____________________.If the sentence still needs a paragraph of explanation, the customer, problem, or outcome is probably too vague.
Step 02
Find the human need behind the product
People rarely care about a feature in isolation. They care about what it changes: security, connection, confidence, progress, convenience, status, or relief. Maslow’s hierarchy can help you inspect that motivation, but it is a thinking tool-not market validation.
| Need | What the customer seeks | Example categories | Question to ask |
|---|---|---|---|
| Physiological | Health, rest, food, or another basic physical need | Food delivery, sleep tracking, grocery and health apps | Would someone notice a meaningful physical effect if this disappeared? |
| Safety | Certainty, protection, control, or peace of mind | Password managers, insurance, antivirus, expense and emergency tools | Does this reduce anxiety, financial loss, risk, or uncertainty? |
| Love & belonging | Connection, inclusion, intimacy, or community | Messaging, dating, communities, multiplayer games and events | Does this help people meet, stay connected, or feel included? |
| Esteem | Confidence, status, competence, recognition, or respect | Fitness, career, streak, makeover, headshot and appearance apps | Does this help someone feel more capable, attractive, successful, or respected? |
| Self-actualization | Growth, creativity, mastery, or meaningful achievement | Education, creative, productivity and language-learning tools | Does this help someone learn, create, improve, or achieve a long-term goal? |
A product can touch several needs. Choose the one most likely to drive the first purchase or repeated use for this specific customer.
Step 03
Name the core emotion
A product may contain twenty features, but the buying decision is often dominated by one feeling. Write the emotional outcome without describing how the product works.
- Uber: “I do not want to wait or feel stranded.”
- Canva: “I want to create something that looks good.”
- A height-prediction app: “I want reassurance, confidence, or to satisfy my curiosity.”
- A reminder app: “I want relief from worrying that I will forget.”
My product makes people feel ____________________.Write an emotion or desired state-not “productive,” “AI-powered,” or another feature-shaped answer.
Step 04
Score the idea out of 25
Give each dimension a score from one to five and write the evidence behind it. The score is not scientific; its job is to expose assumptions that enthusiasm can hide.
| Dimension | 1 means | 5 means |
|---|---|---|
| Pain | A mild inconvenience | People actively complain or experience a meaningful consequence |
| Frequency | Once a year or less | Daily or several times a day |
| Existing solutions | Excellent options already satisfy the customer | People still rely on frustrating workarounds |
| Willingness to pay | No spending or commitment evidence | Customers already pay or make costly tradeoffs |
| Emotional pull | Weak or unclear motivation | A strong human need repeatedly drives action |
Do not let a high total hide a fatal weakness. A five for emotion cannot compensate for an audience you cannot reach or a problem nobody will pay to solve.
Step 05
Find proof that people already care
Before writing code, look for observable behaviour from people who have the problem. Capture exact examples, dates, customer context, current solutions, and any evidence of spending.
- Reddit and communities: search phrases such as “I wish there was,” “How do I,” “Looking for,” and “Does anyone know.”
- TikTok and Instagram: search the problem and read comments for repeated questions, objections, and workarounds.
- Google: search “best [category] app,” “[problem] solution,” and comparison queries. Competition often indicates demand.
- Reviews: read recent one- and two-star reviews to find recurring failures, switching triggers, and unmet expectations.
- Marketplaces: inspect products for sale, existing pricing, customer counts, and business models without treating seller claims as independently verified.
No competition is not automatically an opportunity. Sometimes it means customers tolerate the problem or do not care enough to change.
Step 06
Pass the ten-second explanation test
Ask someone what the product does. If the answer depends on buzzwords, category jargon, or a feature tour, simplify it until the customer and outcome are obvious.
- Weak: “We use AI to revolutionize personal growth.”
- Clear: “It predicts your future height.”
- Clear: “It turns screenshots into searchable notes.”
- Clear: “It reminds you about things you always forget.”
Simple explanations travel faster because another person can repeat them accurately.
Step 07
Run the reality check before you build
Answer each question with evidence. A “no” does not always kill the idea; it identifies what you should validate before investing months in a product.
- Would I personally use or pay for this-and am I actually the target customer?
- Have I seen strangers asking for help with this problem?
- Can I identify at least twenty relevant people today?
- Can I explain the outcome without buzzwords?
- Does it connect to a real human need or emotion?
- Can I test the riskiest assumption without building the full product?
STARTUP IDEA
I am building ____________________ for ____________________ so they can ____________________.
HUMAN NEED
Primary need: Physiological / Safety / Love & Belonging / Esteem / Self-Actualization
Why this need matters in the customer’s current situation:
CORE EMOTION
My product makes people feel ____________________.
SCORE - 1 TO 5
Pain: __ / 5
Frequency: __ / 5
Gap in existing solutions: __ / 5
Willingness to pay: __ / 5
Emotional pull: __ / 5
TOTAL: __ / 25
EVIDENCE
Three examples of strangers asking for this:
1.
2.
3.
Current alternatives or competitors:
1.
2.
3.
TEN-SECOND EXPLANATION
It ________________________________________________.
NEXT STEP
The smallest test I can run before building is:
The evidence that would make me continue is:If most answers are “no,” do not overbuild. Narrow the customer, revise the promise, and run the smallest useful test first.
Final thought
People buy what they care about
Customers may care about saving time, avoiding loss, looking attractive, feeling capable, belonging to a group, or satisfying curiosity. The feature is the mechanism; the meaningful outcome is why they act.
The closer your explanation gets to a real situation and motivation, the easier the idea becomes to test, communicate, and market.
Common questions
Startup idea and human-needs FAQ
Can Maslow’s hierarchy validate a startup idea?
No. It can help identify the human motivation behind an idea, but validation requires evidence such as recent behaviour, repeated problems, existing workarounds, spending, commitments, and usage.
What startup idea score is good enough to build?
There is no universal passing score. Use the total to compare ideas and expose weak dimensions, then inspect the evidence behind every point. A high score should not override weak willingness to pay, distribution, or feasibility.
Does a simple startup idea have a better chance of succeeding?
Simplicity makes an idea easier to explain and test, but it does not guarantee demand. The product still needs a specific customer, meaningful outcome, reachable distribution channel, and credible evidence that people will act.
What should I do if nobody is asking for my idea?
Check whether you are searching in the right community and language. If the problem still produces no complaints, workarounds, searches, spending, or commitments, narrow or revise the idea before building a large product.
Found something worth remembering?
Save the useful idea in Offload with the context that made it matter. Ask for it naturally when you’re ready to use it.
Try Offload free