Fired, Then Free: What r/sideproject Says About Using Layoffs as Fuel

The thread title was simple: “I got fired from my job 6 months ago.” It wasn’t a plea for help. It was a report from the other side. The original poster, u/Miserable_Ride666, had used the severance and the shock to build a micro-SaaS that now covers their rent. The conversation wasn’t about the pain—it was about the pivot. First thing that jumps out: the grief is real, but short-lived. Multiple comments acknowledge the ego hit. u/PixelDrifter bluntly said, “Weeks 1-4: eat ice cream. Week 5: open your laptop.” The consensus is you can’t skip the wallowing, but you must set a deadline for it. Treating unemployment like a project with a two-week “sad sprint” before moving to “build sprint” seems to be a common ritual. This isn’t a golden ticket. It’s a forced sabbatical with a ticking clock. The most practical advice was about money psychology, not code. u/FinanceHacker42 laid it out: “Calculate your true runway (6-12 months) and subtract the first month’s expenses as a ‘panic buffer.’ Don’t touch the rest.” They stressed that the #1 side project killer isn’t technical debt, it’s financial anxiety making you take the first full-time offer that appears. So what do people actually build? The themes are clear. 1) Tools they wished existed at their old job. “I built a better internal sprint retrospective template,” said u/AgileOrBust. “Charging $9/month. My old company pays $45/person for a bloated alternative.” 2) Niche APIs for unglamorous industries. “A friend runs a small HVAC shop. I built him an automated parts lookup. Now three shops pay me $200/month each. It’s boring. It works.” 3) Aggregators or simple data tools. A user named u/CleanDataHobbyist built a scraping tool that aggregates pricing for a specific construction material across 5 suppliers. “It solves one painful problem for a buyer at one company. They pay me to save them 3 hours a week.” Tech stack choices here are brutally pragmatic. Overkill is the enemy. The go-to is Vercel + Next.js + a Supabase or PlanetScale database. “Why?” asked u/JustShipIt. “Because I can deploy in 5 minutes and it scales to my first 1000 users for $0.” A few are using Hetzner VPS with Docker for more control ("$7/month, full control, but you’re your own sysadmin," noted u/SelfHostedSnob). Nobody in the thread is using complex serverless architectures from day one. The hardest lesson, repeated in different words: your first version is not for the public. It’s for one human. u/IndiePM_Jake wrote, “Find ONE person from your old network who has the problem you’re solving. Give it to them for free. If they use it without you nagging, you have something. If not, you’re building a demo, not a product.” A recurring piece of caution: beware the “full-time indie” fantasy. Several users emphasized keeping part-time consulting or contract work. “The pressure to monetize too early will kill your creativity. I kept 15 hours/week of contract work. It paid the bills and kept me sane,” shared u/BalancedBuilder. The mental shift from “I must replace my salary immediately” to “I have time to learn” is everything. Is it for everyone? No. The emotional toll is high, and the financial runway isn’t infinite. But the playbook is less about sides of the bed you wake up on and more about a sequence of unsexy steps: Grieve on a schedule. Calculate your real runway. Talk to one potential customer. Build the boring solution. Ship it to them. As u/Miserable_Ride666 summed it up in an update: “The layoff was the shove I needed. But the building is what keeps you moving. Now, I’m not sure I’d go back.”