How Open Source Has Changed the Software Industry

From P2P Foundation
Jump to navigation Jump to search

Article: How Open Source Has Changed the Software Industry: Perspectives from Open Source Entrepreneurs. Juho Lindman, Risto Rajala. TIM, January 2012



“The emergence of F/LOSS (free/libre open source software) has triggered several changes in the software industry. F/LOSS has been cited as an archetypal form of open innovation; it consists of the convergence and collaboration of like-minded parties. An increasing number of software firms have taken upon this approach to link outsiders into their service development and product design. Also, software firms have been increasingly grounded their business models on user-centric and service-oriented operations.

This article describes a study that investigates these changes from the perspective of F/LOSS entrepreneurs. The findings are summarized into four issues that are critical in managing an F/LOSS business:

i)dealing with organizational changes in the innovation process; ii) mastering user involvement; iii) successfully using resources; and iv) designing revenue models.”

More Information

  • Recent research on open innovation has emphasized the importance to understand the impact of open innovation on firms’ strategies, see
  1. Harison and Koski, 2010;
  2. Hauge et al., 2010,


“Service-dominant logic (Vargo and Lush, 2004) describes a significant transition in business in terms of the use of resources. It considers resources in the development and delivery of offerings as operand resources (i.e., those in which an operation, or act, is performed) and operant resources (i.e., those that act on other resources). F/LOSS development depends, to a great extent, on resources that are external to a firm. The operand resources include, for example, the physical resources required to make services available to customers, while the operant resources, such as the requisite skills, knowledge, and capabilities, represent the intangible resources of the parties engaged in the collaboration. In F/LOSS businesses, resources are accessed through collaborative relationships between two or more parties, or, as suggested by Dahlander and Magnusson (2005), in a company-community relationship.”

“We selected five F/LOSS companies to determine how their managers perceived and described the ongoing changes in their environment. The respondents and their firms are anonymized in this paper. The method used for data collection included semi-structured, in-person interviews and an extensive set of secondary data on the case companies. We conducted interviews with each of the respondents from the selected firms over a five-year period (2004 to 2008). To gain a rich understanding about the organizations in their contexts, we interviewed the entire staff then employed by Tripod (3 persons), Yoga (1 person), and Tulip (5 persons). For larger the companies – OurDB and Nemesis – we limited our discussions to the CEOs and CTOs. This study uses a narrative approach to interpret the stories of F/LOSS entrepreneurs and senior managers. “


F/LOSS induces user involvement in software development

Integrating user feedback and requirements to the software was seen as one of the main opportunities and challenges with F/LOSS activity. The entrepreneur who founded Yoga underscored that “the main idea of F/LOSS is working together to create tools everyone wants to use individually.” The interviewees emphasized that F/LOSS development was organized differently from proprietary development and thus is able to respond more promptly to customer needs.

“We would never have gained 5 million users to our database product without acting according to the principles of the open source software community. Since we first released our software under an open license, we have gathered feedback – development ideas, problem descriptions and solutions – and responded to all possible initiatives from the user community to develop the product with the skillful individuals using the product.” (CEO, OurDB)

F/LOSS enables and invites user participation in software development. The narratives reveal differences in the numbers of possible contributions among the different software product categories, but are harmonious in their descriptions of the clear role users play as contributors to the software project, product, and service. In addition, the narrative of Yoga’s manager shows an example of a “classic open source development”. He described that his own contributions to several F/LOSS projects have been guided by his own personal needs and preferences.

His contributions were motivated by the reason that the available software did not meet his personal needs. Moreover, the CEO of Nemesis narrated that:

- “Our solutions are made for the customers, not for ourselves. We want to build a working solution, but we want the customers to sit down with us, so we can do it on the users’ terms. We believe that it is not enough for us to provide open source software. In our opinion, customers should also have open access to the actual work process – not only through external communication, but also in internal collaboration. We want to get the customers’ messages heard.”

Our respondents assumed that customers had the necessary capability and willingness for the elicitation of their requirements and that this information should guide the development of software products. In this vein, customer expectations determined which solutions would become commercially viable. The significant role played by such expectations was taken for granted; the respondents assured us that customer expectations drive actual customer behavior and their identification is thus salient to software vendors.

Open source development relies on external resources

One of the advantages of F/LOSS is tapping into external contribution in the innovation activity. That is, F/LOSS activity emphasizes access to external capabilities rather than internal resource ownership. Harnessing this innovation potential would allow the production of software and services that would be more tailored to users’ needs. The extant research shows that, due to the search and use of external resources and capabilities, the borders between networked companies and their environments are becoming blurred (Von Hippel and Von Krogh, 2003; Vujovic and Ulhøi, 2008; Elpern, 2009).

The CEO of OurDB clarifies that external resources are of key importance to the company’s success:

“The vast community of [our OurDB product] users and developers is what drives our business – we have five million server installations in use worldwide. Around them there are small “software ecosystems.” There are books and articles written, lectures held, courses taught, and applications developed around our products. This community of volunteers is our most important asset. Yet, it is difficult to define.”

Moreover, a respondent from Tripod described the context in which resources are publicly available, but then stated that the capability to make use of these resources to capture value potential is essential:

- “With a large user group, you can attain a higher product quality, as a larger number of people use the software in different situations and provide feedback. It also limits your development costs, as you will receive some of the software from others. Sometimes, the greatest ideas come from outside – ideas that you never had thought of. Users often widen our view.” (Project manager, Tulip)

In a related exchange, the original developers share the code in the F/LOSS community, and the clients gladly rely on the developers’ knowledge in applying the code in the development of applications, consultancy, training, and maintenance of the software.

According to our narratives, the ability to utilize external resources and capabilities is recognized as one of the key factors in remaining competitive in the software industry. As public goods, F/LOSS-based platforms, components, and applications shift the focus from the development of proprietary innovations to the use of the goods and knowledge that are publicly available.

Open source development encourages open innovation

The openness of innovation activity is a key theme in commercial F/LOSS development (Chesbrough, 2003; Watson et al., 2008). The manager of Tripod argues that this kind of a joint project will succeed “only if you let people see that their response has some effect on the software.” The responses depict a fundamental difference between open and closed innovation paradigms. “There was a lot to do with our software before it was ready, but we opened in a very early stage. We were able to give plausible promise and thus received a lot of valuable feedback. This resulted in a quite different end product.” (Manager, Tripod) Hence, the quality of innovation outputs is an essential reason to engage in open innovation. The open innovation approach embodies working together with numerous partners and various members of the F/LOSS community. In such an innovation model, the feedback loops are short and the software benefits from continuous improvement.

Our narratives underscore that, through F/LOSS activity, firms open their innovation processes to benefit from the knowledge and the innovation capacity of diverse open source communities. In this way, firms aim to benefit from the innovation capacity of both developers and users, resulting in shorter lead-times, shorter times to market, and ultimately, better product quality.

F/LOSS-based public goods change the revenue models

The CEO of OurDB claims that the entire business “will face a fierce price war, where profits disappear”. A vital consideration in F/LOSS activity is how it changes the means of value capture in software businesses. During the interviews, our respondents tended to discuss services, rather than products. The respondents agree that proprietary software cannot compete successfully for long in the same market as a complementary F/LOSS product.

- “Basically, our revenue streams are very broad and far-fetched. So, any reduction of problems in our service reduces cost and is actually an increase in our profit” (Project manager, Tulip). Our narrators discussed their revenue strategies at length, including the following statement from the CEO of OurDB: “Enterprise software buyers are tired of complex pricing models (per core, per CPU, per power unit, per user, per whatever the vendor feels like that day) – models that are still in use by the incumbents. [With OurDb], you pay by service level and the number of servers. No nonsense, no special math.” The case firms in this study have experimented both with revenue models that are directly product or service-related and those that indirectly benefit from the large user base:

- “In the beginning we did not focus on profits at all. Instead, we focused on boosting the use of the software. The vast community of users and developers is what drives our business. Then we sell our offerings to firms – those who need to scale and cannot afford to fail. The enterprise offering consists of certified binaries, updates and upgrades, automated DBA services, 7x24 error resolution, etc.” (CEO, OurDB) The narratives underscore that the software delivery price as such is not a key purchasing criteria, but the total cost of ownership, including all transaction costs and lock-in costs, is of greater concern. The manager of Yoga claims that the strength of F/LOSS is that, in many cases, it is the most cost-efficient solution:

- “Some proprietary software companies communicate – and in some cases quite correctly – that the total cost of ownership of their products is lower the total cost incurred from an open source software installation. In some cases it may be true, but in others, the cost comparison clearly favors the open source software.”

However, our interviewees share the view that, when software is distributed freely, traditional revenue sources wane and firms are compelled to develop novel revenue models that may be based on services and may be only indirectly bound to the distribution of software licenses.”

Manager actions in relation with FLOSS

Summary of findings including implications for managers of firms engaged in F/LOSS development:

Essential themes

Key considerations

Managerial actions

Actions: User involvement

F/LOSS activity emphasizes user involvement in software development and delivery.*

Orient the firm toward richer social interactions with the users.

Means: Utilizing external resources

F/LOSS activity emphasizes access to external capabilities, rather than internal resource ownership.

Maintain access to relevant capabilities rather than assimilate new resources.

Goals: Managing the open innovation processes

F/LOSS-based software development urges software innovators to open up their innovation processes.

Consider the purpose of external contribution in the innovation process.

Outcomes: Revenue models

F/LOSS-based public goods change the revenue models of firms taking part in open source development.

Grasp the logic of generating revenues from increasingly service-oriented offerings.


The lessons learned from the experiences of the entrepreneurs in this study indicate that F/LOSS-based software development urges software innovators to open up their innovation processes in a way that calls increasing attention to user involvement throughout the software development and delivery processes. That is, the F/LOSS activity emphasizes a need to maintain access to external capabilities, rather than leaning on internal resource ownership. In addition, entrepreneurs and managers should consider the objectives of the open innovation activity, because F/LOSS-based public goods change the focus of competition in the software business from product-centric to service-centric operations.


The amount and nature of user involvement in software development and delivery, which is characteristic in the F/LOSS activity, would take many long-haul software entrepreneurs by surprise. In fact, our narratives indicate that rich social interactions with users may bring challenges even for experienced F/LOSS entrepreneurs. However, our informants are harmonious in describing the benefits of rich user interactions for gaining user insight and increased understanding of users’ needs and wants, and they agree that these benefits clearly exceed the burden of managing extensive user interactions. These findings are in accordance with the arguments presented by Fitzgerald (2006). Moreover, user involvement may foster user commitment to the company’s offerings.

In line with the finding of Vujovic and Ulhøi (2008), we found that the F/LOSS activity emphasizes access to external capabilities, rather than internal resource ownership. The key resources include developer capabilities and skills as well as readily available F/LOSS components. On the whole, maintaining access to relevant capabilities seems to be far more rewarding than efforts to assimilate new resources. This was grounded mainly on the reasoning that, if some companies provide their software as “public goods”, the managers of all firms providing competing offerings must rethink the rational for maintaining in-house resources. The narratives express that increased utilization of external resources has long-term effects on the whole software industry. That is, companies that do not endorse F/LOSS will also face changes in regard to resource availability and costs.

Our informants described significant productivity enhancements related to collaborative innovation processes. Our findings highlight that in order to capture the full potential from external contribution in open innovation, managers should try to engage the users or other external contributors already at the early phases of their innovation processes. However, the interviewees emphasized the importance of understanding the purpose such openness and to consider the aims for external contribution in the innovation process. If the goal for collaboration is clear, it would be easier to reveal even the once confidential information, as the innovators are surged forward with enthusiasm, bearing barely in mind that what parts of the innovation should be kept secret to ensure the future presence in the business. These findings are congruent with the views of Watson et al. (2008).

F/LOSS-based public goods change the revenue models of firms taking part in open source development. In our data, it is evident that F/LOSS has an impact on the software industry as a whole, as it degrades traditional sources of revenue and compels firms to develop new revenue models primarily based on services. The interviewed executives recounted the need to grasp the logic of generating revenues from increasingly service-oriented offerings. This is congruent with prior studies on open source software business. Our findings are also consistent with existing studies on F/LOSS business models, and underscore that new revenue models are increasingly grounded on services. These F/LOSS-induced changes can affect all firms in the software industry and are not limited to companies engaged in F/LOSS activity." (