1
0 Comments

Most SaaS founders think they have a distribution problem. Many have a timing problem.

A pattern I've noticed:

Some founders launch too early.

Some launch too late.

Both call it a distribution problem.

The early founder spends months explaining why the problem matters.

The late founder enters after everyone already agrees the problem matters.

Neither situation is ideal.

The best SaaS opportunities often appear when buyers are saying:

"We're starting to feel this pain, but we don't yet have a clear solution."

That's usually the window where markets move.

Examples:

  1. Teams realized spreadsheets couldn't scale before modern CRMs took off.
  2. Companies realized cloud costs were becoming unpredictable before FinOps exploded.
  3. Security teams realized alerts were growing faster than analysts before new security categories emerged.

Most categories don't start because someone builds a product.

They start because enough people independently reach the same frustration at roughly the same time.

A question I ask now:

What problem are buyers just beginning to complain about that doesn't yet have a standard solution?

That's often more interesting than asking:

"What SaaS should I build?"

Curious:

What's a problem you think is entering that phase right now?

on June 16, 2026
Trending on Indie Hackers
I got my first $159 in sales after realizing I was building in silence User Avatar 52 comments I spent more time setting up cold email than actually selling. Here is what fixed it. User Avatar 41 comments Three Days Before Launch, I Let My Own Tool Tear Me Apart User Avatar 35 comments I got tired of rewriting the same content for 9 different platforms. So I built Repostify. User Avatar 29 comments A pattern I keep seeing in EdTech: traffic isn't usually the problem. User Avatar 23 comments I thought I was building a news visualization tool. Users thought it was a catch-up tool. User Avatar 21 comments