Invoice vs quote vs estimate vs proposal

The short answer

A proposal explains how you would solve the client's problem and why you. An estimate is your best guess at the cost. A quote is a fixed price for a defined piece of work, valid until a date. An invoice asks for payment for work that was agreed. On most projects they come in that order, and each one should point back to the one before it.

The rest of this page goes through each one, with what it should contain and where freelancers usually get caught.

Proposal

A proposal is a sales document. It restates the client's goal in your words, explains how you would get there, shows relevant past work, and sets out options and a price range or a price. For larger projects, agencies and companies often ask for one so they can compare several freelancers or studios.

What a useful proposal contains:

• The problem as you understood it, in two or three sentences. If you got it wrong, the client will tell you now, which is cheap.
• Your approach, step by step, with what the client gets at each step.
• The timeline, with the points where you need something from them.
• One or two relevant examples of past work.
• The price, or the price options, and what each includes.
• What happens next, for example "If this works for you, I will send a formal quote and a contract".

A proposal is not always binding on price, and many proposals say so. If you want the price in it to be the agreed price, say that it is a quote too, give a valid-until date, and ask for written acceptance. Otherwise follow it with a quote.

Keep proposals short. A client who has to read twenty pages to find the price will skip to the last page anyway.

Estimate

An estimate is your best guess at what the work will cost, given what you know now. It is the right document when the client asks "roughly how much would this be?" before the scope is pinned down.

The point of an estimate is to protect both sides from a surprise. Write it as a range ("between 3,000 and 4,500, depending on the number of product variants") or as a figure with the assumptions spelled out ("about 3,500, based on 8 product shots and 2 rounds of changes"). State plainly that it is an estimate and that the final price will be in a quote.

The common trap is that the client remembers the low end of the range and nothing else. To avoid it, put the assumptions in the same sentence as the number, and convert the estimate into a quote as soon as the scope is clear. Do not start work on an estimate alone unless you bill by the hour and the client has agreed to that.

Quote

A quote is a fixed price for a defined piece of work. Once the client accepts it, both sides are expected to stick to it: you do the work described for that price, and the client pays it. In many countries a quote accepted in writing is treated as an agreement, which is exactly why it needs to be precise.

A quote should include:

• A quote number and date, and a valid-until date, usually 14 to 30 days.
• The client's legal name and contact.
• The scope: what you will deliver, in what format, with how many revision rounds.
• What is not included. This line saves more arguments than any other.
• The price per line, the tax if you charge it, and the total.
• The timeline and the payment terms, including any deposit.
• How to accept it: a signature, a reply, or a purchase order.

The valid-until date matters. Your availability and costs change, and a client who comes back eight months later should get a fresh quote, not the old price.

If the client asks for changes after accepting, write a short change quote for the extra work and get it accepted before you start it. That is the whole defence against scope creep: every change gets a price before it gets done.

I wrote a longer guide to quote templates with an example, and there is a free quote template that builds the PDF in your browser.

Invoice

The invoice comes last. It asks for payment for work that was already agreed, at the price that was already agreed. It should contain nothing that surprises the client.

What separates it from a quote:

• It has a sequential invoice number that tax offices care about. Quote numbers do not need to be sequential with invoices.
• It has a due date instead of a valid-until date.
• It is a tax document. It goes into your records and the client's, and the rules on what it must contain come from tax law, not from you. See what to put on an invoice for the country details.
• It includes payment details.

The best invoices reference the quote: "As quoted in Q-2026-009". The person approving it can check the price against the accepted quote and approve it in a minute.

Two more you will meet

A pro forma invoice looks like an invoice but is not one. It is sent before the work or the delivery, often so a client can arrange payment or a deposit, or for customs. It is not a tax invoice, should be marked "Pro forma", and should not take a number from your invoice sequence. Once the work is done or the payment arrives, you issue the real invoice. More in what is a pro forma invoice.

A purchase order (PO) comes from the client. It is their internal approval to spend money with you, and larger companies often cannot pay an invoice without one. If a client sends a PO after accepting your quote, put the PO number on every invoice for that work.

A statement of work (SOW) is a detailed scope document, often attached to a contract, used by larger clients. It plays the same role as the scope section of a quote, in more detail. Here is how to write a statement of work.

How they connect on a real project

Here is how it usually runs on a mid-size job, for example a set of product visuals for a launch:

1. A first call. The client explains what they need and their rough budget.
2. You send an estimate in the follow-up email: "For 10 to 12 product images with 2 rounds of changes, this is usually between 4,000 and 5,500."
3. They want to go ahead, and you agree the exact list of images and the deadline.
4. You send a quote for 11 images, 2 rounds of changes, delivered as 4K PNG, at 4,950, with a 30% deposit and a valid-until date.
5. They accept and send a PO. You send a contract if the job needs one, covering usage rights and payment.
6. You invoice the 30% deposit, referencing the quote and the PO.
7. Halfway through, they ask for 3 more images. You send a change quote for the 3 images and wait for acceptance.
8. On delivery, you invoice the balance of the original quote plus the accepted change quote, each on its own line.

Every document points back to the one before it. If anyone asks "where does this number come from", the answer is one click away.

Which one to send when a client asks for "a quote"

Clients use the words loosely. "Can you send me a quote?" sent after a five-minute call with no brief usually means "how much, roughly?" Reply with an estimate and the assumptions, and say you will confirm a fixed price once the scope is clear. Sending a fixed quote for an unclear scope is how you end up doing the 12th image for free.

When the brief is clear, send the quote. When the work is done, send the invoice. Only send a proposal when the client is choosing between approaches or between suppliers, or when the job is big enough that how you do it matters as much as the price.

Questions