Proposal vs quote vs estimate vs SOW

The one-line version

• Estimate, an approximate, non-binding indication of cost. "Roughly £18k–£24k."
• Quote, a firm price for defined work, which you're expected to honour. "£21,500 for this

scope."

• Proposal, a persuasive document that explains the work and why you, usually containing a

quote. "Here's your problem, our approach, the scope, and the price."

• Scope of work (SOW), the binding definition of exactly what will be delivered, how and when,

with terms. The document delivery builds from.

They form a rough sequence, indicate, persuade, commit, define, and in small projects they frequently collapse into a single document.

Estimate: approximate, non-binding

An estimate is your honest best guess before the scope is firm. It exists to give the client a sense of scale early, a range is the usual form, without committing you to a number you can't yet defend. The key word is non-binding: an estimate says "in this region", not "at this price". Label it clearly as an estimate so nobody treats it as a quote later.

Quote: firm and expected to hold

A quote is a commitment. Once a client accepts it, you're expected to deliver the defined work at that price, so a quote is only safe on a scope you can stand behind. This is why quoting and scoping can't be separated, see how to price a website. A quote should name what the price covers and, ideally, what it doesn't, so "firm" doesn't quietly mean "firm plus everything they later assume".

Proposal: the persuasive wrapper

A proposal is the document you send to win the work. It contains a quote, but it does more: it restates the client's problem, explains your approach, defines the scope, and makes saying yes easy. Where a bare quote answers "how much?", a proposal answers "why you, and what exactly?". For its structure, see sections every web design proposal needs. Most web design work is sold on a proposal, not a bare quote, because the buying decision is about trust as much as price.

Scope of work: the binding definition

The SOW is the document that defines exactly what will be built, to what standard, by when, and under what terms, including revision limits, change control and acceptance. It's the one that has to survive the sale and become the reference your team delivers from. A proposal persuades; the SOW governs. See how to write a scope of work, and note that "SOW" is also used for statement of work, we untangle that here.

How binding is each one?

Which do you actually send?

For most web projects the honest answer is: a proposal that contains the quote and the scope, all signed as one document. The estimate is what you say on the first call; the proposal is what you send to win; the scope of work is the binding core inside it that delivery builds from. Splitting them into four separate documents is usually overkill for a studio, the value is having all four jobs covered, not four files.

This is where keeping everything on one live document pays off. In ScopeDeck the same Scope carries from the client-facing quote through to the specification and the delivery tasks, so the persuasive proposal, the firm quote and the binding scope aren't three things to keep in sync. They're one document at different stages.