Custom software vs off-the-shelf
This decision is usually made on price and regretted on fit, or made on fit and regretted on price. The useful question is not which is better but which failure you can live with: paying for capability you do not use, or paying to work around capability you do not have.
Custom build
Built to your process, you own the code
Off-the-shelf product
Buy a licence, adapt to its model
Side by side
| Criterion | Custom build | Off-the-shelf product |
|---|---|---|
| Upfront cost | Significant — scoped per project | A few thousand a month, or a modest licence |
| Time to running | 8 weeks to 9 months | Days to a few weeks |
| Fit to your process | Exact, by definition | Close at best; you adapt to the gaps |
| Cost at scale | Flat — no per-user charge | Grows with users and modules, often steeply |
| Ownership | Source code is yours | You rent access; leaving means migrating |
| Maintenance burden | Yours, or your vendor's | The vendor's |
| Feature roadmap | You decide | The vendor decides, and you wait |
| Support at 2am | Depends who you hired | Usually a mature support organisation |
| Risk of total failure | Real — projects do fail | Low; the product already works |
Choose Off-the-shelf product when
The cases where we are not the right answer.
- Your process is genuinely conventional and a product already models it well
- You need something running in weeks and can live with the gaps
- You have no internal technical capacity to direct a build or maintain the result
- The budget is tight enough that a custom build would be a compromised custom build, which is the worst of both
- The process you want to encode is still changing month to month
Choose Custom build when
- Your process is genuinely your competitive advantage and a product would flatten it
- Per-user licensing has become a significant and growing line item
- You are running three or four products plus spreadsheets to cover one workflow
- You need integrations the product will not build and will not let you build
- Data residency, audit or regulatory constraints rule out the vendor's hosting
Our honest view
Buy off-the-shelf unless you have a concrete reason not to. Most businesses do not need custom software; they need one good product properly implemented. The genuine case for custom is when the gap between your process and every available product is costing you more than the build would — which is a calculation, not a feeling. If you are between the two, our ready-made systems sit in the middle: a working product on day one, with the source code so you can change it later.
Common questions
Is custom software always more expensive?
Upfront, almost always. Over five years, often not — particularly where per-user licensing scales with headcount. The crossover for a 50-user business is typically somewhere between year two and year four, but it depends entirely on the licensing model you are comparing against.
Can we start with off-the-shelf and move to custom later?
Yes, and it is frequently the right sequence. Using a product first teaches you what you actually need, which makes the eventual custom build far better specified. Just make sure you can export your data before you commit.
What is the middle option?
A ready-made system whose source code you own. You get a working product immediately and the ability to change it later without the vendor's permission. That is how our vertical products are licensed.
Still not sure which way to go?
Tell us the situation. We will give you a straight answer, including when that answer is that you should not hire us.