I expected most failed micro-SaaS products to die because the product was bad.
That was not the main pattern I kept seeing.
A lot of them had reasonable ideas.
Some had users.
Some had positive feedback.
Some even had early traction.
But the weak point was usually different:
people liked the idea, but did not change their workflow around it.
They did not pay early.
They did not migrate from whatever they were already using.
They did not invite teammates.
They did not come back often enough.
That changed how I think about validation.
A signup is useful.
A nice comment is useful.
A few early users are useful.
But I now pay much more attention to behavior that costs the user something:
That seems much closer to real demand.
The lesson I took from the 30 cases:
a SaaS product usually does not die because nobody understood the idea.
It dies because not enough people cared enough to change what they were already doing.
The "costs the user something" framing changes which segments you even go after.
The strongest pre-order signal I found in my current sprint is regulated industries. Dentists, restaurant operators, small business owners. For them, not knowing a bill cleared committee is not an inconvenience - it's expensive. They don't get to decide whether to care about a reimbursement change or minimum wage vote. The cost of missing it is real.
Testing this right now: a $9/mo service that monitors every federal bill and alerts you when something in your interest area moves. billwatch-landing.vercel.app - last day of a 17-day sprint today.
The ICP finding: it wasn't about finding people who wanted a product. It was finding people who couldn't afford to miss what Congress was doing.