When you pay someone to estimate a project, you aren’t buying a price. You’re buying a clearer view of the future before you spend the money.
Almost every project starts with the same question.
How much is this going to cost?
The person asking thinks they’re asking for a price.
They’re actually asking me to predict the future.
That’s a very different thing, and most of what I’ve learned about estimating comes from taking that difference seriously.
An Estimate Is a Prediction
Nobody knows the final cost of a project on the day it’s estimated.
The building isn’t built yet.
So an estimate isn’t a fact.
It’s a prediction, made from the information available at the time.
I’m reading the drawings.
I’m counting quantities.
I’m pricing material and labor.
I’m making assumptions about site conditions, schedule, and what the subcontractors will hold their pricing on.
Every one of those inputs is a place where reality can come in different than I expected.
The number I hand over is my best current answer.
It is not a guarantee, and presenting an early estimate as one creates a false sense of certainty.
Every Estimate Contains Uncertainty
Here’s the part people don’t think about when they hear a number.
Some of what’s in that number, I know.
Some of it, I’m assuming.
And some of it, nobody has discovered yet.
The soil, existing conditions, buried utilities, concealed damage — some things don’t reveal themselves until the work starts.
That’s not a flaw in the estimate.
That’s the nature of building.
A good estimate doesn’t pretend the uncertainty isn’t there.
It accounts for it, and it tells you where it lives.
The Estimate Draws the Boundaries
This is where estimating stops being math and becomes judgment.
An estimate isn’t just a total.
It’s a set of boundaries.
What’s included.
What’s excluded.
Who’s responsible for each piece.
What happens if the condition turns out to be different than we assumed.
I learned this most clearly pricing foundations, where my work sits between the excavator, the concrete crew, and the waterproofer.
On an ICF foundation, I can price the forms, the rebar, and the concrete quantities with real confidence.
But whether I’m responsible for the excavation, the footings, the pump truck, the waterproofing, the drain tile, and the backfill is a separate question.
If that isn’t settled before I give the number, the estimate isn’t finished.
The number matters, but the line around the number matters more.
A price without a clear boundary isn’t really an estimate.
It’s a hope with a dollar sign in front of it.
The Cheapest Estimate Isn’t Always the Best One
This is the part I’d want a homeowner or a developer to understand most.
When you get two numbers, you are not just comparing prices.
You’re comparing how much of the project each person actually understood.
Say one estimate comes in at $300,000 with a third of the scope still vague.
And another comes in at $325,000 with the scope clearly defined and the risks named.
The lower number looks better on the day you sign.
It often doesn’t look better six months later, when the vague third turns into change orders.
You’re not choosing between $300,000 and $325,000.
You’re choosing between a number you understand and a number you don’t.
That’s a risk-adjusted decision, even when it doesn’t feel like one.
The Estimate Is Also a Feedback Loop
There’s one more thing an estimate does, and it’s the reason I take mine seriously even on small jobs.
Every estimate is a chance to get better at the next one.
I estimate the job.
I build it.
I find out what it actually cost.
I look at the difference between the two.
I record it.
And the next estimate is built on top of that record instead of starting from scratch.
That’s why I’m building an estimating system for my work rather than pricing everything from memory.
I want the mistakes I’ve already made to stay made once.
Every completed job should make the next estimate better.
A single quote can’t show you that.
It only shows up across dozens of jobs, when the predictions start landing closer to the truth.
What You’re Actually Buying
So here’s what I’ve come to believe an estimate really is.
A good estimate doesn’t tell you exactly what a project will cost.
Nothing can do that before it’s built.
What it tells you is more useful.
It tells you what I believe the project will cost.
It tells you why I believe it.
It tells you what I’m responsible for and what I’m not.
It tells you what I’m certain about and what I’m still assuming.
And it tells you where the risk lives, before you’ve spent the money.
That’s the real product.
When you pay someone to estimate a project, the number is just the receipt.
What you’re actually buying is a better understanding of the future — early enough to still do something about it.
