Every growing South Australian small business reaches the same fork in the road. The spreadsheets, shared inboxes and copy-paste between systems that worked at five staff start to cost real hours at fifteen. The question is whether to buy an off-the-shelf SaaS product, configure and connect the tools you already pay for, or build custom software around the way you actually work. This guide sets out how to make that decision on evidence rather than enthusiasm: what each path really costs over five years, where custom software earns its keep, the risks to price in, and what to ask any developer before you sign. It is general guidance, not financial or legal advice.
Start with the problem, not the product
Most build-versus-buy debates go wrong because they start with a solution someone has seen in a demo. Before comparing options, write down in one page:
- The process. Who does what, in which system, and where the information is re-keyed or chased by email.
- The cost of the status quo. Staff hours per week spent on the manual steps, errors that reach customers, and work you turn away because you cannot scale it.
- What is genuinely different about you. The part of your process that wins you customers, as opposed to the parts every business in your industry does the same way.
- The constraints. Budget range, the date it needs to work by, who will own it internally, and any privacy or industry obligations.
That last distinction matters most. Payroll, accounting, email and rostering are rarely where a small business differentiates, so buying is almost always right. The quoting engine, booking flow, job workflow or customer portal that makes you easier to deal with than a competitor is where custom work can pay back.
The three realistic paths
1. Buy an off-the-shelf SaaS product
A subscription product built for your industry gives you a working system in days or weeks, with hosting, security patching, backups and new features handled by the vendor. It is the right default when the product covers most of your process and the gaps are things you can change your process to fit.
The trade-offs are real, though. Per-user pricing grows with headcount and tends to rise at renewal. You adopt the vendor’s workflow, and the features you need may sit on a higher tier. Your data lives in their platform, so check how easily you can export all of it, in a usable format, if you leave.
2. Configure and integrate what you already have
This is the most underrated option. Many businesses already pay for Microsoft 365 or Google Workspace, an accounting platform such as Xero or MYOB, and a CRM or job management tool, but the systems do not talk to each other. Connecting them through their published APIs, or with low-code tools such as Power Automate, often removes most of the manual work for a fraction of the cost of a new system. Our CRM and Xero or MYOB integration architecture shows how that works in practice, including how to avoid duplicate customers and invoices.
The risk is sprawl: dozens of fragile automations that nobody documented, owned by whoever built them. Treat integrations as software, with an owner, a list of what runs where, error alerts and a test when either system updates.
3. Build custom software
Custom software fits when the process is your competitive advantage, when no product covers it without heavy workarounds, or when you need to join several systems behind one experience for customers or field staff. Modern cloud platforms mean a well-scoped custom application no longer needs its own servers or an IT department to run it.
The trade-off is that you take on ownership. Someone has to host it, patch it, back it up, fix it and keep it current for years, and the upfront cost and delivery time are higher than a subscription. Custom software is a business asset only if it is built and supported like one.
Compare total cost of ownership over five years
The sticker price is the wrong comparison. A subscription that looks cheap per month and a build that looks expensive upfront can land in very different places once you add everything up. For each option, estimate:
- Upfront: licences or build cost, data migration, configuration, integration and staff training.
- Recurring: subscriptions at your expected headcount in year three and five, hosting, support and maintenance, and add-ons you will need. For anything cloud-hosted, ask for a running-cost estimate with its assumptions and set a budget alert from day one (see cloud cost control for SA small businesses).
- Internal time: the hours your own people will spend administering, testing and working around gaps.
- Exit cost: what it would take to move off the option later, including data export and retraining.
- Benefit: hours saved, errors avoided and revenue enabled, valued conservatively.
As a rule of thumb for budgeting, plan for ongoing support and improvement of a custom application each year as a meaningful share of its build cost, not as an afterthought. If that recurring figure is not in the plan, the comparison is not honest.
Where custom software usually earns its keep
- Customer and client portals that let customers book, quote, track jobs or upload documents without phoning or emailing.
- Field and mobile workflows where staff capture photos, checklists and signatures offline and the data lands straight in your systems. See our field inspection architecture.
- Document and request intake where forms, emails and attachments are classified and routed automatically, sometimes with AI extracting the key fields for a person to check. If you are replacing PDF forms or taking payments online, our guide to online forms and payments covers PCI DSS scope and accessibility. See our document intake architecture.
- Online ordering joined to stock and accounts, so orders, inventory, fulfilment and invoices stay in step. See our retail order integration architecture.
- Replacing a fragile spreadsheet or Access database that the business now depends on and only one person understands.
Hybrid is usually the answer
For most small businesses the best result is not one path but a combination: buy the commodity systems, integrate them properly, and build only the thin layer that makes you different, such as a portal or app that reads and writes to your accounting and CRM platforms. This keeps the custom footprint small, which keeps the ongoing cost and risk small, while still giving customers an experience your competitors cannot copy by buying the same subscription.
Risks to price in, whichever path you choose
- Data ownership and exit. Confirm in writing that you own your data and can export it in full. For custom work, confirm you own the source code and receive it, with documentation, at handover.
- Privacy. Know where customer data is stored and who can access it. Many small businesses fall under the Australian Privacy Act small business exemption, but not all, for example health service providers and businesses that trade in personal information. Customers increasingly expect the same care regardless, and keeping data in Australian cloud regions is straightforward. Our data residency guide explains how residency works on AWS and Azure.
- Security basics. Multi-factor authentication on every system, least-privilege access and patching matter more than any feature list. The Essential Eight guide for SA SMEs sets out the baseline that larger customers and government buyers will ask about.
- Backups and recovery. SaaS vendors protect their platform, not necessarily your ability to restore last Tuesday’s data after a mistake. Decide how much data you can afford to lose and how long you can be offline, then check each option meets it.
- Key-person risk. A system only one employee or one freelancer understands is a liability. Require documentation and a support arrangement that survives people leaving.
Questions to ask any developer before you sign
- Have you recommended configuring or buying instead of building, and why not here?
- Will you start with a short, fixed-price discovery that produces a scope, estimate and risks I can take to another supplier if I choose?
- What will it cost per year to host, support and keep this current after launch?
- Who owns the code, the cloud accounts and the data, and what do I receive at handover?
- Where will the data be hosted, and how are backups and restores tested?
- How will you release in small increments so we see working software early, rather than one big launch?
- What happens if your key developer leaves?
A simple decision checklist
- Write the one-page problem statement and cost of the status quo
- Separate commodity processes from the ones that differentiate you
- Check whether integrating existing tools solves most of the problem
- Shortlist SaaS products and test them with your real data and scenarios
- Compare five-year total cost, including internal time and exit cost
- Build only where it differentiates, and keep the custom footprint thin
- Lock in data ownership, code ownership, Australian hosting and support before you start
This article reflects common practice as at late 2026. Product pricing, privacy law and vendor terms change, so confirm current details with suppliers and your advisers before committing.
Talk to an Adelaide team
If you are weighing up a new system, a portal or a set of integrations for your South Australian business, talk through your options with our team or call 0402 401 584. We will tell you plainly if an off-the-shelf product is the better fit. You can also read about our application development, intelligent automation and managed services.