Skip to content

validation

2 posts with the tag “validation”

How to find a startup idea actually worth building

Most people think finding a startup idea means waiting for a flash of genius. It doesn’t. Good ideas come from a repeatable process of noticing real problems — and the hard part isn’t finding an idea, it’s telling a good one from a shiny one. Here’s how to do both.

Where real ideas actually come from

  • Your own annoyances. The thing you hacked together with a spreadsheet because no tool did it well. If you have the problem, you’re a built-in first user.
  • Your unfair knowledge. A job, hobby, or community you know deeply. You see problems outsiders can’t, and you know the language the buyers use.
  • Where people already pay. Look at what’s already selling and find the underserved slice, the bad-but-popular incumbent, or the niche too small for the big players.
  • Public complaints. Reddit, Hacker News, app store reviews, support forums. People describe their pain in their own words, daily. Read where your would-be users complain.

Notice what’s not on the list: “what’s a hot market.” Chasing AI or crypto because they’re hot, with no specific problem, is how you end up building a solution looking for a problem.

The test: is this a problem or just an idea?

The difference between a founder and a daydreamer is this filter. A real idea has:

  1. A specific person with the problem — not “everyone who…”. “Solo therapists who hate writing notes” beats “busy professionals.”
  2. Existing pain, not hypothetical pain. People are already losing time or money on it, today.
  3. A reachable audience. You can actually find and talk to these people online.
  4. Money already moving. Competitors or paid workarounds exist. “No competitors” is usually a red flag — it often means no budget.

If your idea fails these, it’s not a bad idea — it’s an unvalidated one. Which is fine, as long as you validate before you build.

The trap: falling in love with the solution

Founders fall in love with their solution (“an app that does X!”) instead of the problem. The solution feels exciting; the problem feels boring. But the problem is where the money is. Stay obsessed with the pain, stay flexible on the fix.

Don’t trust your own excitement — get a verdict

Your own enthusiasm is the worst possible judge of an idea. You’re not neutral. So before you commit months, get an honest, skeptical read: does the pain exist, who has it, what do they use now, will they pay?

You can do this manually (hunt real complaints, name the tribe, map competitors, force a GO/NO-GO verdict), or run it in one shot with the free AI startup idea teardown — paste your idea, get a blunt verdict, the real risks, and the cheapest way to test the riskiest assumption. You can also browse public teardowns to calibrate what a good idea actually looks like next to a weak one.

The honest summary

You don’t find a startup idea by waiting. You find it by paying attention to real problems — yours, your field’s, and the ones people complain about publicly — and then ruthlessly filtering for a specific buyer with present pain and a budget. Find the problem, validate it cheap, and only then fall in love.

How to validate a startup idea with AI — free, in about 30 minutes

Most founders validate their startup idea by asking ChatGPT “is this a good idea?” and hearing “what a great niche!” That’s not validation — that’s a compliment machine.

Real validation answers four questions with evidence:

  1. Does the pain exist? (Are real people complaining about this, in public, recently?)
  2. Who exactly has it? (A reachable tribe, not “everyone who…”)
  3. What do they do about it today? (Competitors and workarounds — both are good news)
  4. Will they pay? (Is money already moving in this space?)

Here’s how to get evidence-based answers using AI, for free, in about 30 minutes.

Step 1: Hunt the complaint, not the compliment (10 min)

Go where your audience already complains: Reddit, Hacker News, niche forums. The AI move is to use a model with web search and force it to cite:

“Search Reddit and Hacker News for people describing this problem: [your problem]. Give me direct quotes with links, dated within the last 12 months. If you can’t find at least 5, say so.”

The last sentence is the important one. You’re trying to make “there’s no demand” a possible answer. If the AI can’t find recent, specific complaints, that’s your result — cheaper to learn now than after three months of building.

Step 2: Name the tribe (5 min)

“Busy professionals” is not a tribe. “Solo therapists who hate writing post-session notes” is. Push the AI:

“Based on those complaints, describe the single most specific group with this pain. Where do they hang out online? What words do they use for the problem?”

The words matter — they become your landing page headline and your search keywords.

Step 3: Map competitors and workarounds (10 min)

“List products that solve this today, with pricing. Then list the manual workarounds people describe (spreadsheets, VAs, duct tape). What do users complain about in each?”

Two traps here:

  • “No competitors” is usually a red flag, not an opportunity. It often means no budget exists.
  • The workaround is your real competitor. If people solve it with a free spreadsheet, your $49/month tool fights the spreadsheet, not the other SaaS.

Step 4: Force a verdict (5 min)

This is the step everyone skips, because chatbots are agreeable by default. Force it:

“You are a skeptical product advisor who has seen 1,000 failed startups. Given the evidence above, give me: a GO / NO-GO / PIVOT verdict, the 3 biggest risks, and the cheapest possible test for the riskiest assumption. Do not soften the verdict.”

You’re not asking permission to build. You’re asking what would have to be true — and what the cheapest way to check it is.

The traps that invalidate your “validation”

  • Leading the witness. Ask “what problems do you have with X?” — never “would you use a tool that does Y?”
  • Validating the solution instead of the pain. People lie about what they’d use; they don’t lie about what already hurts.
  • Counting upvotes as demand. Likes on “I’d love this!” are not pre-orders. Money, emails, and waitlist signups are.
  • One-and-done. Validation isn’t a gate you pass once; the verdict updates with every new piece of evidence.

Or run the whole thing in one shot (free)

I turned this exact process into a free tool: the AI startup idea teardown. You paste your idea, and the Product cofounder from aicofounders.co runs the full diagnostic — honest verdict, pain level, the specific tribe, named competitors, real risks, and 5 concrete actions for this week.

No signup, takes a few minutes, and the verdict is deliberately blunt — it will tell you NO-GO when the evidence says NO-GO. You can also browse public teardowns other founders have run to calibrate what honest validation looks like.

Worst case, you lose 5 minutes. Best case, you avoid losing 3 months.