Proposal vs. Quote vs. Estimate: Which One Should You Send?

Ask five contractors what the difference between a quote and an estimate is, and you'll get five answers. That would be harmless if the documents didn't carry different legal weight — but they do, and sending the wrong one costs real money.

The short version

Document	Price certainty	Legal weight	Best for
Estimate	Approximate	Low — an educated guess	Early conversations, sight-unseen pricing
Quote	Fixed	High — becomes binding when accepted	Defined work you've scoped properly
Proposal	Fixed or phased	High — it's a quote plus persuasion	Competitive situations, bigger projects

Estimates: the handshake number

An estimate says "based on what I know so far, this will probably cost around X." It's the right document when you haven't seen the site, the scope is fuzzy, or the client is still deciding whether the project is realistic.

Two rules keep estimates from becoming disputes:

Label it. The word "Estimate" should appear on the document, along with a line like "final pricing subject to site inspection."
Give a range, not a number. "Roughly $8,000–$10,500 depending on panel condition" sets honest expectations. A single number gets remembered as a promise.

The most common estimate mistake is treating it as a soft quote — clients don't hear "approximately." If you're not prepared to do the job for the number on the page, don't put that number on the page.

Quotes: the fixed commitment

A quote says "I will do this defined work for this exact price." Once the client accepts it, you're generally bound to it — which is why a quote should never leave your hands until the scope underneath it is genuinely nailed down.

A quote earns its fixed price with specificity: counts, materials, exclusions, and an expiry date ("valid for 30 days" protects you from being held to March pricing in August). If any part of the job can't be scoped yet — a wall you can't see behind, a fixture the client hasn't chosen — carve it out explicitly with an allowance or a "quoted separately on discovery" clause.

Proposals: the quote that sells

A proposal contains a quote, but it does more work: it restates the client's problem, explains your approach, shows why you're the right choice, and then presents the price. It's the right document whenever you're being compared to someone else — which, for anything above a small job, is always.

The practical difference shows up in close rates. A bare quote invites price comparison because price is the only information on the page. A proposal changes the comparison to approach, professionalism, and fit — which is where a good operator actually wins.

So which do you send?

Phone inquiry, haven't seen the job: estimate, as a range, labeled.
Scoped work, repeat client, straightforward job: quote.
New client, competitive situation, or anything over a few thousand dollars: proposal.

One more distinction worth knowing: in most jurisdictions an accepted quote plus commencement of work can constitute a contract even without a signature. That's good news when a client tries to renegotiate mid-job — and dangerous news if your quote was vague. The fix is the same either way: write the scope like it will be read in a dispute, because occasionally it will be.

Whichever document you send, send it fast. Speed-to-quote is one of the strongest predictors of winning work — the first professional document in the client's inbox frames how every later one gets judged.