Proposal vs quote: what's the difference?

A proposal sells the approach, why you, why this method, what the client gets. A quote states the scope and price for agreed work. In practice, most small studios use one document that does both jobs, and the words get used interchangeably.

What it means in practice

Where teams do draw a line, a proposal usually leads with narrative: the problem as you understand it, your approach, relevant experience, sometimes case studies. A quote is closer to a priced scope of work, sections, deliverables, a total, with less selling and more specifying. Regional habit matters too: "quote" is more common in the UK trades and web/agency world, "proposal" more common in US sales and consulting contexts, for broadly the same document.

The risk with a heavily "proposal" style document is that the narrative crowds out the specifics, so nobody can point to exactly what was included once the sale is made. A quote built from structured sections keeps the persuasive framing thin and the scope precise, useful either way, since delivery only ever works from the specifics.

Example

An agency sends a client a short cover page (the "why us"), followed by priced, itemised sections for design, build and launch checks, proposal framing on the outside, quote precision underneath.