Business Strategy
Custom Software
Custom Software vs Off-the-Shelf: A Practical NZ Business Decision Guide
Configure, buy, connect or build? Use business importance, fit, ownership and economics rather than an arbitrary percentage rule.
Quick answer
Buy off-the-shelf software when your process is standard, the product fits most of your workflow, and the subscription cost is easier than building. Consider custom software when your process, data, permissions, reporting, integrations, or client experience are materially different from what generic tools support.
- Use SaaS for standard workflows.
- Use custom when the workflow is your advantage.
- Map the process before choosing either option.
Put your business technology questions into a broader roadmap that reflects your business goals and the resources available. Explore Tech Clarity.
Key takeaways
- Buy standard software when it handles the important workflow without costly workarounds.
- Configure or connect existing tools before commissioning a new system.
- Build custom software when the workflow is genuinely valuable and distinctive enough to justify ownership, maintenance and change.
- Use a short decision scorecard instead of an arbitrary “80% fit” rule.
The buy-versus-build decision is not a referendum on whether custom software is clever. It is a business decision about fit, cost, control and ongoing ownership.
Evidence before certainty
Option 1: keep and configure what you have #
Start here. Many problems are settings, permissions, poor templates or an unclear process rather than missing software.
Option 2: buy a commercial product #
Buy when the workflow is common, the product is well supported and the important gaps are tolerable. Payroll, accounting, payments and commodity collaboration are usually places to look for established products first.
Option 3: connect existing tools #
If two good systems force staff to copy the same information between them, an integration may solve the problem without replacing either system.
Option 4: build something focused #
Custom software earns its place when the workflow is genuinely important to how the business operates and existing products force expensive workarounds, poor visibility or repeated manual effort.
Use a scorecard, not an 80% rule #
- Business importance: how much does this workflow matter?
- Fit: are the gaps minor, or do they affect the core job?
- Change: is the process stable enough to encode?
- Integration: can existing tools be connected instead?
- Ownership: can the business support another system for years?
- Economics: is the likely benefit comfortably larger than build and running cost?
A practical test #
If you removed the workaround tomorrow, what would materially improve: fewer errors, faster service, less admin, better control, or a capability the business cannot otherwise deliver? If the answer is vague, do not build yet.
The decision rule #
Configure first. Buy when the market already solves the problem. Connect when the tools are good but the handoff is bad. Build when the workflow itself is valuable enough to deserve software shaped around it.
A useful companion: Workflow Mapping Worksheet.
Quick Questions
How much of my process should off-the-shelf software cover?
There is no magic percentage. Focus on whether the missing parts are minor conveniences or expensive, risky constraints in the core workflow.
When should I connect tools instead of replacing them?
When each tool does its own job well and the real pain is repeated data entry or poor handover between them.
What is the biggest hidden cost of custom software?
Ownership. Someone must maintain dependencies, security, integrations, documentation and the system as the business changes.
Other articles worth reading
Custom Software
10 Signs Your Business Has Outgrown Off-the-Shelf Software
Still patching together spreadsheets and SaaS tools? Here are 10 signs it's time to consider building something custom.
Business Strategy
Outgrowing Spreadsheets: When Your Business Needs a Better System
Spreadsheets are useful until they quietly become the system your business depends on. Here are the signs you have outgrown them, and how to move to a better system without buying the wrong tool.
Custom Software
Replace Spreadsheets With a Custom Internal System
A spreadsheet should become a system when it carries workflow, decisions, permissions, reporting, or data the business depends on. The trick is preserving the logic while reducing risk.