The choice between a quote and an estimate isn’t about formality — it’s about how much you actually know. The right document is the one that matches your level of certainty about the work.
The core distinction
A quote says: “I will do this work for this price.” An estimate says: “Based on what I know, I expect this work to cost approximately this much.”
The difference sounds simple. In practice, it shapes every conversation you’ll have about money for the rest of the project.
When you send a quote and the client accepts it, you’ve made an agreement. If the work ends up taking longer or being more complex than expected, you can’t simply charge more — you’d need to document a scope change and issue a change order. Clients are entitled to hold you to the original number.
When you send an estimate, you’ve communicated a range of likelihood, not a commitment. If your actual costs are higher, there’s room to have that conversation without it feeling like a breach of agreement.
When to use a quote
Use a quote when you can answer yes to all three:
- Do you understand exactly what you’re being asked to deliver?
- Do you have a realistic sense of how long it will take?
- Are you prepared to do the work for this price, even if it takes a bit longer than planned?
For most established freelancers working on familiar project types, a quote is the right document most of the time. The discipline is in doing enough scoping before you write it.
When to use an estimate
Use an estimate when:
- The client is still defining what they need
- You haven’t done a full discovery session yet
- The project involves significant technical unknowns
- You’re in a competitive pitch and need to show numbers before committing to a full scope
The estimate keeps the conversation moving without locking you into a price based on incomplete information.
The sequence that works
For most freelance projects, the optimal flow is:
- Discovery call — understand what the client needs
- Estimate — if the client needs a number before you’ve fully scoped the project
- Detailed scoping — clarify all remaining questions
- Quote — based on confirmed scope, sent as the formal agreement
Skipping the estimate stage is fine when you can scope the project fully in the initial conversation. Adding it is smart when projects are complex or clients are still making decisions about scope.
If you give a client a rough number in conversation, follow up immediately with a written note that it was an informal estimate, not a quote. Verbal numbers stick in client memories as fixed prices.
How clients think about quotes vs estimates
Most clients, especially non-business-owners, don’t fully understand the legal distinction between a quote and an estimate. They often treat whatever number you give them as the real price.
This is why your document label matters as much as your document content. If you send an estimate but write it like a quote — specific scope, specific line items, specific total — the client will read it as a quote. The label at the top needs to match the certainty level of the content.
If your estimate has a specific total with no range and no caveats, you might as well have sent a quote.
Practical advice for freelancers
Keep estimates short and clearly labeled. A one-page estimate with a price range, a list of assumptions, and a note that “final pricing will be provided in a formal quote after discovery” does the job.
Once you move to a quote, build it properly — scope, line items, terms, expiry date. Use a quoting tool like Waco to send it as a tracked document and convert it to an invoice when the project is approved. Moving between estimate, quote, and invoice in the same tool prevents version-control confusion and keeps your records clean.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
