Pricing documents, defined
Estimate, quote, bid, proposal.
Four words, four levels of promise.
An estimate approximates a price, a quote commits to one, a bid competes on one, and a proposal argues for one. They are four different levels of promise — and sending the wrong level costs you jobs, margin, or both. Here is what each document is, what it commits you to, and which one to send when.
A Chalmsy guide · 10-minute read · Last reviewed 17 August 2026
What is the difference between an estimate, a quote, a bid, and a proposal?
All four put a number in front of a client before the work starts. The difference is what stands behind the number.
- An estimate approximates — it says "the job will land somewhere near here," based on what you can see today. It is a professional opinion, not a commitment.
- A quote commits — it says "this exact scope costs this exact price," and once the client accepts it inside its validity window, you are expected to hold it.
- A bid competes — it is a quote submitted against other people's quotes, usually for a scope the buyer defined, where the number is doing most of the talking.
- A proposal argues — it carries a price, but it spends most of its pages making the case for the approach, the scope, and you.
The words get used interchangeably on job sites and in inboxes, and mostly nobody dies. But the document you choose sets the client's expectations about how firm the number is — and courts, when things go wrong, tend to care about what the document actually promised. So it is worth being deliberate.
What is an estimate?
An estimate is an educated approximation of what a job will cost, given before the full scope can be known. It exists because some work cannot be priced until you are inside it.
Take a plumber called out for a leak somewhere under the kitchen floor. Until the floor comes up, nobody knows whether it is a pinhole in one accessible pipe or a corroded run that all needs replacing — two jobs whose costs are not in the same neighborhood. The plumber can honestly give a range and promise to confirm once the floor is open, and that range is genuinely useful to the homeowner. What the plumber cannot honestly do is name a single firm number for work nobody has seen.
What an estimate commits you to is good faith, not the figure. You are expected to have estimated competently, and to say something the moment reality starts diverging — a job that comes in at three times its estimate with no phone call in between is how you end up in small-claims court, or at least off the referral list. But the number itself is understood by everyone, including most courts, to be an approximation.
Send an estimate when the scope is genuinely unsettled: diagnostic work, early-stage conversations, "roughly what would something like this run?" inquiries. And label it. The word "estimate" on the document is doing legal and relational work — don't let a range travel in an email that reads like a promise.
What is a quote?
A quote is a fixed price for a defined scope, valid for a stated window. Accept it in time and that is the price — no "it ran long," no "materials went up."
Picture a florist quoting a wedding. The scope is knowable in advance — a bridal bouquet, six bridesmaids' bouquets, twenty centerpieces, an arch installation — so she can itemize it, price each line from her own stem costs and markups, and put a total on it. She will also date-limit it, typically 14 to 30 days, because wholesale flower prices move and because a quote for a specific Saturday cannot sit open forever while the date gets booked by someone else.
What a quote commits you to is the price itself, for the scope as written, within the window. That has two practical consequences:
- The scope description is load-bearing — everything the price covers should be in it, and anything it doesn't cover ("delivery beyond 20 miles," "candles not included") should be excluded in writing. A vague quote is a fixed price for an argument.
- Changes need a new document — when the client adds ten centerpieces, that is a revised quote or a change order, not a bigger invoice at the end. The original stays what it was; the revision replaces it.
Send a quote when you know exactly what the job is and can price it firmly. Which, for most custom-work businesses, is most of the time.
What is a bid?
A bid is a quote submitted in competition. The buyer — a property owner, a developer, a procurement office — defines the scope, sends it to several firms, and compares the numbers that come back.
Consider a general contractor bidding a commercial fit-out. The owner's architect has issued plans and a spec; three GCs each take off quantities, price the work from their subs and their own labor, and submit by the deadline. Because the scope was defined by the buyer, the documents are directly comparable — which is exactly the point, and exactly the pressure. In a pure bid situation, the low number usually wins unless someone gives the buyer a reason to look past price.
What a bid commits you to depends on the process. In private work it usually behaves like a quote: accepted bid, agreed price. In public and formal tenders the commitment is harder — sealed bids often cannot be withdrawn or corrected after opening, and some require bid bonds. Read the instructions to bidders before you price a thing.
Two rules for bidding well:
- Qualify what you're pricing — where the drawings are ambiguous, state your assumption in the bid. Silence means you have absorbed the risk.
- Give the buyer a reason beyond the number — the bids that win at second-lowest price come with a page that reads like a proposal. Our guide to writing a construction proposal covers how to build that page.
What is a proposal?
A proposal is the persuasive document. It carries a price, but the price is the conclusion, not the content — most of a proposal is spent defining the client's problem, describing your approach, and making the case that you are the right firm to do it.
Think of a consultant responding to "our order fulfillment is a mess and we don't know why." There is no spec to price against. The proposal has to construct the scope itself: here is what I understand the problem to be, here is the diagnostic phase, here are the deliverables, here is the timeline, here is who does what, and here — finally — is the fee. The scope section of that document matters so much it often becomes its own attachment; we have written separately about how to write a statement of work that actually protects you.
What a proposal commits you to is everything in it: the approach, the deliverables, the assumptions, and the price. Once signed, it typically is the agreement, or gets incorporated into one — which is why the boilerplate sections (payment terms, revision limits, what happens when the client is late with inputs) deserve as much attention as the pitch.
Send a proposal when the client is choosing whether to do the project at all, when you are defining the scope rather than pricing someone else's, or when the decision will be made on more than price. In consulting and creative work, that is nearly always.
Which one should you send?
Three questions decide it:
- How settled is the scope? — Unknowable until you open the wall: estimate. Defined and priceable: quote. Defined by the buyer and sent to your competitors too: bid.
- How competitive is the situation? — If the client is comparing numbers side by side, you are bidding whether the paperwork says so or not, and your document needs to survive comparison: tight scope, clear exclusions, and one reason to pick you that isn't the price.
- How much does the client need persuading? — If they have already decided to buy and are choosing a vendor, a clean quote may be all they want. If they are still deciding whether the project should happen, whether it is worth the money, or whether they trust you — that is a proposal.
In practice, the document that wins custom work is usually a hybrid: a proposal wrapped around a quote. The itemized, committed price of a quote — because serious clients deserve a real number — inside the framing of a proposal: what we understood you to want, how we will approach it, why us, what happens next. A florist's wedding "quote" with a paragraph on the design direction, a builder's "bid" with a page on sequencing and site management — both are really this hybrid. Businesses that price custom trade work well tend to converge on it without being told: the number earns the trust, the argument earns the job.
Is an estimate or a quote legally binding?
The general shape — and it is only the general shape; ask your attorney what applies in your state and industry:
- An estimate is generally not binding as to price — it is an opinion, and courts mostly treat it as one. But "generally" is carrying weight: some states regulate estimates in specific industries (auto repair is the classic case), a grossly careless estimate can still create liability, and an "estimate" the client reasonably read as a firm offer may be enforced as one. Label it, keep it honest, communicate when it moves.
- A quote generally holds once accepted — inside its validity window, a quote is usually an offer; the client's acceptance can form a contract at that price. This is why the window matters: an undated quote is an open offer with no expiry.
- Anything signed is an agreement — a signed proposal, a countersigned quote, an accepted bid with an award letter: at that point you are not arguing about labels, you are reading a contract. Electronic signatures carry the same weight as ink for most business documents under the federal ESIGN Act and state UETA laws.
The practical takeaway is not legal at all: write every document as if it will be read aloud in a dispute two years from now, by someone who was not in the room. Scope in, exclusions out, validity dated, assumptions stated.
Where the software comes in
Whichever one you send, the work around it is the same
Chalmsy doesn't much care what you call the document — it is built for the work around it. Paste the inquiry, the email thread, or the RFP, and it drafts the response in your own voice, learned from proposals you have actually written, not template-speak. It prices only from your own rates, materials and multipliers; any figure you enter by hand is locked, and the AI cannot alter it. Nothing sends until you have read and approved it, and it goes out from your own Gmail address, not ours.
After the send, the distinctions in this guide stop being academic. The client comments on the exact line they want changed, signs with email-code identity verification, and when the scope moves, the revision becomes version 2 of the signed document — the original stays locked, so there is never an argument about what was agreed when. An accepted proposal becomes deposit, stage and balance invoices — each its own invoice with its own due date, and each stage raised from the approved version in one click. What Chalmsy does not do: takeoffs, cost databases, or inventing numbers. The price is yours; Chalmsy makes the argument around it — and everything after it — light work. See how on the proposal side of Chalmsy.
Asked and answered
The questions that come up.
Is a quote legally binding?
Generally, a quote is an offer: once the client accepts it within its validity window, a contract can form at that price, and you are expected to honor it. An unaccepted or expired quote binds nobody. The specifics vary by state and situation, so ask your attorney if real money turns on it.
Can I change my price after giving an estimate?
Yes — that is the point of an estimate. It is an approximation, not a commitment, and the final price can differ. The professional (and self-protective) move is to flag the change as soon as you see it coming, before doing the extra work, and get the client's agreement in writing. Springing a much larger invoice at the end is how estimates turn into disputes.
How long should a quote be valid?
Long enough for the client to decide, short enough that your costs cannot move underneath it. Fourteen to thirty days is the common range for trades and creative work; businesses exposed to volatile material prices go shorter. Whatever you choose, date it — an undated quote is an open offer with no expiry.
When should I send a proposal instead of a quote?
When the client is deciding whether to do the project at all, when you are defining the scope rather than pricing a spec someone else wrote, or when the decision will be made on more than price. If they just need your number for a job everyone already understands, a quote is faster and reads more confident.
What is the difference between a bid and a quote?
Mostly the structure of the situation. A quote is a fixed price you give a client directly; a bid is a quote submitted in competition, usually against a scope the buyer defined, alongside other firms' numbers. Formal bids can also carry stricter rules — sealed submission, no withdrawal after opening — that ordinary quotes do not.
Is an invoice the same as a quote?
No. A quote comes before the work and says what it will cost; an invoice comes after the work, or at agreed stages, and requests payment for it. In a well-run process the invoice is born from the accepted quote — same line items, same figures — which is exactly how Chalmsy raises deposit, stage and balance invoices from the signed version of a proposal.
Stay calmsy
Whatever you call it, send it today.
Start free, paste the inquiry, and send the right document while the client is still deciding.