Custom software vs off-the-shelf: a decision framework
“Should we build it or buy it?” comes up in almost every growing business. Usually it’s a team that has outgrown a spreadsheet, or is paying for three tools that each do 70% of the job. Both answers can be right. The mistake is deciding on gut feel, or on the first year’s cost alone.
The real question
Don’t start with “custom or off-the-shelf?” Start with: is the process we’re supporting a source of advantage, or just a cost of doing business?
- Payroll, accounting, email and basic CRM are the same for nearly everyone. Buy them.
- The way you quote complex jobs, schedule specialists or manage a particular supply chain may be exactly why customers choose you. That’s where custom software earns its keep.
When off-the-shelf wins
Buy when:
- your process is standard, or you’re happy to adapt to the tool’s way of working;
- you need it running in weeks, not months;
- the vendor is established and the product is improving;
- the total subscription cost stays reasonable as you grow;
- you can export your data if you ever leave.
Modern SaaS is excellent at standard work. Building your own version of something a mature product already does well is rarely a good use of money.
When custom pays off
Build when:
- the tool would force you to give up a process that’s part of what makes you different;
- you’re stitching several tools together with manual copying in between, and errors are creeping in;
- per-user pricing grows faster than the value as your team grows;
- you need a portal or app your customers use, and it has to feel like your brand;
- you need integrations or data ownership the vendor won’t support.
The hybrid most businesses miss
It’s rarely all or nothing. The most cost-effective setup we see is often:
- off-the-shelf for the standard backbone (accounting, email, CRM);
- custom integrations that move data between them automatically;
- a small custom tool or portal for the one process that’s genuinely yours.
That keeps the custom part small, focused and cheaper to maintain, while removing the manual work between systems.
Total cost over five years
Compare options over five years, not one. For each, list:
| Cost | Off-the-shelf | Custom |
|---|---|---|
| Upfront | Setup, configuration, migration, training | Discovery, design, build, migration, training |
| Ongoing | Subscriptions per user or tier, add-ons, price rises | Hosting, maintenance, improvements |
| Hidden | Workarounds, manual steps, extra tools to fill gaps | Your team’s time on requirements and testing |
| Exit | Data export, switching costs | Handover if you change developers |
Put rough numbers against each row. The answer is often obvious once the hidden costs, such as the hours spent copying data between tools, are written down.
A quick test
- Is this process a reason customers choose us? If no, buy.
- Does an established product do at least 90% of what we need without workarounds? If yes, buy.
- Will the five-year subscription cost exceed a focused custom build plus upkeep? If yes, consider building.
- Is the real pain the manual work between tools? If yes, start with integrations, not a rebuild.
Custom software is one of the things we do, so take this with that in mind. We’ll still tell you when a subscription is the better answer. See our custom software service, or describe the process that’s slowing you down.
