Home › Guides › Estimate vs. Quote vs. Invoice

Estimate vs. quote vs. invoice: what's the difference?

These three documents follow each other in a typical project, and it's easy to blur them together — but each represents a different level of commitment, and using the wrong one at the wrong stage causes real problems: a client held to a number they thought was flexible, or a contractor unable to bill for costs a "fixed" quote didn't actually promise to fix.

The short version

An estimate is a good-faith prediction of cost, understood by both sides as approximate and subject to change. A quote is a fixed-price offer that becomes binding once the customer accepts it. An invoice is the request for payment sent once work is underway or complete. They represent increasing levels of commitment, roughly in that order, across the life of a project.

Estimate: an approximate prediction

You send an estimate when you can't (or don't want to) commit to an exact final price yet — often because the full scope isn't known until work starts, as is common in construction, repair, and any job where site conditions matter. An estimate should say clearly that it's an estimate, and ideally state a range or a stated margin ("+/- 10%") rather than a single number that reads as a promise. If the final cost is likely to move, an estimate is the honest document to send, and it protects you from being held to a number you never actually fixed.

Quote: a fixed-price offer

A quote is a specific, fixed price for a defined scope of work, and once the customer accepts it, it's generally treated as a binding offer — you're committing to deliver that scope for that price, barring a scope change both sides agree to separately. Quotes suit jobs where the scope is genuinely knowable upfront: a fixed product order, a service with a standard, well-understood price. If you send a quote and then costs increase for a reason within your control (not a client-requested change or a genuinely unforeseen condition), you generally can't simply bill more — that's the entire point of quoting a fixed price.

Invoice: the request for payment

Once work is agreed (via an accepted quote or estimate) and either underway or complete, the invoice is what actually requests payment — see our full guide to writing an invoice for what it needs to include. An estimate or quote is not itself a billing document; converting it into an invoice once work begins is a distinct step; skipping straight to an invoice without a prior estimate or quote is fine for simple, well-understood work, but skips the useful step of getting the client's cost expectations aligned before you start.

Side-by-side comparison

	Estimate	Quote	Invoice
When it's sent	Before work, scope uncertain	Before work, scope defined	During or after work
Binding?	No — approximate	Yes, once accepted	Yes — payment is due
Includes a due date	No	No	Yes
Typical validity	Short (may need revisiting)	15–60 days, stated	N/A — due date instead

Moving from one to the next

A clean project follows the sequence: estimate (if scope is uncertain) → quote (once scope is confirmed and you're ready to commit to a price) → invoice (once work starts or completes). Not every project needs all three — plenty of simple jobs go straight from a quote to an invoice, or even straight to an invoice for routine, well-understood work. What matters is that whichever document you send matches the actual level of commitment you're making; sending something that looks like a firm price when you mean it as a rough guess (or vice versa) is where most of the friction between these three documents comes from.

Where people get this wrong

• Sending an estimate that reads like a fixed quote — if the number could change, say so explicitly and state a range or margin.
• Treating an accepted quote as renegotiable without a documented scope change — that undermines the entire reason a client accepted it.
• No stated validity period — without one, you can end up honoring a months-old price on materials or labor that have since gotten more expensive.
• Adding a due date to an estimate or quote — neither is a payment request; a due date on either sends a confusing signal.
• Reusing an invoice template unmodified as an estimate — the content requirements are different enough that a purpose-built document avoids ambiguity.

Still have questions?

Is a quote legally binding?

Generally yes, once accepted — a quote is normally treated as a fixed-price offer that becomes binding when the customer agrees to it, unlike an estimate, which is usually treated as a good-faith prediction that both sides understand may shift. Whether a specific quote is legally enforceable, and under what terms, depends on your jurisdiction's contract law and exactly how the quote was worded — this is general practice, not a legal guarantee.

Can I still charge more than an estimate if costs change?

Usually yes, if you communicated that the figure was an estimate rather than a fixed quote and the increase reflects a genuine change (unforeseen site conditions, a client-requested addition) rather than simple underquoting. Document the reason for the increase and get the client's sign-off before doing the additional work, the same way you'd handle a construction change order — see our construction invoicing guide for that process in detail.

How long should an estimate or quote stay valid?

Most businesses state a validity window — 15, 30, or 60 days is common — after which prices may need to be revisited due to material cost changes, scheduling availability, or seasonal pricing. Stating this explicitly on the document protects you from being held to an old price on a job that gets accepted months later.

What happens to the estimate once the client accepts?

It typically gets converted into an invoice (or, for larger jobs, a series of milestone invoices) once work is agreed and begins — the estimate itself isn't a billing document and generally isn't what you'd send to request payment.

Do estimates and quotes need to look the same as an invoice?

They should share your branding and general layout for consistency, but the content differs enough that using your invoice template unmodified for an estimate can be actively confusing — an estimate shouldn't have a due date or payment instructions, since nothing is owed yet. Using a document type built specifically for estimates (rather than repurposing an invoice) avoids sending mixed signals.

Create yours

Our estimate generator uses the same accurate calculations as our invoices, framed as a quote rather than a bill — with no due date or payment instructions to send the wrong signal.

Create an Estimate