Clients ask for quotes, estimates, and proposals — often interchangeably, and often meaning different things depending on who’s asking. Using the right document type for the right situation makes your response more professional, sets clearer expectations, and reduces disputes about what was agreed. Here’s when to use each.
What a quote is
A quote is a firm price for a defined scope of work. When you send a quote and a client accepts it, you’re committing to deliver the specified work at the stated price.
Quotes are appropriate when:
- The work is clearly defined and familiar (you’ve done it many times)
- The scope is unlikely to change
- The client just needs a price, not a full explanation of your approach
A quote might look like this:
Quote for logo design Client: Farrow & Bright Date: May 27, 2026
Primary logo design (2 concepts, 1 revision round): $1,800 Delivery: 5 business days from approval Payment: 50% upfront, 50% on delivery
That’s a quote. It’s not a proposal — it doesn’t explain your process or build a case for hiring you. It states a price for a specific output.
Use quotes when the client already trusts you (repeat client or strong referral) and just needs the number in writing, or when the work is so standard that it doesn’t require explanation.
What an estimate is
An estimate is an approximate price for work where the final cost isn’t certain. Unlike a quote, an estimate isn’t a commitment — it can change if the scope turns out to be more complex than anticipated.
Estimates are appropriate when:
- You can’t fully scope the work upfront (unknown complexity, undefined requirements)
- The client is in early planning and needs a ballpark before committing
- The work is hourly and the time required is genuinely uncertain
A good estimate includes the range and explains what drives variability:
Estimated cost for website audit and recommendations Estimated: $1,500–$2,500 depending on the number of pages reviewed (currently unknown) and depth of technical issues found. Final cost confirmed after initial discovery session.
The most common mistake with estimates: giving a range without explaining what drives it. A range of $1,500–$2,500 without context just creates anxiety. Tell the client what would push it toward the high end.
Never use an estimate when you mean a quote. Clients who believe they’ve received a fixed price and later get a higher invoice feel misled — even if your document said “estimate.” When scope is clear enough to commit to a price, send a quote.
What a proposal is
A proposal is a complete document that makes the case for a specific engagement. It includes context the client needs to understand and approve the investment:
- A summary of their situation (showing you understood the brief)
- Specific deliverables
- Timeline
- Pricing
- Your relevant credentials
- A next step
The pricing section of a proposal is typically a quote — a fixed commitment to the stated price for the stated scope. But the proposal is more than the price. It answers: what are we doing, when, for how much, and why should you hire me to do it?
Proposals are appropriate for:
- Custom or complex work where the client needs context
- Higher-value engagements where the client needs internal approval
- Situations where you’re competing against other freelancers
- New clients who don’t know your work
When to use each
| Situation | Document to send |
|---|---|
| Repeat client, familiar scope, just needs a number | Quote |
| New client, simple work, no explanation needed | Quote |
| Early discovery, cost genuinely unknown | Estimate |
| Hourly project with variable scope | Estimate with cap |
| Custom work, new client, competitive situation | Proposal |
| Complex scope with multiple deliverables | Proposal |
| High-value engagement needing internal approval | Proposal |
Most freelancers send proposals more than quotes. The extra context — scope, timeline, deliverables — is valuable for both parties even when it’s not strictly required. A proposal creates a shared understanding that a bare quote doesn’t.
Quote + proposal together
The cleanest format for most freelance work: a proposal that contains a fixed quote in the pricing section.
The proposal provides context. The pricing section commits to a specific number. The client gets everything — understanding and certainty — in one document.
Tools like Waco are built around this format: proposal documents with scope, timeline, and a clear price in the investment section. When the client approves, the proposal becomes the written record of what was agreed. When you invoice, the invoice references that proposal.
How clients think about these terms
Clients don’t always use these terms precisely. “Can you send me a quote?” often means “can you tell me how much this will cost?” — they may actually need a proposal. “Can you put together a proposal?” from a corporate client sometimes means they want a very specific format.
When in doubt, ask: “Do you need a full proposal with scope and timeline, or just a price for the work we discussed?” The answer tells you which document to send.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
