Build or buy? Choosing between custom and off-the-shelf software
When off-the-shelf software is the right answer, when custom development earns its cost, and why integrating the two is often the real choice.
Few decisions shape a technology budget more than whether to build software or buy it. The honest answer is rarely “always build” or “always buy”. It depends on how distinctive your process is, how much change you can absorb, and what you will need in five years — not just next quarter.
When buying is the right answer
- The process is common to many organisations — payroll, accounting, email, document storage.
- A mature product already does what you need with configuration, not workarounds.
- You would rather adopt a standard way of working than maintain your own.
- Time to value matters more than a perfect fit.
When building earns its cost
- Your process is genuinely different, and that difference matters to the people you serve.
- Products force staff into workarounds — spreadsheets beside the system, re-typed data, manual checks.
- You need several functions working on one record, and no product connects them well.
- Local realities — mobile money, regulation, connectivity, language — are poorly served by available products.
The option people forget: integrate
Many organisations do not need to replace anything. They need the systems they already have to share data — payments matched to records automatically, one sign-in, reports drawn from source systems. Integration is often faster and cheaper than either building or buying something new.
Look at the five-year cost, not the first invoice
Compare options on the total cost of ownership: licences or development, implementation, data migration, training, hosting, support, and the cost of changing the system as you grow. A cheaper licence can be expensive if every change needs a vendor request; a custom build can be expensive if nobody plans for maintenance.
Questions to settle before deciding
- Which parts of our work are standard, and which are distinctive?
- What workarounds do staff use today, and what do they cost?
- Who will own and change the system after launch?
- Can we leave — what happens to our data if we switch?
- What must the system connect to?