He Got Laid Off. Then a Product Roast Changed Everything.

Last year, Rakesh was laid off. This month, one of his SaaS products crossed $1.8K in 19 days.

The tempting version of this story is: persistence wins.

The useful version is messier. It includes part-time work, free MVPs for strangers, products that went nowhere, co-founder offers that were not the original plan, and a product roast that forced a painful rebuild close to launch.

That is exactly why it is worth sharing.

He did not wait for the perfect client

After the layoff, Rakesh needed momentum and income. He offered to build complete MVPs for founders in the community for free, asking only for a small credit, a launch mention, and an honest testimonial.

It did not turn into the agency pipeline he expected. It did something more interesting: it created relationships, led to technical co-founder conversations, and gave him more real problems to work on than solo idea-hunting ever could.

That is a useful reminder for any founder stuck at the blank-page stage: sometimes the fastest way to find your next opportunity is to become useful before you know exactly where it leads.

The roast was not a detour. It was the product work.

One version of CrawlRaven was close to launch. Then came direct feedback at a Roach Mafia in-person meetup: the angle was wrong. Not a few tiny tweaks wrong. The kind of wrong that makes you want to defend the work because you have already spent time on it.

Rakesh changed direction anyway. The launch moved. The product was rebuilt around a clearer problem.

The result: a Product Hunt launch that reached #4 Product of the Day, more than 300 upvotes, over $1,000 in launch-day revenue, and the first $1.8K+ over the following 19 days.

Those numbers are public, and they are impressive. But they are not the transferable part.

The part you can copy this week

1. Put one imperfect thing in front of real people. A landing page, a demo, a rough MVP, a problem interview. Do not keep refining in private.
2. Ask for the sentence that hurts. Praise feels good. Specific confusion is more valuable.
3. Separate feedback from your ego. A product can be wrong without your effort being wasted. The work bought you a clearer next move.
4. Keep the loop moving. Ship, listen, change, launch again. That is how a scattered year turns into a credible win.

What Rakesh's story says about community

Good founder communities are not motivational wallpaper. They are places where someone can tell you your product is unclear before your customers do.

Rakesh found collaborators, feedback, and a room willing to be honest. The win belongs to him. The loop is available to every builder who is willing to show the unfinished work.

No magic. Just more launches, more feedback, and fewer months spent protecting a weak first draft.

Browse more articles for indie hackers.