A quote is a short price estimate, a proposal sells the scope and price together to win the project, and an invoice requests payment for work that's already been agreed. Sending the wrong one at the wrong moment slows deals down and confuses clients. Here's the plain-English breakdown and the order to use them.

Quote: the quick price estimate

A quote answers one question — "roughly what will this cost?" — before anyone has committed. It's short: the service, a price (or price range), and validity ("valid for 30 days"). Use it early, when a client is still comparing options and wants a number fast.

  • Purpose: give a price so the client can decide whether to proceed.
  • When: at first contact, before scope is fully defined.
  • Keep it: fast and light — a few lines, not a full document.

Proposal: the document that wins the work

A proposal is where you actually sell the project. It restates the client's goal, lays out the scope as concrete deliverables, states one clear price, and ends with a way to say yes. It does the persuasion a bare quote can't. This is the document that turns interest into a booked project.

  • Purpose: win the project by pairing scope with price and a clear next step.
  • When: once you understand the goal and can define the work.
  • Keep it: one page, scannable, with a single obvious action.

Invoice: the request for payment

An invoice comes after agreement. It's a formal request for payment for work that's been scoped and accepted — deposit, milestone, or final balance. It includes amounts, dates, and payment details, and it's what your accounting is built on.

  • Purpose: collect payment for agreed work.
  • When: at deposit, on milestones, and on delivery.
  • Keep it: clear, numbered, and easy to pay.

The order, in a typical project

  • 1. Quote — a fast price so the client can decide to move forward.
  • 2. Proposal — scope + price + next step to win the project.
  • 3. Invoice — request the deposit, then the balance.

The modern shortcut: fold payment into the proposal

The traditional flow has a gap — the client approves the proposal, then waits for a separate invoice to actually pay. That gap is where momentum dies. The faster approach is to build the payment into the proposal itself, so approving and paying the deposit is one action. That's what Tendrly does: your proposal carries a one-click Stripe payment link, so the client reads, approves, and pays in the same place — no separate invoice needed to get started.

FAQ

Is a quote legally binding?

A quote is generally an estimate, not a contract. The binding agreement is the accepted proposal (and any contract attached to it). Always state how long a quote is valid.

Do I still need invoices if my proposal collects payment?

Often you'll still issue an invoice or receipt for records and taxes, but you don't need it to collect the first payment — the proposal's payment link handles that. Many tools generate a receipt automatically.

Can one document be both a proposal and an invoice?

Effectively, yes — a proposal with a built-in payment link acts as both the pitch and the first payment request, which is why it closes faster than sending them separately.