Quote vs Estimate: Which One Should You Send?

A quote is a fixed price you commit to. An estimate is your best guess at the cost, and it is allowed to change. If the client needs to know exactly what they will pay before they say yes, send a quote. If the scope is still loose and the final figure depends on how the work unfolds, send an estimate.

That single distinction decides who carries the risk of the job costing more than expected. Get it wrong and you either scare off a client with a number you cannot stand behind, or you lock yourself into a price that no longer covers the work.

	Quote	Estimate
What it is	A fixed, committed price	An approximate figure
Can the price change later?	No, once accepted	Yes, as scope or hours change
Best for	Defined scope, clear deliverables	Loose scope, unknowns, hourly work
How the client reads it	A firm offer	A guide to plan a budget
Who absorbs overruns	You do	The client does, within reason

What is a quote?

A quote is a formal offer to do a specific piece of work for a specific price. Once the client accepts it, that price is fixed. You have effectively made a promise: this scope, this money, no surprises.

Because the number is locked, a quote only works when you understand the job well. You need a clear list of deliverables, a defined timeline, and confidence that nothing hidden will blow up the hours. A logo design with three concepts and two rounds of revisions can be quoted. A vague "help us sort out our branding" cannot, at least not safely.

A good quote spells out exactly what is included so there is no argument later about what the price covered. It usually carries an expiry date too, because your availability and costs do not stay still forever. Thirty days is a common window.

What is an estimate?

An estimate is your honest projection of what the work is likely to cost, with the clear understanding that the real figure may land higher or lower. It is the right tool when the scope is genuinely uncertain, when you bill by the hour, or when the client is still shaping what they want.

Estimates protect you from committing to a number before you have enough information. They also help a client plan. Someone deciding whether they can afford a project does not always need a binding price. They need a realistic range so they can budget.

The catch is that an estimate must be defensible. If you estimate 20 hours and bill 45, the client will feel misled even if every hour was genuine. Estimate from real experience, build in a sensible buffer, and tell the client what would push the figure up.

When should you send a quote?

Send a quote when three things are true: the scope is clear, the deliverables are defined, and you have done similar work often enough to price it with confidence.

Fixed-scope projects are the obvious fit. A five-page website, a set of product photos, a translation of a known document length. The client wants certainty, and you can give it because you can see the whole job from the start.

Quotes also win competitive situations. When a client is comparing freelancers, a firm price is easier to say yes to than a range. It signals that you have done this before and you know what it takes. Just make sure your scope statement is tight, because the firmer the price, the more the boundaries of the work matter.

If you want to sharpen how you present a fixed price, the guide on how to write a quote covers the structure, the wording, and the follow-up that turns a sent quote into an accepted one.

When should you send an estimate?

Send an estimate when the work has real unknowns. Maybe the client cannot yet describe the full scope. Maybe the project depends on materials, third parties, or decisions that have not been made. Maybe you bill hourly and the total simply depends on how long it takes.

Discovery-style work is a classic case. You cannot quote a fixed price to "audit our systems and recommend fixes" because you do not know what you will find. An estimate based on a typical engagement, with a note that complex findings may extend the work, is honest and useful.

When you do estimate, break the figure down. Show the phases, the assumed hours, and the rate. A transparent estimate is far easier to defend if the work runs long, because the client can see exactly where the time went. The project cost estimator does this for you: list the phases, add expenses, apply a markup, and get a clear total you can hand over. For a deeper walk-through, see how to estimate a project cost.

How to protect yourself with either one

Both documents need the same backbone: a clear description of what is included, what is not, your payment terms, and a validity date. The single most common cause of payment disputes is a scope that was never written down.

For a quote, the protection is precision. Spell out the number of revisions, the page count, the deliverable formats, anything that could expand. Add a line that work beyond the listed scope is charged separately at your standard rate. That one sentence converts scope creep from an awkward conversation into a simple, pre-agreed adjustment.

For an estimate, the protection is communication. State plainly that the figure is an estimate, not a fixed price. Name the assumptions it rests on. Tell the client you will flag it before you cross the estimate, not after. A client who is warned never feels ambushed.

Turning a quote or estimate into an invoice

Whichever you send, the document that asks for payment at the end is the invoice, and it should match the agreement the client accepted. If you quoted a fixed price, the invoice shows that price. If you estimated and billed by the hour, the invoice shows the actual hours and the rate, and ideally references the original estimate so the client can see how the final figure relates to it.

Keep the numbering and references consistent across the chain. A quote, then an invoice that points back to it, reads as one tidy transaction to a client's finance team. When you are ready to bill, you can build a clean, numbered invoice with the free invoice generator in a couple of minutes, with no signup and nothing stored on a server.

The line between quote and estimate is really a line about certainty. Sell certainty when you have it. Sell an honest projection when you do not. Both are professional. Pretending you have certainty you do not is the only real mistake.

Common questions

Is a quote legally binding?

Once a client accepts a quote, it generally functions as a binding offer at that price, so you are expected to deliver the stated scope for the stated money. This is why a quote needs a precise scope and an expiry date, since both define and limit what you committed to. An estimate is not binding in the same way, because it is presented from the start as an approximation that may change. The certainty a quote gives the client is exactly the certainty you take on, so only quote work you understand well.

Can I change a quote after I have sent it?

Before the client accepts it, yes, and you should revise it if your costs or the scope shift. After acceptance, the price is fixed for the agreed scope. If the work then grows beyond what you quoted, you do not quietly raise the original figure. You treat the extra as additional work and charge it separately at your standard rate, which is why a clear scope line saying out-of-scope work is billed separately is worth including on every quote.

What should I do if an estimate turns out too low?

Tell the client before you cross the estimate, never after. A good estimate names the assumptions it rests on and warns what would push the figure higher, so an overrun becomes a conversation you flagged in advance rather than a shock on the final invoice. Showing the phases and assumed hours up front makes this easy, because the client can see exactly where the extra time went and why the projection moved.

---

Related articles

• How to Write a Quote That Clients Actually Accept
• Invoice vs Quote: What Is the Difference?
• How to Estimate a Project Cost Before You Quote