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

These four words get used interchangeably, and that causes real problems. A client treats your rough estimate as a promise. A "quote" gets sent without a scope and turns into an argument. A proposal goes out with no price and stalls. Knowing exactly which document you're sending, and what it commits you to, protects your margins and your client relationships.

At a glance

What is an estimate?

An estimate is your best educated guess at what a job will cost, given what you know now. It's useful early, when the client wants to know whether you're even in their budget, but before either of you has defined the work.

Use an estimate when: the scope is fuzzy, the client is exploring, or the work depends on unknowns (e.g. "we'll know more after the audit").

How to write one safely:

• Give a range, not a single number: "$4,000–$5,500."
• List the assumptions it's based on: "Assumes up to 8 pages, copy supplied by you."
• Label it clearly: "Estimate — not a fixed quote."

What is a quote?

A quote (or quotation) is a fixed price for a specific scope of work. Once a client accepts it, you're generally expected to deliver that scope for that price. That's why a quote needs to be precise about what's included and what isn't.

A good quote includes:

• A unique quote number and date.
• Line items with quantity, rate and total.
• What's included, and just as important, what's excluded.
• Number of revision rounds.
• Payment terms: deposit, milestones, due dates.
• An expiry date ("Valid for 30 days"), so an old price can't be accepted months later.
• Tax, if you charge it.

What is a proposal?

A proposal is a sales document. It explains why you're the right person for the job and how you'll approach it, and it usually includes a quote. Proposals matter most when the client is comparing options, the project is large, or several people have to sign off.

A proposal that wins usually has:

1. The problem, in the client's words. Show that you listened.
2. The outcome they want, and how you'll measure it.
3. Your approach: phases, deliverables and milestones.
4. Timeline.
5. Investment: the quote, ideally with two or three options (e.g. Essential / Recommended / Complete).
6. Relevant proof: a short case study or two.
7. Terms and next step: how to accept, the deposit, and the start date.

Keep it focused. A proposal the client actually reads beats a thorough one they skim. And make accepting easy. "Reply to this email and we'll send a contract" is slower than a one-click approval.

What is an invoice?

An invoice is a formal request for payment, for work that was agreed in the quote or proposal and has been delivered (or reached a milestone). It needs a unique number, dates, line items, totals, tax and payment instructions. Our freelance invoice checklist covers every field.

If the invoice doesn't match the accepted quote, expect questions. The cleanest invoices are built directly from the approved quote, plus any extra hours or change requests the client agreed to along the way.

Is a quote legally binding?

In many places an accepted quote can form a binding agreement, because there's an offer, acceptance, and payment for work. An estimate usually isn't binding, precisely because it's labelled as an approximation. The details depend on your jurisdiction and your wording. For larger engagements, pair your quote or proposal with a proper contract that covers IP, cancellation, liability and payment terms.

How they fit together: one workflow, not four documents

The classic freelance workflow looks like this:

1. Discovery call, then a rough estimate to check you're in budget.
2. Proposal with a fixed quote (or options).
3. Client approves it. You take a deposit and start the project.
4. You track time and deliver milestones.
5. Invoice for each milestone or at completion, then follow up until it's paid.

The problem is that most freelancers do each step in a different tool: a Google Doc for the proposal, a spreadsheet for the quote, a project tool for tasks, a timer app, and an invoicing app. The scope gets retyped four times, and the numbers drift a little with each copy.

That's the gap Velo is built to close. You send the proposal as a link the client approves in one click. Approval automatically builds the project, milestones and budget. The time you log against it becomes invoice lines. So the quote, the project and the invoice are the same record, and you only type the scope once. Clients see every proposal and invoice in their client portal.