In conversation, “quote” and “estimate” often mean the same thing. On a document sent to a client, they mean different things — and the one you choose determines your exposure if the final price doesn’t match.
The real-world consequence of confusing the two
Here’s how the confusion plays out in practice.
A freelancer has a quick call with a potential client. The client asks what a website redesign might cost. The freelancer says “probably around $4,000” and follows up with a document labeled “Quote” showing $4,000.
Three weeks into the project, it’s clear the work is more complex than it appeared. The real cost will be closer to $5,500.
The client pulls up the document. It says “Quote: $4,000.” In their mind — and possibly in a legal sense — that’s what they agreed to pay.
If the freelancer had sent an estimate instead, with a note that the price would be confirmed after discovery, the $5,500 conversation would be normal. With a quote in hand, it’s a dispute.
What a quote actually commits you to
When you send a quote with a specific price, a defined scope, and the client accepts it, you have a contract. The scope and price in the quote govern the work. Charging more than the quoted price requires either:
- A written change order documenting new scope
- The client’s explicit written agreement to a revised price
Without one of those, charging more than the quote is legally problematic in most jurisdictions — regardless of whether the work actually justified a higher price.
What an estimate actually commits you to
An estimate is a projection, not a promise. It gives the client a sense of what the work might cost based on current information. The key protection: an estimate should always include a statement like “This estimate is based on [specific assumptions] and is subject to change as the project scope is confirmed.”
An estimate without that language starts to look like a quote the moment a client is trying to hold you to it.
The safest estimate includes a price range rather than a single number. “$3,500–$5,000 depending on final scope” is harder to misread as a fixed price than “$4,000.”
How to tell which one you should be sending
Ask yourself one question: “If this project takes 30% longer than I expect, am I comfortable delivering it for the price in this document?”
If yes: send a quote. If no: send an estimate and convert it to a quote after proper scoping.
For freelancers who do similar work repeatedly, quotes are usually the right choice — you know how long the work takes and can price accordingly. For new project types or clients with complex or unclear needs, an estimate buys you time to scope properly before committing.
The transition from estimate to quote
Once you’ve done discovery and have a clear scope, replace the estimate with a formal quote. Reference the earlier document: “This quote supersedes the estimate dated [X] and reflects the agreed project scope.”
This keeps the paper trail clean and signals to the client that the quote — not the estimate — is the governing document.
Some quoting tools, including tools like Waco, let you maintain both documents in the same system, so you always have a record of both what you estimated and what you formally quoted. That matters if there’s ever a question about what was agreed.
The terminology varies by industry
In construction and contracting, “estimate” often means “non-binding approximation” and is legally distinct from a contract-level quote. In many service businesses, clients use the terms interchangeably. In either case, the document you send should be labeled accurately and the language inside should match the label.
When you want to make a price commitment: quote. When you want to give a ballpark: estimate. When you’re not sure: estimate with clear caveats.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
