app logoEstimaker

Quote vs Estimate: What's the Difference (and Which One to Send)

Quote vs Estimate: What's the Difference (and Which One to Send)

Most people use quote and estimate as if they were the same word with different syllable counts. They are not. The difference is legal, not stylistic, and it decides who absorbs the cost when a job runs over.

Send an estimate when you meant a quote and you may have to eat the overage. Send a quote when you meant an estimate and you have handed the customer a fixed price on work you have not scoped. Both mistakes are expensive, and both are avoidable in about thirty seconds of care.

The distinction in one line

A quote is a fixed price offer. An estimate is an informed guess.

That is the whole thing. Everything else follows from it.

A quote says: this is the price, and if you accept it, that is what you pay. Once the customer accepts, you have a contract, and you are bound to that number. If the job takes twice as long as you thought, that is your problem.

An estimate says: based on what I know today, I expect this to land around here. It is not an offer to be bound. If the work turns out to be bigger, the final invoice can be bigger, provided you have been reasonable and kept the customer informed.

The practical consequence: you can only quote what you have actually scoped. If you have not seen behind the wall, you do not have enough information to quote, and saying so is more professional than guessing and then arguing about it in six weeks.

Diagram comparing a quote as a binding fixed price and an estimate as a non-binding projection
The line between the two, and what it costs you to put a document on the wrong side of it.

Quote, estimate, bid, proposal

Four words circulate in this space and they are not interchangeable either.

DocumentWhat it isPrice commitmentTypical use
QuoteA fixed price offer for a defined scopeBinding once acceptedDefined work: a bathroom install, a 6-page website
EstimateA projection of likely costNot binding, can moveUnknown scope: diagnostics, repairs, restoration
BidA price submitted in a competitive processUsually binding, often on a deadlineConstruction, government and commercial tenders
ProposalA document that sells the approach, with price attachedDepends on what the pricing section saysConsulting, agency work, larger creative projects

Bid is essentially a quote entered into competition. The word carries a procedural connotation: there are other bidders, there is a submission deadline, and there are usually rules about how long your number stays open.

Proposal is the odd one out, because it is defined by content rather than by price commitment. A proposal argues why you before it says how much. It can contain a quote, an estimate, or a set of options. In agency and consulting work, it is the standard format — and its pricing section still has to make the commitment explicit.

Which one to send

Send a quote when you can define the scope precisely. You have measured, you have seen the site, you know the materials, you have a spec. Most planned work falls here: an installation, a defined build, a design package, a photo shoot with a fixed shot list.

Send an estimate when the scope genuinely cannot be pinned down yet. Emergency repairs, diagnostics, water damage, legacy code with no documentation. The honest position is a range with a stated basis.

Send an estimate first, then a quote, on anything where a paid inspection lets you convert uncertainty into a real number. This is the strongest commercial move available to trades: the estimate gets you in the door, the inspection gets you paid, and the quote that follows is accurate enough to be safe.

What you should not do is send a document that hedges in both directions — a "quote" with the word approximately in it, or an estimate with no basis. A customer reading a document that cannot decide what it is will assume whichever reading favours them, and a court generally will too.

The “This is fine” cartoon dog sitting calmly in a burning room
Sending a fixed price on work you have not actually scoped. GIF: Giphy.

The word on the document matters, but not as much as you think

Writing "Estimate" across the top helps. It is not a magic word.

What actually determines how a document is read is its content and the circumstances. A document headed "Estimate" that gives one precise total, a start date and payment terms, and never mentions that the price could move, reads like an offer of a fixed price no matter what the header says. Conversely a document headed "Quote" that says the price depends on what is found once the floor comes up is not going to bind you to the number.

So label the document correctly and make the commitment explicit in the body:

  • On a quote: "This price is fixed for the scope described below and is valid until [date]."
  • On an estimate: "This is an estimate based on [what you inspected]. The final price may vary. Any change over [10%] will be confirmed with you in writing before the work continues."

That second sentence is the one that saves the relationship. Customers rarely object to a price moving. They object to finding out about it on the invoice.

Protecting yourself when the scope is genuinely unknown

You do not have to choose between an unsafe fixed price and a vague number nobody can act on. Three devices sit in between:

  • A range with a basis. "$4,200–$5,800 depending on whether the subfloor needs replacing." The range is only credible if you say what moves it.
  • Allowances. Quote the work firmly and carry a named sum for a component the customer has not chosen yet — fixtures, tiles, stock photography. Everyone understands that an allowance is a placeholder.
  • A not-to-exceed cap. Time and materials, billed as used, with a ceiling. The customer gets protection against a runaway bill, you get paid for what you actually do. This is the standard structure for consulting and remediation work, and there is a time-and-materials template set up for it.

The fourth device, and the one most people forget: change orders. Whatever you sent, the moment the scope moves, the new work gets its own written, signed document before it is performed. Doing the work first and arguing about it on the invoice puts you in the weakest possible position, because nothing was agreed.

Diagram of three pricing devices for unknown scope: a range with a basis, an allowance, and a not-to-exceed cap
Three structures that sit between an unsafe fixed price and a number nobody can act on.

Once it is accepted, the difference stops being academic

A quote that has been accepted is a contract. In the United States, the mechanics depend on what you are selling — the Uniform Commercial Code governs sales of goods, common law governs services — and the acceptance itself can be a signature, an email, or in some circumstances simply starting the work.

That matters in both directions. It binds you to the price, and it binds the customer to pay it. The details of when a quote becomes enforceable, how long it stays open, and when you can still withdraw it are covered in is a quote legally binding.

Start from a document that already makes the commitment clear

The fastest way to stop mixing the two up is to stop writing them from scratch. Our templates state the price commitment, the validity period and the exclusions in the right places, per trade:

The rest are in the full template library.

A quote is a fixed price offer that binds you once it is accepted. An estimate is a projection that can move, provided you said so and you keep the customer informed. Choose based on whether you have actually scoped the work, label the document accordingly, and put the commitment in a sentence in the body rather than trusting the header to carry it. When the scope really is unknown, a range with a stated basis, an allowance or a not-to-exceed cap will serve you better than a fixed price you cannot honour.

Your next proposal can be signed this week.