Estimate vs Quote
Same numbers, same client, same job — and one of the two words at the top of the page can commit you to the figure. Here is the difference, and how to decide which one to send.
The one-sentence difference
An estimate is your best good-faith approximation of what a job will cost, offered on the understanding that the real number can move as the work reveals itself. A quote is a fixed-price offer: you are naming a number you are prepared to be held to, and when the client accepts it, that price is generally the price. Both come before the work — which is why they get confused with each other, and never with an invoice, which comes after.
Side by side
| Estimate | Quote | |
|---|---|---|
| What it claims | Approximately what this should cost | This is the price for this scope |
| Binding on acceptance? | Generally not — it's an approximation | Generally yes — it's a fixed offer |
| Best used when | Scope has real unknowns | Scope is fully visible and measured |
| Who carries the risk | Shared — surprises become change orders | You do, within the quoted scope |
| Price can move because | Discovery, conditions, client changes | Client-requested changes only |
| Must state | Validity date, exclusions, change-order rule | Validity date, exact scope, what's excluded |
| Typical trades | Remodels, repairs, excavation, restoration | Replacements, service packages, supply-and-fit |
Why the label decides who absorbs the surprise
Every job has variance. The only real question is who pays for it. When you send a quote, you are volunteering to absorb the variance inside the scope you quoted: if the install takes six hours instead of four, that is your six hours. When you send an estimate, the variance is shared, and the mechanism for sharing it is the change order — you stop, price the newly discovered work, get written approval, and continue.
That is why quoting unknown scope is the expensive mistake. A contractor who quotes a bathroom remodel firm before opening a wall has priced a job they have not seen, and every discovery comes out of margin. The inverse mistake is milder but real: estimating work that is completely visible invites clients to treat your number as negotiable and to expect it to drift.
Making an estimate read like an estimate
If you intend a number to be an approximation, the document has to say so in more than the title. Three things do the work. First, an exclusions list — the adjacent work you are not doing and the conditions you have not seen. Second, a change-order clause in plain language: additional work is priced in writing and approved in writing before it starts. Third, a validity date, because an estimate with no expiration is an open offer at last season’s supplier pricing.
A quote needs the same validity date and an even tighter scope statement, since precision is the only thing standing between a fixed price and unpaid work. In both cases the itemization does the persuading: a lump sum invites haggling, while an itemized scope shows the client where the money goes and lets them cut scope instead of cutting your price.
Many contractors write “estimate” on everything out of habit and mean different things by it on different jobs. Pick the word deliberately per job, and write “quote” only when you mean to be held to the number. The free estimate generator lets you edit the document title, terms, and validity date, so the label and the terms can agree with each other before it reaches the client.
Where each one sits in the paper trail
- Estimate or quote — itemized scope, exclusions, validity date, terms. Build one free.
- Written acceptance — a signature or an email that says yes. A quote generally locks its price here; an estimate does not.
- Signed contract — incorporates the accepted document and adds schedule, payment milestones, and the change-order procedure.
- Change orders — priced and signed as scope moves. On an estimate these are expected; on a quote they should exist only where the client changed something.
- Invoice — matching the accepted document plus signed change orders, line for line.
None of this is legal advice — consumer-protection rules around estimates and quotes vary by state and country, and some jurisdictions cap how far a final bill may exceed a written estimate. Check your local rules before relying on the general pattern above.
Estimate vs quote FAQ
Is a quote legally binding?
A quote is generally treated as a fixed offer: once the client accepts it, both sides are usually committed to that price for that scope. An estimate is generally treated as a good-faith approximation and is not binding on its own. Wording, conduct, and local consumer-protection rules all matter, so treat this as the general shape rather than legal advice for your situation.
Can I raise the price after sending a quote?
Not for the scope you quoted, absent agreement. You can price additional or changed work as a change order, and you can withdraw a quote before it is accepted or after its validity date passes — which is exactly why every quote needs an expiration date on it.
Which should I send: an estimate or a quote?
Send a quote when you can see the entire scope and control the variables — a like-for-like replacement, a standard package, a measured room. Send an estimate when something is genuinely unknown: what is behind the wall, what the ground is like, what an inspector will require. The wrong choice is quoting unknown scope, because you absorb every surprise.
Does calling it an estimate protect me if the price goes up?
Partly, and less than most contractors assume. The label matters, but so does what you told the client and how precise your number looked. A document titled 'estimate' that states a single confident figure with no ranges, no exclusions, and no change-order clause will not read as an approximation to anyone. Protection comes from the terms, not the title.
What about bids and proposals?
A bid is a fixed price submitted competitively, usually against a specification the buyer wrote — functionally a quote in a procurement process. A proposal is a persuasive package: scope, approach, timeline, and price together. Both usually contain estimate-style or quote-style pricing inside them, so the same binding question applies to whatever number they carry.