Article
Custom Software vs Off-the-Shelf: A Decision Framework for Business Managers
The buy-vs-build question is rarely answered well because each side is sold by someone with an interest in the answer. Here is the framework we use — including when we tell clients not to build.
Every growing business hits the same wall: the spreadsheets multiply, the SaaS subscriptions pile up, and someone asks, "should we just build our own system?" The honest answer is sometimes — and the businesses that get it right use a framework, not a feeling. This is the one we use with our own clients, including the many times it concludes: don't build.
The 70% rule
If an off-the-shelf product does 70% or more of what you need, buy it and adapt your process to the rest. The last 30% is rarely worth a custom build — it is worth configuration, an integration, or a small workflow change.
Custom earns its place when the gap sits in the part of your business that makes you different. Nobody should custom-build accounting software; Xero exists. But if your competitive edge is a scheduling model, a pricing engine, or a customer experience nobody else offers, renting the same tool as your competitors caps you at parity.
Compare total cost of ownership, not price tags
Off-the-shelf looks cheap ($99/month) and custom looks expensive ($40,000), until you run both over five years:
| Cost over 5 years | Off-the-shelf | Custom build |
|---|---|---|
| Licences (10 seats, growing) | $30,000 – $90,000 | — |
| Build | — | $25,000 – $80,000 |
| Maintenance & hosting | Included | $20,000 – $60,000 |
| Workarounds for missing features | Real but unbudgeted | Minimal |
| Price rises & plan changes | Outside your control | — |
| Asset value at year five | Nothing — you rented | You own it |
Per-seat pricing is the quiet killer: SaaS costs scale with your headcount whether or not the value does. Custom flips that — the cost is front-loaded, then flattens while the asset compounds. The maths favours buying for small teams and standard problems, and building for scale and differentiation. The cost ranges above are unpacked in our Australian app development cost guide.
The signals it is time to build
- Spreadsheet sprawl: a critical process lives in a spreadsheet only one person understands, emailed around with version numbers in the filename.
- Swivel-chair work: staff re-type the same data into two or three systems because the tools do not talk to each other.
- Process contortion: you have changed how you work — for the worse — to fit what the software allows.
- Per-seat pain: the licence bill has crossed what a build would have cost, and it renews every year.
- The differentiator gap: the thing customers choose you for is managed in a generic tool your competitor can subscribe to tomorrow.
The signals you should buy
- The problem is standard: accounting, email, payroll, documents, video calls.
- A mature product with a healthy ecosystem covers 70%+ of your need.
- You need it running this quarter, not next year.
- Nobody on your side can own the product decisions a build requires.
The hybrid path most managers miss
Buy vs build is a false binary. The best-run systems we see are hybrids: an off-the-shelf core, customised where it counts, and automated in between.
A CRM is the classic case. HubSpot, Salesforce, or Zoho gives you the proven core — but out of the box it reflects a generic sales process, not yours. The value appears when it is designed and configured around how you actually sell, then wired into your quoting, invoicing, and reporting so data flows without re-typing.
The connective tissue is automation: AI and workflow automation now closes most of the 30% gap that used to force a full custom build — document processing, handovers between systems, follow-ups that fire themselves. And when the gap really is your differentiator, that is when a focused custom build makes sense: build the one thing that makes you different, buy everything that does not.
Questions to ask before any build
- What specifically can't the off-the-shelf option do, and what does that limitation cost per month?
- Who on our team owns this product after launch — decisions, not just passwords?
- What is the five-year cost of each path, including licences, maintenance, and workarounds?
- If we build, do we own the source code and the data outright? (With us, yes — always.)
- Can we stage it — smallest useful version first — instead of betting the full budget at once?
If you want those questions answered against your actual systems, a free Discovery Session maps your workflow and gives you the buy, build, or hybrid recommendation with numbers attached — whichever way it points.
Custom vs off-the-shelf FAQs
How much does custom business software cost in Australia?
Focused internal tools typically run $8,000–$30,000; full custom platforms $25,000–$80,000+. Eligible builds can recover up to 43.5% through the R&D Tax Incentive.
Isn't custom software risky?
Unscoped custom software is risky. Staged builds — prototype, smallest version, then iterate with you approving each stage — remove most of it. The riskiest software decision we see is actually years of unbudgeted workarounds on a tool that never fit.
What happens if our developer disappears?
Insist on owning the source code, the hosting accounts, and documentation from day one. If a provider resists any of those, that is your answer about them.
Can we start off-the-shelf and go custom later?
Yes — and it is often ideal: the off-the-shelf phase teaches you exactly what your process needs before you pay to encode it. Just export your data regularly so the migration is yours to make.