Most businesses don't start out choosing between custom and off-the-shelf software. They start with off-the-shelf tools because that's the sensible thing to do. The question only comes up later, when the tools stop fitting the way the team works and the workarounds start to pile up.
If you're at that point, this article compares the two options on the things that actually matter day to day: cost and speed, fit, scalability, integrations, ownership, maintenance and vendor dependency. If you want the broader business case for building, our article on when custom software actually pays off covers that. This one is the side-by-side comparison.
The short answer
Off-the-shelf software is usually the right choice for standard business functions. Accounting, payroll, email, calendars and file storage are solved problems. Tools like Xero, MYOB, Microsoft 365 and Google Workspace exist so you don't have to build them.
Custom software starts to make sense when a specific workflow is central to how you operate, generic tools can't model it cleanly, and the cost of working around them keeps growing.
For many small and medium businesses, the best answer is neither extreme. It's keeping the core tools you already use and building only the missing layer.
Cost and speed
Off-the-shelf software is generally faster to start with. You sign up, configure it and your team can be using it quickly. You pay a subscription instead of an upfront build cost.
But the subscription isn't the whole cost. The Australian Government's business.gov.au guidance on digital tools suggests working out the total cost of ownership for any tool, meaning the upfront cost plus the running costs over its life. For off-the-shelf software, that includes per-user licences as the team grows, add-ons, training and the staff time spent on workarounds the tool doesn't cover.
Custom software costs more upfront and takes longer before anyone can use it, because it has to be designed, built and tested. Custom software and automation projects typically start from A$2,500. Final pricing depends on the systems involved, complexity and scope. Larger platforms are scoped through an initial consultation rather than a quick estimate. We explain what drives that scope in how much custom software costs in Australia.
The fair comparison is not subscription versus build cost. It's the total cost of each option over the years you expect to use it, including the manual work each one leaves behind.
Fit to your workflow
Off-the-shelf products are built for the common case. That's their strength. Most businesses can configure them to fit well enough, and sometimes adapting your process to a well-designed tool is an improvement.
The problem comes when your workflow is genuinely different. Then staff start exporting to spreadsheets, copying data between screens and keeping side processes going just to get the job done. If that sounds familiar, see how to replace spreadsheet-based business processes.
Custom software is built around the workflow you have. That's useful when the workflow is part of what makes your business work. It's wasteful when the workflow is standard and a product already handles it well.
Scalability
Both options can scale, but in different ways.
Off-the-shelf software usually scales well technically, because the vendor has built it for many customers. What changes as you grow is the cost (more seats, higher plans) and whether the tool still fits once you add new services, locations or teams.
Custom software scales in the ways you design it to. That gives you control, but it also means scaling has to be planned and paid for, rather than coming with the product.
Integrations
Integrations are often where the decision really gets made.
Many popular tools offer native integrations and APIs. When your systems already talk to each other, off-the-shelf software becomes much more useful. When they don't, people become the integration, retyping information between platforms.
You don't always need custom software to fix that. Often the answer is system integrations between the tools you already have. Our guide on what to do when your business software doesn't integrate walks through the options, from native connectors to custom API work.
Custom software can be designed to connect with your existing systems from the start, but only where those systems provide a way in, such as an API, webhooks or a supported import and export.
Ownership and control
With off-the-shelf software, you're renting access. The vendor decides the roadmap, the pricing and which features stay or go. Your requests may or may not be prioritised.
With custom software, you have far more control over how it works and when it changes. Before any build, make sure the agreement is clear about who owns the code, who controls the hosting and accounts, and how you get your data. If that isn't clear, get advice before you sign.
In both cases, check that you can export your data in a usable format. It's the simplest protection you have.
Maintenance
Off-the-shelf software is maintained by the vendor. Security updates, bug fixes and new features arrive without you having to arrange them.
Custom software needs ongoing care. Dependencies need updating, third-party APIs change, and the software needs monitoring. The Australian Signals Directorate's small business cyber security handbook lists keeping software up to date as one of its three starting measures, and that applies to software you own just as much as software you buy. Budget for ongoing support from the start rather than treating launch as the finish line.
Vendor dependency
Both options create dependency. They just create different kinds.
With off-the-shelf software, you depend on the vendor's pricing, roadmap and continued existence. Niche products with a small customer base can carry more of that risk.
With custom software, you depend on whoever built and maintains it. Good documentation, clean code, sensible hosting and clear ownership reduce that risk. Software that only one developer understands increases it.
When off-the-shelf is the smarter choice
Choose an existing product when:
- the process is standard across most businesses
- a mature product covers most of what you need
- you need something working quickly
- the process is still changing and you're still learning what you need
- the vendor handles compliance or regulatory updates you'd otherwise have to manage
- the tool connects to the rest of your systems
For example, a trades business using ServiceM8 for job management, or a recruitment agency running Bullhorn and posting to SEEK, usually has no reason to rebuild those core systems.
When custom becomes economically sensible
Custom software is worth considering when:
- the workflow is central to how you deliver your service
- staff spend significant time on workarounds every week
- several tools are being stitched together by hand
- you're paying for multiple products and still doing the job manually
- no product handles your rules or reporting properly
- the cost of the workaround is growing as the business grows
The test is simple to describe and harder to answer honestly: will the build remove enough manual work, errors or delay to justify its cost and its ongoing maintenance?
The hybrid approach: keep your core tools and build the missing layer
For many businesses, the best answer is to keep the off-the-shelf systems that work and build only the piece that's missing. That might be an integration, a small internal tool, a customer portal or an automation that moves information between systems.
The Huntress Recruitment project is a good example. Bullhorn stayed as the core recruitment system. The work focused on how job information moved from Bullhorn to SEEK and the company's website, so the team kept the platform it relied on while removing duplicate admin. Similarly, the CorIT Tech onboarding project connected the CRM with project management tools without replacing either.
Because you're only building what the products can't do, this is often smaller and lower risk than a full replacement.
When neither is the answer
Sometimes the problem isn't the software at all. If the process is unclear, constantly changing or the data going into it is unreliable, buying a new tool or building one will just move the problem. Fix the process first. Our article on whether to automate a process or replace the software has a decision framework for working out where the real constraint sits.
Frequently asked questions
Is custom software always more expensive than off-the-shelf?
Upfront, usually yes. Over several years it depends on licence costs, the number of users and how much manual work the off-the-shelf option leaves behind. Compare the total cost of ownership, not just the first invoice.
Can custom software work with Xero, MYOB or Microsoft 365?
Often, yes, as long as the system provides a supported way to connect, such as an API. What's possible depends on the specific product, plan and data involved, so it should be checked during scoping.
Should a small business ever build custom software?
Yes, when a specific workflow justifies it. A small, focused tool that removes a recurring bottleneck can make more sense than a large platform. Start with the smallest version that solves the problem.
Talk through your options
If you're not sure whether to buy, build or connect what you already have, we're happy to look at the workflow with you. 23Labs builds custom software when it's the right call, and we'll tell you when it isn't. Start a conversation and tell us where the current tools fall short.