When developing an information system, organisations are faced with a fundamental choice: to buy a pre-developed package (potentially customise it or redesign/reengineer the business processes of the company concerned to fit the package), or to build the system in-house. Past literature has indicated the importance of the buy vs build decision to the organisation even suggesting that correctly managing the choice could be the key to managing IT. This research aims to identify the factors that an organisation should consider when making an information systems buy vs build decision. Interviews were conducted with 10 organisations across a spread of industries, involving key strategic IT decision-making personnel at the senior IT executive level. By examining the operational approaches adopted in each of these organisations and the key drivers behind these approaches, we identify the core factors that affect real-world buy vs build decisions in large Australian organisations with a turnover in excess of $750 million. We found that a number of core factors - strategy, commodity and competitive advantage, maturity, cost and requirements fit - critically affect buy vs build, while peripheral factors - risk, time and timing, political factors, and ongoing support - are secondary considerations.
AbettiP.A. (1989). Technology: A key strategic resource, Management Review78(2): 37–41.
2.
AnthesG.H. (2004). Roll Your Own, Computerworld38(31): 29–30.
3.
BalakrishnanJ., and ChengC.H. (2005). The Theory of Constraints and the Make-or-Buy Decision: An update and review, Journal of Supply Chain Management41(1): 40–47.
4.
BalakrishnanS. (1994). The Dynamics of Make-or-Buy Decisions, European Journal of Operational Research74: 552–571.
5.
BenbasatI., GoldsteinD.K., and MeadM. (1987). The Case Research Strategy in Studies in Information Systems, MIS Quarterly11: 369–386.
6.
BrooksB. (1997). Buy vs. build: The website dilemma, Wall Street & Technology15(9): 42–45.
7.
BuchowiczB.S. (1991). A Process Model of Make vs. Buy Decision Making: The case of manufacturing software, IEEE Transactions on Engineering Management38(1): 24–32.
8.
CánezL.E., PlattsK.W., and ProbertD.R. (2000). Developing a Framework for Make-or-Buy Decisions, International Journal of Operations & Production Management20(11): 1313–1330.
9.
CarrN.G. (2003). IT Doesn't Matter, Harvard Business Review81(5): 41–49.
10.
CarrN.G. (2004). Does IT Matter? Information Technology and the Corrosion of Competitive Advantage, Boston: Harvard Business School Publishing.
11.
CavanaR.Y., DelahayeB.L., and SekaranU. (2001). Applied Business Research: Qualitative and Quantitative Methods, Brisbane: John Wiley & Sons.
12.
CerielloV.R. (1984). Computerizing the Personnel Department: Make or buy?Personnel Journal63(9): 44–48.
13.
DaleB.G. (1984). The Importance of Factors Other Than Cost Consideration in Make or Buy Decisions, International Journal of Operations and Production Management4(2): 43–54.
14.
DavenportT.H., HarrisJ., and CantrellS. (2002). The Return of Enterprise Solutions: The Director's Cut, Wellesley, MA: Accenture.
15.
DavisG.B. (1988). Commentary on Information Systems: To buy, build, or customize?Accounting Horizons2(1): 101–103.
16.
EllisG. (1992). Make-or-Buy: A simpler approach, Management Accounting, 70(6): 22–23.
17.
EllisG. (1993). Solving Make-or-Buy Problems with Linear Programming, Management Accounting71(10): 52–53.
18.
EzzyD. (2002). Qualitative Analysis - Practice and Innovation, Crows Nest: Allen and Unwin.
19.
FordD., and FarmerD. (1986). Make or Buy - A key strategic issue, Long Range Planning19(5): 54–62.
20.
FowlerK. (2004). Build Versus Buy, IEEE Instrumentation & Measurement7(3): 67–73.
21.
GremillionL.L., and PyburnP. (1983). Breaking the Systems Development Bottleneck, Harvard Business Review61(2): 130–137.
22.
HayesF. (1995). Corporate Development Puzzle: Buy versus build, Computerworld29(50): 79.
23.
HigginsC.C. (1955). Make-or-Buy Re-Examined, Harvard Business Review33(2): 109–119.
24.
KeilM., and TiwanaA. (2006). Relative Importance of Evaluation Criteria for Enterprise Systems: A conjoint study, Information Systems Journal16: 237–262.
25.
KelleyR. (1992). Build v. Buy: When the going gets tough, do the tough go shopping… or building?Insurance & Technology17(1): 28–32.
26.
KnowlesJ. (1997). Buy Versus Build in Six Words, Datamation43(1): 31.
27.
KurokawaS. (1997). Make-or-Buy Decisions in R&D: Small technology based firms in the United States and Japan, IEEE Transactions on Engineering Management44(2): 124–134.
28.
LyonsD. (1995). To Build or To Buy: How to decide, Infoworld17(38): 117.
29.
MartinJ., and McclureC. (1983). Buying Software Off the Rack, Harvard Business Review61(6): 32–58.
30.
McIvorR.T., HumphreysP.K., and McaleerW.E. (1997). A Strategic Model for the Formulation of an Effective Make or Buy Decision, Management Decision35(2): 169–178.
31.
McManusD.J. (2003). A Model of Organizational Innovation: Build versus buy in the decision stage, The International Journal of Applied Management and Technology1(1): 29–44.
32.
McNallyR.C., and GriffinA. (2004). Firm and Individual Choice Drivers in Make-or-Buy Decisions: A diminishing role for transaction cost economics?Journal of Supply Chain Management40(1): 4–17.
33.
MintzbergH., RaisinghaniD., and TheoretA. (1976). The Structure of ‘Unstructured’ Decision Processes, Administrative Science Quarterly21(2): 246–275.
34.
NelsonP., RichmondW., and SeidmanA. (1996). Two Dimensions of Software Acquisition, Communications of the ACM39(7): 29–35.
35.
NonakaI., ToyamaR., and NagataA. (2000). A Firm as a Knowledge-creating Entity: A new perspective on the theory of the firm, Industrial and Corporate Change9(1): 1–20.
36.
NovakS., and EppingerS.D. (2001). Sourcing By Design: Product complexity and the supply chain, Management Science47(1): 189–204.
37.
PadilloJ.M., and DiabyM. (1999). A Multiple-Criteria Decision Methodology for the Make-or-Buy Problem, International Journal of Production Research37(14): 3203–3229.
38.
ParrA., and ShanksG. (2000). A Model of ERP Project Implementation, Journal of Information Technology15(4): 289–303.
39.
PoppoL., and ZengerT. (1998). Testing Alternative Theories of the Firm: Transaction cost, knowledge- based, and measurement explanations for make-or- buy decisions in information services, Strategic Management Journal19: 853–877.
40.
ProbertD.R. (1999). Technology Sourcing: The link to make-or-buy, PICMET'99, Portland, USA, July.
41.
RandsT. (1992). The Key Role of Applications Software Make-or-Buy Decisions, Journal of Strategic Information Systems1(4): 215–223.
42.
RandsT. (1993). A Framework for Managing Software Make or Buy, European Journal of Information Systems2(4): 273–282.
43.
RosenJ. (2001). Build Versus Buy: A fresh look & other gotchas, Wall Street & Technology19(10): 71–72.
44.
RyanG.W., and BernardH.R. (2003). Techniques to Identify Themes, Field Methods15(1): 85–109.
45.
SeddonP.B. (2005). Are ERP Systems a Source of Competitive Advantage, Strategic Change14: 283–293.
46.
ShangS., and SeddonP. (2002). Assessing and Managing the Benefits of Enterprise Systems: The business manager's perspective, Information Systems Journal12(4): 271–299.
47.
SingletonJ.P. (1981). Some Tips on Taming Troublesome Software, ABA Banking Journal, (September) 133–134.
48.
StalkerI. (2003). The Role of 3u Compact PCI in Military System, Embedded Computing Design1(3): 40.
49.
UlfederS. (2003). Buy! No, Build!, Computerworld37(22): 39–40.
50.
VenkatesanR. (1992). Strategic Sourcing: To make or not to make, Harvard Business Review70(6): 98–107.
51.
VoutsakisN., and KaltD. (2004). Is it Better to Buy or Build Financial Systems?Optimize (March) 19–20.
52.
WelchJ.A., and NayakP.R. (1992). Strategic Sourcing: A progressive approach to the make-or-buy decision, The Executive6(1): 23–31.
