Why SaaS Turf? What a Decade of Building and Failing Taught Me

There are billions of websites out there. So why create another one?

Because after 10 years as a developer — working across startups and large companies, directly handling clients, and building products — I’ve learned lessons I need to share. (I’ve since become what you’d call a solopreneur — one person building and owning the whole thing.) Not as a saint, not as a guru, but as someone who’s been in the trenches, failed, and figured things out the hard way.

This blog is my way of giving back. It’s for anyone who wants to build, grow, or simply understand SaaS better. And yes, it’s also for me — to build an audience, a brand, and ultimately, products that actually help people.

What this blog is about

The pain of being a broke entrepreneur

I’ve built SaaS products, mobile apps (Flutter, React Native — I compared the two head-to-head here), and failed more times than I can count. One of the hardest lessons? Cost matters. When you’re making $0 or $100 MRR, every dollar spent on subscriptions feels like a punch to the gut. At $1,000 MRR, a $100 expense is fine. But at $0? It’s emotionally draining.

Here, I’ll share everything I’ve learned about cutting costs without cutting corners — because as an engineer, I’ve spent years optimizing not just code, but survival.

The engineer’s curse (and superpower)

Engineers love to optimize. Sometimes, that’s a problem — we overcomplicate things. But sometimes, it’s the key to making a SaaS work when you’re bootstrapping. I’ve tried countless databases, architectures, and hacks to keep my projects alive on a shoestring budget. I’ll share those secrets with you.

No fluff. No paywall.

This blog is free. No subscriptions, no hidden agendas. Just raw, unfiltered insights from a decade of hustle, failure, and (occasionally) success.

In the future, I might create products. But for now? It’s just you and me.