10 Signs Your Business Needs Custom Software
Listen to this article · 10 min
On this page 11 sections
- 1. Growth is outpacing the tool
- 2. The same data is typed in twice
- 3. The features you need do not exist
- 4. Compliance is being managed outside the system
- 5. Staff complain, and training takes weeks
- 6. You are paying for features nobody uses
- 7. The customer experience is shaped by the software
- 8. Manual processing is producing errors
- 9. Every process change needs a vendor ticket
- 10. You cannot get your data out
- Where to start
The short version
- The ten signs, condensed: growth outpacing the tool, disconnected systems creating data silos, missing industry-specific features, compliance gaps, staff frustration and long training, licence spend on unused features, a customer experience the software limits, manual processes at error-producing volume, process changes that need a vendor ticket, and data you cannot get out.
- The useful ones are the measurable ones: what you pay for unused licences, and how many hours go into manual reconciliation between systems that will not talk to each other.
- Custom software does not end recurring cost. Budget roughly 15 to 25 per cent of the build each year for hosting, maintenance and iteration, which is the number in our [2026 cost guide](/how-much-does-custom-software-cost-in-perth-2026).
- No thresholds anywhere: no number of users, licences or wasted hours at which a sign becomes a decision.
Every business we work with has at least two of these. Having one is not a reason to commission software. Having four that cost money every week is.
The signs are ordered by how easy they are to measure, not by how serious they are.
1. Growth is outpacing the tool
The software was right for fifty users and there are now two hundred. Pages are slow, reports time out, and someone has started exporting to a spreadsheet because the screen will not load.
The fix is not always a rebuild. Sometimes it is a database index and a hosting change. But once the vendor's answer to every question is "that's the next tier", you are paying for their architecture instead of your work.
2. The same data is typed in twice
Two systems that do not talk. A nightly export that half works. Someone re-keying invoices because the accounting package and the job system disagree.
Measure it before you decide anything: count the hours a week spent moving data between systems by hand, then multiply by a loaded hourly rate. That number is the budget the project has to beat.
3. The features you need do not exist
Every industry has a requirement that no general product covers: a specific approval chain, a regulatory form, a pricing rule with an exception on the exception.
Workarounds accumulate. A custom field here, a spreadsheet there, a person who knows the trick. The question is whether those workarounds are a nuisance or the way the business now runs.
4. Compliance is being managed outside the system
If the compliance evidence lives in a folder, and the system of record just happens to be involved, the software is not doing the job.
This matters more than it used to. Australian businesses now have clearer obligations around the personal information they hold, and an audit trail that exists only in email is not an audit trail. We cover the security side in more detail on our app security page.
5. Staff complain, and training takes weeks
Software that fits its users needs a short induction. Software that fights them needs a training program, a cheat sheet taped to a monitor, and one person everyone asks.
Ask new starters what confused them in their first fortnight. They will tell you what long-serving staff have stopped noticing.
6. You are paying for features nobody uses
Pull the last invoice and the usage report. If you are paying for two hundred seats and eighty people signed in last quarter, the licence cost is the smallest part of the waste.
The larger cost is the complexity: every unused module is a menu item staff have to learn to ignore.
7. The customer experience is shaped by the software
Customers do not care what your system can do. They care whether they can book, pay, track or ask a question without calling.
If the answer to "can we change the booking flow" is "not without the vendor", the product is deciding how your customers experience your business.
8. Manual processing is producing errors
Not errors that get caught. Errors that reach a customer, a supplier or a regulator.
Automation earns its cost fastest here, because the alternative is a person doing the same check four hundred times a week and eventually missing one. Start with the step that has caused the last three problems, not the whole process.
9. Every process change needs a vendor ticket
A rule changes, and the software takes six weeks and a fee to catch up. The business starts working around the system rather than in it.
This is the quiet one. It does not feel like a crisis, and over two years it means the software describes how you worked in 2024, not how you work now.
10. You cannot get your data out
Ask for a full export before you need one. If the answer is a PDF, a screenshot, or a fee, you do not own your data, whatever the contract says.
This sign matters whether or not you ever build anything. It is also the cheapest one to test this week.
Where to start
Do not start with a build. Start with the two signs that cost you the most money, write down what the current process costs per month, and take that number to a scoping conversation.
If a product already covers the problem, we will say so. If it does not, we will tell you what a first release would include and what it would cost. Talk to us or read the 2026 cost guide first.
Was this useful?
Thanks — noted.
Share
Petr Červenka
Petr is the founder and lead developer at Nano Solutions, a Perth-based custom software firm. With over a decade of experience building enterprise platforms for government and private sector clients, he leads delivery of complex projects across Australia.
Connect on LinkedIn