Quote vs proposal, and what the number commits you to.

A quote is a price for work both sides can already describe, and a proposal is an argument for why you should be the one doing work nobody has fully described yet. The quote is short and itemized and meant to be accepted as it stands. The proposal explains the approach, carries a fee somewhere inside it, and expects a conversation first. Most agencies pick between the two in about four seconds and never lose a night over it, which is fair, because the choice itself rarely costs anything. Sending a quote that names a price without naming what the price counts is the part that costs you.

That shows up on a specific day rather than in the abstract, usually around week three, when a client asks for something reasonable that the number was never sized for and nobody can say whether it's included. What follows is one five-week project priced both ways, the lines that decide which version of that conversation you get, and the arithmetic on the request when it lands.

What's the difference between a quote and a proposal?

A quote answers "how much" and a proposal answers "why you", which is why the two fail in completely different ways. The quote is a list of countable items with money attached, sent to someone who already knows what they want and is deciding whether they can afford it from you. The proposal goes to someone who hasn't decided what they want or who they want it from, so it has to think out loud before it earns the right to name a number.

That difference in reader changes the whole document. A quote of six lines and a total is a good quote, because the client is comparing it against two others and anything longer gets skimmed, while a proposal of six lines and a total answers none of the questions that made them ask three agencies in the first place. Length isn't the variable that matters though, and precision runs the other way from what most people expect.

The proposal is allowed to be vague, since it describes work that hasn't been specified yet and everyone knows it. The quote isn't, because a quote is an offer, and an offer with soft edges is an offer whose edges the client gets to decide later. This is the same tension that sits between a statement of work and a proposal, except that a quote skips the persuasion and goes straight to the number, which strips out the part of a proposal that usually explains what the number covers.

Should you send a quote or a proposal?

Send a quote when you could write the line items today without asking another question, and a proposal when the price depends on decisions the client hasn't made. That's a sharper test than deal size, and it's the one that predicts trouble.

Try it on a brief before pricing anything. If two people at your agency produce different item lists from it, the job isn't quotable yet, and quoting it means committing to whichever reading is cheaper. A client who sends a product list, a location and a delivery date has already handed you the line items, and pricing that takes about twenty minutes. A client who asks for "launch content" hasn't handed you anything, because six images and sixty images are both launch content and most of the fee sits in the gap between them.

The shortcut most agencies use instead is price: big job gets a proposal, small job gets a quote. That mostly holds, since bigger jobs do arrive less specified, but it fails in both directions and both failures cost you. A $40,000 retainer for a client whose monthly work you've run for two years should go out as a quote, and proposing it wastes a week. A $3,000 logo for a founder who can't yet describe the company needs the proposal, and quoting it puts you on round nine of a design nobody can approve because the brief never existed.

What does the same project look like as a quote and as a proposal?

It looks like the same five weeks of work described once in a paragraph and once in five priced lines. Here's a product photography and launch content package for an outdoor gear brand, written first the way it appeared in the proposal that won the job and then the way it appeared on the pricing page of the same document.

Page 3 and page 7 describe the same five weeks and only one of them can be held to. The arithmetic on page 7 is visible on purpose, since $4,500 across 60 images is $75 an image and a client can do that division as fast as you can. Hiding the per-unit rate doesn't make the total easier to accept, it just means the rate gets invented under pressure the first time somebody asks for image 61.

A quote without counts is a price for whatever the client turns out to have meant.

Page 7 gives every number a unit, prices the three likeliest ways the job grows, dates itself and says how a change gets made. That's four ideas in six lines, and none of them slow down a client who's ready to say yes.

Is a quote binding once the client accepts it?

An accepted quote usually carries real weight, how much depends on your state and on what the document says, and the safe assumption is that you're on the hook for it. That's about as far as a useful answer goes, and the confident versions you'll find in both directions are mostly people flattening a question that stays murky no matter how firmly it gets answered.

The version you can act on this week doesn't depend on the answer at all, because whatever an acceptance binds you to is the text you wrote, and that holds whether the binding turns out to be strong or weak. A quote listing five one-line items binds you to five one-line items, which is exactly the problem, since "retouching" with no number next to it means whatever the person paying decides it means once the shoot is over. Precision is the half of this you control, it takes the same six lines either way, and it works on the client who'd never dream of suing anyone but does think 90 retouched images sounds like a fair reading of the word.

What four lines turn a quote into a boundary?

Counts, priced exclusions, an expiry date and a change route, which together take about six lines and turn a number into something you can point at. Most quote templates carry none of the four, so building your quote from one still leaves you holding a price with soft edges.

Counts come first because nothing else works without them. Every line gets a unit and a rate, so "retouching" becomes "60 selected images at $75 each" and the client learns the price of the 61st image at the same moment they learn the price of the first 60. Priced exclusions come second, and the trick is to price the three growths you can already predict rather than listing everything the job isn't. On a shoot those are an extra day, an extra image and an extra cutdown, which covers most of what actually happens, and it's the same discipline as putting a number next to everything you've excluded compressed into one line.

The expiry date is the cheapest of the four and the most often skipped. Thirty days is the convention, and putting it in the document rather than the covering email is what makes it work, since a quote with no expiry is a standing offer and clients really do come back in October holding a number you priced in February. The change route is the fourth, and one sentence does it: accepted scope changes only in writing, priced before the work starts. That's what turns a mid-project request into a transaction rather than a negotiation, and it's why a standing change request form is worth keeping in the template folder.

What happens when the work outgrows the number you quoted?

Either it becomes a two-line message or it becomes an argument, and which one you get was decided when you wrote the quote rather than when the request arrived. This is the part of the whole quote-versus-proposal question that turns up on a bank statement, and it's the part nobody is thinking about at the moment they choose which document to send.

Halden & Pike's new colorway arrives late from the factory in week three, after both shoot days are done. They want it photographed, which means a third shoot day, and they want the twenty extra shots retouched to match the set. Under page 7 that's $2,500 for the day plus 20 images at $75, so $4,000, or just over 29% of the original fee. The message writes itself: the accepted scope covers two shoot days and 60 retouched images, the third day is $2,500 and the extra 20 images are $1,500, please confirm the $4,000 and we'll book the studio for the 14th.

Nobody has to be persuaded of anything there, because the client agreed to both rates in February and is being shown a multiplication. Under page 3 the same request is a different conversation. "Studio product photography" doesn't say how many days, "lifestyle imagery" doesn't say how many images, and the agency is introducing limits that appear nowhere in writing at the exact moment those limits cost the client $4,000. You'll probably eat some of it, and agencies in the same position every month mostly eat all of it.

Notice that the $4,000 isn't a scope creep story at all, since the request is reasonable, the extra work is real, and both sides would agree it should be paid for. The only variable is whether the document made that agreement cheap to reach.

Does the proposal still matter once the quote is accepted?

It matters more than agencies expect, because the client read it more carefully than anything you sent afterwards and its friendliest sentence is the one they'll quote back at you. Page 3 doesn't stop existing when page 7 gets accepted. It sits in the same file saying "a full launch content package", and in week three that phrase is working against you.

Two lines fix it, both belonging in the template rather than in a per-project negotiation. One goes in the proposal, saying the approach section describes intent while the pricing page defines the scope and the terms. The other goes on the pricing page, saying that where the two conflict the pricing page applies. That's the small version of the ranking problem that decides which document governs once a proposal and a contract are both signed, and none of it argues for a colder proposal: keep the argument warm on the pages that win the job, do the counting on one page, and say which one wins.

Where the $4,000 actually came from

It came from six lines on page 7, written in twenty minutes in February, and specifically from the four words "60 selected images at". Without them, week three is an argument about what "retouching" reasonably includes with someone about to spend $4,000 they hadn't budgeted. With them, it's a multiplication both sides already agreed to.

That's the difference between a quote and a proposal you actually feel, and it has nothing to do with which one is longer or which one sells. A proposal costs you a week of writing whether or not you win, while a quote costs nothing to write and everything you failed to count, which is why the shorter document is the one that needs the discipline. The five minutes spent turning "retouching" into "60 selected images at $75 each" pays out exactly once, on the day something changes, and it pays for the whole habit.

Docket handles the part after that. The third shoot day, the $4,000, the rate it was priced against and the written yes from the person allowed to give it land on one record attached to the project, so in June there's a single place showing what was asked, what it cost and who approved it. The counting still has to happen in the quote, and on larger jobs it comes from a scope of work clients can't misread.

Frequently asked questions