A client asks you for “an invoice for the project” before you’ve even scoped it. Another says “just send a receipt” after paying the deposit. A third calls your proposal an “estimate” and treats the number as a starting point for negotiation. Each of these is a different document, and using the wrong one at the wrong stage causes disputes, delayed payments, and scope creep that could have been prevented in ten minutes.
Here’s the complete breakdown: what each document is, when to send it, and exactly what to include.
Quick reference: the four documents at a glance
| Document | When you send it | Binding? | What it represents |
|---|---|---|---|
| Estimate | Before discovery is complete | No | Approximate cost range |
| Quote | After scoping is done | Yes (when accepted) | Fixed price for defined scope |
| Invoice | After work is delivered (or per milestone) | Yes | Request for payment |
| Receipt | After payment is received | Yes | Proof of payment |
The sequence on a standard project runs in that order: estimate → quote → invoice → receipt. Skipping stages, especially sending an invoice in place of a quote, is where most document confusion originates.
Estimate: use it before you know the full scope
An estimate is the document you send when a client asks “roughly how much would this cost?” and you don’t yet have enough information to answer precisely. It’s an educated range, not a commitment.
Use an estimate when: the client is exploring options before committing to a discovery session, when the scope is genuinely unclear, or when you’re responding to a cold inquiry.
Always include this phrase, or something close to it: “This estimate is based on the information provided. Final pricing will be confirmed in a formal quote after a discovery session.”
What to avoid: putting a single number in an estimate. If your estimate says “$5,000–$8,000,” the client hears “$5,000.” That becomes their anchor, and any quote higher than that feels like you’ve changed the price. Either give a range with a high end that gives you room to move up, or skip the estimate entirely and go straight to a discovery call.
Estimates are not binding. If a client tries to hold you to an estimate number after scope has been defined, that’s a scope conversation, not a pricing argument. The estimate was explicit about what it was.
Quote: use it when scope is defined
A quote is a binding document. Once a client accepts it, in writing, even just “confirmed” in an email, it’s an agreement. You’re committing to deliver the scope at that price. They’re committing to pay.
Use a quote after any project where you’ve done enough discovery to define deliverables precisely: what’s included, how many revisions, what the timeline is, and what the payment structure is.
The part most freelancers skip: the exclusions list. “Does NOT include…” is what makes a quote defensible. If your quote doesn’t say “copywriting not included,” a client can reasonably expect it’s included. If your quote doesn’t specify revision rounds, they’ll ask for ten. Every quote needs a section that lists what is explicitly outside the scope.
A complete quote includes: exact deliverables, revision rounds, timeline, payment schedule, expiration date (quotes are usually valid for 30 days), and a specific list of exclusions.
The exclusions list on a quote is what protects you from scope creep. “Does NOT include…” is as important as the deliverables list, and most freelancers leave it out entirely.
Invoice: use it when a deliverable is complete
An invoice is a request for payment tied to work you’ve already done, or to a milestone payment that’s due based on the project schedule.
Timing matters more than most freelancers realize. Send invoices immediately when a deliverable is complete, not at the end of the month. Every day you wait to invoice is a day added to your payment timeline. A client who received a deliverable on the 15th but doesn’t get the invoice until the 30th will treat their payment window as starting from the 30th, not the 15th.
Every invoice should reference the quote or project number it relates to, describe the work it covers (one clear line is enough), state the due date explicitly, and include your payment terms and late fee clause.
If you send invoices without referencing the underlying quote or agreement, you’re making it easy for clients to dispute what was agreed. “Invoice, Website Redesign per Quote #24-08 dated April 1” is cleaner and harder to argue with than “Invoice, Web Design Work.”
Receipt: use it after payment clears
A receipt is issued after payment has been received. It’s proof that the transaction happened, not a request for money, not an expectation.
Clients ask for receipts for expense reports, accounting records, and tax documentation. Sending them without being asked is a small professional touch that saves your client a follow-up email.
Tools like Waco3 generate receipts automatically when a payment is marked as received. This happens in the background, you don’t have to think about it.
A real scenario walkthrough
Here’s how all four documents play out on a single $6,500 web design project.
Week 1, Discovery call. The client asks how much a redesign costs. You don’t have full scope yet, so you send an estimate: “Based on what you’ve described, a project like this typically runs $5,000–$8,000. I’ll have a firm number after our discovery session next week.”
Week 2, After scoping. You have enough information to define the project. You send a quote: “$6,500 for the defined scope, see deliverables list. Does NOT include copywriting, photography, or hosting setup. Two rounds of revisions included. Quote valid for 30 days.”
Week 2 end, Client accepts. Client emails back “confirmed, let’s do it.” That email is acceptance in writing. You send the first invoice: “$3,250, 50% deposit per Quote #26-04. Due within 7 days. Project start date confirmed upon receipt.”
Week 6, Launch. Project is complete and delivered. You send the final invoice: “$3,250, remaining balance per Quote #26-04. Due within 15 days.”
Client pays final invoice. You send a receipt: “Payment of $3,250 received on [date] for [project name]. Full balance paid. Thank you.”
Five documents, four stages, no confusion about what anything was. The client has a clean paper trail for their accountant. You have a clean record if anything needs to be referenced later.
The practical rule
When in doubt about which document to send: ask yourself whether payment has happened yet, and whether scope is defined yet.
- Scope undefined, no payment: estimate
- Scope defined, no payment, work not started: quote
- Scope defined, work complete or milestone due: invoice
- Payment received: receipt
Getting these right takes five minutes of habit change. Getting them wrong costs hours in client disputes, scope arguments, and confused payment timelines.
Related reading: For how to structure the payment terms inside your quotes and invoices, see Net 30 vs. Net 15 vs. Net 60 and How to Ask for a Deposit Before Starting Work.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
