Estimate, quote, invoice — freelancers and clients toss these words around as if they're the same thing, and that confusion causes real problems. Send a casual "estimate" the client reads as a fixed "quote," and you're stuck doing the work for less than it costs. Knowing exactly what each document is — and when to send which — is one of those small fluencies that prevents disputes and makes you look like a professional.
Here's the clear difference, and how the three fit together.
The one-line version
- Estimate — an educated guess at the cost. Not binding. Used when the scope is still fuzzy.
- Quote (quotation) — a fixed offer: this exact scope for this exact price, valid until a date. Binding once accepted.
- Invoice — a request for payment for work delivered or a milestone reached. Issued after the agreement.
Get these three roles right and the rest is detail.
Side by side
| Estimate | Quote | Invoice | |
|---|---|---|---|
| Purpose | Rough cost guess | Fixed price offer | Request for payment |
| When | Scope unclear, early talks | Scope clear, ready to commit | After delivery / milestone |
| Binding? | No — can change | Yes, once accepted | Yes — payment is due |
| Contains a price | A range or ballpark | An exact, fixed figure | The amount owed + due date |
| Client's next step | Refine scope | Accept → you start | Pay by the due date |
| Sent by | You → client | You → client | You → client |
Estimate: the educated guess
An estimate is what you send when you don't yet know enough to commit to a price — the scope is loose, or you need a discovery phase first. "This will probably run $1,400–$1,800, refined after we scope the details."
The danger with estimates is psychological: clients remember the bottom of any range as a promise. If you say "$1,400–$1,800" and the work lands at $1,800, some clients feel overcharged. So if you send an estimate, label it clearly (the word ESTIMATE, and "subject to change once scope is final"), and avoid ranges so wide they're meaningless. If a number could be mistaken for a commitment, you should be sending a quote instead.
Quote: the fixed offer
A quote (or quotation) is a firm offer: a specific scope for a specific, fixed price, usually valid for a set window (e.g., 14–30 days). Once the client accepts, you're generally bound by it — which is exactly why it's the right document when scope is clear and you're ready to win the job.
A good quote includes the things that prevent later fights: an itemized scope, what's excluded ("not included: copywriting, hosting"), payment terms, an expiry date, and a clear way to accept. The expiry date does real work — it creates a decision deadline and protects your pricing from being held to months later. (Full breakdown: how to write a quotation that gets accepted.)
Invoice: the request for payment
An invoice comes after the agreement — it's the document that says "the work (or this milestone) is done; here's what you owe and when." It's a binding request for payment with a unique number, the amount, a due date, and how to pay.
For corporate clients, the invoice usually references earlier documents: the quote it's based on and the client's purchase order number. Getting those references right is what keeps your invoice from sitting in an approval queue (see what a purchase order is and how to use it). For the full anatomy, see how to make an invoice online for free.
How they fit together
From first contact to getting paid
- 1
Estimate (sometimes)
Early, when scope is fuzzy — a ballpark to keep the conversation going.
- 2
Quote
Once scope is clear — your fixed offer with terms and an expiry date.
- 3
Client accepts (and PO, if corporate)
The quote becomes the agreement; corporate clients issue a purchase order.
- 4
You deliver the work
Per the agreed scope; extras get a fresh quote.
- 5
Invoice
Bill the agreed amount, citing the quote/PO, with a due date.
Not every job uses all four — small projects often skip the estimate and even the formal PO. But the order never changes: you offer (estimate/quote), you agree, you deliver, you bill.
The mistakes that cause disputes
- Sending an estimate the client treats as a quote. If the number might be read as fixed, make it a quote — or label the estimate unmistakably.
- A quote with no expiry date. Clients resurface old quotes and demand old prices. Always add "valid until [date]."
- A quote with no exclusions. "Just one more thing" lives in the gap between what you quoted and what you didn't say you'd exclude.
- Invoicing an amount that doesn't match the quote/PO. Corporate AP systems flag mismatches; mirror the agreed figure and wording.
- Treating the quote as the contract. A quote covers scope and price; it doesn't cover revisions, IP, or kill fees. For bigger work, pair it with a proper contract.
The takeaway
Estimate to explore, quote to commit, invoice to collect. Using the right document at the right moment — with clear terms and matching numbers — is most of what separates freelancers who get paid smoothly from those stuck in "but I thought you said…" arguments.
Create quotes and invoices that match
Tuplify's free quotation and invoice generators produce clean, numbered, tax-correct documents with consistent details — so your quote, PO, and invoice line up and get paid faster.
Create a quote or invoice free