Freelance Quote vs Proposal: Which to Send

A quote says what something costs. A proposal makes the case for doing it, and doing it your way. Sending the wrong one either wastes your time or undersells the work. Here's how to tell which the client needs.

Updated September 30, 2026

The difference

• A quote is a price for defined work: line items, quantities, a total and terms. The client already knows what they want.
• A proposal explains the problem, your approach, the scope, options, timeline, price and terms. The client is still deciding what to do, or who to do it with.
• An estimate is a rough, non-binding range. Useful early on, but say clearly that it isn't a fixed price.

Send a quote when

• The client has already defined the work ("20 product photos on white", "fix this bug").
• It's a repeat job for an existing client.
• The job is small enough that a full proposal would take longer than the work.
• They're comparing like-for-like prices and the decision really is mostly about cost.

Send a proposal when

• The client knows the problem but not the solution.
• The project is large enough that scope, timeline and terms need agreeing.
• You're competing on approach, not just price.
• Several people will read it before a decision is made.
• You want to offer options at different levels of investment.

A quote template for small jobs

QUOTE #[number]
From: [Your name / business]
To: [Client name]
Date: [Date]   Valid until: [Date + 14 days]

Item                                       Qty   Price
[E.g. Product photos, white background]     20   [price each]
[E.g. Retouching]                           20   [price each]
[E.g. Rush delivery (48 hours)]              1   [price]
                                                  ------
Total                                             [total]

Includes: [what's covered, in one line]
Not included: [one line]
Payment: [terms, e.g. 50% to book, balance on delivery]
To accept: reply "approved" to this email.

Even a short quote should include what's not included, payment terms and a valid-until date. Those three lines prevent most small-job disputes.

The mistake in each direction

Sending a quote when the client needed a proposal turns your work into a line item they compare on price alone. Sending a long proposal for a small, defined job slows everyone down and can make you look expensive before they've read the number. When unsure, ask: "Would it help if I outlined a couple of approaches, or do you just need a price for this?"

Moving from a quote to a proposal

If a client asks for "a quick quote" on something that clearly needs scoping, send a short proposal with two options instead. It still leads with the price they asked for, but gives you room to show the difference between a cheap version and one that solves their problem.