Your app failed, then you changed one thing

Pranav, a software engineer from India, was making $250,000 a year at his job but always planned to build his own product. When he finally quit and launched his first app, it went nowhere. The first version was a productivity tool called Signal — a smart notification manager that would silence unimportant alerts while letting through urgent ones. He built it, launched it, and watched it generate almost no traction.

Then he rebuilt it as a completely different product, and in six months it made $80,000.

The mistake most first-time builders make

Pranav's original instinct was to solve a problem he personally experienced. He was overwhelmed by notifications on his phone, so he built Signal to filter them intelligently. The app worked technically — it did what it promised — but nobody cared. The problem was real but not urgent enough for people to pay for a solution.

The deeper issue, as Pranav came to see it, was that he was building a product that required ongoing behavior change from users. People had to install the app, configure it, and trust it to manage their notifications. That's a high bar for a tool that solves an annoyance rather than a crisis.