PitchLeaf — free proposal & quote builder, no signup

Proposal vs quote vs estimate: which one to send a client

A client emails "can you send me something for this?" and you have to decide what "something" is. Send a full proposal when they wanted a number and you look slow. Send a bare number when they were weighing three vendors and you look thin. Here is what each document is, what it commits you to, and a simple rule for choosing.

The short version

EstimateQuoteProposal
What it isAn informed guess at the likely costA fixed price for defined workA quote plus the case for hiring you
Price commitmentApproximate; can changeFirm for the stated scope and validity periodFirm, same as a quote
LengthA few linesHalf a page to a pageOne to three pages
Send whenScope is still fuzzy; they need a ballpark to decide whether to talk furtherScope is clear; they already want you and just need the priceScope is clear and you are being compared, or the budget is large enough to justify explaining your approach

Estimate: an informed guess, clearly labelled

An estimate tells the client roughly what the work is likely to cost before either of you has pinned down the details. The important word is roughly. Consumer advice bodies describe an estimate as an educated guess that is not binding and can change once the real work is known (Citizens Advice Bureau NZ: estimate vs quote). That does not mean anything goes; if the final cost drifts far from the estimate without warning, you will have an argument on your hands, and in some jurisdictions the law expects the final charge to be reasonable.

The way to send an estimate well:

Example estimate: "Based on what you described, a five-page rebuild is likely to land between $3,200 and $4,000. The main variable is whether we reuse your existing copy or rewrite it. This is an estimate; I will send a fixed quote once we have confirmed the page list."

Quote: a fixed price for a defined scope

A quote is a firm offer: this work, for this price, accepted by this date. Once the client accepts it, both sides generally expect the price to hold for the scope described, which is exactly why quotes are more useful than estimates to a client trying to budget (Lawyer Monthly: estimate vs quote vs invoice). How enforceable an accepted quote is depends on where you and the client are and how it was accepted, so treat this as a description of how quotes are normally understood rather than legal advice, and use a contract when the stakes call for one.

Because a quote binds the price, the scope on the quote has to be tight. A quote for "website redesign, $3,700" is a trap. A quote for "five pages listed below, two revision rounds, launch support, $3,700, valid until 30 September" is a tool.

Every quote needs:

Not sure how to lay out the line items and terms? The pricing and terms sections of our freelance proposal guide apply to quotes word for word.

Need a quote or a proposal in the next ten minutes? PitchLeaf does both: keep every section for a proposal, or switch off Overview, Scope and Timeline and you have a clean quote with itemised or fixed pricing, tax, discount and a valid-until date.

Build one now, free, no signup

Proposal: a quote plus the reason to choose you

A proposal contains everything a quote does, wrapped in context: what problem you are solving, what the client gets, how the work will run, and what happens next. The price is still fixed; what changes is that the client is not just comparing numbers, they are comparing understanding.

That is why the business proposal vs estimate question usually answers itself. If the client is deciding whether to do the project, or who to do it with, send a proposal. If they have already decided both and only need the price, a proposal wastes their time.

A proposal is the right call when:

Keep it short even so; two pages covers most freelance proposals.

A rule for choosing

Ask two questions.

  1. Is the scope defined well enough that I would be comfortable holding this price? No: send an estimate with a range and a path to a quote. Yes: continue.
  2. Does the client still need convincing, either that the project is worth doing or that I am the right person? Yes: send a proposal. No: send a quote.

For a bigger job the natural sequence is estimate, then call, then proposal. For a repeat client with a routine request, go straight to a quote.

Three mistakes that blur the lines

Calling an estimate a quote

If you write "quote" on a rough number, the client is entitled to treat it as a firm price. If you are not sure, label it an estimate and give a range.

Quoting without a validity date

Costs change and so does your availability. A valid-until date is the polite way to say the offer is current, not permanent.

Sending a proposal with no clear acceptance step

Say what "yes" looks like: reply with "approved", or sign and date the last page and send it back. A signed page is a plain written record that both sides agreed the scope and price; it is not a substitute for a contract when you need one.

Invoices are none of the above

One more term that gets tangled in: an invoice is a request for payment for work done or due, sent after acceptance. Estimates and quotes come before the work, proposals come before the decision, invoices come after.

Whichever one you are sending, it should look like you meant it. PitchLeaf builds proposals and quotes with section toggles, line-item maths and a clean PDF export. Nothing is uploaded; it all stays in your browser.

Build one now, free, no signup