Quote vs Estimate vs Invoice: When to Use Each

An estimate says roughly what a job will cost before you can know for sure. You send it when the scope is still uncertain — a repair where you can't see the damage yet, a project where the client hasn't fixed the requirements. An estimate of $1,200 to $1,500 tells the client the ballpark without promising the final figure.

Because it's an approximation, an estimate is generally not binding: the final bill can come in higher or lower. That flexibility is the point, but it's also why you should put your assumptions in writing — what the price covers, what would change it, and that you'll flag any significant overrun before doing the extra work. Some places have consumer rules limiting how far a final bill can drift from a written estimate for certain kinds of work, so check your local rules before treating an estimate as infinitely elastic.

A quote states a firm price for a defined scope: this work, for this amount. You send it when you know enough to commit — you've measured the site, counted the pages, scoped the deliverables. A quote of $3,000 means the client pays $3,000, not $3,400 because the job ran long.

In many countries, a quote the client accepts becomes a binding agreement at that price, so treat it as a commitment, not an opener. Protect yourself with two lines: a validity window — 'this quote is valid for 30 days' — so old prices can't be accepted after your costs move, and a precise scope so extras are visibly extras. If you charge VAT, GST, or sales tax, say whether the figure includes it; a client who accepted $3,000 and gets invoiced $3,300 will feel ambushed. Give each quote a reference number, such as QUO-014 — you'll want it on the invoice later.

If the scope changes after acceptance, don't silently absorb it or silently raise the price. Agree the variation in writing — 'add second coat, plus $250' — so the final invoice has a paper trail for every dollar above the quoted figure.

An invoice comes last: after the work is delivered, it states what's owed, by when, and how to pay. Unlike a quote or estimate, it isn't a proposal — it's the formal request that turns finished work into money owed.

The link back matters. If the job was quoted, the invoice should match the quote plus any agreed variations, and it should cite the quote number: 'As per accepted quote QUO-014.' If the job was estimated, itemize the actual hours and materials so the client can see exactly why the final figure is $1,450 rather than the $1,200 they had in mind.

A tidy job follows one sequence: estimate or quote, written acceptance, the work itself, then the invoice. In practice that looks like this: you send quote QUO-014 for $3,000, the client replies 'accepted' by email, halfway through you agree a $250 variation in writing, and on delivery you send invoice INV-058 for $3,250 referencing QUO-014.

The acceptance step is the one people skip, and it's the one that matters most. A quote nobody accepted commits the client to nothing; a quote accepted in writing anchors everything that follows. Even a one-line email reply is enough to establish that the client agreed to the price before you started.

Some jobs start with an estimate and firm it into a quote once the scope is clear — estimate a kitchen renovation at $8,000 to $10,000, survey the site, then quote $9,200 fixed. That's a perfectly good flow; just make sure the client knows which document they're holding at each stage.

Labels set expectations, and in a dispute they can set more than that. Call a document a quote and, in many places, you can be held to the figure; call it an estimate and the client can reasonably expect movement. Mislabeling cuts both ways: a rough guess titled 'Quote' can lock you into a price you never meant to fix, and a firm offer titled 'Estimate' invites the client to treat your price as negotiable after the work is done.

If a price argument ever escalates, the documents usually decide it — what was offered, what was accepted, what changed, and what was invoiced. Titling each document correctly, dating it, and numbering it is cheap insurance. And never send a quote hoping it will work as an invoice: a client's accounts team won't pay against a quote, because a quote isn't a request for payment.

Estimate: an approximation sent before the scope is certain, generally not binding, and the price may move — say so in writing. Quote: a fixed offer for a defined scope, valid for a stated window, and in many places binding once accepted, so check your local rules. Invoice: sent after delivery, requests payment, carries an invoice number and a due date, and should reference the accepted quote where there is one.