1
0 Comments

I just mapped my 100th product idea. It changed how I think about building.

Two months ago, I started writing down every product idea instead of chasing whichever one felt exciting.

Today, I hit number 100.

Surprisingly, the biggest lesson isn't that I have 100 ideas.

It's that most of them aren't independent ideas at all.

They're connected.

One problem leads to another.
One tool reveals a missing piece.
Eventually, you stop seeing products and start seeing a system.

I've already shipped 4 of them, and building those changed the remaining 96.

Some ideas became better.
Some turned out to be unnecessary.
Others split into smaller, more useful products.

The list keeps evolving.

So I don't really think of it as a backlog anymore.

It's more like a map of problems I want to solve.

I'm curious how other founders approach this.

Do you keep a long-term product map, or do you focus entirely on the next thing to ship?

on June 29, 2026
Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 120 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 102 comments Ferguson is LIVE on ProductHunt today... so I audited their homepage first! User Avatar 34 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 29 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 24 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 22 comments