In a lot of Adelaide businesses, one of the most important systems isn't software at all. It's a spreadsheet.
The quote calculator. The job tracker. The stock list, the roster, the commission sheet, the WIP report. Someone built it years ago, it worked, and now part of the business runs on it.
That was the right call at the time. Spreadsheets are still brilliant for one-off analysis and for figuring out how a process should work. The trouble starts when the spreadsheet stops being a tool and becomes the system.
Owners don't call it a spreadsheet problem
Here's an interesting gap. In Budgetly's 2026 CFO survey of 106 senior finance decision-makers in Australian SMEs (a vendor survey; Budgetly sells spend-management software, fieldwork 17-24 March 2026), only 11.3% picked "managing multiple systems / spreadsheets" as a top challenge. Yet 49.1% said their teams spend 40% or more of their time on manual, repetitive work, and 86.8% said at least 20%. Open-text answers mentioned "bad data" and "outdated or fragmented systems". The figures are self-reported and directional, weighted to businesses with 20-99 staff. (Budgetly CFO survey 2026)
SA owners describe the same thing in their own words. From the SA Business Chamber / William Buck Survey of Business Expectations for the June 2026 quarter: "Lots of busy work easily consumes any productivity gains we make." That's an SA professional services firm with 50 to 199 staff. An SA agriculture business with 5 to 9 staff asked to "reduce the number of times we enter the same data for different compliance requirements." (SA Business Chamber / William Buck SOBE, June 2026 quarter)
Nobody calls that a spreadsheet problem. But the spreadsheet is often where that busy work and retyping hide.
When the spreadsheet becomes the system
A spreadsheet is fine while one person owns it. It starts to creak when it turns into a shared system that runs a real process. Several people edit it. There are copies called final_v3. Numbers get retyped from it into Xero, MYOB or the job system. Nobody knows who changed a price, and one person understands the formulas. (If that last part sounds familiar, our post on when one person is the process goes into it.)
The failures are usually quiet ones:
- Someone pastes over a formula with a plain number, and that row stops calculating.
- A lookup range stops one row short after someone adds rows at the bottom.
- Numbers stored as text silently drop out of a SUM.
- Two people each edit their own copy, and the changes never meet.
- The price list in one tab doesn't match the prices on the quote tab.
- Nobody can say for sure which version went to the customer.
None of that is anyone's fault. Excel is a calculation tool, not a multi-user database with a history. Microsoft's own Excel specifications and limits page lists 100 undo levels, and it notes that a workbook using the legacy "Allow changes by more than one user" setting can't have Excel tables. That's fine for analysis, but it isn't built to be the record of who changed what in your business.
What OrionX would build
Here's how we'd turn that spreadsheet into a small app without losing what made it work.
- Read the spreadsheet properly first. We map every tab, formula, lookup and manual step, and who touches it when. Most of your business logic is already in there, and we keep it.
- Move the data into a proper database (for example Postgres), with real tables for customers, jobs, products and prices. We add the rules the spreadsheet never enforced: required fields, valid ranges, no duplicate job numbers, and prices pulled from one price list.
- Put a simple web app on top, built around the way your team already works. It uses the same column names and the same words, with a screen per job or quote instead of a row to scroll to. It works on a phone for people in the field.
- Set up roles and permissions. The apprentice can update job status, only the office can change prices, and only the owner sees margins.
- Keep a full change history of who changed what, when, and what the old value was. "Who changed this price?" takes seconds to answer.
- Keep Excel where it helps. A live export or read-only connection for Excel or Power BI means the person who loves pivot tables still gets them, on clean data.
- Migrate in stages. We import the history, run both side by side for a couple of weeks, then retire the spreadsheet for that process.
- Wire it into Xero or MYOB and your job system through their APIs, so approved quotes become invoices without retyping. Our post on connecting your job system to Xero covers that side.
The offer
We work with Adelaide and South Australian businesses whose systems haven't kept up with how much they've grown. If a spreadsheet is quietly running part of your business, the offer is a free 20 to 30 minute chat, then one free demo built around your business. We take a copy of one of your real spreadsheets, with sensitive data stripped if you prefer, and show it working as an app with your own columns and logic. There's no obligation, and we don't promise savings. Get in touch through the OrionX website to book the chat.
This post is general information only and isn't legal, financial or technical advice.
