Key takeaways
- The licence fee is the smallest line in the transition budget; the real cost is the tendering capacity you lose while the new system is being built and calibrated.
- A spreadsheet carries years of unwritten assumptions that only surface when you try to move it, so the migration itself is a costing exercise, not an IT exercise.
- Running two systems in parallel is the only reliable way to catch a pricing error before it reaches a client, and it must be planned into the programme rather than absorbed as overtime.
- Cost volatility in materials and freight means a rate library needs a review rhythm and an owner, or the new system will price off stale numbers just as confidently as the old one.
- The decision to change should be driven by a specific failure you can name, because a system change with no defined problem will not fix an estimating problem that is really a scope or documentation problem.
Most builders who ask about estimating software are asking the wrong question. They want to know what it costs per month, when the number that actually determines whether the switch works is the cost of running two estimating methods at once while the new one earns your trust.
A spreadsheet is not just a file. It is a set of habits, shortcuts and unwritten assumptions that have been tuned over years against real jobs. Replacing it means rebuilding all of that in a new structure, and doing it while you are still tendering, still pricing variations, and still carrying the jobs already on the books.
This article is about the transition, not the software. It covers where the money goes, what breaks, and how to sequence the change so a pricing error does not reach a client.
Why the licence fee is the least important number
The subscription is easy to compare and easy to budget, which is exactly why it dominates the conversation. It is also the only part of the cost that is fixed and known in advance. Everything else is a function of how much of your own time the transition consumes.
Estimating capacity is the constraint in most small and mid-sized residential businesses. There is usually one person who can price a job properly, sometimes two, and they are also the person answering subcontractor queries, checking scope against drawings, and chasing the client for a decision on a variation. Every hour that person spends building a rate library in a new system is an hour not spent pricing work.
That trade-off is the transition cost. It is not a line item on an invoice, so it rarely gets budgeted, and it shows up later as a quiet month in the tender pipeline. A builder who prices a steady flow of jobs will feel it within a quarter.
What a spreadsheet actually contains
The most common surprise in a transition is discovering how much of your pricing logic was never written down. A spreadsheet that has been in use for years typically holds a mix of things that look similar but behave differently.
- Base rates that came from a supplier quote at some point and have been adjusted by feel since.
- Waste factors applied inconsistently, sometimes per trade, sometimes per job type.
- Assemblies where a single cell hides a labour rate, a material rate and a productivity assumption.
- Job-specific overrides that were meant to be temporary and are now load-bearing.
- Formulas that reference other sheets, other workbooks, or files on someone’s desktop.
Moving this into a structured system forces every one of those assumptions into the open. That is the value of the exercise, and it is also the work. If you have not documented your rates and factors, the migration is effectively a re-costing of your entire library, and it should be resourced as one.
This is where a related discipline helps. The way you build and defend a price is the same whether it sits in a spreadsheet or a database, which is why the method covered in our article on quoting residential building jobs in NSW still applies after the software changes.
How a transition actually runs
- Decide and defineName the failure you are fixing and the jobs the new system must price well before anyone signs a licence.
- Rebuild the libraryConvert your rates, assemblies and waste factors into the new structure and write down the assumptions that were never written down.
- Parallel runPrice live tenders in both systems and reconcile every difference before you trust either number.
- Cut overStop issuing prices from the spreadsheet only when the reconciliation has been clean across a run of jobs.
- Review cycleGive someone ownership of rate reviews so the library tracks what suppliers and subcontractors are actually charging.
The four cost layers you need to budget
It helps to separate the transition into layers, because they fail in different ways and are funded from different places.
Layer one: the licence and setup
This is the visible cost. It is comparable across vendors and it is the one most builders negotiate hardest on, which is fine, but it is not where the risk sits.
Layer two: library construction
Rebuilding rates, assemblies and waste factors into the new structure. This is skilled work and it is usually done by your most experienced estimator, not by an administrator. If you delegate it to someone who does not price jobs, you will get a library that looks complete and prices badly.
Layer three: parallel running
Pricing live tenders in both systems and reconciling the differences. This is the only reliable way to catch a systematic error before it reaches a client, and it doubles the estimating workload for the period it runs.
Layer four: the cost of getting it wrong
If a rate library is wrong in a consistent direction, every tender priced from it carries the same error. That is different from a one-off mistake in a spreadsheet, which is visible on the page. A system error is invisible because the output looks clean.
The mistake that costs the most is cutting over too early. A builder who abandons the spreadsheet before the new system has been reconciled against real tenders has no way of knowing whether a low price is a competitive advantage or a systematic error, and the first place that shows up is a signed contract.
Parallel running is not optional, and it is not free
Parallel running means exactly what it says: for a period, you price the same job twice, once in the old method and once in the new, and you reconcile the totals line by line. Where the numbers differ, you find out why before you decide which one is right.
The differences you find are the useful output. A consistent gap in one trade usually means a waste factor or a labour rate was translated incorrectly. A gap that varies by job type usually means an assembly is being applied where it should not be, or a scope item is being missed.
The cost is real. You are paying for tendering capacity twice over the same period, and it lands on the same person who is already busy. Builders who try to absorb it as unpaid overtime tend to shorten the parallel period, which defeats the purpose. Plan it into the programme and accept that the tender pipeline will slow while it runs.
There is a safety dimension to getting scope right that is worth noting here. Undocumented scope assumptions create the same problem on site as they do in a price, which is why the questions raised in our article on working alone on site are a useful prompt when you are checking whether a price has actually covered the work.
Before you commit to a new estimating system
- You can name the specific estimating failure the change is meant to fix.
- You have a written list of the assumptions and waste factors buried in the current spreadsheets.
- Your rate library has an owner and a review rhythm that will survive the transition.
- You have costed the tendering hours lost during parallel running, not just the licence.
- You have mapped which spreadsheets are used for pricing, which for claims, and which for both.
- You have agreed who signs off a price once the system produces it.
- You have a plan for the jobs already tendered under the old method.
Rate currency is a maintenance obligation, not a setup task
A spreadsheet has a hidden advantage: it is easy to change. A structured system can feel harder to adjust, so builders leave rates alone and the library quietly ages. The result is a system that prices confidently off stale numbers.
Material and freight costs move for reasons that have nothing to do with your business. Industry cost reporting has consistently pointed to geopolitical disruption feeding into Australian construction input costs, particularly through freight, fuel and imported components. You do not need a forecast to act on this. You need a review rhythm.
Give one person ownership of the rate library and a defined review interval. At each review, check the rates that move most: anything imported, anything with a significant freight component, and anything where a supplier has changed terms. Record what changed and why, so the next review has a starting point.
The same discipline applies to labour. Productivity assumptions built during a busy period may not hold when subcontractor availability changes. A rate library that is reviewed on a schedule is worth more than one that is merely well structured.
Where the risk sits on the jobs already in the system
Transition risk is not limited to new tenders. Jobs already priced under the old method continue to run, and their claims, variations and cost reporting may sit in spreadsheets that are being retired.
Before you switch anything off, map which spreadsheets serve which purpose. Some are used for pricing, some for progress claims, some for both. A workbook that only ever priced a job can be archived. A workbook that is the only record of what was allowed for a variation is a contractual document and needs to be retained and still readable.
This is also where the cost of a poor transition becomes a legal cost rather than an administrative one. If a variation claim cannot be substantiated because the supporting calculation lived in a file nobody can now open, the argument is with the client, not the software vendor.
A worked example
Consider a builder in western Sydney running a small residential operation: one estimator who also does site coordination, a handful of projects running at any time, and a rate spreadsheet that has been in use for years across two workbook versions.
The trigger for change is a specific failure. Two tenders in a row come in low against the builder’s own expectations, and the reason turns out to be a waste factor that was updated in one workbook and not the other. The error is not large per job, but it is systematic, and it has been applied to every tender priced from the older file.
The builder selects a system and budgets the licence, then makes the mistake of treating the rest as a weekend task. The rate library is rebuilt quickly, using the newer workbook as the source. Parallel running is skipped because two tenders are due and there is no spare capacity.
The new system goes live. The first tender priced from it comes in noticeably higher than the builder expects. The cause is not a rate error but a structural one: an assembly that was applied once per job in the spreadsheet is now being applied per dwelling, which is correct for the way the new system models the work but was not what the old spreadsheet did.
The builder catches it because the number looks wrong, which is luck rather than method. Had the tender been priced in a quiet month with less scrutiny, the error would have gone out. Two weeks of parallel running on a couple of tenders would have surfaced the difference at no risk to a client.
The lesson is not that the system was wrong. It is that the transition has its own failure modes, and they are different from the failure modes of a spreadsheet.
How to decide whether the change is worth it
The decision should be driven by a problem you can name. “Spreadsheets are messy” is not a problem, it is a feeling. A specific failure is a problem: a waste factor applied inconsistently, a scope item missed on a job type, a tender that takes longer to produce than the market allows, a variation that cannot be substantiated after the fact.
If you cannot name the failure, the change is unlikely to fix it. Many estimating problems are actually scope, documentation or client-selection problems wearing an estimating costume, and no software resolves those.
If you can name the failure, work out what it costs you per year in margin, rework or lost tenders. Compare that against the four cost layers. That comparison, not the subscription price, is the business case.
It also helps to keep the transition in proportion with the rest of your obligations. A builder running a residential business in NSW is already maintaining a compliance rhythm, and the system change should be scheduled around it rather than competing with it. The way that rhythm works is set out in our guide to how NSW builder CPD works, and the courses themselves are listed in the PointCPD course catalogue if you want to time the transition against a quieter part of your year.
Sequencing the change so it does not cost you a job
The order of operations matters more than the choice of vendor. A slow, well-reconciled transition on an adequate system will beat a fast cutover on a better one.
Define the problem first. Rebuild the library second, with the person who actually prices jobs doing the work. Run parallel third, for long enough to see differences across more than one job type. Cut over only when the reconciliation has been clean, and keep the old method available for any job already tendered. Then hand the rate library to someone with a review schedule and the authority to change it.
The last step is the one most often skipped, and it is the one that determines whether the new system is still accurate in a year. A transition is not finished when the software is live. It is finished when the library has an owner and a rhythm, and the prices coming out of it can be defended against a supplier invoice.
Questions builders ask
How long does it take to move estimating off spreadsheets?
It depends on how much of your pricing logic is undocumented and how many job types you price. The library rebuild and the parallel run are the two stages that set the timeline. Plan for the tender pipeline to slow during parallel running rather than assuming you will absorb it.
Can I run my old spreadsheets alongside new estimating software?
Yes, and for a period you should. Pricing the same tender in both methods and reconciling the differences is the only reliable way to catch a systematic error before it reaches a client. The differences you find are the point of the exercise.
What is the biggest risk when changing estimating systems?
Cutting over before the new system has been checked against real tenders. A spreadsheet error is visible on the page, but a rate library error is applied consistently to every price the system produces, and the output still looks clean.
Do I need to keep old estimating spreadsheets after I switch?
Yes, for any job already priced or contracted under the old method. Some workbooks are the only record of what was allowed for a variation, and those need to remain readable and retrievable. Map which files serve pricing and which serve claims before you archive anything.
How often should I review rates in a new estimating system?
Set a defined interval and give one person ownership of the library. At each review, check the rates that move most, which usually means imported materials, anything with a heavy freight component, and any trade where a supplier has changed terms. Record what changed so the next review has a starting point.
Is estimating software worth it for a small residential builder?
Only if you can name the specific failure you are trying to fix, such as an inconsistent waste factor or a scope item regularly missed on a job type. If the underlying problem is scope, documentation or client selection, changing software will not resolve it.
Sources
- Safe work method statement for high risk construction work · Safe Work Australia
- Flood risk management manual · NSW Government
- Managing the risk of falls in housing construction: code of practice · Safe Work Australia
- What the Middle East conflict means for Australian construction costs · Rider Levett Bucknall
Published 25 June 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
