If Shakespeare was an IT manager, the famous question ‘To be, or not to be’ would have been ‘To build or to Buy.’ In fact, the phenomenon of DIY-ing something or buying a commercial product is not only limited to enterprise software. IKEA is running a whole business out of providing utility to ‘build proponents’ and DIY enthusiasts. While building furniture can be fun, building enterprise-level software – not so much. Most organizations come across this build vs buy confusion and often make the wrong decision.
Like any other business decision, the decision to either build software or buy software is significantly influenced by the total cost of the approach and return on investments. If you’re facing a similar dilemma, the table below summarizes the prospects and consequences of the build vs buy software approaches.
Explaining the Build vs Buy Approach
The following table compares the two approaches to help you decide if you should build or buy software:
|Metrics and KPIs||Build Approach||Buy Approach|
|Cost of deployment||Hiring a team of developers, designers, programmers to build the solution||The license fee of the product and deployment costs|
|Time to market||– Time to develop the product |
– Time for performing QA analysis
– Time to fix any patches or bugs found
– Time to deploy the solution
|– Product development, QA analysis, and patch fixes are already taken care of by the solution provider. Therefore, a solution can directly be deployed. |
– Time to configure and install the product.
|Ongoing maintenance and support costs||A dedicated team of IT professionals should be on board to help with ongoing product support and maintenance||The solution provider handles updates, maintenance, and customer support. However, the solution provider might charge a fee for providing these services|
|Learning curve||A steep learning curve is usually associated with the developed product||Commercial products are developed to be used by a wide range of audience with varying levels of technical skills; therefore, in most cases, these solutions are designed to be more intuitive and user-friendly|
Build vs Buy: When is ‘Building’ the right approach?
Building software is going to be beneficial for your business if:
- The software is going to give you a sustainable competitive advantage
- No other available solution can meet your business needs
- The end-points from where your business collects data are not volatile or prone to frequent changes
- You have substantial resources to cover the costs associated with building and maintaining the software
Build vs Buy: When is ‘Buying’ the right approach?
You should opt for buying commercial software if:
- Building software is not the core of your business and is not going to yield you any competitive advantage
- You have limited resources, and you would rather invest them in improving your core business activities
- There are solutions available that address the challenges your business is facing
- You are looking for a quick solution that can be immediately deployed
In summary, the build vs buy software approach doesn’t follow a one size fits all strategy. The answer to if you should build or buy depends on a case-by-case basis and especially the requirements of your enterprise.
See How Brickell Bank Made the Build vs Buy Decision?
IT manager at Brickell Bank, formerly known as Espirito Santo Bank, faced challenges in migrating broker data from MS Access database to IBM mainframe data warehouse.
Learn more about the approach he opted for and other factors that influence build vs buy decisions by downloading the free white paper.