Quick answer: How do I validate a startup idea quickly?
- Day 1: one sentence: who has the problem, how often, and what it costs them.
- Days 2–4: 10–15 interviews about past behaviour, not your idea.
- Day 5: a one-page offer with a clear promise and a price.
- Day 6: send targeted people to it; ask for a sign-up, deposit or pre-order.
- Day 7: decide on evidence: pain, existing spend, commitments.
Key takeaways
- Validation is evidence of behaviour, not opinions: what people already do and pay for, and whether they'll commit now.
- Interviews about the past ('when did this last happen?') are more reliable than questions about the future.
- A price on the page tests value; free sign-ups only test curiosity.
- Seven days can kill a bad idea or justify a first build; it can't prove a business.
- Decide by criteria you set on day 1, so you don't move the goalposts.
Most startups that fail don't fail because they built badly. They fail because they built something people didn't need enough. A week of validation won't prove a business, but it can stop you spending six months on the wrong one, or give you real evidence to start. This day-by-day plan focuses on behaviour, not opinions: what people already do, what they already pay, and whether they'll commit to you now. Jump to the plan, interview questions or how to decide.
- Days
- 7
- Interviews with one target group
- 10–15
- Page with a promise and a price
- 1
- Kinds of evidence: pain, spend, commitment
- 3
The 7-day plan
- Day 1
Write the hypothesis
"[Who] struggles with [problem] [how often], which costs them [time or money]. They currently [workaround]." Set your pass criteria now.
- Days 2–4
Interview 10–15 people
People who have the problem, about their past behaviour. Record exact words.
- Day 5
Build a one-page offer
The problem in their words, your promise, how it works in three steps, a price, a call to action.
- Day 6
Test demand
Send it to interviewees and targeted communities; ask for a sign-up with intent, a deposit or a pre-order.
- Day 7
Decide
Score against your day-1 criteria: build, change the problem, or stop.
Day 1: the hypothesis and pass criteria
| Write down | Example |
|---|---|
| Who | Founders of 5–20 person design agencies |
| Problem | Chasing client approvals over email |
| Frequency | Several times a week |
| Cost | Hours a week; delayed invoices |
| Workaround | Email threads, shared folders, spreadsheets |
| Pass criteria | 8 of 12 describe it unprompted; 5 already pay for a partial fix; 10 sign-ups with intent or 3 pre-orders |
Table: A startup idea hypothesis with pass criteria (example)
Days 2–4: interviews about the past
| Ask | Don't ask |
|---|---|
| "When did this last happen? Walk me through it." | "Would you use an app for this?" |
| "What did you try? What did it cost?" | "Do you like this idea?" |
| "What's the worst part?" | "How much would you pay?" |
| "Who else deals with this?" | "Is this a good business?" |
Table: Interview questions that produce evidence
Find interviewees in your network, in communities where the problem is discussed (help first; read the rules) and among founders on Indie Hackers if your users are founders. For outside opinions on the pitch itself, roast my startup lists where to post.
Day 5: a one-page offer with a price

- The problem in their words — lifted from your interviews
- One clear promise — the outcome, not the features
- How it works in three steps — so it feels real
- A price — or a deposit; free sign-ups only test curiosity
- One call to action — pre-order, deposit, or "join the paid pilot"
Day 6: test demand
Send the page to everyone you interviewed and to two or three communities where the problem is discussed, with a short honest note: "I'm testing whether to build this; here's what it would cost." Count commitments, not visits.
Day 7: decide
| Signal | Strong | Weak |
|---|---|---|
| Pain | Most describe it unprompted, with emotion and detail | Polite agreement when you describe it |
| Existing spend | They pay for workarounds or tools today | "I'd probably pay" |
| Commitment | Pre-orders, deposits, paid pilots, specific follow-ups | Likes, compliments, vague sign-ups |
Table: How to read validation evidence
- Most strong: build the smallest version for the people who committed.
- Pain but no commitment: sharpen the offer or price, or find who pays.
- No consistent pain: narrow or change the problem; run the week again.
After validation

Once a first version is live, a free Science of Apps Launchpad profile gives it a permanent page people find by the problem you validated, and your product is tested end to end with a detailed report, so your committed early users get a product that works.
Validation mistakes

- Interviewing friends — they don't have the problem, and they're kind
- Pitching instead of listening — people become polite
- No price — interest without commitment isn't validation
- Moving the goalposts — set criteria on day 1
- Building during validation — build after people commit
How we know
The plan is our editorial framework, consistent with common customer-discovery practice: behaviour over opinions, past over future, commitment over praise. Platform references were checked on 16–17 November 2026. Science of Apps runs the Launchpad mentioned above.
Key terms, defined
- Validation: evidence that people will use or pay for a solution.
- Hypothesis: a testable statement of who has a problem and what it costs them.
- Commitment: a real action such as a pre-order, deposit or paid pilot.
- Workaround: what people do today instead of your product.
- Pass criteria: the evidence you decide in advance will mean "build".
Frequently asked questions
How do I validate a startup idea quickly?
Spend a week on evidence: define who has the problem, interview 10–15 of them about how they handle it today, publish a one-page offer with a price, send targeted people to it, and count real commitments such as sign-ups with intent, deposits or pre-orders. Decide using criteria you set at the start.
What counts as validation?
Behaviour, not praise: people describing the same painful problem, already spending time or money on workarounds, and committing to your solution with something real, such as a pre-order, a deposit, a paid pilot or repeated use of a prototype.
How many interviews do I need?
Usually 10–15 with one target group is enough to see whether the problem repeats. If every interview describes a different problem, narrow the group rather than doing more interviews.
Should I build an MVP to validate?
Not first. A one-page offer, a clickable prototype or a manual service can test demand faster and cheaper. Build once people commit.
Can I validate an idea without spending money?
Mostly, yes. Interviews, a simple landing page and outreach in communities cost time, not money. Small paid tests can help but aren't required in the first week.
What if validation fails?
That's a good result: you saved months. Look at what you learned (often a different, sharper problem appears in interviews) and run the week again on that.
Sources
- Indie Hackers — Homepage
- Reddit — r/roastmystartup, top posts of the month (via ScrapeCreators, retrieved 17 Nov 2026)
- Product Hunt Help Center — What kind of products get featured (checked 17 Nov 2026)
- Science of Apps — Launchpad: launch your product free
- Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- How to validate an app idea — app-specific validation
- How to get feedback on your idea — ten places and the right questions
- How to launch a startup — what comes after validation
- How to make an appHow to validate an app idea before you write a single line of codeValidate an app idea in two weeks without code: problem interviews, demand signals, landing-page and fake-door tests, pre-sales and a concierge MVP.
- Career guidesHow to validate a business idea in 2027: problem interviews, riskiest assumptions, landing page and pre-order tests, concierge MVPs, pricing signals, success criteria and deciding whether to buildHow to validate a business idea in 2027: problem interviews, riskiest assumptions, landing pages, pre-orders, concierge MVPs, pricing signals and decisions.
- Science of Apps - LaunchpadHow to launch a startup in 2027: from a validated problem to a working product, a public launch and your first customersHow to launch a startup in 2027, step by step: validate the problem, build a small product, test it, publish a permanent page, launch and win first users.
- Science of Apps - LaunchpadHow to launch a SaaS product in 2027: from private beta to public launch to the first paying customersHow to launch a SaaS in 2027, step by step: private beta, pricing, onboarding that activates, a permanent page, launch days, and turning trials into customers.
- Science of Apps - LaunchpadProduct launch strategy for 2027: how to plan, run and follow up a launch that brings users, not just a spikeA product launch strategy for 2027: set goals, size the launch, build a permanent page, sequence launch days, run launch week and follow up, step by step.
- Science of Apps - LaunchpadThe startup launch checklist for 2027: everything to do before, during and after launch, in orderA startup launch checklist for 2027: product, page, visibility, assets, launch-day and follow-up items, in order, with the platform rules that matter.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
Launch day ends. Your listing shouldn't.
Once the idea is validated and a first version is live, list it free: a permanent page people find by the problem, plus your product tested end to end with a detailed report.





