How to validate a SaaS idea without building anything

You have an idea. It feels real. It solves a problem you've had yourself. You're already thinking about the tech stack.

Stop.

Before you write a single line of code, before you buy the domain, before you tell your friends — you need to know if anyone else on this planet has the same problem badly enough to pay to have it solved.

Most founders skip this step. Not because they're lazy. Because it feels uncomfortable. Validating means you might find out the idea is bad, and that's a conversation nobody wants to have with themselves.

But here's the truth: finding out your idea is bad in week one costs you a weekend. Finding out in month six costs you everything.

The validation mistake almost every founder makes

The most common approach is asking friends. You describe the idea, they say "that sounds cool," and you take it as a green light.

It's not a green light. It's politeness.

Friends don't want to hurt you. They'll find something positive to say about almost any idea you pitch them. This is useless signal.

The second most common approach is building a landing page and running ads. Real signal, but expensive — €500-2000 to get enough traffic to mean anything, and you're now spending money to validate before you've made any.

There's a better way. It's free, it takes 15 minutes, and it uses data that already exists. People complaining on the internet.

Where real validation lives: Reddit and GitHub

Every market has a Reddit community. And in those communities, people say things they'd never say in a survey or on a call.

They complain, specifically and repeatedly, about the exact problems they have with existing tools. They describe workarounds they've built because nothing on the market solves their problem. They ask "does anyone know an app that does X?" — which is someone telling you exactly what to build.

GitHub is different but equally valuable. If you know how to read GitHub issues for product inspiration, issues tagged as "feature request" are a direct window into what users of existing tools wish existed. Stars and activity tell you if a market is growing or dying. Abandoned repos show you where someone tried to build something and gave up — sometimes because it was too hard, sometimes because there was no market.

Together, these two sources give you something no survey can: real signal from real people who weren't asked to perform for you.

The 15-minute validation framework

Here's the exact process. No tools required — just a browser.

Step 1: Find your Reddit communities (3 minutes)

Search Reddit for the problem your idea solves, not the solution.

If you're building an AI meal planner: search "meal prep" not "meal planning app." If you're building a focus tool: search "can't focus at work" not "focus app."

You're looking for the pain, not the cure.

List every relevant subreddit you find. You're looking for communities with at least 50k members where the problem is a recurring topic.

Step 2: Search for complaints and workarounds (5 minutes)

In each subreddit, search for these phrases:

• "is there an app that"
• "I wish"
• "frustrated with"
• "does anyone know"
• "there has to be a better way"
• "I just built a hack to"

Sort results by Top and by New. You're looking for posts with significant upvotes where multiple people are describing the same pain.

What strong signal looks like:

"4 hours sunday meal prepping for the week and my training split changed wednesday. all of it wrong macros. there has to be a better way." — 312 upvotes, 87 comments

That's not one person. That's 312 people saying "this is my problem too." And 87 people taking the time to discuss it further.

What weak signal looks like:

"anyone else think meal planning apps could be better?" — 3 upvotes, 1 comment

Vague question, low engagement, no specific pain. Move on.

Step 3: Check GitHub for market confirmation (4 minutes)

Go to GitHub and search for tools in your space.

Look for:

• Issues with 20+ thumbs up (people voting for features with their cursor)
• "Feature request" labels on issues that describe your core idea
• README files that explicitly say "roadmap includes X" — showing unmet demand

Also search for repos that were abandoned 1-3 years ago in your niche. Sometimes a market exists but the timing or execution wasn't right. An abandoned repo with 200 stars is evidence of demand.

Step 4: Score what you found (3 minutes)

For each piece of evidence, ask:

1. Is this a specific complaint or a vague preference?
2. Does it have social proof (upvotes, comments, reactions)?
3. Is it repeated across multiple posts and people?
4. Does the person describe a workaround (strongest signal)?

A workaround is the gold standard. When someone builds a Zapier zap, writes a spreadsheet, or describes a manual process they do every week to solve a problem — that's a person who would pay to have it automated. Understanding how to find out if people will pay for your idea is the natural next step once you've confirmed workarounds exist.

What the numbers mean

If you found:

• 5+ posts with 100+ upvotes each describing the same pain → strong signal
• Workarounds described in multiple threads → very strong signal
• GitHub issues with 20+ votes for your core feature → confirmed market
• Competitors with negative reviews mentioning your idea's core value → perfect

If you found:

• Vague complaints with low engagement → weak signal, idea may be too broad
• Nothing at all → either the market doesn't exist or you searched wrong

The tools worth using at this stage

Once you have the signal, you need to understand the market size. Two tools are genuinely worth paying for:

Ahrefs — keyword research that shows you exactly how many people search for your problem every month. If 40,000 people search "meal planning app for gym" monthly, that's a quantified market. If 200 do, it's a niche — not necessarily bad, but you need to know.

Notion — not for validation itself, but for organizing what you find. Create a database of signals: source, quote, upvote count, date, relevance. This becomes your investor deck, your marketing copy, and your product roadmap all at once.

When to stop validating and start building

You have enough signal when:

1. You can describe the exact person who has this problem (not a persona — a real type of person)
2. You have 10+ verbatim quotes from real people describing the pain
3. You've found at least one person describing a workaround
4. You understand why existing solutions fail (this becomes your positioning)

If you can check all four: build the smallest possible version that solves the core pain. Not the full vision. The version that proves the unit economics work.

The faster way

Everything above takes 15-30 minutes if you do it manually.

PledgeOFF does it in 15 seconds. You describe the idea, it scans 847 live signals across Reddit, GitHub, and Trends, and returns a weighted GO / KILL / PIVOT verdict with the verbatim evidence attached.

Same framework. Automated.

Validate your idea now →

The uncomfortable truth

You're going to find ideas that don't validate. That's the point.

Every bad idea you kill in the research phase is weeks or months of your life you get back. Every good idea you confirm gives you the conviction to build with confidence instead of anxiety.

The founders who succeed aren't the ones with better ideas. They're the ones who validate faster and kill bad ideas earlier.

That's the edge.