Your Builder Knows the Number. You Don't.

August 7, 2026

Every quote you receive is a summary of a document you never see.

To put a price on your build, a builder has to break it into parts — every trade, every material, every allowance, every thing they've decided not to include. That working document exists. It has to. It's the only way the number could have been arrived at.

What you're handed is the last line of it.  As we've explored throughout the Albert AI Insights series, the biggest problems in residential construction often begin long before the contract is signed.

That's the asymmetry at the centre of almost every building dispute. Not dishonesty — structure. One party knows precisely what the price contains. The other has a figure, a page, and an assumption.

Three quotes, three different buildings

The standard advice is to get three quotes and compare them. It sounds prudent, and it's close to useless, because the three numbers are not describing the same project.

One builder has allowed for the retaining wall. One has assumed the landscaper handles it. One has priced it, but at a standard block rather than the stone on your drawings. One has included the driveway; two have left it out. None of this is visible. You are looking at three totals and trying to reverse-engineer three sets of unstated assumptions from them.

So the comparison collapses into the only variable you can actually see, which is price. And the lowest number wins — even though, more often than not, the lowest number is simply the one that left the most out. You didn't choose the best builder. You chose the shortest list, without ever being shown the list.

Silence is not inclusion

The costly half of a scope isn't what's in it. It's what isn't.

Exclusions are rarely stated as exclusions. They simply don't appear. And an absence reads as nothing at all until the build reaches that point and the conversation starts with "that was never in our price" — a sentence that is usually, technically, true. The line isn't there. It never was. You just had no way of noticing which lines weren't there, because you were never given the set to check against.

This is why "what's included?" is the wrong question to ask a builder. It invites a summary, and a summary is what caused the problem. The right question is a document: every trade, every inclusion, every exclusion, written down, before anything is signed. Not because your builder is adversarial, but because the things nobody wrote down are the things everybody remembers differently.

What it looks like from the other side of the gap

Holding a proper scope of works changes the conversation from the first meeting.

You stop asking builders what they'd charge and start asking them to price the same defined thing. Their numbers become comparable, because they're now answers to an identical question. A quote that comes in well under the others stops looking like a bargain and starts looking like what it is — a signal to go and find which lines are missing. And when the build is underway, the argument about whether something was included has already been had, in writing, by people who weren't yet in dispute.

None of that requires you to know anything about building. It requires you to hold the document the builder is working from, rather than the summary they chose to send you.

Albert AI Scope produces that document from your plans. Every trade, every inclusion, every exclusion, written in plain language and structured the way a builder reads it — generated from the same data that priced the job, not from a consultant's template. The document that should sit between you and your builder before a contract is signed, and that almost no client ever has.