Standard product or custom build? The five-year answer

The build-vs-buy decision usually arrives as a stack of proposals: a proven product with licence fees, a custom build with a bigger day-one price. The spreadsheet comparison looks objective. It almost never is — because it compares year one, and the decision lives for five.

Where standard products win

For standard support functions — accounting, HR, document management — a proven off-the-shelf product usually wins, and it isn’t close: faster to adopt, lower risk, someone else pays for its maintenance. When this is the answer, we say so, even when a custom project would have been better business for an advisor.

Where custom pays for itself

Where the process is your competitive edge — the customer experience only you offer, the core workflow your margin depends on — bending it to fit a standard product means paying licence fees to become more like your competitors. That is where custom development earns its price back.

The five-year questions

Before you sign either way, price these into the comparison: What does the licence cost at your year-five user count? Who owns the integrations when either side changes? What does leaving cost — data, retraining, downtime? And with today’s AI-assisted development, the custom price is often lower than the last time you checked.

One more thing: micro-applications

For many “we need a small tool” cases the honest answer is now neither buy nor a traditional build — it’s a micro-application your own team creates in days inside a governed environment. Think it, build it, try it.

Proposals on the table? Book a 30-minute discussion — you’ll get an independent view with no software to sell you.