Use off-the-shelf software when your need is common and a mature product already does it well. Build custom software when the process is specific to your business, when existing tools force costly workarounds, or when the software is itself the product you sell. Most businesses end up with a mix: standard products for standard jobs, connected by custom integrations, plus custom software only where it creates an advantage.
Key takeaways
- Accounting, email, payroll and similar functions are almost always better bought.
- Custom software earns its cost where your process is different and that difference matters.
- Compare total cost over three to five years, including licences, add-ons and workarounds.
- Integration between existing tools is often the cheapest way to fix a broken process.
What are the advantages of off-the-shelf software?
- Available immediately, often with a free trial.
- Maintained, secured and improved by the vendor.
- Predictable subscription pricing at small scale.
- Plenty of people already know how to use it.
What are the disadvantages?
- Your process has to adapt to the product, not the other way round.
- Per-user pricing grows with headcount and annual price rises.
- Important features may sit in higher plans or paid add-ons.
- Your data and workflows are tied to the vendor’s roadmap and terms.
When does custom software make sense?
- The software is the product: a SaaS platform, customer portal or marketplace you sell or operate.
- Your workflow is a competitive advantage and no product models it properly.
- Staff spend hours each week on spreadsheets and copy-paste between systems.
- Licence costs for many users exceed what a focused build would cost over a few years.
- Compliance, data residency or integration needs go beyond what products allow.
How do you compare the costs fairly?
Put both options on the same five-year timeline. For a product, add every licence, the add-ons you will need, the integration work, and the internal time spent on workarounds. For custom software, add the initial build, ongoing maintenance and improvement (commonly planned at 15 to 20% of the build cost per year) and hosting. Then compare. If the numbers are close, buy: the product’s vendor carries the maintenance risk.
What is the middle path?
Many problems that look like “we need custom software” are really “our tools do not talk to each other”. Connecting the products you already use, for example sending website enquiries straight into the CRM and invoices into accounting, often removes most of the manual work at a fraction of the cost of replacing anything. Custom code is then reserved for the part of the process that is genuinely yours.
Buy the commodity, build the advantage, and integrate everything in between.
How should a custom project start?
- Write down the process as it works today, including the workarounds.
- Identify the single workflow that costs the most time or money.
- Build that first, in a few weeks, and put it in front of the people who use it.
- Expand only once the first part is in daily use.
- Keep the code, data and hosting in your own name.