Is a quote legally binding?

Once a client accepts it, yes, in the sense that it functions as an agreed price for a defined scope, much like accepting an offer. If the actual work matches what was scoped, you're expected to honor the quoted price even if it takes longer or costs you more than planned. If the client changes the scope after accepting, you're entitled to revise the price for the new work.

Can I turn an estimate into an invoice later?

Not directly. An estimate isn't a billing document. What you can do is use an estimate to set expectations, do the work, and then send an invoice based on what was actually delivered. If the final number differs from the estimate, it's worth a quick note on the invoice or in your message explaining why, rather than letting the client discover the difference on their own.

What happens if the actual work costs more than my estimate?

That's expected. An estimate isn't a promise, so a reasonable variance from the original figure isn't a breach of anything. The risk is a client who assumed the estimate was fixed. If costs are climbing significantly beyond the estimate, flag it before you finish the work, not on the final invoice, so the client isn't surprised by the total.

Do I need a separate quote before every project?

Only when the scope is knowable upfront and the client needs price certainty. For ongoing clients with a stable, well-understood arrangement, or for small jobs where a quick estimate is enough to get a go-ahead, a formal quote for every single engagement is often unnecessary overhead. Use a quote when precision matters and skip it when a quick estimate does the job.

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

By the Billebly team · Published 13 May 2026 · Last updated 22 August 2026

A lot of billing disputes trace back to one mix-up: someone sent a rough number and the client treated it as a fixed price, or someone sent a fixed price and later tried to move it like a rough number. Quote vs estimate vs invoice isn't a paperwork technicality: each one commits you to something different. Use the wrong one, and you're not just filling in the wrong template. You're setting an expectation you can't walk back without an awkward conversation.

What a quote actually is

A quote is a fixed price. You're telling the client: for this defined scope of work, the total is €X, and that number won't change unless the scope does. Once accepted (in writing, by email, or by signing off), it functions as an agreed offer, which is why quotes work best when you already know exactly what the job involves: a website build with a fixed page count, a fixed number of coaching sessions, a defined deliverable with clear boundaries.

The binding nature of a quote is the whole point. It protects the client from a number that creeps upward mid-project, and it protects you from being asked to do "just one more small thing" for free. If the job takes longer than expected, you still honor the price, which is why quotes should only go out once you've scoped the work properly, not as a placeholder sent early to keep a conversation moving.

What an estimate actually is

An estimate is a rough figure, not a commitment. You're telling the client: based on what I know right now, expect to pay around this amount, but the scope isn't locked down, so the number could move. Estimates fit situations where you can't price the work precisely upfront: a website rebuild where nobody's decided on page count, a consulting engagement where the first few sessions determine the workload, a renovation-style project where unknowns surface once you're inside it.

The value of an estimate is honesty, not precision. A client who gets a rough range and ends up paying close to it trusts you more than one who got a "fixed" quote that quietly grew by 40%. But estimates only work if you actually tell the client it's an estimate. Hand over a bare number, and most people will hear "price," not "rough guess."

Say the word out loud

If a figure could move, say "estimate" and give a range, not a single number. A single number reads as a commitment even if you didn't mean it that way. "Around €2,000 to €2,500" reads as exactly what it is.

What an invoice actually is

An invoice is neither of the above. It's a request for payment. It shows up after a quote or estimate has already done its job, once work is delivered or about to be delivered on agreed terms. It isn't negotiable like an estimate or a proposal like a quote. It's the bill for work both sides already agreed would happen, which means the pricing conversation should already be over.

This is also where freelancers get the sequence backwards: sending an invoice before any quote or estimate, then dealing with a client surprised by the number because nothing set expectations beforehand. For the exact fields and wording that keep an invoice from causing confusion once it's the right document to send, see how to write an invoice clients pay on time.

Comparing the three directly

Document	Purpose	Binding?	When to send
Quote	A fixed price for defined work	Yes, once accepted	Before work starts, when scope is fully known
Estimate	A rough expected cost	No	Before work starts, when scope is still uncertain
Invoice	A request for payment	Yes, per agreed terms	After work is delivered, or per agreed milestones

The "binding" row is where most disputes start. A client given an estimate but remembering it as a quote will push back hard when the final number comes in higher, not because they're being difficult, but because to them, a number is a number unless you said otherwise.

How the wrong document causes disputes

The most common failure isn't picking the wrong price. It's picking the wrong document type for how certain you actually were about the scope. Send a quote when you should have sent an estimate, and you've locked yourself into a number you'll either eat the loss on or try to revise through an uncomfortable scope-creep conversation. Send an estimate when the client needed a quote (say, a fixed-budget client who needs sign-off from someone else) and they can't commit to your rough number because their approval process needs a fixed figure.

The scope-creep argument specifically comes from treating an estimate as if it were a quote. The client remembers "you said around €1,500," you deliver extra revisions because the scope shifted, and the final number lands at €2,200. If you never framed the original number as an estimate (clearly, in writing), the client has every reason to feel blindsided, even though nothing you did was technically wrong. The fix isn't a better estimate. It's being explicit about which document you sent and what it does and doesn't promise.

Turn an accepted quote into an invoice in minutes

Once the scope is locked and the work is done, generate a clean, professional invoice with the right details. Free, no account needed.

Try the free invoice generator

Choosing the right one for your situation

Run through this before you send anything:

Do you know the full scope right now? If yes, and you're comfortable locking in a price, send a quote. If the scope could still shift (revisions aren't capped, hours aren't fixed, requirements aren't final), send an estimate instead.
Does the client need a number for their own approval process? Some clients, especially at larger companies, need a fixed figure to get internal sign-off. If that's the case, push to firm up scope early so you can give them a quote rather than a number that might change later.
Has work already happened, or is a milestone due? That's an invoice, full stop: not a revised estimate, not a "final quote."
Are you working with a new client where scope tends to shift once work starts? Lean toward an estimate even if you think you know the scope. It's easier to convert an estimate into a quote once details firm up than to walk back a quote you already committed to.

Getting this right at the start of a client relationship matters more than it seems. A client onboarding checklist is worth building specifically so scope questions (and therefore the quote-vs-estimate decision) get settled before any number goes out.

It's also worth deciding upfront whether you're collecting a deposit, regardless of which document goes out first. A quote or an accepted estimate is a natural point to request one, and structuring deposits and upfront payments covers how much to ask for and how to word it so it doesn't read as a lack of trust. Once you're ready to bill, a freelance invoice template keeps the final step consistent whether the number started as a quote or an estimate.

Frequently asked questions

: Once a client accepts it, yes, in the sense that it functions as an agreed price for a defined scope, much like accepting an offer. If the actual work matches what was scoped, you're expected to honor the quoted price even if it takes longer or costs you more than planned. If the client changes the scope after accepting, you're entitled to revise the price for the new work.
: Not directly. An estimate isn't a billing document. What you can do is use an estimate to set expectations, do the work, and then send an invoice based on what was actually delivered. If the final number differs from the estimate, it's worth a quick note on the invoice or in your message explaining why, rather than letting the client discover the difference on their own.
: That's expected. An estimate isn't a promise, so a reasonable variance from the original figure isn't a breach of anything. The risk is a client who assumed the estimate was fixed. If costs are climbing significantly beyond the estimate, flag it before you finish the work, not on the final invoice, so the client isn't surprised by the total.
: Only when the scope is knowable upfront and the client needs price certainty. For ongoing clients with a stable, well-understood arrangement, or for small jobs where a quick estimate is enough to get a go-ahead, a formal quote for every single engagement is often unnecessary overhead. Use a quote when precision matters and skip it when a quick estimate does the job.