Invoicing · Updated 2026-10-06

Quote vs Estimate vs Invoice: What's the Difference?

Freelancers throw around the words "quote," "estimate," and "invoice" like they're interchangeable. They aren't — each document does a different job, carries different weight, and appears at a different stage of a project. Mixing them up confuses clients and can cost you money. Here's the clear distinction, and the workflow that ties them together.

The short version

• A quote is a fixed-price offer: "I will do X for $Y." If the client accepts, you're generally expected to honour that price.
• An estimate is an educated approximation: "This will probably cost around $Y, give or take." It sets expectations without locking you in.
• An invoice is a request for payment after the work is done: "I did X, you owe $Y, please pay by this date."

Quotes: a fixed commitment

A quote (sometimes called a quotation or proposal price) states exactly what you'll deliver and exactly what it costs. When a client accepts your quote, it typically forms the basis of your agreement — in many places, an accepted quote can function as a binding contract for that price.

Use a quote when: the scope is well defined and you can price it confidently — a logo package, a fixed-scope website, a wedding photography day.

What to include: the same care as an invoice — your details, the client's details, a quote number and date, an itemised breakdown, the total, how long the quote is valid (quotes should always have an expiry date, typically 14–30 days), and your terms.

The risk of quoting is under-scoping: if the work grows but the price is fixed, your margin evaporates. Protect yourself with a precise scope description and a clause covering how out-of-scope requests are handled and priced.

Our free quote generator produces professional quotes with expiry dates built in.

Estimates: an honest approximation

An estimate says: based on what I know now, here's roughly what this will cost. It's explicitly not a fixed price — it acknowledges uncertainty. Estimates suit work where the full scope can't be known upfront: exploratory consulting, repairs where the extent of the problem is unclear, or phased projects.

Use an estimate when: there's genuine uncertainty, and pretending otherwise would be dishonest or risky.

What to include: everything a quote includes, but labelled clearly as an estimate, ideally with a range ("$2,000–$2,800") or a stated accuracy ("estimated within ±15%"). Never let a client mistake an estimate for a fixed quote — that misunderstanding is the source of most billing disputes.

An estimate that consistently lands far from the final invoice destroys trust. Track your accuracy over time; if your estimates are usually 30% low, your estimating method needs work, not your clients' patience.

Invoices: the payment request

The invoice comes after the work (or after an agreed milestone). It references what was agreed — ideally the accepted quote or estimate — states the amount due, and tells the client how and when to pay. Unlike quotes and estimates, which are pre-work documents, the invoice is a formal demand for money and a tax record.

Key difference in tone: quotes persuade, invoices instruct. An invoice doesn't sell the work; it assumes the sale and asks for payment.

For the full breakdown of every field, see how to write an invoice.

The professional workflow: quote → invoice → receipt

Here's how the documents chain together on a well-run project:

1. Quote or estimate — you price the work; the client accepts.
2. Work happens — possibly with interim invoices for milestones or deposits on larger projects.
3. Invoice — you bill for the completed work, referencing the quote number so the client's accounts team can match them.
4. Payment — the client pays by the due date.
5. Receipt — you confirm payment received. Our free receipt maker handles this in seconds.

Referencing the quote number on the invoice is a small habit with an outsized payoff: it answers "what is this charge for?" before anyone asks, which is one less reason for payment to stall in approvals.

What about proforma invoices?

A proforma invoice sits between quote and invoice: it's a preliminary bill sent before the work is complete or before payment is due — common in international trade and for advance payments. Crucially, a proforma is not a tax invoice and generally shouldn't be recorded as one. We cover it in detail in what is a proforma invoice.

Legal weight: why the distinction matters

The practical legal difference is about commitment. An accepted quote is much closer to a contract term — change the price afterwards and you're on shaky ground. An estimate, properly labelled, preserves your right to bill the actual cost. An invoice creates the debt: once issued correctly, it's the document you'd rely on if you ever had to chase payment formally (see how to chase late payments).

None of this is legal advice — contract law varies by country — but the principle is universal: label each document for what it is, and make sure the client understands which one they're looking at.

A concrete example: how it plays out

Say you're a freelance web designer quoting a small business site. You send a quote: "5-page website, copy supplied by client, two revision rounds, delivery in 4 weeks — $3,200, valid 30 days." The client accepts. Mid-project they ask for an online shop too — that's outside the quoted scope, so you agree an additional $1,500 in writing. On completion you send an invoice for $4,700 referencing the quote number, due in 14 days. The client pays; you send a receipt. One project, three documents, zero ambiguity about what was agreed and what is owed.

When the scope is fuzzy at the start — "redesign our site, we're not sure what we need yet" — you'd begin with an estimate ("likely $2,500–$4,000 depending on page count") instead of a fixed quote, then firm it up into a quote once the scope is clear. The document matches the certainty: uncertain scope gets an estimate, defined scope gets a quote, finished work gets an invoice.