VIABUILD vs spreadsheets

Every comparison page on this site is written to be fair to the other side. This one is harder to write than the rest, because the other side is not a company with a marketing department. It is the workbook you built yourself, that fits your business exactly, that has never sent you an invoice, and that you know better than anyone will ever know a piece of software. Any page that opens by telling you spreadsheets are the problem has not understood why you are still on them.

What spreadsheets are genuinely better at

A spreadsheet has no opinion about how you build. That is its single greatest advantage and no software can match it. If your business prices a knock-down rebuild differently from an extension, treats one supplier on a rise-and-fall arrangement, splits a stage claim in a way no standard contract does, or carries a margin structure you would rather nobody else understood, you can model all of it in an afternoon and change it in ten minutes. Software makes you a case in someone else’s model.

The other advantages are real and worth naming plainly. It costs nothing beyond what you already pay for the office suite. There is no learning curve, because everyone in construction already reads a spreadsheet, including your accountant and your bank. It works offline, in a shed, with no reception. It is yours in a way a subscription never is, and it will still open in fifteen years when the vendor you were considering has been acquired twice. For a builder running two or three jobs where one person holds the whole picture in their head anyway, a well-built workbook is not a compromise. It is an efficient system.

How a spreadsheet system stops being true

Spreadsheets do not fail loudly. Nothing crashes, no data is lost, and there is rarely a single moment you could point at afterwards. What happens is quieter than that. The workbook keeps opening, keeps calculating, keeps looking exactly as trustworthy as it did when it was right, and gradually stops describing the business. That is the failure mode worth understanding, because it is the reason builders stay too long. There is no alarm.

It happens through five specific mechanisms. The first is version drift. The estimate exists as a file, then as an attachment on an email, then as a copy someone made to try a scenario, and within a month there are four workbooks with the same name and different numbers, and no rule about which one is authoritative. The version that goes to the client is the one that was open at the time.

The second is re-keying. A quantity is measured, typed into the estimate, typed again into the budget with the margin stripped, typed into an order to the supplier, typed into the claim schedule, and typed a fifth time into the accounting system as a bill. Five entries of one number, each an independent chance to be wrong, and none of them aware of the others. This is the reconstruction tax, the ongoing cost of rebuilding by hand a picture the business already had.

The third is the absence of a single source of truth. Ask what the committed cost is on a job and the honest answer is that it depends which file you open, because orders live in one place, the budget in another and the invoices in the accounting system. Nobody is lying. There simply is no authoritative number, only several partial ones maintained at different moments. What that means in practice is set out in committed costs.

The fourth is the missing audit trail. A formula in the retention column gets adjusted, a row is deleted during a tidy-up, a cell that was a calculation becomes a typed number because someone was in a hurry. Months later the total is wrong and there is no way to find out when it changed, who changed it, or what it said before. On a defect claim years after handover, that absence is not an inconvenience. It is the reason a position cannot be defended.

The fifth is concentration. One person built the workbook and one person understands the links between its sheets. That person is usually the owner or the estimator, and the business has quietly made itself dependent on them being available, well and employed. It is the most serious of the five and the least often discussed, because it does not look like a systems problem until the day it becomes one.

Four questions that tell you where you actually are

Feature lists will not tell you whether you have outgrown spreadsheets. These four questions will, and you can answer them this afternoon without talking to a single vendor.

• How many places does one number live? Pick a real quantity from a current job and count every file it has been typed into. One or two is a system. Five is a reconciliation habit that somebody is paying for in evenings.
• How old is the number on the screen? Open your cost position for the busiest job and ask when it was last updated. If the answer is a fortnight ago, you are not running a live cost control system, you are running a periodic reconstruction of one.
• Who else could answer this? If the only person who can produce the committed cost for job twelve is the person who built the workbook, the business does not own its own numbers.
• What happens when it is wrong and nobody notices? If a broken formula would surface at the next claim, you have time. If it would surface at handover, or in a dispute, the cost of being quietly wrong has already outgrown the cost of a system.

What moving to a system actually costs

Software marketing tends to price the subscription and stop. The subscription is usually the smallest of the three costs, and the other two are what determine whether the change sticks.

Setup is the first. Your cost codes have to be decided properly rather than inherited from whatever grew in the sheet, your rates and assemblies have to be loaded into a catalogue, your standard designs have to be priced into a price book, your suppliers and contacts have to come across, and someone in the business has to make those decisions rather than delegate them to an implementation consultant who has never built a house. That is real work, done by the person who is least free to do it. Being honest about it is the difference between an implementation that lands and one that stalls in month two.

Learning is the second, and it is smaller than most builders fear and larger than most vendors admit. The estimating and job costing concepts are already familiar because you have been doing them by hand. What is new is where things live and what order they happen in. Expect a few weeks of being slower before you are faster, and expect the site team to take longer than the office to change habits.

Discipline is the third and the only one that decides the outcome. A system reflects reality only if the purchase order is raised in the system rather than by text message, the variation is written up before the work starts rather than at the end, and the supplier invoice is approved rather than left in an inbox. A spreadsheet forgives an undisciplined week by letting you catch up on Sunday. A system tells you the truth about the week you had, which is more useful and less comfortable. That is the actual change being bought, and it is a management change, not a software one. The process of running that decision properly is set out in the guide to choosing construction software and the software evaluation checklist.

When staying on spreadsheets is the right answer

There are three situations where moving would be a poor trade, and a page that could not name them would not be worth reading.

If you run a small number of jobs and one person genuinely holds the whole picture, the reconciliation cost a system removes is close to zero, because there is nothing to reconcile. Buy the system when the picture stops fitting in one head, not before.

If your business is mid-way through something that is consuming all its attention, a contract dispute, a cash squeeze, a key departure, then an implementation competing for the same attention will fail and will be blamed on the software. Timing is a real criterion, and the honest answer from a vendor is sometimes that this is the wrong quarter.

And if the spreadsheets are genuinely working, if nobody is re-keying, the numbers are current, more than one person can produce them and nothing has been quietly wrong, then you are being sold integration you do not need. That is a rarer situation than most builders believe about themselves, and it is not a fictional one. The four questions above will tell you which case you are in more reliably than any demonstration will.

What VIABUILD does that a workbook cannot

VIABUILD is the Construction Operating System for Australian residential builders. The specific thing it replaces is not the spreadsheet, it is the gap between spreadsheets. A quantity measured once flows into the estimate, the estimate locks into the budget, the budget into purchase orders, the orders into committed cost, approved supplier invoices into actual cost, and the stages and approved variations into the next progress claim, which pushes to Xero as an invoice. The number is entered once because there is only one of it.

The cost position is computed from those source records at the moment you ask, not stored as a running total and not refreshed overnight, so it cannot be stale and it cannot silently drift from what it is derived from. Every figure is arithmetic, deterministic and unit tested. No model produces a number anywhere in that chain, which is why none of it is described as AI forecasting.

Oryn™, the intelligence layer, sits at the point where paperwork enters the system rather than at the point where numbers leave it. It reads supplier invoices and plans, extracts line items, matches them to orders and suggests cost codes from the vocabulary of your own history, always citing the document and page a value came from, and never committing anything that touches money or a contract without a person confirming it. It is not a chatbot, and asking it to have opinions about your margin is not what it is for.