The short answer: buy off-the-shelf when your process is standard, build custom when the process is your competitive advantage. The practical test is the 80% rule: if a packaged product covers 80% of your need and the missing 20% is not what wins you customers, buy it and adapt. If the missing 20% is your business, that is exactly the part worth building.
We sell custom software development, so read what follows knowing our bias — and knowing that we put this framework in every specification we write, including when it concludes "don't hire us, buy Odoo."
The case for buying
Someone else pays for improvements. A product with thousands of customers gets features, security patches and compliance updates funded by all of them. Your accounting package handles the new e-invoicing mandate because it must; your custom build handles it because you paid again.
Faster to value. Configuration takes weeks; development takes months. If the need is urgent and standard, buying wins on time alone.
Predictable early costs. Licences are known numbers. Custom estimates — even honest, specified ones like ours — carry more variance.
Standard processes are usually fine. Payroll, bookkeeping, email, HR administration: your company does not win customers by processing expenses differently. Adopt the package's process and move on.
The case for building
The process is your edge. If the way you quote, schedule, price or serve is why customers choose you, forcing it into a package's shape sands off the very thing that differentiates you. This is the strongest reason to build, and the only one that survives scrutiny alone.
The per-seat math turns against you. SaaS pricing that is trivial at 10 users becomes a permanent tax at 200. We have replaced tools whose annual licence cost exceeded the one-time build cost of a custom equivalent — every eighteen months, forever.
Integration is the actual product. Sometimes what you need is not an application but connective tissue: your ERP talking to your logistics provider talking to your e-commerce. Packages rarely fit the gaps between packages.
Workaround sprawl. When a packaged tool is surrounded by fourteen spreadsheets that fix its shape mismatch, you are already paying custom-software costs — in labour, errors and fragility — without getting custom-software fit.
The five-year comparison
Compare honestly over five years, not one:
| Cost | Off-the-shelf | Custom |
|---|---|---|
| Year 1 | Licences + implementation + config | Specification + build (larger) |
| Years 2–5 | Licences × users × price rises | Hosting + maintenance agreement |
| Change requests | Within product limits, or impossible | Yours to prioritise |
| Exit | Data export, retraining, re-implementation | You own it; nothing to exit |
Custom is front-loaded; SaaS compounds. Where the lines cross depends on user count, licence tier and how much customisation the package needs anyway — which is why we produce this table with real numbers during discovery.
Traps on both sides
The customised package. The most expensive option is usually a heavily customised commercial product: you pay licence fees and development costs and every vendor upgrade risks your customisations. If you need more than modest configuration, that is the signal to reconsider the choice entirely.
The custom system with one parent. A bespoke build that only its original developer understands is a business risk, not an asset. Insist on documentation, tests, standard frameworks and code ownership — the things that make a second team able to take over. (This is a deliverable list; we publish ours in how we work.)
A decision checklist
- Write down the workflow. If you can't, you're not ready to build or buy.
- Score the best two packages against it honestly. What % fits without workarounds?
- Ask: is the unfitting part our differentiator, or just our habit?
- Run the five-year cost table for realistic user counts.
- Whichever way you decide — keep your data exportable and your process documented. That discipline preserves the option to change your mind, which is worth more than either choice.
If you want a second opinion with numbers, our discovery phase produces exactly this comparison for your specific case — and it is yours to keep whichever way it points.