How to Validate a Startup Idea in 7 Days (Free Framework)

Most startup validation advice falls into two failure modes. The first is academic — frameworks full of Innovation Funnels and Strategic Canvases that take three months to fill out and produce a slide deck no one reads. The second is dangerously vibes-based — "just ship and see what happens" — which works for the rare founder with great instincts and burns everyone else for six months on something nobody wanted.

After running every idea in our database through the same validation gauntlet, we built a 7-day version. It produces a real go/pivot/kill decision in a week. No code. No funding. No slide decks. Just enough signal to know whether the idea has a pulse.

Day 1: Find the painful version of the problem

Every startup idea, when you first say it out loud, sounds like a solution looking for a problem. "I'm building an AI scheduling tool for SMBs." Cool. Who specifically? With what pain? At what cost today?

Spend Day 1 sharpening the problem statement into something defensibly painful. The template:

[Specific person] currently does [specific painful thing] because [reason]. They'd pay [specific amount] to make it stop, because [stakes].

If you can't fill in every blank with a real human you could name, the idea isn't ready for validation yet. Go back to the database and study how founders in similar categories framed their problem.

Day 2: Find 10 strangers with the problem

Friends and family will lie to you. They want you to succeed. Strangers will be honest because they don't care about your feelings.

The 10-stranger rule:

• Reddit + niche subreddits: search for the problem phrasing, find people complaining about it within the last 30 days, DM them.
• X/Twitter: search exact-match queries like "wish there was a way to" or "why is X so hard" + your domain.
• LinkedIn search: filter by job title, send a connection request with one sentence: "Researching [problem] — could I ask you two questions?"
• Discord servers + Slack communities: read the #questions or #help channels for recurring complaints.
• Indie Hackers + niche forums: people self-identify as having pain.

Goal by end of Day 2: 10 strangers who've agreed to a 15-minute call this week. Yes, cold outreach works. Yes, most people will ignore you. You only need 10.

Day 3: Run customer interviews (with this script)

Don't pitch your idea. Don't mention your solution. Your goal is to learn whether the problem is real, what they currently do about it, and how much it costs them.

The script that works:

1. "Walk me through the last time you ran into [problem]." — story, not opinion
2. "What did you do about it?" — current workaround
3. "What does it cost you in time/money/headcount?" — quantification
4. "Have you tried anything to solve this?" — existing tools, what failed
5. "If you could wave a magic wand, what would happen?" — desired outcome

Five of these conversations and you'll know if the problem is real or imagined. The signal you're hunting for: two or more people independently described the same workaround. That's the shape of unmet demand.

Day 4: Build a landing page (in 2 hours)

No code. No backend. Just a single-page website that describes the product as if it already exists, plus an email capture. Use Carrd, Framer, or a free template. The page needs:

• Headline: the specific outcome, not the mechanism ("Stop losing 4 hours a week to manual scheduling" beats "AI-powered scheduling tool")
• One paragraph of context: who it's for, why now
• 3 bullet outcomes: what changes in their life when this exists
• Email signup with a credible promise: "Get access when we launch in 4 weeks"
• Price anchor (optional but powerful): "$39/mo at launch" — filters tire-kickers

Don't skip the price anchor unless you have a strong reason. People who give you their email after seeing a price are 5x more qualified than people who give it for free.

Day 5: Drive 100 visitors

You need real eyeballs to test signal. 100 targeted visitors is enough to show whether the proposition resonates. Five places to get them in a day:

• Post in 2–3 relevant subreddits with the "I built this because [pain story]" framing — value-first, link at the end
• X/Twitter thread walking through the problem, soft mention at the end
• Indie Hackers "Show IH" post
• LinkedIn post if you have a relevant audience
• $25 in Reddit/Meta ads targeting the niche (only if you can't hit 100 organically)

Set up basic analytics (Plausible, PostHog, or even Google Analytics) before you launch. You want to see traffic source, time on page, scroll depth, and signups.

Day 6: Read the signal

Three numbers matter:

1. Visit → signup conversion. Below 1% = weak signal. 1–3% = decent. 5%+ = strong, especially with a price anchor.
2. Signups → reply rate. Email the signups asking one question ("Why did you sign up?"). 25%+ reply means engaged audience.
3. Pre-orders or deposits. The gold standard. If even 3 strangers paid $1 to lock in early-bird pricing, you're not in idea territory anymore.

Day 7: Decide — go, pivot, or kill

Pick one. No middle ground.

• Go: ≥3% landing page conversion, ≥25% interview reply rate, at least 2 humans independently described the same workaround. Start building the smallest possible MVP next week.
• Pivot: the problem was real but your framing was wrong, OR a related but distinct problem kept coming up in interviews. Adjust positioning, repeat Day 1–6.
• Kill: low conversion, no interview replies, no recurring workarounds. The idea doesn't have a pulse. Walking away now saves you 12 months.

Common objections

"What if my idea needs a working product to validate?"

It probably doesn't. 95% of B2B and SaaS ideas can be validated with a landing page and interviews. The exceptions: hardware, regulated industries (some health/fintech), marketplaces with strong network effects. For those, replace the landing page with a concierge MVP — manually doing the work for 3 early customers — and budget 30 days instead of 7.

"What if I'm too early to a trend?"

Then your landing page conversions will be weak and your interview pool will be thin — which is itself useful signal. Either you're wrong about timing (kill) or you're right and need to wait 6–12 months (park the idea, build something adjacent now).

"What if 7 days isn't long enough?"

Stretch it to 14 if you have a day job. The point isn't the exact timebox — it's the discipline of forcing a real decision instead of letting it drift for months. Founders who can't decide in 14 days usually can't decide in 14 weeks either.

Don't skip validation because you're excited

Excitement is the single most expensive feeling in startups. It convinces you to skip the boring work of talking to humans because obviously the idea is good. That excitement is also what 95% of failed founders had. The 5% who made it weren't less excited — they just ran the validation anyway.

Every case study in our database that hit $1M+ ARR ran some version of this loop. Pieter Levels with Photo AI. Sahil Lavingia with Gumroad. Marie Martens with Tally. None of them wrote a line of production code until at least 50 people had told them, in some form, "take my money."

Seven days. One idea. Real decision. Try it on something this week.