Client: I’d like to build a system for X process using a low code platform.
Agile CIO: What is your rationale for choosing to build when there are ready-made solutions available to purchase?
This type of conversation occurs more often than I would expect (even in 2024). The desire to build is typically because of a perception that custom is somehow cheaper (or even faster). However, I have to remind myself that I have a point of view that my clients don’t have.
So here are 3 reasons that would lead to me making a build recommendation:
- There are no COTS solutions that address the problem the client is trying to solve.
- This is rarely the case but it is possible.
- The business processes you are trying to automate are unique to your organization.
- You have money to burn.
- Clients rarely understand that it’s not just the initial cost of building their desired system that they need to consider but the ongoing costs required to maintain and update it (people, time, and money).
All 3 reasons have to be true for me to recommend building vs. buying.
Did I miss anything? What are other reasons to recommend developing an application from the ground up vs. buying something off the shelf?
