Off-the-shelf is faster and cheaper — until it isn't. Here is the honest framework we use to tell Caribbean institutions when to buy a product, when to build custom, and how to stop paying monthly forever for a system that only half-fits.
"Should we buy something off the shelf, or build it ourselves?" is one of the most consequential technology questions an institution asks — and it is usually framed as a false binary. The honest answer is that it depends on a small number of factors you can actually reason about.
When Buying Is the Right Call
Off-the-shelf software is the correct choice when your need is genuinely common and the product fits it well. Email, accounting, document storage, video calls — these are solved problems. If a mature product does 90% of what you need and the remaining 10% does not touch your core operation, buy it. Building your own would be a waste of money and a maintenance liability.
When Off-the-Shelf Becomes the Expensive Option
The calculation flips when the software touches the work that makes your institution *your institution* — the case management, the compliance workflow, the citizen-facing service, the confidential records. Generic tools force you to work the way the vendor imagined, and the gaps get filled with spreadsheets, manual workarounds, and rising subscription fees. The "cheap" option quietly becomes the costly one.
The Hidden Cost of Renting Forever
Every month on a rented system that half-fits is money spent without building anything you own. Worse, it deepens the dependency: the longer you build your operations around someone else's product, the more expensive it becomes to ever leave. This is the same trap that undermines an institution's digital sovereignty, and it applies just as much to a private practice as to a ministry.
A Simple Decision Framework
Before you build or buy, answer these honestly:
- Is this need common and well-served by a mature product? → Lean buy.
- Does the software touch your core, differentiated operation? → Lean build.
- Will off-the-shelf force manual workarounds within a year? → The "cheap" option is not cheap.
- If the vendor vanished, would we lose our operation and our data? → Build, and own the result.
- Do we have a clear enough picture of how we actually work to specify it? → If not, that is the first project.
Own the Result Either Way
Building custom does not mean building everything from scratch or running it yourself — it means the architecture, the data, and the result are yours, documented for your own team, with no lock-in. Whether you buy, build, or do both, the goal is the same: a system that fits how you actually work and that you control. The starting point is an honest map of your operations, which is exactly what planning a digital transformation is for.