Open source profiteering strategy No. 2: Open-sourcing code to reduce support costs.
Have a problem? Here is a stack of code. Figure it out for yourself. Whileit sounds callous, many open source companies rely on pointers to the source code when dishing out support. The proprietary companies need to write a complex description of what the API does, but the open source companies just point to the API gateway that does the decoding. Anyone can read the source — and many do. It’s now common for companies to run a support forum next to the code with open debate about the software. It’s just faster.
Good, well-documented open source software can be a gift for everyone involved. The able customers can answer their own questions without waiting for a support technician to dig up the code. The support team can save themselves the hassle of trying to translate the code into English. Done well with a vibrant community, everyone can benefit with access to the open source.
Your company needs a tool or library or component. Developing it in-house would cost big bucks. Now imagine there is an open source version tahat does half of what you need already. paying for someone to add the necessary features may look foolish or generous or both because the open source license will mean all the additons must be shared with everyone. But it will also cut the development bill in half. If the software is’t a critical part of the business, this can be asmart way to slice development costs while appearing to be magnanimous and devoted to the community.
Some companies solve thes problems by paying the developers they know and trust. Others advertise for people who are already contributing to the project. A number of crowdfunding sites like BountySource let users pool their money to sponsor programmers to deliver the code. They come and go, but the idea lives on.
In some situations, a groupd of companies can rally aorund an open source code base, with each contributing a fraction of the develpmetn costs. They all save money while building a crucial tool they use together. The savings can be significant. Even if ther is only one other partner, the costs migh be cut in half. If there are 10, the costs could be cut by 90 percent.
Open source profiteering strategy No. 4: Open-sourcing code to push back against a rival.
When google launcehd its android OS, Apple’s iPhone controlled an overwhelming amound of the smartphone market. Giving Android away as an open source platfor made if easier for Google to work together with the other phone manufacturers to create a flourishing platform that could support apps that everyone could use. The open source license made each company an equal partner in the project by giving them access to the source code and control. They could feel secure in choosing it because they knew that google couldn’t revoke access.
This shared process is growing more common. openStack, a project sopnsroed by Rackspace, lets smaller cloud companies band together and offer a common platform that will be more attractive tahn the dominatn cloud from Amazon. Not only can the customers choose between multiple companies, they can also install the cloud tools in their own dat center. The same basic structure is found in all of the clouds, and the scripts wrk the smae everywhere.