The Great Software Dilemma: When to Build and When to Buy

Deciding between building custom software and buying an off-the-shelf solution is one of the most consequential choices a technology leader makes. Get it wrong and you either pay for capability you'll never use, or spend years working around limitations baked into a product you don't control.

The case for buying

Off-the-shelf software gets you to market faster. The implementation risk is lower because the product is already proven. Vendor support, updates, and compliance patches come as part of the subscription. For non-core functions — HR, payroll, CRM — buying almost always makes sense.

The case for building

When the software IS your competitive advantage, buying means handing that advantage to a vendor. Custom software fits your process exactly, integrates with your existing stack on your terms, and can be evolved as your needs evolve. The total cost of ownership over five or ten years is often lower than it appears when you account for vendor lock-in, price increases, and the opportunity cost of workarounds.

The questions to ask

• Is this software core to your competitive differentiation? If yes, lean build.
• What does the total cost look like over five years? Include implementation, training, customisation, and vendor price escalation.
• How much of the off-the-shelf product will you actually use? Paying for 80% you don't need is waste.
• What is your in-house engineering capacity? Build requires capability and commitment.
• How quickly do requirements change in this domain? High volatility favours custom.

The honest answer

Most decisions are hybrid. Buy the commodity, build the differentiator. The mistake is treating it as binary.