Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Bootstrapped Founders Are Using Solo Developer Success Stories
Transcript
- Lucas: So there's a story I keep coming back to, and I think it's worth unpacking because it challenges a lot of assumptions about what it takes to build a profitable software company. Luna: Which one — hopefully not another 'two founders in a garage' tale? Lucas: No, the opposite actually. One founder, no garage, no VC, and a product that started as a side project. I'm talking about Mike Perham and Sidekiq. Luna: Sidekiq — that's the background job processor for Ruby, right? I've used it in a past life. Lucas: Exactly. It's a library that lets Ruby applications handle tasks like sending emails or processing uploads in the background. Perham built it back in 2012, open-sourced it under a permissive license, and then released a paid 'Pro' version with additional features. Today, Sidekiq generates over three million dollars in annual recurring revenue — and it's still essentially a one-person operation. Luna: Three million ARR as a solo developer? That's wild. But isn't he also selling licenses to big companies like GitHub and Shopify? Lucas: He is. And that's part of the genius. Perham structured the pricing so that individual developers could use the open-source version for free, but companies needing enterprise features — like reliable queuing or real-time monitoring — pay for the Pro license. It's a textbook open-core model, but executed with a level of transparency that's rare. Luna: Transparency how? Lucas: He publishes his revenue every year. In 2023, he shared that Sidekiq did about $3.4 million in revenue, with a profit margin north of 80 percent. He keeps costs low — no office, no full-time employees, just himself and some contractors for support. And he's been doing this for over a decade. Luna: That's the kind of story that makes every developer with a side project think, 'I could do that.' But is it actually replicable? Lucas: That's the question. And I think the honest answer is: partly yes, but not without some serious caveats. Perham had a unique advantage — he was already a well-known figure in the Ruby community. His open-source contributions gave him a built-in audience and credibility. That's hard to manufacture from scratch. Luna: So it's the classic 'you need a reputation to build a reputation' problem. Lucas: Right. But there are actionable takeaways. First, he identified a genuine pain point that wasn't being well-served — background job processing was handled by other tools, but they were either too complex or not reliable enough. He built something simpler and better. Luna: And he didn't try to boil the ocean. It's one focused library. Lucas: Exactly. Second, he used open source not as a charity, but as a marketing funnel. The free version got adoption, created network effects, and then he could upsell the paid version to the companies that needed it. The community itself became his sales team. Luna: And he avoided the freemium trap of giving away too much. The free version is genuinely useful, but the Pro features are what enterprises actually pay for. Lucas: Right. And this is the part that I think applies broadly: he found a pricing model that aligns with the customer's willingness to pay. Individual developers don't want to shell out hundreds of dollars, but companies with thousands of users will happily pay for reliability. Luna: Yeah, it's classic value-based pricing. But let's be real — most founders aren't going to build a piece of infrastructure that becomes industry standard. What's the lesson for someone building a niche SaaS tool? Lucas: I think the deeper lesson is about asymmetric advantage. Perham didn't need a sales team or a marketing budget because his product had a built-in distribution channel: the Ruby ecosystem. If you can find a community where your product 'belongs' — whether it's a programming language, a CMS, or a specific industry — you can achieve a lot with very little. Luna: So it's about finding your ecosystem rather than trying to build one from scratch. Lucas: Exactly. And there's also a lesson about patience. Perham didn't get to three million dollars overnight. He started in 2012, and for the first few years, revenue was modest. He kept iterating, kept engaging with the community, and the growth was gradual but compounding. Luna: I think that's a helpful antidote to the 'viral launch' fantasy we see so much on social media. Lucas: Totally. And speaking of staying power — if you find value in conversations like this, where we dig into real business models without the hype, listener support is what keeps this show ad-free. If that's something you'd like to help with, you can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a simple way to support the kind of deep-dive content that doesn't fit the usual media mold. Lucas: Back to Sidekiq — one more angle I want to touch on. Perham also wrote extensively about his journey on his blog, sharing revenue numbers, lessons learned, and even his failures. That transparency built a lot of trust and turned customers into advocates. Luna: So content marketing, but authentic. Not the 'growth hacking' kind. Lucas: Exactly. And I think that's a strategy any bootstrapped founder can adopt. You don't need to be a famous developer to share your journey. If you're solving a real problem, documenting the process — the wins and the struggles — can attract the right kind of attention. Luna: Are there any other solo dev success stories you'd point to? Lucas: Yeah, there's Pieter Levels with his various projects like Nomad List and Remote OK, but he's more of a serial indie hacker. And there's the creator of Plausible Analytics, Uku Taht, who built a privacy-focused analytics tool as a solo founder and now does over a million in ARR. Luna: So there's a pattern: niche tool, community-first, transparent pricing, and a long time horizon. Lucas: Yeah. And I think the most important takeaway is that you don't need a team to start. You need a clear problem, a focused solution, and a way to reach the people who have that problem. The team can come later — if at all. Luna: But what about founders who aren't developers? Can they replicate this? Lucas: It's harder, because you need to either build the product yourself or find a technical co-founder who shares your vision. But the principles still apply. You can build a community around a niche, use content to establish authority, and create a product that solves a specific pain point. The tools for building software are easier than ever — no-code and low-code platforms can get you a long way. Luna: Fair point. I think the myth of the solo developer is that they're some kind of genius, but really it's about focus and perseverance. Lucas: Exactly. Perham would be the first to say he's not a genius — he just kept showing up, kept improving the product, and kept listening to his users. That's a recipe that works in any market. Luna: So if there's one thing listeners should take away from this, what is it? Lucas: Find your ecosystem, build something that serves it well, and be transparent about the journey. You don't need a venture check to build a real business. You just need a problem that people will pay to solve.