In August 2012, Mike Perham calculated his hourly pay for developing Sidekiq: $3.5.
People were using the Ruby background-job processor and contributing to it. But roughly $700 in license sales over the previous six months stood against an estimated 200 hours of work. He had a family and needed to explain why spending that spare time on free software made sense. Perham’s contemporary account
Stop the story there and the outlook is uncertain. Attention suggests the product has met a need. Growing use also makes maintenance harder to put aside. Users have gained a tool; the author has not yet gained the conditions for continuing to provide it.
Sidekiq would later become an example of a one-person business. The early records are useful precisely because they preserve the gaps before that label of success.
First, put the software inside someone else's daily work
Sidekiq processes background jobs for websites. After a user finishes an immediate action, the system may still need to send notifications or process data. This software eventually has to withstand the workload and failures of a real business. Its developer’s own tests cover only part of that.
In a 2017 interview, Perham recalled that his employer used Sidekiq and tested its commercial features. He gave the company a free license in exchange for early testing and was responsible for running it in production. That let him observe what happened once the software entered the business. Founder interview, around 15:40
The relationship is absent from a feature list, but supplied an important development condition: a real setting for use and a route for problems to reach the author. Another independent developer could download the same tools and write similar code without having an organization willing to bear the cost of early adoption.
For someone starting a similar project, more features may not be the best next action when a real usage setting is missing. Finding a suitably sized partner willing to try the product and give feedback may expose the problems worth solving sooner.
Once the usage relationship existed, another gap began to close. Perham introduced the commercial extension Sidekiq Pro. Looking back in 2014, he described users willing to pay for additional features and continuing support, and his move to full-time open-source development. The free part still needed to be useful enough. The path to full-time open source
Charging changed where the time came from. Work previously squeezed out of family and spare time could be purchased continually by its beneficiaries. The community could provide feedback, code, and word of mouth; paying relationships let the author continue responding. They supplied different conditions.
Other labor required to operate the company did not fall entirely on the author either. He used a lawyer to help establish the company, learned bookkeeping from an accountant, and automated repetitive tasks such as granting access after purchases. The same interview, around 5:03 and 30:12
“Run by one person” becomes more concrete: professional services provide some capabilities, programs perform some actions, and the author retains other judgments. An employee list records internal employment relationships. It cannot show all the labor supporting the product.
Customers buying Sidekiq’s commercial products make a related choice. In his 2015 business review, Perham described fixes, improvements, and expert support as parts of the product’s value. Customers could thereby avoid some development and maintenance of their own. 2015 business review
The company buys legal and accounting expertise on one side and supplies a repeatable service to software customers on the other. Its range of action grows through these concrete exchanges.
The same approach did not produce a second Sidekiq
The same annual review records the failure of Inspeqtor.
Perham tried applying the open-source-plus-commercial-extension approach to this new product. Adoption and sales remained limited, and he decided to stop adding features. Technical experience, business experience, and an established business model did not automatically make the next product work. The Inspeqtor account
The material is insufficient to explain the failure fully. It is enough to caution against attributing all of Sidekiq’s outcome to an exceptionally capable founder, then assuming that capability can move to another need at will. Willing users, occasions for use, and reasons for continuing payment have to be established again.
This article draws on the founder’s contemporary records and later recollections. They help reconstruct these turns; they do not establish the success rate of one-person businesses or independently audit the business figures.
The practical judgment left by this history is modest. When assessing a small project, follow the work beyond what its author can do: who brings it into contact with real needs, who provides expertise the author lacks, who pays for continued maintenance, and how do problems return to someone who can address them?
A missing relationship can leave a very busy individual advancing their own time against business conditions that have not yet formed.