Quote vs estimate vs invoice: what's the difference?

An estimate is your best guess at what a job will cost. It's a rough number, given early, and it can change as the work takes shape.

A quote is a firm price you commit to. Once the client accepts it, both sides are agreeing to that figure for the work described.

An invoice is the bill. You send it after the work is done (or at agreed milestones) to ask for payment for what was actually delivered.

Think of it as a timeline: estimate first, when details are fuzzy; quote next, once you can pin down the scope; invoice last, when it's time to get paid. Not every job uses all three. A simple, predictable job might skip straight to a quote, or even straight to an invoice.

An estimate is an approximate cost you give a client before the details are fully nailed down. It signals roughly what to expect so they can decide whether to keep talking. Builders, mechanics, designers, and consultants lean on estimates because the real cost depends on things nobody knows yet: how much prep a wall needs, what's actually wrong with the engine, how many rounds of revisions a logo takes.

An estimate is generally not a binding promise. Because it's explicitly a projection, the final cost can come in higher or lower. That flexibility is the point, but it's also the risk: if a client treats your estimate as a fixed price, you have a problem.

Protect yourself by labeling it clearly as an estimate, noting what it's based on, and saying that the final figure may change if the scope or conditions do. The more variables in a job, the more an estimate (rather than a quote) is the honest choice.

A quote is a fixed price for a clearly defined piece of work. When you issue a quote and the client accepts it, you're both agreeing to that amount for that scope. In practice, an accepted quote often functions as a contract, so you're expected to honor the price even if the job turns out harder than you thought.

That's exactly why a quote demands a tighter scope than an estimate. Before you commit to a number, spell out what's included, what isn't, and any assumptions you're relying on. Vague scope is how a profitable quote becomes a money-losing one.

Give a quote a validity period, like 'valid for 30 days.' Your costs (materials, your own time, subcontractors) can move, and an open-ended quote leaves you exposed to accepting old pricing months later. If the client asks for more than the quote covered, that's new work — issue a change or a fresh quote rather than absorbing it.

An invoice is a formal request for payment for work you've delivered or goods you've supplied. It comes at the end of the cycle — after a quote is accepted and the work is done, or at agreed stages along the way. Unlike an estimate or quote, an invoice creates an actual obligation to pay.

A usable invoice includes a unique invoice number, the issue date, a payment due date, your business details and the client's, a line-by-line breakdown of what's being charged, any tax, and the total owed. It should also state how to pay and the terms (for example, 'Net 14' meaning payment is due within 14 days).

Invoice numbers matter more than people expect. They should be unique and sequential so every invoice can be traced for your records and for tax purposes. Reusing or skipping numbers makes your bookkeeping messy and can raise questions in an audit. Many tools generate these numbers automatically so you never collide or skip one.

These documents are stages of one relationship, not isolated paperwork. A typical sales flow looks like this: a client asks what something will cost; you send an estimate to set expectations; once the scope firms up, you send a quote with a committed price; the client accepts; you do the work; you send an invoice; the client pays.

A huge practical win is that each document feeds the next. The line items and scope in your quote should carry straight into the invoice, so you're not retyping anything or introducing errors. If you quoted three deliverables at set prices, those same lines become the invoice when the work is done. This is exactly where 'quote-to-invoice conversion' earns its keep: one accepted quote becomes a draft invoice in a click, with the numbers already matching.

Keeping this chain tight also keeps you honest with clients. When the invoice mirrors the quote they accepted, there are no surprises — and far fewer payment disputes.

Choose based on how certain you are about the work and where you are in the conversation.

Send an estimate when the client is still exploring and the scope is genuinely unclear — you want to give a useful ballpark without locking yourself into a number you can't yet stand behind. Send a quote when you can define the work precisely and you're ready to commit to a price; this is your move once discovery is done and you want a clear yes. Send an invoice only when there's an agreed basis to charge — completed work, a delivered product, or a milestone you both signed off on.

A few rules of thumb keep you out of trouble: never let a casual estimate get treated as a firm price; never quote a number before you understand the scope; and never invoice for work or amounts you haven't actually agreed. When in doubt, slow down one step — a clear quote up front prevents an awkward invoice argument later.

The most expensive mistake is blurring an estimate and a quote. If a client believes your ballpark is a fixed price, you either eat the difference or have a fight on your hands. Label each document for what it is and say plainly whether the number can move.

The second is quoting without locking scope. A quote with fuzzy boundaries invites scope creep, and because the quote is binding, every extra request comes out of your margin. Write down what's included and what counts as new work.

Other frequent slip-ups: forgetting an expiry on quotes (so stale pricing comes back to bite you), inconsistent or duplicated invoice numbers (a bookkeeping and tax headache), and missing payment terms (which is the fastest route to getting paid late). Finally, don't make clients chase the document — the longer the gap between accepting a quote and receiving the invoice, the slower you get paid.

Once you're sending these regularly, the manual version gets old fast: rewriting line items, hand-numbering invoices, chasing overdue payments, and hoping the invoice still matches what you quoted.

This is where dedicated invoicing software helps. Platybooks is built around exactly this flow — create a quote with a live PDF preview, let the client accept it, and convert it to an invoice (or auto-convert on acceptance) so the numbers carry over with no retyping. Invoice numbers are generated automatically and gaplessly per business, hosted payment links let clients pay in a couple of clicks with the status updating itself, and overdue reminders go out on their own at +3, +7, and +14 days.

The free plan covers a few documents a month with no credit card, which is enough to get the rhythm down. Whatever tool you use, the principle holds: keep estimates honest, quotes tightly scoped, and invoices matched to what was agreed — and the money tends to follow.