Build or buy: when custom software is the right call

Accounting, payroll, email, a basic online shop, a ticketing desk — these work much the same way everywhere. If a product already does 80% of what you need and the rest is preference, buy it and adapt your habits to it. Paying to rebuild a solved problem is the most common waste we see.

Some work is specific to you: the way you price, schedule, inspect, allocate or serve customers. When that is what makes you better than a competitor, forcing it into a generic product either blunts the advantage or buries it in workarounds and spreadsheets.

Custom software also earns its cost when you need to connect several systems in a way no product supports, when local rules (bilingual documents, post-dated cheques, Emirates ID, government portals) are central rather than an afterthought, or when your staff spend hours a week re-keying data between tools.

• Your team keeps a spreadsheet next to the system “because the system can’t do it”.
• The same data is typed into two or more places every day.
• You have bought two products already and neither fitted.
• The process you want to support is how you win customers.
• You need an app for people outside the company — customers, suppliers, field staff — that reflects your own service.

Between buying and building there is customising: keeping a solid product as the core and building the missing piece around it — a portal on top of your ERP, an integration between two systems, a mobile app that feeds your back office. It is often the cheapest way to get the benefit of both, because you only build what is genuinely yours.

Compare the full picture. A product costs licences that grow with users, plus the time lost to workarounds. Custom software costs the build, then hosting, support and changes for as long as you use it. Neither is free after launch; anyone who tells you otherwise is selling something.

What custom software gives you in return is ownership: the code, the data model and the roadmap are yours, and changes follow your priorities rather than a vendor’s.

List the processes you want to improve, mark which are standard and which are yours, and try the best two or three products against your five must-haves. If a gap remains, that gap — and only that gap — is what you should build.