Build, buy or configure?
One of the most expensive decisions a growing business makes — and most of the advice about it is written by people with one thing to sell. Here's a neutral way to think it through.
One of the most expensive decisions a growing business makes — and most of the advice about it is written by people with one thing to sell. Here's a neutral way to think it through.
Every growing business hits the same fork in the road. A process that used to run on a spreadsheet and a bit of goodwill is now too big, too slow, or too risky to leave as it is. Someone says, "we should get some software for this." And then the real question lands: do we buy something off the shelf, configure a platform to fit, or build something of our own?
It's a big call, and an expensive one either way. Get it right and you quietly remove a handful of daily headaches for years. Get it wrong and you either pay for a custom system you never needed, or spend the next five years bending your business around a product that doesn't quite fit.
Most of what you'll read on this subject is written by someone with one thing to sell. A software vendor will tell you to buy. A development shop will tell you to build. We've been doing this work since 2001 — custom software, ERP and data projects for Australian businesses, government and not-for-profits — and the honest truth is that build is the right answer less often than the people selling builds would like you to believe. Here's how we'd walk you through it.
Buy (off-the-shelf / SaaS). A ready-made product you subscribe to. Fast to start, low cost upfront, and someone else handles the upgrades, hosting and security. The trade-off: you fit your business to the software, and you're a tenant, not an owner.
Configure (extend a platform). Take a flexible platform you already have — or a low-code tool — and shape it to your needs without starting from a blank page. The trade-off: a sensible middle path, but you're still working within someone else's limits.
Build (custom software). Software designed around the way you actually work. It does exactly what you need and nothing you don't, and you own it. The trade-off: it costs more upfront, takes longer, and someone has to look after it.
This is the part the order-takers skip. A custom build is worth it when one of these is genuinely true for you. If you can't point to at least one, buying or configuring is almost always the cheaper, smarter call — and a good partner will tell you so.
Your process is your edge. If the way you do a particular thing is a real competitive advantage, off-the-shelf software will flatten it to match everyone else in your field. Custom is how you protect what makes you different.
The glue costs more than the build. When you'd need three or four separate products stitched together — each with its own licence, each with an integration to maintain — the total can quietly exceed the cost of a single system that does the lot.
Your data can't leave the country — or the building. For health, finance, government and other regulated work, where your data lives and who can touch it is a hard requirement, not a nice-to-have. Off-the-shelf products often can't promise you that; a system you control can.
You'll depend on it for years. Subscription economics flip over time. As a rough rule, a well-scoped custom system tends to beat the equivalent stack of SaaS on total cost somewhere around the three-to-five-year mark. If this is core infrastructure you'll lean on for a decade, ownership usually wins.
Answer these before you talk to anyone trying to sell you something. They'll tell you which way you're really leaning.
If your answers lean toward commodity process, few tools, no data constraints, short horizon — buy. If they lean the other way, a build (or a serious configure) starts to earn its place.
Nobody likes giving a straight answer here, so here's one. In the Australian market, a serious custom build for a mid-sized business typically lands somewhere between the mid-teens of thousands and a few hundred thousand dollars, depending entirely on scope. That range is wide because "software" can mean a tidy internal tool or a company-wide platform.
But the sticker price isn't the real number. Custom software needs looking after — plan for roughly 10–25% of the build cost each year for support, hosting, security and improvements. Off-the-shelf hides its cost the other way around: a modest monthly fee that quietly grows with every extra user, module and integration, and never stops.
The right question isn't "what's the price?" — it's "what does this cost us over the five years we'll actually use it?"
Count the licences, the workarounds, and the hours your team loses fighting a tool that doesn't fit. That's the figure that decides whether a build pays for itself.
For real Australian price ranges by project size — and the costs that show up after launch — see our companion guide: what custom software and ERP actually cost in Australia.
Whatever you choose, three things matter more than they first appear — and they're the ones people wish they'd asked about later.
There's a simple test for anyone you're thinking of trusting with this: do they ever tell you not to build? A partner who recommends a custom build every single time isn't giving you advice — they're reading from an order book. The ones worth trusting start with your problem, not their product, and are perfectly happy to point you at an off-the-shelf tool when that's the cheaper, smarter answer.
That's the lens we bring to every conversation. We're technology-agnostic on purpose — we'd rather recommend the boring, cheaper option that fits than sell you a build you'll regret. And when a build genuinely is the answer, we design it around your process, you own what we make, and we're still here to support it years down the track.
Tell us the problem in plain English and we'll give you an honest read on whether it's a buy, a configure or a build. No obligation, and no order book.