When a team drifts back to its spreadsheet a month after new software goes in, the software usually asked them to change how they work, and the old way won. Watch how the work really happens before you choose anything: buy off the shelf when a tool fits that work, and build around the team only when nothing does.
Most owners read the drift as stubbornness. It rarely is. The old way is fast for the people doing it, and they are protecting their day.
What does software nobody uses cost?
More than the subscription. While the new tool and the old way both run, the team does the job twice: once where they actually work, and once where the manager looks. The monthly bill keeps arriving for the empty one.
The bigger cost comes later. The next tool you bring in gets a colder welcome, because the team remembers the last one. That trust is slow to earn back.
Why do teams go back to the old way?
Because the old way was built by them, for exactly the job in front of them. A spreadsheet has the columns they need and no others. Paper goes where the van goes. A message to a colleague gets an answer in two minutes.
New software often arrives chosen from a demo, by someone who does not do the job. It adds a login, then a form with ten required fields, half of which feed a report the person filling them in will never read. The person entering the data carries the cost while someone else gets the benefit. That trade never lasts.
What did we see in our own work?
Fit keeps going after the day the software goes in, even when it is built around the team.
In September 2026, we were bringing tools into a property team we work with, each one built for the way that team already runs. Building them was half the job. What we learned is that software built for a team still has to be walked into each role's day, because a tool nobody has seen inside their own day is easy to pass by.
So we changed how we brought it in. Each role is shown only its own part, one role at a time, instead of everyone in one room at once. The next step goes inside the alert people already read, so nobody has to go looking for the tool.
Is off the shelf the right call?
Most of the time, yes. Common jobs like booking, invoicing and reminders are shared by thousands of businesses, and a standard tool will be cheaper and better tested than anything built for you. The signs you have outgrown one are in buy the tool, or build it?
The test for fit is simple. Can your team do the job in the tool the way they do it now, or close to it? If yes, buy it, even if it does less than the demo promised.
When is it time for something built around the team?
When the way your team works is part of why customers choose you, and every tool asks you to give it up. Four signs:
- Two tools have drifted the same way. You have tried twice for the same job, and both times the team went back to the spreadsheet.
- Someone copies between apps every day. The tool cannot hold one step, so a person carries it across by hand. A list kept for one week shows how often.
- Your best step is the tool's exception. The part your trade does differently is the part the software treats as a special case.
- Training never ends. Every new starter needs the workarounds explained, because the workarounds are the real process.
What does custom software cost in Australia?
It depends on the job far more than on the code, so treat any number quoted before someone has watched your team work as a guess. Weigh it against what the current way costs each week, counted in hours of double handling.
Two Australian details change the sum. The ATO treats software subscription fees as an operating expense you generally claim in the year you incur them, while software you have someone develop for your business is in-house software, usually a capital cost with its own rules, including some for small business. Your accountant can say which applies to you.
And IP Australia's guidance says IP created by a contractor belongs to the contractor unless the contract says otherwise. Get ownership in writing before any work starts. It is the third of the five questions to ask any supplier.
Where does it go wrong?
At the description. Ask an owner how a job runs and you hear how it should run. Ask the person doing it and you get closer. Watch them do it and you see the notebook, the second screen and the colleague they message. Software chosen from the first version will not fit the third.
It also goes wrong when software is built too early, for a way of working the team is still changing every month. Settle the process first. By hand is fine.
One step for this week
Pick one job your team does every day. Sit beside the person who does it for one full run, start to finish, and say nothing. Write down every time they leave the main tool: for a spreadsheet, a sheet of paper, a phone, a colleague. Each exit is a place where the software does not fit, and the list tells you whether to change the tool, change how it is set up, or leave it alone.
Software built around how your team already works is what we build for teams. See how it works.

