--- title: "Build, buy, or configure: the three ways to get business software" url: "https://www.octalhq.com.au/insights/articles/build-buy-or-configure-software" kind: article description: "Build, buy, or configure software? A plain guide to the three ways to get business software, what each costs and risks, and how to choose the right one." published: "2026-09-05T00:00:00.000Z" updated: "2026-09-21T03:06:22Z" topics: ["Buying software"] --- # Build, buy, or configure: the three ways to get business software There are three ways to get business software — buy it off the shelf, configure an existing product, or build custom. Here's what each really means, and how to pick. Buy off-the-shelf when your need is common and a product fits. Configure when a product is close but needs bending. Build custom when your process is unusual or is your advantage. Those are the only three ways to get business software, and most businesses use all three — the skill is knowing which to use where, and not paying custom prices for a job you could have bought. ## The short version - **Buy** — rent a ready-made product; fastest and cheapest to start; you fit your process to it. - **Configure** — an off-the-shelf product adjusted with settings and add-ons; more flexible, but hits a ceiling. - **Build** — software made around your process; the best fit, higher up-front cost, no compromises. - **The right answer is usually a mix** — buy the standard, configure the near-standard, build the part that's genuinely yours. ## What does "buy" actually mean? Off-the-shelf software is built for lots of businesses at once. It's the right call for common, well-solved needs — accounting, email, payroll — where a product will beat anything you'd build. You trade fit for speed and price, and for standard tasks that trade is worth it. The upside is real: someone else maintains it, improves it and fixes it, and you get going in a day. The catch is that you live inside the product's rules. When those rules match how you work, buying is the obvious, smart choice. When they don't, you start paying in workarounds — which is the moment to look at the other two options. ## What does "configure" mean, and where does it stop? Most products let you adjust things — fields, workflows, integrations, add-ons. Configuration gets you closer to your process without a custom build. For a business that's *close* to the product's assumptions, it's often the sweet spot: cheaper and faster than building, and a better fit than the tool out of the box. It works well until the product's underlying assumptions don't match yours. Every off-the-shelf tool is built around a model of how a business "should" work, and configuration lets you decorate that model — it can't replace it. Once your process contradicts the core assumption, you're stacking workarounds, and heavy configuration can quietly cost more than a purpose-built system while still not quite fitting. Knowing where that ceiling sits is half the decision. ## What does "build" mean? Custom means the software is shaped around your process rather than the reverse. It's the right call when your operation is unusual, multi-step, or a genuine part of why customers choose you. It costs more to set up, but it removes the workarounds instead of automating them. The old fear was that building meant a huge quote and a risky project. That's changed. Good custom builds start from proven foundations — the plumbing every system needs is already there — so you pay for what's unique to you, not the basics. And you can start with one focused piece rather than the whole operation, prove it, then expand. ## How do you choose between them? Ask two questions about any given need: how standard is it, and how central is it to your business? - **Standard and peripheral** (accounting, payroll) → buy. - **Close to standard, slightly particular** → configure. - **Unusual and central to your edge** → build. When you find yourself forcing your business to fit the tool, you've crossed out of "buy" territory and into configure-or-build. And when configuration means constant workarounds and a spreadsheet still doing the real work, you've crossed from configure into build. ## What does each one cost and risk? - **Buy** — lowest to start, but watch per-seat and per-transaction fees as you grow, plus the hidden hours lost to workarounds when the fit isn't quite there. - **Configure** — moderate cost, but the risk is over-configuration: piling on add-ons to chase a fit you never quite reach, and paying more than a build would have cost. - **Build** — higher up-front, but priced to your operation and free of the workaround tax. The main risk — a system no one maintains — is a maintenance question, solved by planning for ongoing care from the start. The point isn't that one is always best. It's that each is best somewhere, and using the wrong one is what quietly costs businesses money. ## Related reading - [Off-the-shelf vs custom software: how to actually decide](/insights/articles/off-the-shelf-vs-custom-software-how-to-actually-decide) - [Can you customise off-the-shelf software enough? The limits of configuration](/insights/articles/limits-of-configuring-off-the-shelf-software) - [How much of your business is actually standard vs genuinely unique?](/insights/articles/how-much-of-your-business-is-standard-vs-unique) - Part of our guide to [custom vs off-the-shelf software for Australian businesses](/insights/articles/custom-vs-off-the-shelf-software-guide). ## The honest first step You can't answer "build, buy, or configure" from a brochure — you answer it by understanding how your operation actually runs. That mapping tells you which parts to buy, which to configure, and which are worth building. The value is in what we find. *Tell us what you run, and we'll show you what's possible.*