In a lot of Australian modular and residential construction businesses, estimating still runs on a spreadsheet, a plan set and someone's memory. That works in the narrow sense that quotes go out and jobs get won. It fails quietly rather than loudly. The failure rarely shows up as a broken formula or an obviously missing line. It shows up later, when the job is back-costed, the margin is thinner than the quote said it would be, and nobody can reconstruct which assumption caused it.
Every job starts from a blank sheet
The first structural problem is that quantities get re-derived by hand for every job. An estimator opens the plans, scales off the dimensions, works out linear metres of framing, sheet counts, fixings and finishes, and types the results into a workbook. The next job, even one that is nearly identical to the last, gets the same treatment. Nothing carries forward except the spreadsheet template and whatever the estimator remembers.
That is expensive twice over. It is slow, so fewer quotes go out the door than the business could otherwise price. And it is fragile, because every re-derivation is a fresh chance to make a mistake that nobody downstream is positioned to catch.
The specific ways it breaks
The failure modes are not exotic. They are a short list, and they repeat.
- Transcription slips: a dimension read correctly off the plan and typed into the wrong cell, or carried across from a superseded revision.
- Stale pricing: supplier rates that have moved since the workbook was last touched, applied as though they are current.
- Inconsistent waste: one estimator's allowance for offcuts and breakage differs from another's, and neither allowance is written down.
- No version history: a quote revised several times with no record of what changed between revisions, or why.
- Silent overrides: a manual number typed over a formula to make a total look right, invisible to the next person reading the sheet.
- Knowledge in one head: the rules that make the numbers correct live with whoever has been doing this longest, and leave when they do.
Why the errors compound instead of cancelling
It is tempting to assume the mistakes wash out, some quantities over, some under. They do not, for two reasons.
The first is that they are directional. Adjustments made under deadline pressure follow the estimator's habit, and habits do not alternate. Whichever way a person tends to round, they round that way consistently, so error accumulates in one direction across a quote rather than balancing out.
The second is that an estimate is not a single output. It is the input to purchasing, to programming and to back-costing. A wrong sheet count does not just misprice one line. It becomes a purchase order, and then either a shortfall that stops a crew or surplus stock that gets written off. The cost of a bad number is rarely limited to the number itself.
An error in a take-off does not stay in the take-off. It becomes a purchase order, and then it becomes a problem on site.
The trail matters as much as the total
When a client queries a quote, or a job is reviewed internally after the fact, the useful question is not what the number is. It is how the number was reached. A spreadsheet answers with a formula and a hardcoded rate. It cannot say which plan revision the dimensions came from, which waste factor was applied to that material, who changed the rate, or when. Without that trail, disagreements get settled by seniority rather than by evidence, and the same argument gets had again on the next job.
The same gap makes back-costing close to useless. Comparing an estimate to actuals only helps if the estimate can be decomposed. If it cannot, the review says the job ran over without saying where, so the next quote gets priced on the assumptions that just cost money.
The fix is a rules engine, not a faster spreadsheet
None of this is solved by a better template or a quicker estimator, because speed is not the problem. The fix is to separate two jobs that estimating currently mixes together: reading the plan, and calculating from it.
Reading a plan is a perception task. Vision AI is well suited to it, and what it reads should be confirmed by a person before anything downstream runs, because a misread dimension caught at that point is cheap and a misread dimension found on site is not. Calculating quantities is not a perception task at all. It is arithmetic against explicit rules: geometry-based formulas, material specifications, and waste factors that belong to the business rather than to whoever happens to be estimating that week.
That half should be deterministic. The same confirmed inputs produce the same bill of materials every time, and every line traces back to the rule that produced it. Waste factors stop being personal preference and become a setting. Pricing comes from a supplier catalogue that is updated in one place. Revisions are versioned, so the change between quote two and quote three is a fact rather than a recollection.
None of that makes estimating effortless. It makes it repeatable, and a repeatable process can be checked, corrected and taught. A business that can explain every quantity on a quote can defend it, learn from it, and price the next job on what the last one actually cost.