Science of Apps - Launchpad · Playbook

How to validate a startup idea
in 7 days

You can validate a startup idea in seven days: day 1, write the problem and who has it; days 2–4, run 10–15 interviews about how they handle it today; day 5, publish a one-page offer with a price; day 6, drive targeted people to it and ask for a commitment; day 7, decide on evidence: repeated pain, existing spending and sign-ups or pre-orders, not compliments.

By , FounderUpdated 6 min read

Share

Quick answer: How do I validate a startup idea quickly?

  1. Day 1: one sentence: who has the problem, how often, and what it costs them.
  2. Days 2–4: 10–15 interviews about past behaviour, not your idea.
  3. Day 5: a one-page offer with a clear promise and a price.
  4. Day 6: send targeted people to it; ask for a sign-up, deposit or pre-order.
  5. 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

  1. 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.

  2. Days 2–4

    Interview 10–15 people

    People who have the problem, about their past behaviour. Record exact words.

  3. 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.

  4. Day 6

    Test demand

    Send it to interviewees and targeted communities; ask for a sign-up with intent, a deposit or a pre-order.

  5. Day 7

    Decide

    Score against your day-1 criteria: build, change the problem, or stop.

Day 1: the hypothesis and pass criteria

Write downExample
WhoFounders of 5–20 person design agencies
ProblemChasing client approvals over email
FrequencySeveral times a week
CostHours a week; delayed invoices
WorkaroundEmail threads, shared folders, spreadsheets
Pass criteria8 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

AskDon'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

Checklist: Day 5: a one-page offer with a price — The problem in their words; One clear promise; How it works in three steps; A price; One call to action.
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

SignalStrongWeak
PainMost describe it unprompted, with emotion and detailPolite agreement when you describe it
Existing spendThey pay for workarounds or tools today"I'd probably pay"
CommitmentPre-orders, deposits, paid pilots, specific follow-upsLikes, 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

Science of Apps Launchpad homepage with the headline Launch your product. Get it found.
The Science of Apps Launchpad: where a validated product gets a permanent page.Image: Science of Apps · © Science of Apps · source

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

Checklist: Validation mistakes — Interviewing friends; Pitching instead of listening; No price; Moving the goalposts; Building during validation.
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

  1. Indie Hackers — Homepage
  2. Reddit — r/roastmystartup, top posts of the month (via ScrapeCreators, retrieved 17 Nov 2026)
  3. Product Hunt Help Center — What kind of products get featured (checked 17 Nov 2026)
  4. Science of Apps — Launchpad: launch your product free
  5. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

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.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

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.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition