Build or Buy? A Software Decision Guide

Off-the-shelf software, something built for you, or a mix of both? How to decide without a technical background.

The Question Every Growing Business Faces

Your spreadsheets or old system can't keep up, and you need something better. You can buy software off the shelf, or have something built around how you work. Custom projects can run over time and budget, while bought software can disappoint when it doesn't fit how the business really works. This guide helps you choose, and we can help you test the choice before you commit.

The Costs People Often Miss

When Building

  • • Upkeep: shortcuts taken early cost more to fix later
  • • Security updates, for as long as you use it
  • • Relying on the people who built it
  • • Hosting costs that grow as you do
  • • Keeping it in line with changing rules

When Buying

  • • Connecting it to your other systems
  • • Hard and costly to leave once you're in
  • • Limits on what you can change
  • • Moving your existing information across
  • • Subscription prices that rise over time

Seven Questions to Ask

QuestionLeans Towards BuildingLeans Towards Buying
Does it set you apart?
Is this how you win work, or is it the same for every business?
It is part of what makes you differentIt is standard, like payroll or accounts
How soon do you need it?
Can you wait while something is built and tested?
You have time to get it rightYou need it working soon
What will it cost over several years?
Count running costs, not just the first bill.
Cost up front, then upkeepSubscription fees that tend to rise
How well does it fit?
Does it match how your business really works?
Fits exactlyFits most of it; you adjust the rest
How much risk can you carry?
What happens if the project runs late or over budget?
More risk if the scope isn’t clearLess risk; it already works for others
Will it cope as you grow?
More staff, more sites, more transactions.
Built for your growth plansLimited by the vendor’s plans and pricing
How much control do you need?
Can you change it when the business changes?
You decide what changesThe vendor decides

How to use it: Decide which questions matter most to your business, then see which way your answers lean. If they lean both ways, a mix of bought and built is often the answer.

When Building Makes Sense

Build When:

  • The way you work is part of what sets you apart
  • You have rules or requirements no off-the-shelf product handles
  • You need full control of your information
  • You have a clear picture of what you need
  • Your budget allows for surprises
  • You have time before you need it

Usually Worth Building:

  • ✓ Quoting or job costing that matches how you price work
  • ✓ A replacement for a home-grown database the business relies on
  • ✓ Connections between the systems you already have

Rarely Worth Building:

  • ✗ Your own accounting system (Xero and MYOB exist)
  • ✗ Your own email system
  • ✗ Your own video calling

When Buying Makes Sense

Buy When:

  • The process is standard (payroll, accounts, customer records)
  • You need it working soon
  • You don't have technical staff
  • Plenty of good products already do the job
  • You want something proven and stable
  • You prefer a predictable monthly cost to a large up-front one
Watch out: If you'd have to change bought software a lot to make it fit, building may cost less in the long run.

Often the Best Answer: A Mix of Both

Many businesses buy the main software and have a few pieces built around it:

Main Software + Add-Ons

Use Xero or MYOB as the base (with ERPNext alongside for operations if needed), and add custom pieces where you need them

✓ Quicker than building it all

Connect What You Buy

Buy the right software for each job, and have it connected so information flows between them

✓ Easier to swap one product later

Build Only the Gap

Buy for the standard parts, build only what no product does

✓ Room to change as you grow

Counting the Full Cost

Total Cost Over Several Years

If You Build:
  • The first build
  • Yearly upkeep and changes
  • Hosting and backups
  • Security updates
  • Support from the people who built it
  • The cost of waiting while it is built
If You Buy:
  • Subscription fees per user
  • Setup
  • Connecting it to your other systems
  • Training, at the start and as staff change
  • Changes to make it fit
  • Yearly price rises

Comparing the Risks

RiskIf You BuildIf You BuyHow to Reduce It
Runs lateHighMediumStart with a small first version and add to it
Goes over budgetHighLowFixed quotes, delivered in stages
Gets harder to change over timeHighLowBudget for upkeep, not just the first build
Stuck with one vendorLowHighMake sure you can get your information out
Can't keep up with growthMediumMediumPlan for growth from the start

Checklist Before You Decide

Before You Commit:

Common Mistakes

When Building:
  • Underestimating how much is involved
  • Not budgeting for upkeep
  • Building what you could simply buy
  • Taking shortcuts that cost more later
When Buying:
  • Changing off-the-shelf software too much
  • Forgetting about connecting it to other systems
  • Not checking how to leave
  • Choosing on features, not fit

Get a Second Opinion

We help Australian businesses decide whether to build, buy or do a bit of both. We'll look at your situation and give you a straight answer, including:

  • The full cost of each option over several years
  • The risks, and how to reduce them
  • Which products to look at if buying
  • What a custom system would involve if building
  • Where a mix of both makes sense

Start with a free initial chat. If there's work to do, you get a fixed quote.