For builders · Software category
Builder software,
judged by the week you actually work.
Written for the Australian builder rather than for a buying committee. You price the job, order the materials, book the trades, check the invoices, raise the claim and answer the client, and most weeks you do all six. This page covers what builder software has to do, in the order a job hits you, how to choose it without a procurement process, what to ask before you hand over a card, where it goes wrong, and where VIABUILD fits.
01 / The direct answer
What builders mean by builder software
Builder software is the system a building business runs its jobs in, as opposed to the accounting system it keeps its books in. In a small Australian building business it has to carry nine things: the price, the orders, the programme, the supplier invoices, the variations, the claims, the client, the site record and the seam into the accounts. Software for builders and home builder software describe the same thing.
The reason this page exists separately is that the industry sells the same products to very different businesses under the same name. A product built for a contractor with a project engineer, a contract administrator and a document controller is a different proposition for a builder who is all three of those people and also on the tools. Nothing on this page is about which platform is largest. It is about what a builder can realistically keep current.
Two neighbouring questions get asked in the same breath, and they have their own pages here because they deserve longer answers than this one. If you want the category itself, what it covers and what this market demands of it, that is construction management software. If you want the segment view, what changes because you build homes rather than warehouses, that is residential construction software. This page stays on the role.
02 / The shape of the problem
The week the software has to fit into
A lot of software in this market is designed around a role that does not exist in a small building business. It assumes somebody whose job is to sit with the system, because in a commercial contractor that person is real and is called a contract administrator. In a business running a handful of jobs at a time, the person who prices the job also orders the materials, books the trades, approves the invoices, raises the claim and answers the client, and they do it between site visits with a phone in one hand.
That has one consequence worth stating plainly, because it decides most software purchases and is almost never on the evaluation list. Every module you buy is a habit somebody has to keep. A system with twelve modules where four are current is worse than four modules that are all current, because the reports built across the stale eight are confidently wrong, and a confidently wrong number is more expensive than no number at all.
The second consequence is about where the work actually goes. The admin does not disappear when the site shuts. It moves to the evening, which is when supplier invoices get typed up, the spreadsheet gets reconciled and the claim gets written. A fair way to judge any product is to ask what it does to that evening. If it makes the day slightly nicer and the evening exactly the same length, it has not solved the problem you have.
03 / The nine jobs
What it has to do, in the order a job hits you
Not a feature list. These are the nine things a builder does on every job, in roughly the order they arrive. Any product you look at covers some of them well, some badly and some not at all, and the useful exercise is marking which ones you are keeping elsewhere.
Price the job
Measure off the drawings, build the price off your own rates rather than someone else’s book, and set the allowances you will have to live with for the next nine months. This is the one job on the list where a number you type still decides what the job makes. Everything after it is mostly about not losing what you priced.
Order the materials and the trades
A written order, against a job, against a code, before the truck rolls. Most small builders order by phone or text, which works right up until the invoice arrives at a number nobody agreed to. The order is also the only thing that tells you what a job has committed before the bills turn up.
Book the trades in an order that works
Not a Gantt chart for its own sake. A sequence you can move when the slab pour slips a fortnight, where the trades behind it move too and get told. The test is not how the programme looks on the day you build it, it is whether it is still true in week six.
Check the supplier invoices
Against the order, line by line, before they are paid. A supplier invoicing above the rate you were quoted is one of the leaks builders raise most often, and the argument is usually lost at the moment the original pricing cannot be produced. It stays invisible unless somebody compares two documents that live in different places.
Price and approve the variations
Every change gets priced, sent, agreed in writing and added to the contract sum before the work is done. The expensive failure here is rarely pricing a variation a bit thin. It is doing the work before it was agreed, because an unapproved variation is free work with your name on it, and the client is under no obligation to see it your way afterwards.
Get the claim out the week the stage finishes
Frame is done Thursday, the claim should go Thursday. A claim raised a fortnight late is a fortnight of your money funding someone else’s job, and on a small book that is the difference between paying trades on time and juggling. The stage, the approved variations and the GST all have to land on one document.
Keep the client informed without losing your Saturday
Homeowners are spending more than they ever have and they will ring you about it. The job here is not a portal. It is whether the person can see where their money went and what they chose, on a phone, without a login, so the question gets answered before it becomes a phone call.
Hold the site record and the safety paperwork
Diaries, photos, who was on site, inductions, SWMS and the weather. Ninety-nine days out of a hundred this is filing. On the hundredth it is the only version of events you have, and it cannot be written up afterwards from memory, which is exactly when it usually gets written up.
Keep the books straight
Your accountant works in an accounting system and that should not change. What has to change is entering the same bill twice. Decide which system owns the bill, which owns the invoice, and which way each one flows, and get that in one sentence before you sign anything.
These nine are a chain, not a menu, and that is the part a feature comparison hides. The price sets the budget. The budget makes the order mean something. The order is what the supplier invoice gets checked against. The invoice is what makes the cost position real. The stage and the approved variations are what the claim is built from. Break any link and the ones after it degrade quietly rather than failing loudly, which is why builders usually discover the break at close-out rather than at the time.
What this list deliberately does not do is describe the market. If you want the category itself, what is sold under it and what this country demands of it around GST, stage claiming and the accounting seam, that is the job of construction management software Australia. Come back here for what you personally have to keep current.
04 / How to choose
Choosing it without a procurement process
You are not going to run a formal evaluation and you should not pretend otherwise. What you can do is four things, in an afternoon and then a week, and they are worth more than a scoring matrix.
Start from the leak rather than the feature. Write down where the last two jobs actually hurt. A job that went backwards and you found out late is a front-of-chain problem, so judge the estimate, the budget and the orders. Evenings spent typing invoices is a different problem and points at the accounts payable end. Trades standing around is a sequencing problem. Ranking by pain rather than by what demonstrates well is the single decision that most changes the outcome.
Then test on a job you already know the ending of. Take a finished, paid job, ideally one that surprised you, and rebuild it in the trial. You know what it cost, so you can tell whether the system would have told you earlier and by how much. A live job is a bad test because you cannot mark the answer and you cannot afford to get it wrong.
Get the other person in the room. If someone else does the books, they have to see the accounting seam work on one real bill, because they will be living in it and they will quietly work around anything that does not fit. A tool chosen by one half of a two-person business and rejected by the other half does not get half used. It gets abandoned, with the subscription still running. Where that second person is your partner, the same decision from their side is set out in software for husband-and-wife builders.
And be honest about what you will keep doing anyway. If your estimating spreadsheet is genuinely good and twenty years old, replacing it to gain integration may be a poor trade, and there is no shame in buying a system for the seven jobs it does better and keeping the one it does not. The broader method, for a bigger purchase, is in the guide to choosing construction software, and the evaluation checklist is vendor-neutral and free. If you are already on an Australian all-in-one and weighing what else is out there, the Wunderbuild alternatives roundup sorts the options by the builder each one suits.
05 / The conversation
What to ask before you hand over a card
Six questions with specific answers. The second is the one that predicts whether you will still be using it in six months, and the last one tells you the most about the person you would be buying from.
- 01
Give me a login and a real set of drawings
Not a demonstration, the keys. Price one of your own finished jobs in it, from the same plans, with your own rates, and time yourself. You already know what that job cost, so you are the only person in the room who can tell whether the answer is right. A vendor who will not let you drive before you pay is telling you something.
- 02
Let me raise an order standing in a driveway
On a phone, one hand, ordinary reception. If raising an order takes a laptop and a quiet ten minutes, orders will keep going out by text, and then there is no committed cost, no invoice to check against and no point to the rest of it. This one question predicts adoption better than any feature list.
- 03
Who else has to touch it, and what do they cost
Count the people honestly. You, whoever does the books, a supervisor, maybe a leading hand who only ever needs to look. Then ask what each one costs, what happens when you add a fifth, and what the price is in year two rather than in the first month.
- 04
What happens if nobody opens it for a week
Busy weeks happen and the system gets away from you. Ask what the screen shows on the following Monday. A product that degrades into a stale but obviously stale picture is far safer than one that keeps confidently showing last month’s plan as though it were current, because the second one gets believed.
- 05
What exactly moves between this and my accounting system
Object by object, direction by direction. Bills, invoices, contacts, tracking categories, GST. Then ask what does not move, and what is on a roadmap rather than shipped. Take one real supplier bill through the whole path during the trial, and have whoever does your books watch it happen.
- 06
What do you not do
The fastest read on any vendor, and the one worth asking last. Payroll, timesheets, civil work, heavy plant, commercial tendering. A provider who names their edge is telling you where you will be working around them. A provider who says there is no edge has either not understood the question or is not being straight with you.
06 / Honest limits
Where this goes wrong for builders
Four failures, and none of them are really software failures, which is why buying a different product rarely fixes them.
The first is buying the whole thing and using the last third of it. Estimating and orders get adopted because they are the front of the chain and the pain is immediate. Safety, selections and the client side get set up during onboarding and then go quiet. Nobody announces it. The system just stops being true in the places nobody visits, and the reporting keeps producing numbers from those places.
The second is expecting it to fix a price that was wrong. Every module downstream compares against the budget, so a job priced optimistically will be reported accurately and early as losing money. That is genuinely worth knowing and it is not profit, and the cause sits upstream in estimating.
The third is the one nobody warns you about. A system that is nearly current is more dangerous than one that is obviously out of date, because it gets believed. A whiteboard two weeks old looks two weeks old. A cost position missing four supplier invoices looks exactly like a cost position, and you will make a decision on it.
And the fourth is compliance. Domestic building contracts, security of payment and home warranty cover are state-by-state legal frameworks, and software can hold the dates, the records and the evidence a position is argued from without having any view on the position itself. Any product implying it manages your obligations is overclaiming, and a specific matter belongs with a lawyer. The structure is set out in security of payment by state.
07 / How VIABUILD does it
Where VIABUILD fits for a builder
VIABUILD is the Construction Operating System for Australian residential builders, and the part that matters for the nine jobs above is that they share one data model rather than being joined by integrations. The estimate becomes the job budget, and purchase orders are raised from its lines, so the code is decided once, at the commitment, by the person who knows which job the delivery is for.
Upload a supplier invoice and Oryn™ reads it and fills in the lines for you to check against the purchase order and approve, in accounts payable. Progress claims run against contract build stages with approved variations carried in, and the client approves on a link rather than in an app. Client selections are tracked against their allowances, so a choice above allowance becomes a priced variation rather than a discovery. ViaSite carries the diaries, photos, defects, inductions and QR site sign-in from a phone. And it connects to Xero, which stays your accounting system.
What we do not claim. VIABUILD does not run payroll and does not cost your own labour hours to jobs from timesheets, so a builder who self-performs heavily should weigh that. It is not built for civil work, commercial tendering or a heavy plant fleet. And Oryn suggests rather than commits: every value it extracts cites the document and page it came from and waits for a person to confirm it, and nothing touching money or a contract is committed on its own. The product page for this audience is VIABUILD for residential builders.
08 / FAQ
Common questions.
Builder software is the system a building business runs its jobs in, as distinct from the accounting system it keeps its books in. For a small Australian builder it usually has to do nine things: price the job, raise purchase orders, book the trades in a sequence, check supplier invoices against those orders, price and approve variations, raise progress claims against contract stages, keep the client informed, hold the site and safety record, and connect to the accounting system so nothing is entered twice. Software for builders, home builder software and builder management software all describe roughly this. The names differ because the market sells the same thing to a one-man band and to a company with a project controls department, and those two need very different amounts of it.
Something assembled rather than chosen, in most cases. The common arrangement is a spreadsheet for pricing that has been refined over years and is genuinely good, a separate takeoff tool, a calendar or a whiteboard for the programme, a phone for ordering, an email folder for the paperwork, and an accounting system the bookkeeper owns. That arrangement is not stupid and it is not free. Each piece works; the cost sits in the gaps between them, where the same number exists in four versions and somebody reconciles them at night. The useful question is not which of those tools is worst. It is how many hours a week are spent moving information between them, because that number decides whether you have a tool problem or a joining problem, and they have different answers.
More than most builders expect, and the split is worth being honest about before you buy. Almost everything the office wants out of a system is produced by information the builder creates. There is no cost position without a budget, and the budget comes from your estimate. There is nothing to check a supplier invoice against unless somebody raised the order. Nobody can raise a claim on time unless they know the stage is finished. The office can carry invoices, claims and the paperwork on its own, and it cannot manufacture the three things above. If you will realistically only use part of a system, make sure the part you use is the estimate and the orders. Where the work splits between two people who are also married to each other, there is a page on software for husband-and-wife builders written to the other half of that partnership.
Change the thing that is costing you the most and that you can still test cheaply, which for most small builders is one of two. If you regularly find out a job went backwards after it finished, fix the front of the chain: get the estimate to become the budget, and get orders raised against that budget, because nothing downstream can tell you anything until those two exist. If instead your pricing is sound and your problem is the evenings, fix the supplier invoices, because that is the task that is genuinely repetitive rather than genuinely difficult. What is usually not the right first move is the programme, not because scheduling tools are poor but because a programme is a habit rather than a setup task, and a habit is far easier to start once the money side of the system is already telling you the truth every week.
Some of it does and some of it never will, and knowing which is which saves an argument. Reading works well on a phone: the programme, the cost position, a drawing, a supplier invoice waiting for approval. Capturing works if it was designed for it: a diary entry, a photo, a defect, a site sign-in, an approval. Building an estimate does not, and any vendor suggesting you will price a house on a phone is selling. The practical test is the one in the questions above. Stand in a driveway, on ordinary reception, with one hand, and try to do the thing you would actually be doing there. Ask what happens when the signal drops mid-entry, because sites have dead spots and the honest answer is a design decision rather than a marketing one.
It changes it more than the size of your business does. Building homes brings a domestic building contract, stage claiming, client selections against allowances, provisional sums and prime cost items, and home warranty cover, and products built for commercial or civil work represent all of that rather than supporting it. That is a whole question of its own and it is answered properly on residential construction software, which covers why a house is not a small commercial project. This page is about the role rather than the segment, so if you already know you build homes and you want the segment view, start there.
It puts the nine jobs on this page on one data model, so the work you do once is not re-done by somebody else later. The estimate becomes the job budget, and purchase orders are raised from its lines. Upload a supplier invoice and Oryn reads it and fills in the lines for you to check against the purchase order and approve. Progress claims run against contract build stages with approved variations carried in, client selections are tracked against their allowances, and the site surface handles diaries, photos, defects, inductions and QR site sign-in on a phone. It connects to Xero, which stays your accounting system. What we do not claim: VIABUILD does not run payroll, it does not cost your own labour hours to jobs from timesheets, it is not built for civil work or commercial tendering, and Oryn suggests rather than commits, citing the document and page every value came from and waiting for a person to confirm it.
09 / Keep reading
Keep reading before you buy
The selection method, the checklist, the orders and cost workflows underneath all of this, and the other category guides.
Run one of your own jobs through it.
VIABUILD carries the estimate into the budget, the budget into the orders, the orders into the invoice check, and the stage into the claim, on one data model, with Xero staying your accounting system.