The words “quote” and “estimate” get used interchangeably in conversation. They shouldn’t. Once a document is sent to a client, the label it carries determines what each party can reasonably expect.
What a quotation commits you to
A quotation is an offer to do specific work for a specific price. When the client accepts it, you have an agreement. The price in the quotation is the price — unless scope changes, which should be handled with a written change order.
This is why the scope description matters so much in a quotation. If the scope is vague, the client can argue that the agreed price covers things you didn’t intend to include. If the scope is specific, there’s a clear line between “what I quoted” and “what’s extra.”
A quotation should be sent when:
- You’ve had a full discovery conversation or discovery session with the client
- You understand what the project involves and roughly how long it will take
- You’re prepared to deliver the work at the stated price, within the described scope
What an estimate commits you to
An estimate is a price projection, not a promise. It tells the client “this is approximately what it will cost, based on what I know right now.” The final price may be higher or lower.
An estimate should be sent when:
- The project scope is still evolving
- The client needs a ballpark to assess feasibility before committing
- There are significant unknowns that could materially affect cost
The key requirement for a credible estimate: state the assumptions it’s based on. “This estimate assumes X number of pages, Y revision rounds, and Z deliverables. Changes to any of these may affect the final price.”
Without assumptions stated, an estimate is just a number — and clients remember it as the price you offered.
The practical sequence for most freelance projects
Most freelancers use estimates and quotations at different points in the same client relationship:
- Early inquiry: Client asks for a ballpark. You give a rough range verbally or in a brief email.
- After initial scoping: You send a formal estimate to give the client a realistic number before either party commits.
- After full discovery: You send a quotation based on confirmed scope. This is the document that becomes the agreement.
You don’t always need all three stages. For simple, well-defined projects, you can skip straight to a quotation. For complex or open-ended projects, the estimate stage protects both parties.
If you’re not sure whether to send a quote or an estimate, ask yourself: “Would I be comfortable if the client held me to this exact price?” If yes, send a quote. If no, send an estimate.
What happens when you use the wrong label
Using “estimate” when you mean “quote”: The client treats it as approximate and is surprised when you invoice the same amount. Low risk.
Using “quote” when you mean “estimate”: The client treats it as a firm price commitment. If your actual costs come in higher, you either eat the difference or have a difficult conversation about why you’re now charging more than the “quote.”
The second scenario is far more common and far more damaging to client relationships. When in doubt, use “estimate” and convert it to a formal quotation once you’re certain of the scope.
Does the label matter legally?
In most jurisdictions, yes. A quotation accepted by the client creates a binding contract at the stated price for the described work. An estimate does not. But contracts can be implied by behavior — if you’ve acted as if the estimate was a fixed price, a court may treat it as one.
For projects above a few thousand dollars, use clear labels, document scope changes in writing, and keep a record of all communications. These practices protect you regardless of whether the document is labeled an estimate or a quotation.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
