Sidekick

Mike Parham spent 20 years as a software developer, working for a dozen startups and always solving someone else's problem. After his latest startup, he realized he'd spent years contributing to open source libraries without making any money. While consulting for a San Francisco company, he saw their massive background job processing infrastructure—a dozen machines chewing through jobs inefficiently—and had an epiphany: "I can build something that's much more efficient that can process all these jobs with one machine rather than a dozen machines."

Mike spent two months building Sidekick and launched it as an open source project. It got "pretty good take up almost immediately." But as the project grew in popularity, he faced a real problem: how would he sustain this for 5-10 years without burning out? The answer was simple but radical for an open source maintainer—charge money.

After six months of building the free version, he released Sidekick Pro, a closed-source layer with additional features. "I saw sales almost immediately." His existing open source user base became his natural market. Within about 18 months, the business was making enough money to rival his full-time salary. When his employer's growth stalled, the choice was obvious: go full-time on Sidekick. He switched to an annual subscription model ($1,000 for Pro, $2,000 for Enterprise) four months before he quit.

Mike's first customers were already using Sidekick for free. "When I said I'm going to start selling this pro version, probably five to 10 almost immediately purchased it." He'd built trust over six months of visible, high-quality development. His day job at the same company that was his first Sidekick user gave him an unfair advantage—he could dogfood his own product during work hours while spending about 20 hours a week on it nights and weekends.

What worked: product-led growth. "90% of my sales come without me saying a word to the person who's buying it." Mike does zero outbound sales, no advertising, no webinars. He just maintains excellent documentation, fixes bugs quickly, and lets word-of-mouth do the work. He also made a deliberate choice to never discount—everyone pays the same price, which paradoxically attracts better customers (the ones who ask for discounts become the worst support burdens).

What didn't work: trying to expand. He built Inspector, a product in a different category, but it "did not work as well as Sidekick didn't sell as well." He also created a Crystal version with minimal success. These failures taught him to stay focused on his niche.

He also deliberately rejected hiring and complex operations. "I don't want to run a SaaS. I do have a server running 24-7 that I do have to monitor, but it's extremely simple." By keeping operations minimal and automating everything through Stripe, he scales with just himself.

Sidekick brings in close to $80,000 a month ("close to $80,000 a month in revenue") with approximately 800 customers, growing 50-100% annually. Despite competitors and open source alternatives, Mike dominates because he spends full-time on product polish while competitors burn out. His advice to other open source developers: "figure out what your natural advantages are. What are the points or the break points where you can say, I'm going to give this away for free, but I'm going to charge money for this additional value."

Mike remains solo by design, not circumstance. He rejected VC funding because the margins required to satisfy investors would force pricing changes that wouldn't work in the Ruby market. He's chosen a different path: sustainable, profitable, solo-founder success in a niche most people overlook.