Quick comparison
Here's the fundamental difference between these three documents:
- Estimate — "This will probably cost around $X." An approximation, sent early in the process when the scope is unclear. Not binding.
- Quote — "This will cost exactly $X." A fixed-price commitment, sent when the scope is defined. Binding once accepted.
- Invoice — "You owe $X for work completed." A payment request, sent after the work is done (or at agreed milestones). A financial record.
What is an estimate?
An estimate gives the client a ballpark figure for a project before you've fully assessed the scope. It's your best guess based on available information — a site visit, a phone conversation, or a project brief.
Estimates are not binding. The final cost can go up or down depending on what you discover as the work progresses. Common in repair work, renovations, and custom projects where the full scope isn't clear until you start.
When to use an estimate:
- The client asks "roughly how much?" before you've done a detailed assessment
- The scope depends on unknowns (hidden damage, client decisions, conditions on site)
- You need to give a range, not a commitment
- It's the first touchpoint — you'll follow up with a formal quote
Learn more in our estimate template guide.
What is a quote?
A quote (or quotation) states the exact price you'll charge for a defined scope of work. Once the client accepts, you're committed to delivering at that price — no surprises.
Quotes are typically sent after you've assessed the job fully: visited the site, understood the requirements, and calculated your costs. The scope is defined, the price is fixed, and the client can make a decision based on a firm number.
When to use a quote:
- You've assessed the job and know exactly what's involved
- The scope of work is clearly defined
- The client needs a firm number to compare with other providers
- You're ready to commit to a price
See our complete guide to creating a job quote.
What is an invoice?
An invoice is a formal request for payment. It's sent after the work is completed (or at agreed milestones during the project) and tells the client exactly what they owe, when it's due, and how to pay.
Unlike quotes and estimates — which come before the work — invoices come after. They're financial records used for bookkeeping, tax filing, and payment tracking.
When to use an invoice:
- You've completed the work (or reached a milestone)
- The client owes you money
- You need a formal payment request for your records
- You need documentation for tax purposes
See our guide to creating a professional invoice.
How they work together
In a typical project workflow, these documents flow in sequence:
- Client inquiry — the client contacts you and describes what they need.
- Estimate (optional) — you give a rough cost based on initial information. This helps the client decide if the project is within their budget before investing time in a detailed assessment.
- Assessment — you do a site visit, detailed consultation, or technical review to understand the full scope.
- Quote — based on your assessment, you send a formal quote with a fixed price, defined scope, and validity period.
- Acceptance — the client signs and accepts the quote. Work begins.
- Invoice — you send an invoice when the work is complete (or at milestones). The amount should match the quote unless agreed changes were made.
- Payment — the client pays the invoice. You send a receipt as proof of payment.
Not every project needs all three. A simple freelance job might skip the estimate and go straight to a quote. A recurring service might skip the quote entirely and just send monthly invoices. Use what makes sense for the situation.
Key differences at a glance
- Timing: Estimate (before assessment) → Quote (after assessment) → Invoice (after work)
- Price commitment: Estimate (approximate) → Quote (fixed) → Invoice (final amount due)
- Binding: Estimate (no) → Quote (yes, when accepted) → Invoice (yes, payment obligation)
- Purpose: Estimate (set expectations) → Quote (win the job) → Invoice (get paid)
Common mistakes to avoid
- Calling an estimate a quote — if you label something a "quote" but intend for the price to change, you'll have disputes. Use the correct term.
- Invoicing a different amount than the quote — the invoice total should match the accepted quote unless you documented and got approval for scope changes.
- Skipping the quote — starting work without a signed quote means no clear agreement on scope or price. This is the most common cause of payment disputes.
- Not numbering your documents — use sequential numbers (EST-001, QT-001, INV-001) for all three. This creates a paper trail that links the estimate to the quote to the invoice.