Build or Buy? Custom Software Versus Off-the-Shelf for a Growing Company
When to buy standard software and when to build your own: the real cost of each over three to five years, a decision table, and the hybrid most growing companies end up with.
The short answer
Buy software for the work that every company does the same way: accounting, payroll, email, a standard CRM. Build software for the work that makes your company different, or that no product fits without painful workarounds. Many good systems are both: a bought core, with custom software around the processes where you compete.
Weighing this for your business? Request a project review

Our take
Axiom Forge advises buying wherever a standard product fits. We build where a process is a real advantage or where standard products force the business to bend, and we connect the custom parts to the bought ones so that the team works in one system, not five.
In this article6 sections · 4 min
Martin Fowler describes the distinction as utility versus strategic. A utility function has to work well, and nobody wins customers by doing it better: payroll is the classic example. A strategic function is part of how the company competes.
For utilities, a standard product carries the experience of the many companies that already use it and usually costs less than building your own. For strategic functions, a standard product makes you the same as everyone else who bought it.
The subscription price is only the start. Add the cost per user as the team grows, the configuration, the integrations with your other systems, the training and the paid tiers that unlock the features you actually need.
Add also the workarounds: spreadsheets beside the system, manual copying between tools, steps the staff perform only because the software requires them. This cost is real, and it appears in no invoice.
Custom software has a build cost and a running cost: hosting, monitoring, security updates and improvements. It also needs an owner inside the company who decides priorities. Without one, a custom system decays as surely as a neglected one you bought.
In return you own the system, pay no licence fee per user and can change it when the business changes.
Answer each question for the process in front of you, not for the company as a whole.
| Question | Points to buying | Points to building |
|---|---|---|
| Is the process an advantage? | No, it is standard practice | Yes, it is how you win |
| Does a product fit without workarounds? | Yes, for most steps | No, core steps need workarounds |
| How many systems must it connect to? | Few, with ready connectors | Many, with rules of your own |
| Who should own the data model? | The vendor’s model is acceptable | You need your own |
| Five-year cost | Licences stay below build and run | Licences and workarounds exceed them |
The choice is rarely all or nothing. A common, healthy design keeps standard products for finance, communication and storage, and adds custom software where the company is unusual: a customer portal, a pricing engine, a scheduling system, an internal tool that removes a manual process.
The custom parts connect to the bought ones through their interfaces. The quality of those connections decides whether the result feels like one system.
Map the process as it runs today, including the spreadsheets and the messages between people. Price both routes over three to five years, counting the staff time on each. UK government guidance for public services gives similar advice: test your understanding of user needs first, and minimise the total cost of ownership, including the risk of being locked in to long contracts with particular tools and providers.
If the answer is still unclear, build the smallest custom piece that removes the most painful workaround, and measure what changes.
Discuss your project with the founder
Is custom software more expensive than SaaS?
In the first year, usually yes. Over several years the comparison changes: subscriptions grow with every user and every tier, while custom software has a build cost and a running cost that does not rise with every user. Compare both over three to five years, including staff time spent on workarounds.
When does custom software make sense?
When the process is part of how you compete, when standard products force workarounds in core steps, or when several systems must be connected by rules of your own.
Can custom software work with our existing tools?
Yes. Most modern business products offer interfaces for integration. Custom software commonly sits beside a bought core and connects to it, so the team works in one flow.


