1
0 Comments

Stop Building. Start Validating.

How I Stopped Guessing and Started Finding SaaS Ideas That Actually Sell

Every founder thinks their idea will work — until it doesn’t.
The thing that separates the ones who make it from the ones who quietly shut down? Validation.

Yash Chavan once asked five people to pay him for a product that didn’t exist.
They said yes.
That’s how SARAL was born — now doing $1.1M ARR with a nine-person team.

Most of us do the opposite.
We build for months, launch to silence, then pretend we’re “still iterating.”
But the truth? 42% of startups die because nobody wanted what they built. Not because the code was bad — because nobody cared enough to pay.

I used to fall for that trap too — thinking “interest” meant “demand.”
500 signups, 50 people saying “I’d use this”… I thought I was onto something.
Turns out only 2–5% of those would ever pay.

Real validation is simple:
Someone gives you money before the product exists.
Everything else is noise.

Here’s the system that worked for me — took three weeks, zero code, and got real paying users.

I didn’t start with a “problem.” I started with where money was already flowing.
If people are already paying to solve something, it’s a real pain. Your job is to make it faster, cheaper, or simpler.

So I went through G2, read every 1-star and 2-star review in my niche.
When 30 people complain about the same thing, congratulations — you’ve found your wedge.
That’s how I found my angle: Mailchimp was “too complicated for beginners.”
Boom. There’s the gap.

Then I talked to users — cold DMs, emails, whatever worked.
Not to pitch. To listen.
When people start sentences with “I wish it did…” — that’s gold.

Once I had a few “yes, that’s a problem” signals, I built a fake landing page — real pricing, fake product.
If they clicked “buy,” it redirected to:

“We’re in private beta. Want to be one of the first 10? Let’s chat.”

No signups, no vanity metrics — just real conversations.
Spent $100 on ads and DMs. Got 100 visits, 5 booked calls.

Three people said yes to paying for a manual version.
That’s validation.

So I became the product.
Literally.
Did the work by hand for two weeks.
It sucked — but it showed me what people actually used, what they ignored, and what was worth automating.

By the end, I knew:

Which features mattered

What customers hated

And what they’d happily pay for

That’s when I started building — not before.

If you’ve been grinding for months without users, this might sting a bit:
Your idea might be fine. You just built too soon.

Validation isn’t about doubt. It’s about respecting your time.
Peter Levels made $10K in pre-sales before writing a line of code.
Drew Houston made a Dropbox demo video, not a product.
Yash pre-sold SARAL.

Same playbook. Different outcomes.

If I had to sum it up:

Don’t ask friends.

Don’t count email signups.

Don’t ask “Would you use it?” — ask “How do you solve this today?”

Don’t spend six months building what nobody asked for.

The faster you kill bad ideas, the more time you have for the right one.

Validate first.
Build second.
Scale third.
Always in that order.

If you’ve been through your own version of this — validation gone right (or wrong) — drop it here. Let’s make “build fast, fail faster” mean something useful again.

→ I’m Sonu, a SaaS content marketer who helps founders turn messy ideas into real revenue. Let's connect: https://www.linkedin.com/in/sonu-goswami-6209a3146/

posted to Icon for group Saas Makers
Saas Makers
on November 13, 2025
Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing User Avatar 113 comments The coordination tax: six years watching a one-day feature take four months User Avatar 74 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 64 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 52 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments Why I built a SaaS for online front-end projects that need more than a playground User Avatar 17 comments