When to make proprietary software open source

J.P. Caulkins, G. Feichtinger, D. Grass, R.F. Hartl, P.M. Kort, A. Seidl

Research output: Contribution to journalArticleScientificpeer-review

Abstract

Software can be distributed closed source (proprietary) or open source (developed collaboratively). While a firm cannot sell open source software, and so loses potential sales revenue, the open source software development process can have a substantial positive impact on the quality of a software, its diffusion, and, consequently, the demand for a complementary product from which the firm does profit. Previous papers have considered the firm's option to release software under a closed or open source license as a simple once and for all binary choice. We extend this research by allowing for the possibility of keeping software proprietary for some optimally determined finite time period before making it open source. Furthermore, we study the impact of switching costs. We show that in case of high in-house R&D costs, the firm always makes the software open source at some point (unless switching itself is too expensive). The timing, however, depends on the initial software quality. On the other hand, when R&D is inexpensive, the firm opens the source code only when the initial level of software quality is low. For intermediate R&D costs, the firm might have the choice between opening the code immediately, opening it at some subsequent and optimally determined time, or keeping it closed forever. Finally we find that whereas high switching costs might prevent firms from adopting an open source business model, low switching costs mainly affect the timing of the opening of the source code.
Original languageEnglish
Pages (from-to)1182-1194
JournalJournal of Economic Dynamics and Control
Volume37
Issue number6
DOIs
Publication statusPublished - Jun 2013

Fingerprint

Open Source Software
Open Source
Costs
Software Quality
Software
Closed
Timing
Binary Choice
Software engineering
Profitability
Sales
Software Process
Business Model
Business
Open source software
Development Process
Software Development
Immediately
Profit
Industry

Keywords

  • open source
  • optimal control
  • multi-stage modeling
  • complementary product
  • software

Cite this

Caulkins, J. P., Feichtinger, G., Grass, D., Hartl, R. F., Kort, P. M., & Seidl, A. (2013). When to make proprietary software open source. Journal of Economic Dynamics and Control, 37(6), 1182-1194. https://doi.org/10.1016/j.jedc.2013.02.009
Caulkins, J.P. ; Feichtinger, G. ; Grass, D. ; Hartl, R.F. ; Kort, P.M. ; Seidl, A. / When to make proprietary software open source. In: Journal of Economic Dynamics and Control. 2013 ; Vol. 37, No. 6. pp. 1182-1194.
@article{734b36108f454d599cec22730ceeab5b,
title = "When to make proprietary software open source",
abstract = "Software can be distributed closed source (proprietary) or open source (developed collaboratively). While a firm cannot sell open source software, and so loses potential sales revenue, the open source software development process can have a substantial positive impact on the quality of a software, its diffusion, and, consequently, the demand for a complementary product from which the firm does profit. Previous papers have considered the firm's option to release software under a closed or open source license as a simple once and for all binary choice. We extend this research by allowing for the possibility of keeping software proprietary for some optimally determined finite time period before making it open source. Furthermore, we study the impact of switching costs. We show that in case of high in-house R&D costs, the firm always makes the software open source at some point (unless switching itself is too expensive). The timing, however, depends on the initial software quality. On the other hand, when R&D is inexpensive, the firm opens the source code only when the initial level of software quality is low. For intermediate R&D costs, the firm might have the choice between opening the code immediately, opening it at some subsequent and optimally determined time, or keeping it closed forever. Finally we find that whereas high switching costs might prevent firms from adopting an open source business model, low switching costs mainly affect the timing of the opening of the source code.",
keywords = "open source, optimal control, multi-stage modeling, complementary product, software",
author = "J.P. Caulkins and G. Feichtinger and D. Grass and R.F. Hartl and P.M. Kort and A. Seidl",
year = "2013",
month = "6",
doi = "10.1016/j.jedc.2013.02.009",
language = "English",
volume = "37",
pages = "1182--1194",
journal = "Journal of Economic Dynamics and Control",
issn = "0165-1889",
publisher = "Elsevier Science BV",
number = "6",

}

Caulkins, JP, Feichtinger, G, Grass, D, Hartl, RF, Kort, PM & Seidl, A 2013, 'When to make proprietary software open source', Journal of Economic Dynamics and Control, vol. 37, no. 6, pp. 1182-1194. https://doi.org/10.1016/j.jedc.2013.02.009

When to make proprietary software open source. / Caulkins, J.P.; Feichtinger, G.; Grass, D.; Hartl, R.F.; Kort, P.M.; Seidl, A.

In: Journal of Economic Dynamics and Control, Vol. 37, No. 6, 06.2013, p. 1182-1194.

Research output: Contribution to journalArticleScientificpeer-review

TY - JOUR

T1 - When to make proprietary software open source

AU - Caulkins, J.P.

AU - Feichtinger, G.

AU - Grass, D.

AU - Hartl, R.F.

AU - Kort, P.M.

AU - Seidl, A.

PY - 2013/6

Y1 - 2013/6

N2 - Software can be distributed closed source (proprietary) or open source (developed collaboratively). While a firm cannot sell open source software, and so loses potential sales revenue, the open source software development process can have a substantial positive impact on the quality of a software, its diffusion, and, consequently, the demand for a complementary product from which the firm does profit. Previous papers have considered the firm's option to release software under a closed or open source license as a simple once and for all binary choice. We extend this research by allowing for the possibility of keeping software proprietary for some optimally determined finite time period before making it open source. Furthermore, we study the impact of switching costs. We show that in case of high in-house R&D costs, the firm always makes the software open source at some point (unless switching itself is too expensive). The timing, however, depends on the initial software quality. On the other hand, when R&D is inexpensive, the firm opens the source code only when the initial level of software quality is low. For intermediate R&D costs, the firm might have the choice between opening the code immediately, opening it at some subsequent and optimally determined time, or keeping it closed forever. Finally we find that whereas high switching costs might prevent firms from adopting an open source business model, low switching costs mainly affect the timing of the opening of the source code.

AB - Software can be distributed closed source (proprietary) or open source (developed collaboratively). While a firm cannot sell open source software, and so loses potential sales revenue, the open source software development process can have a substantial positive impact on the quality of a software, its diffusion, and, consequently, the demand for a complementary product from which the firm does profit. Previous papers have considered the firm's option to release software under a closed or open source license as a simple once and for all binary choice. We extend this research by allowing for the possibility of keeping software proprietary for some optimally determined finite time period before making it open source. Furthermore, we study the impact of switching costs. We show that in case of high in-house R&D costs, the firm always makes the software open source at some point (unless switching itself is too expensive). The timing, however, depends on the initial software quality. On the other hand, when R&D is inexpensive, the firm opens the source code only when the initial level of software quality is low. For intermediate R&D costs, the firm might have the choice between opening the code immediately, opening it at some subsequent and optimally determined time, or keeping it closed forever. Finally we find that whereas high switching costs might prevent firms from adopting an open source business model, low switching costs mainly affect the timing of the opening of the source code.

KW - open source

KW - optimal control

KW - multi-stage modeling

KW - complementary product

KW - software

U2 - 10.1016/j.jedc.2013.02.009

DO - 10.1016/j.jedc.2013.02.009

M3 - Article

VL - 37

SP - 1182

EP - 1194

JO - Journal of Economic Dynamics and Control

JF - Journal of Economic Dynamics and Control

SN - 0165-1889

IS - 6

ER -