The Difference Between an Estimate, a Quote, and a Contract

Why this matters

Estimate, quote, and contract get used like synonyms on job sites, and the mix-up costs real money. A customer hears "estimate" and holds you to a fixed price. You send a "quote" as a ballpark and the customer treats every number as locked. Someone signs nothing, the job goes sideways, and now you are arguing over what was actually agreed. These three words name three different things with three different levels of commitment. Knowing which one you are handing over tells you whether you can still revise the number, whether the customer can walk, and whether you have a deal a court would enforce.

The estimate: an educated guess

An estimate is your best prediction of what a job will cost, given what you can see right now. It is not a promise to do the work at that number. The whole point of the word is that the final figure can move as the job reveals itself: hidden damage behind a wall, a code upgrade you could not see, more hours than the access allowed for.

An estimate protects you on jobs where you genuinely cannot know the full scope until you open things up. It only protects you if you labeled it clearly as an estimate and said, in writing, what would cause it to change. An "estimate" with no variance language reads to a customer as a price, and a judge may agree.

The quote: a firm price offer

A quote (sometimes called a firm quote or fixed bid) is an offer to do a defined scope for a specific price. Once you put a quote in front of a customer, you are on the hook for that number as long as the scope does not change. When the customer accepts it, you have the makings of a binding deal.

A quote only works when the scope behind it is nailed down. Quote a fixed price against a fuzzy scope and you have handed the customer every gray area for free. Put an expiration on it too ("valid for 30 days") so material and labor cost swings do not trap you into an old number months later.

The contract: the actual agreement

A contract is the full agreement that governs the job: who, what, for how much, on what terms, with what promises on both sides. A quote is a price offer; a contract is everything. It binds both parties and it is the document you point to when there is a dispute.

An accepted quote can itself be a contract if it contains the essential terms and both sides agree to it. Most shops formalize it into a signed service agreement so the payment terms, warranty, and protections are all captured, not just the price.

Field key: how the three compare

How they flow into one another

On many jobs all three appear in sequence. You walk the job and give an estimate. Once you can define the scope, you turn it into a quote with a firm price. When the customer accepts, you formalize it into a signed contract before work starts. Skipping the last step is where small shops get hurt: a verbal "yeah, go ahead" on a quote is weaker than a signature, and it leaves the payment terms, warranty, and liability limits unwritten.

The labels that get you in trouble

The word on the document matters as much as the number. Two habits cause most of the trouble:

• Calling a firm price an "estimate" to sound flexible. If you intend to hold the price, call it a quote. If you call it an estimate, expect to defend any increase.
• Calling a rough guess a "quote" to close faster. You just bound yourself to a number you cannot actually hit.

Say what you mean on the page. When you are unsure whether a number can move, it is an estimate, and the document should say so and say why.

References

• U.S. Small Business Administration (SBA), guidance on bids, estimates, and contracts
• State attorney general consumer-protection guidance on written estimates
• Trade-standard practice for fixed-price bids versus time-and-materials work
• See related: What a Basic Service Agreement Must Contain; Does This Job Need a Written Contract