Now that I’ve had the opportunity to observe the Open Source industry from the inside for a couple of years, I find myself musing a fair bit about the economics - broadly speaking the exchange of value - involved. Much of the customer appeal for open source solutions comes from the sticker price, which is generally zero. But as the adage goes, if something sounds too good to be true, it generally is. If open source software is to be high quality and broadly applicable, the customer demand for low-cost software needs to be matched with incentives for vendors and individuals to continue to produce high-quality software. When the transaction isn’t based on actual currency, what is the commodity that makes this a successful transaction for both sides?
For individual open source authors the incentives might include the joy of having a large and loyal user base. It might include fame and the development of skills that lead to greater personal satisfaction and a more impressive and marketable resume. But I’d like to focus here on the incentives for professional software development businesses to invest in producing more and better open source software.
The research, development and deployment of software is a complex and costly process. How are open source vendors able to accomplish these goals without getting licensing revenue in return? I believe there are many ways a vendor can receive value from a user besides an exchange of currency. Although the commodities exchanged aren’t tangible the exchange is rarely a zero-sum game, and can enrich the supplier without depriving or depleting the customer. No matter how many smiles you give, you never run out.
Enforcement of non-tangible exchanges is impossible, and thus the exchange relies on the good will of the customer to give back. My intention in this post is to enumerate some of the ways this non-monetary economy works, and I hope to encourage users to participate more fully and consciously in holding up their end of the transaction, and thus to perpetuate a virtuous cycle of open source software development. If you use open source software, please consider one of the following ways you can remunerate the creator.
|
What the user gives |
How the creator benefits | |
|
Tell the author whether you |
= | Reduced cost of soliciting customer feedback, ability to target new features more cost-effectively |
|
Tell a friend or blog about it |
= | Reduced awareness-marketing costs |
| = | Reduced awareness-marketing costs | |
|
Lend an eyeball to a promotion or advertisement |
= | Makes marketing expenditures more productive |
|
Become a registered user |
= | Reduces costs of contacting users, helps accurately judge the popularity of the product and thus the level of continuing investment |
|
Ask a question on the mailing list |
= | Reduces costs of getting customer feedback |
|
Answer someone else’s question on the mailing list |
= | Reduces general product support costs |
|
Write an article or blog about creative uses of the product |
= | Reduces documentation and marketing costs |
|
File a bug |
= | Reduces QA costs |
|
Send a patch |
= | Reduces development costs |
|
Implement a new feature |
= | Reduces development costs |
|
Download additional products |
= | Reduces marketing costs and strengthens the business |
|
Consider purchasing other products or services from the author |
= | Improves profitability and increases ongoing R&D |
|
Be grateful for the software |
= | Increases everyone’s karma |
The laws of economics state that the more rewards there are for a product or service, the more of that product and service will be produced. By increasing the rewards for vendors to create useful and high-quality open source software, you encourage more of that software in the future. Isn’t that worth an investment of a little time? It doesn’t even lighten your wallet!

Posts (RSS)