Quote vs Invoice vs Proposal: When to Send Which Document

A client emails you and says "send me a proposal." You send a one-page quote. They reply, "this isn't a proposal." Frustrating, right?

Quote, invoice, and proposal are three different documents that look similar at first glance but serve completely different commercial functions. Mixing them up makes you look unprofessional and costs you deals. Here's the clean separation.

The 30-second summary

• Proposal: explains the what and why of a project. A pitch document.
• Quotation: commits to the price of doing it. A binding offer.
• Invoice: requests payment for work already done. A bill.

Roughly in time order: proposal → quotation → contract → work → invoice → payment.

Most small contractors skip the proposal entirely and go straight to a quote. That works for simple jobs, but for higher-value or longer-term work, the proposal is what sells the engagement.

What is a proposal?

A proposal is a sales document. Its job is to convince the client that you are the right person to do the work, and to justify your approach. It is typically longer (3–10 pages), heavier on narrative, and includes things like:

• Executive summary
• Understanding of the client's problem
• Proposed approach / methodology
• Timeline and milestones
• Team / experience credentials
• Case studies or references
• Indicative pricing (often a range, not a fixed quote)
• Terms and next steps

A proposal does not legally bind you to a price. It positions you and your method. The actual fixed pricing usually comes in a separate quotation once the client says "yes, let's proceed."

When to send a proposal:

• Project value is $5,000+ and worth the effort
• Multiple firms are bidding and you need to differentiate on approach, not just price
• The client has a fuzzy problem that needs scoping
• It's a longer engagement (multi-month consulting, retainer, build-out)
• The client is corporate or institutional and expects formality

When NOT to send a proposal:

• The job is small, well-defined, and competing on price (just send a quote)
• The client said "send me a quick price" — match the energy
• You haven't won the right to write a proposal (more on this below)

What is a quotation?

A quotation is a commitment document. It says: "If you accept this offer, I will do the work described for this price, and I am legally bound to that price unless you change the scope."

A typical quote has:

• Header (your branding, quote number, date)
• Bill-to (client details)
• One-sentence scope summary
• Itemized line items with quantities and rates (the BOQ)
• Subtotals, taxes, grand total
• Assumptions and exclusions
• Payment terms
• Validity period
• Acceptance signature line

For deeper structure guidance, see our winning quotation guide.

A quote is shorter and tighter than a proposal. It is typically 1–2 pages for small jobs, 3–5 for larger ones. It's the document the client signs (literally or implicitly) to authorize you to start work.

When to send a quotation:

• Scope is well-defined and you can confidently price it
• The client has decided to work with you (or your competitors) and is choosing on price + terms
• It's a one-off project with a clear deliverable
• The work is repeatable enough that a fixed price is fair to both sides

What is an invoice?

An invoice is a payment request. It comes after work is done (or after a milestone, like 50% deposit). It says: "I have delivered what we agreed on. Here is what you owe me, and how to pay."

A typical invoice has:

• Header (your branding, invoice number, issue date)
• Bill-to (client details)
• Reference to the original quote/contract
• What was delivered (often just summarized — the detail was in the quote)
• Amount due, taxes, total
• Payment terms (due date, accepted methods)
• Your bank/payment details

An invoice is much shorter than a quote, because by this point everything has been agreed. The invoice is just the request for the money you've already earned.

When to send an invoice:

• Deposit milestone hit (typically 30–50% on contract signature)
• Project completion (the balance)
• Monthly retainer billing
• Variation order completion (a small invoice for an add-on the client agreed to mid-project)

A typical project flow

For a $20,000 solar installation, the document flow might look like:

1. Discovery call. Client describes their need.
2. Proposal sent. Explains why your tier-1 panels are worth the extra cost, includes case studies, indicative range of $18,000–$25,000. Client picks you.
3. Site survey done. You measure, confirm specs.
4. Quotation sent. Fixed price of $19,850, valid for 30 days, with detailed BOQ.
5. Quote signed. Client agrees.
6. Deposit invoice sent. 40% on signature = $7,940. Client pays.
7. Work executed. Installation, commissioning, net metering paperwork.
8. Final invoice sent. Balance of $11,910. Client pays.
9. Project handed over. Warranty starts.

Notice the proposal, quote, and two invoices are all different documents with different jobs. Mixing them up — for example, sending a "proposal" with binding fixed pricing, or an "invoice" before the work is done — confuses the legal commitment and can hurt enforceability if a dispute arises.

Common mistakes

1. Sending a quote when a proposal is expected. If a corporate client asks for "a proposal," sending a 1-page line-item quote can feel insufficient. Read the room. Larger orgs expect narrative; smaller clients want the number fast.

2. Sending a proposal when a quote is expected. Equally common. A homeowner who asked "how much for new wiring" doesn't want a 5-page methodology document. They want the number.

3. Calling an estimate a quote. As we covered in quotation vs estimate, a quote is binding, an estimate is not. Labelling matters.

4. Invoicing before work is delivered. Common mistake: sending the full invoice on day one. Use a deposit invoice for upfront cash, and the final invoice on completion.

5. Mixing payment terms across documents. If the quote says "50% deposit, 50% on completion" but the invoice says "net 30," you've contradicted yourself. The client will pay on whichever terms favor them.

Numbering convention

Use a simple, unique reference for each document type:

• Proposal: PROP-2026-001, PROP-2026-002, ...
• Quotation: Q-2026-0142
• Invoice: INV-2026-0287

This makes accounting and follow-up conversations clean. When a client asks "which quote was that?" you say "Q-2026-0142" instead of "the one from last Tuesday."

A note on contracts

For larger or longer-term work, the quotation alone isn't enough. You'll want a separate contract or service agreement that covers liability limits, IP ownership (for creative/software work), termination terms, and dispute resolution. The quote describes what and how much. The contract describes the legal relationship.

For small contractor work under $10,000, the quotation usually doubles as the contract — when the client signs and pays the deposit, you have a contract by conduct. For bigger work, get a real contract drafted.

Where EstimateQuote fits in

We focus specifically on the quotation side of this flow — the most common pain point for contractors and service businesses. The platform generates the quote PDF, tracks when the client views it, sends follow-up reminders, and converts to an invoice when the client says yes.

If you write quotes regularly and find yourself re-typing the same line items every week, give EstimateQuote a try. And if you're refining your overall sales rhythm, our follow-up email templates cover what to send between the quote going out and the deposit landing.