Why Pannly exists.
I've shipped a handful of side projects. Most of them died because I picked the wrong idea, not because I built them badly. Pannly is the tool I wish I'd had four years ago.
When you're scrolling Reddit and Hacker News looking for ideas, you're doing the same thing every other indie hacker is doing — staring at noise, hoping a pattern emerges. Sometimes one does. Most of the time it doesn't.
So I built a thing that watches those threads for me. It pulls posts where real founders are saying “I'd pay for X” or “why does no one build Y”, scores how reachable those buyers are, and turns the strongest signals into briefs you can actually act on.
The refund-on-ship mechanic exists because I've seen too many tools — and built too many of my own — where the cost of finding out is greater than the cost of trying. Pannly should pay you back for taking the swing.
If you ship something using a Pannly brief, I'll personally see your refund clear. That's the deal.
Rohit
founder of Pannly · building from India
How we score ideas, in plain English.
Demand
How many people are actually feeling this pain? A single rant is noise; the same complaint surfacing across multiple subreddits and HN threads in the same month is a market. We weigh signal volume across communities and time.
Reachability
Can a solo builder actually find these buyers? Indie SaaS lives or dies on distribution. We score harder for problems with clear, public communities you can post into — and lower for buyers who only exist behind enterprise sales motions.
Competition
If three companies already do this perfectly, the score drops. If they exist but charge enterprise prices, ship clunky UX, or only serve the top 5% of the market, the score rises. The wedge matters more than the absence of competition.
Building in the open
Every refund processed, every shipped build, every monthly revenue update — posted publicly. No vanity metrics, no hustle theatre.
See the refund ledger