Quote vs Estimate vs Invoice
A freelancer sends an invoice. The client replies, "Thanks, we'll consider it." Or sends an estimate and gets back, "Great, go ahead" — at a number that was never agreed as final. In both cases the document was wrong for the moment.
Key takeaways
- A quote asks. An estimate suggests. An invoice demands. Different jobs, different moments.
- A quote is a firm price and needs an expiry date. An estimate is an approximation and needs a stated tolerance.
- An invoice comes after approval. Sending it before is how disputes start.
- Number every document. The sequence is your evidence chain.
- The chain is estimate > quote > approval > work > invoice > payment. Skip a link and the dispute wins.
Quote vs estimate vs invoice: the definitions
A quote is a firm offer to do defined work at a set price. You commit to the number. It needs an expiry date, because prices do not hold forever. A quote asks the client for a decision. Some clients call this a proposal or a fixed-price quotation; the job is the same.
An estimate is an educated approximation, usually a range or a best guess with a note that the final amount may change. It is honest about uncertainty. An estimate suggests a direction. A ballpark estimate is still an estimate — it sets expectations, not a price.
An invoice is a demand for payment for work done or a milestone reached. It states the final amount and expects money in return. An invoice demands. The moment a client pays, the invoice becomes a record — part of your receipt chain.
Proforma invoice
A proforma invoice is not a real invoice. It is a quote dressed as an invoice — a preview of what the final bill will look like, sent before work is done. Use it when the client needs a document that looks like an invoice for internal approval or to raise a purchase order, but no payment is due yet.
Good software should know the difference between these documents too. If your invoicing tool treats quotes, estimates, and invoices as unrelated files, the evidence chain is already broken.
When the wrong document starts a dispute
John sends an estimate for a website redesign. The client replies, "Looks good, let's go." John takes that as approval and starts work. Three weeks later he sends the invoice at the top of the estimate's range. The client pushes back: "I never agreed to that price."
John reaches for proof — and finds there is none. "Looks good" was a reaction to a range, not an approval of a number. The estimate was never converted into a quote, and no quote was ever approved. John now has to prove something that never existed.
After building business software for twenty years, I have noticed a pattern: freelancers rarely lose disputes because they charged the wrong amount. They lose because they cannot prove when the client agreed. The number is almost never the problem. The missing approval is.
The difference, side by side
| Document | Job | Price commitment | Binding when | Sent | Client should |
|---|---|---|---|---|---|
| Quote | Propose work at a fixed price | Fixed — you commit | The client accepts | Before work | Accept, decline, or negotiate |
| Estimate | Approximate the cost | Approximate, with a tolerance | Informational, not binding | Before work | Approve the direction |
| Invoice | Request payment | Final | On issue; sealed once paid | After work, or per terms | Pay |
| Proforma | Preview the final bill | Approximate | Not binding | Before work | Use for internal approval |
Which document do you need?
When to send a quote, an estimate, or an invoice
- New client, defined scope > send a quote first.
- Unclear scope, discovery phase > send an estimate with a range.
- Work done, or a billing milestone reached > send an invoice.
- Repeat client with a rate already agreed > invoice directly; the rate is on file.
- Time-and-materials under a signed agreement or retainer > invoice per the agreement; the agreement replaces a per-project quote.
- The client asks "roughly how much will it cost?" > estimate.
- The client asks "what's the price to do this?" > quote.
- The client needs a document for internal approval before work > proforma invoice.
The document chain
Skip the estimate when the scope is already clear.
Each step is a link in the evidence chain: agreement, scope, work, approval, invoice, payment. When a client disputes a number, you walk the chain back to the link that proves it. Skip the approval step and the chain has a gap exactly where disputes form. The full dispute playbook is in the evidence chain article.
Does a quote become a contract?
Short answer: a quote becomes binding when the client accepts it. The quote itself is an offer, not a contract. Acceptance is what turns the offer into an agreement.
- Acceptance can be an email reply, an electronic signature, a signed PDF, or a purchase order — the form varies by jurisdiction.
- The US, the UK, and EU member states treat offers and acceptance differently, and some industries carry their own rules.
- What matters in a dispute is a written, dated acceptance you can produce. Keep it with the quote.
I am not a lawyer, and this is not legal advice. For contracts worth real money, ask one.
Common freelance invoicing mistakes that lead to disputes
- Invoicing instead of quoting. You demand before you have asked. The client feels pressured, and you have no approval to fall back on.
- Treating an estimate as a fixed price. Scope grows, the invoice surprises the client. State a tolerance up front.
- Quotes with no expiry date. An open-ended quote is a promise you may not be able to keep.
- Invoicing without a written approval. With no "yes" on record, the dispute is already half lost.
- Mixed or reused document numbers. Break the sequence and the evidence chain breaks with it.
If you recognized two or more mistakes above, your current setup is already costing you disputes and late payments. LockMargin links quotes, approvals, and invoices into one sequence — no gaps, no mix-ups. See how it works >
Five myths about quotes, estimates, and invoices
- "Quotes are always legally binding." No. A quote is an offer; it binds only when the client accepts it.
- "Estimates are useless." No. They set expectations; they just are not bills.
- "Every invoice needs a quote." No. Repeat clients, retainers, and signed agreements can invoice directly.
- "Estimates do not need numbers." Wrong. Number everything; the sequence is your evidence.
- "A PDF equals proof." No. A PDF is a document; proof is the chain — quote, approval, invoice, payment.
How LockMargin handles the chain
The Quotes module creates both quotes and estimates. When a client approves, the same record converts into an invoice — the numbers carry over automatically, and the sequence stays unbroken.
Snapshot Billing freezes the billed amounts so they cannot be changed retroactively. Once paid, the Immutability Guard seals the record: no edit, no accidental deletion. The chain is one continuous record, not four separate files you keep in sync by hand. See the features page for the full flow.
Questions freelancers ask
Is a quote legally binding?
On its own, no. A quote is an offer; it becomes binding once the client accepts it. That acceptance — an email, a signature — is what turns an offer into an agreement. Keep the approval with the quote.
What is the difference between an estimate and a quote?
A quote is a firm price you commit to. An estimate is an educated approximation, usually with a range or a note that the final amount may change. Estimates need a stated tolerance; quotes need an expiry date.
Should quotes and estimates have numbers?
Yes. Number every document in a sequence. Numbers make the chain provable and disputes easier to resolve. A quote you cannot point to is a memory, not a record.
Can I send an invoice without a quote?
For repeat clients with an agreed rate, yes. For time-and-materials work under a signed master agreement or retainer, the agreement replaces the per-project quote. For new fixed-scope work, send the quote first and get approval. Invoicing without approval is how disputes start.
What if a client disputes an invoice against an estimate?
Compare the estimate, the approval, and the invoice. If the invoice exceeds the estimate, explain the extra scope and issue a correction or credit note. The evidence chain decides.
Should quotes have an expiry date?
Yes. Prices change. An open-ended quote is a promise you may not be able to keep. Thirty days is a common window.
What is a proforma invoice?
A proforma invoice is a quote dressed as an invoice — a preview of the final bill, sent before work is done. Use it when the client needs an invoice-looking document for internal approval, but no payment is due yet.
Can I turn an estimate into an invoice?
Only after the client approves it and you do the work. An estimate is not a bill. Convert it to a quote, get approval, then invoice.
About the Author
Vlad (Volodymyr) Shiyan — Founder & Developer, Kharkiv, Ukraine. Building LockMargin since December 2025. Offline-first invoicing for freelancers who are tired of subscriptions. Standard is $49 one-time. Read more about Vlad →
Ready to own your freelance data?
Own your tools for $49 once → Read the Manifesto →Get the Client Data Protection Checklist — PDF, no email required.
Not ready to own yet? Start is free — 5 clients, 5 projects a month, unlimited invoices.
No subscription · No account required · Your data stays yours forever