How I Built a Profitable SaaS With Zero Employees

This is not a success story. Or rather, it's not only a success story. It's the full picture — including the three months I spent building the wrong thing, the pricing mistake that cost me $40K in annual revenue, and the moment I almost quit to take a job at Google.

I'm sharing this because when I was starting out, every solo founder story I read was either impossibly inspiring ('I hit $1M ARR in 6 months!') or uselessly vague ('just find product-market fit!'). I wanted the messy middle. So here it is.

The idea (and why my first version was wrong)

I was a data engineer at a Series B startup. Every week, our marketing team would ask me to pull the same reports with slightly different parameters. I thought: 'I'll build a self-serve analytics tool for non-technical marketers.' That was the wrong product.

The right product, which took me three months to discover, was much narrower: a tool that automatically generates the one specific report that marketing teams need for their weekly stand-up. Not analytics. Not a dashboard. One report, generated automatically, delivered before the meeting starts.

“The wrong version tried to replace a data engineer. The right version replaced a recurring task that annoyed a data engineer. That distinction is everything.”

Month 1-3: Building the wrong thing

I spent three months building a general-purpose analytics dashboard. It was technically impressive. It had drag-and-drop chart builders, SQL editors, collaboration features. Nobody wanted it. I showed it to 15 potential customers. The response was universally: 'This looks cool but I already have Metabase/Looker/Mode.' I was competing with funded companies on their turf.

Month 4: The pivot that saved everything

I almost gave up. Then one potential customer said something that changed everything: 'I don't need another analytics tool. I need someone to make Monday morning's marketing report stop being a 2-hour pain in my ass.' That was the product. Not analytics. Pain relief for a specific, recurring task.

I rebuilt the entire product in two weeks. One feature: connect your data sources, define your weekly report template, get it in your inbox every Monday at 7am. That was it.

Month 5-9: $0 to $18K MRR

• Month 5: Launched on Product Hunt. 12 paying customers. $960 MRR.
• Month 6: Added Slack integration (customers asked for it). Word of mouth started. $2,800 MRR.
• Month 7: Raised price from $80/mo to $149/mo. Lost 2 customers, gained 8. $5,200 MRR.
• Month 8: Got featured in a newsletter. 200 signups in one day. $11,000 MRR.
• Month 9: Added team plans. Enterprise inquiry from a Fortune 500. $18,400 MRR.

The three decisions that actually mattered

Looking back, only three decisions made a real difference:

• Narrowing from 'analytics tool' to 'one specific report.' This is the hardest thing for solo founders. Your instinct is to build more. The market rewards less.
• Raising the price early and aggressively. At $80/mo, I attracted tire-kickers. At $149/mo, I attracted people with real budgets who valued their time. Higher price = better customers = less support = more time to build.
• Saying no to features. I got requests for custom dashboards, API access, white-labeling, mobile apps. I said no to all of them for 9 months. Every feature you add as a solo founder is a feature you maintain alone. The constraint is not what you can build — it's what you can support.

What I'd tell my day-one self

Talk to customers before you write code. Not 3 customers — 15. The product you imagine is wrong. The product they need is simpler, narrower, and more boring than you think. Boring is good. Boring means it's a real problem that real people pay real money to solve. Chase boring.