A quote and an estimate both answer the same client question — "how much will this cost?" — but they answer it differently, and that difference has real consequences when the final bill arrives. Sending an estimate when you meant a quote, or a quote when the job was too uncertain to price firmly, is how payment disputes and stalled deals happen.
The distinction is not a technicality. It is a commitment. A quote is one. An estimate is not.
What is a quote?
A quote is a firm, written offer to complete a defined scope of work at a stated price. If the client accepts it, the price is locked — you cannot charge more without issuing a change order. In most jurisdictions, an accepted quote is a legally binding agreement under standard offer-and-acceptance principles.
A quote is appropriate when the scope is fully defined before the work starts. You know what materials are required, how long the job will take, and there are no unknowns that could cause the price to move. The client accepts the quote; you deliver the work; you invoice for the quoted amount.
What is an estimate?
An estimate is a ballpark figure — an approximate cost based on current information, with the explicit understanding that the final price may differ. Estimates are appropriate when full scope cannot be determined upfront: a renovation where hidden structural issues might add materials, a software project where requirements are still being defined, or any job where site conditions have not been assessed.
An estimate is not a commitment. The client knows they are getting an approximate number. Whether the final price can exceed the estimate — and by how much — depends on what you write on the document and the rules in your jurisdiction.
The practical difference between a quote and an estimate
| | Quote | Estimate | |---|---|---| | Price | Fixed — cannot change without a change order | Approximate — final may vary | | Scope | Fully defined before issue | Partially defined; unknowns remain | | Legal status | Accepted quote is binding | Estimate is indicative, not binding | | When to use | Known job, catalog pricing, competitive pitch | Early scoping, variable materials, first site visit | | Client expectation | Exact final number | Range; real cost may be higher or lower |
When to use an estimate
Use an estimate when you do not know enough to commit to a firm price. Common scenarios:
Variable materials. A plumber estimating a bathroom renovation cannot see inside the walls. If the pipework requires more extensive rerouting than expected, the materials cost changes. An estimate protects you.
Unknown site conditions. Landscapers, builders, and tradespeople frequently quote over the phone without seeing the site. An estimate gets the conversation started; a firm quote follows after the site visit.
Early-stage projects. For software or creative work, an estimate helps a client understand budget range before you invest time in a full scope document. It is a planning tool, not a commitment.
Regulatory and approval uncertainty. If the final scope depends on permits, engineering assessments, or client decisions not yet made, an estimate is honest. A quote would be a guess dressed as a commitment.
When to use a quote
Use a quote when you know exactly what you are delivering and you want the price locked before work starts.
Catalog-based service businesses. If you quote office cleaning, landscaping maintenance, AV installation, or web design from a defined price list, you have enough information to quote firmly. An estimate creates unnecessary ambiguity.
Competitive pitches. Clients comparing three bids need like-for-like numbers. An estimate versus a quote from a competitor is not comparable — the client reasonably assumes the final number is the one on the document that says "quote."
Repeat clients and standard packages. If you deliver a known package to a known client, an estimate adds nothing. Quote the standard package.
For any quote built from a price list, the Excel quote template guide covers why spreadsheet-built quotes break at volume and what replaces them.
Can an estimate become a quote?
Yes — and this is the correct workflow for jobs that start with unknowns. Issue a budgetary estimate to start the engagement. After the site visit, scoping session, or requirements workshop, convert the estimate to a firm quote.
The firm quote supersedes the estimate. The client accepts the quote before work begins. This sequence protects you: if the estimate was higher than the final quote, the client is pleasantly surprised. If site conditions pushed the scope up and the final quote exceeds the estimate, the client has been warned — and the gap between the estimate and the quote becomes the conversation, not a dispute after the invoice.
Always label estimates clearly as estimates. "Cost estimate" or "budgetary estimate" on the header removes any ambiguity. A document labelled "estimate" that is treated as a binding quote by either party is a dispute waiting to happen.
What happens legally when the final bill exceeds the estimate
This varies by jurisdiction, but the general principle is consistent: an estimate is not a price cap. A client who received an estimate cannot refuse to pay a higher final invoice on the grounds that the estimate was lower — provided the estimate was clearly labelled as indicative and the variance is reasonable.
"Reasonable variance" is where it gets contested. Courts have found that a final bill materially exceeding an estimate — without client notification during the work — can reduce the enforceable amount. If your job is tracking toward an overrun, tell the client before the invoice. A change order or mid-job notification email is better documentation than an after-the-fact explanation.
For defined-scope service businesses, the cleanest protection is to quote rather than estimate wherever the scope allows it. A firm accepted quote eliminates the variance conversation entirely. The quote vs invoice guide covers the full document sequence — quote, acceptance, work, invoice — and why each step matters in a dispute.
The version that causes the most disputes: unlabelled estimates
The most common problem is not issuing the wrong document type. It is issuing a document with no clear label — "here's a rough number" in an email, or a spreadsheet titled "Project costs" — and having the client treat it as a binding quote while you treated it as a working estimate.
Verbal estimates are worse. "Probably around $4,000" is a number the client will remember and quote back when the invoice reads $5,200.
Label every pre-work document. If it is a quote, it says "Quote" at the top. If it is an estimate, it says "Cost Estimate" or "Budgetary Estimate" — not "quote," not "pricing," and not nothing. The label sets the expectation. The expectation is what the client reads when they open the invoice.
A qrafted quote timestamps acceptance automatically. The client knows exactly what they agreed to — and so do you.
Frequently asked questions
What is the difference between a quote and an estimate?
A quote is a firm, binding price for a defined scope of work. If the client accepts it, you cannot charge more without a change order. An estimate is an approximate cost when the full scope is not yet known — it is not a binding commitment, and the final price may be higher or lower. Use a quote when you know exactly what you are delivering. Use an estimate when unknowns remain.
Is a quote legally binding?
An accepted quote is generally treated as a binding agreement under standard offer-and-acceptance principles. When a client accepts your quote in writing, the price and scope are locked. You cannot charge more than the quoted amount without issuing a change order and getting the client to agree. This is why labelling documents correctly matters — a document labelled 'estimate' that a client treats as a binding quote creates the same dispute risk as no document at all.
Can you charge more than your estimate?
Generally yes, within reason — an estimate is not a price cap. However, if the final bill materially exceeds the estimate without the client being notified during the work, you may have difficulty enforcing the full amount. Best practice: if a job is tracking toward a significant overrun, tell the client before the work is complete and document the conversation. A mid-job change order is cleaner than an after-the-fact explanation on the invoice.
Should I send a quote or an estimate to a new client?
If you have enough information to commit to a price, send a quote. If the scope is still uncertain — you have not seen the site, the client's requirements are not finalised, or material costs are variable — send an estimate labelled clearly as approximate, then follow up with a firm quote once you have the information you need. Never send an unlabelled rough number by email and treat it as either.
What should I include in an estimate?
An estimate should include the same basic fields as a quote — your business details, the client's name, a reference number, an issue date, line items with approximate costs, and a total — but with two additions: a clear label ('Cost Estimate' or 'Budgetary Estimate') and an explicit note that the final price may vary based on stated conditions. Include the assumptions the estimate is based on so that if those assumptions change, the scope of any variance is clear.