The working definitions, kept short
A quote confirms a price for work both sides already agree on. A proposal defines the deal and carries the price.
In ordinary usage, a quote is a stated price for specified work. The scope is assumed agreed; the price is the new information.
A proposal does more. Chris Do, writing on what a proposal contains for creative-services work, describes it as a packaged document carrying who you are, samples of past work, your process, and the deliverables that come next. The proposal makes the case for the work, and the price travels inside that case.
The three-question check that decides for this deal
Three questions
- 1. Has the client already agreed to the scope?
- 2. Is the price the only open question?
- 3. Can the client evaluate the number without the document making the case for it?
Three "yeses": send a quote. Any "no": send a proposal.
Has the client already agreed to the scope? Not the broad goal. The actual scope: number of pages, number of revision rounds, whether copywriting is in or out, whether you are handling photography or working from supplied assets, whether SEO migration is part of the bundle. If you could write the scope in three lines without inventing anything, the deal is quote-shaped on this dimension. If the answer is "mostly yes, but we still need to figure out X and Y," the scope is open and the deal is proposal-shaped.
Is the price the only open question? A repeat-client repeat-scope deal often gets here. The client booked the same work last year. They emailed asking for a similar project this year. They are not asking what you do or how you work. They are asking for the number. Brennan Dunn names the inverse case directly: when the scope is variable, locking both scope and price at the same moment is hard. When the scope is still in motion, a quote will hold a number while the kickoff call quietly becomes the scoping call.
Can the client evaluate the number without the document making the case? A long-time client comparing two studios for a bespoke project might accept your quote at the price you sent, then quietly compare it to the other studio's proposal, and the proposal will read more serious because it makes the case for the work. A consultant sending a $40,000 number for an engagement the client has never bought before will need that number to sit inside an argument. Consulting Success makes the operator point: a proposal in consulting work is best read as the document that summarizes and formalizes an agreement already developed in conversation. If the client has to do work to understand what they are buying, the document must do the work, not the price tag alone.
Three "yeses" means a quote is enough. Any "no" means a proposal.
When each document is the right call
| Quote | Proposal | |
|---|---|---|
| Scope | Agreed before the document is sent | Still being defined; the document helps define it |
| Price | The only open question | One of several; the document has to make the case for it |
| Document does | Records the price for work already understood | Defines the deal, names the outcome, carries the price |
| Right when | Returning client, repeated or repeatable work | New client, bespoke work, unfamiliar engagement |
A quote is right when the work is well-scoped, repeated or repeatable, and the only open question is the number. The document is short: the line item, the price, a one-paragraph confirmation of scope so both sides have it in writing, terms and validity. The job is to record the price for agreed work.
Imagine a wedding photographer sending a returning client a number for next summer's portraits. The shoot is the same as last year: half-day, fifty edited images, online gallery, two prints. The price is the only open question. A one-line quote is right. A five-page proposal would read as the photographer doubting the relationship and walking the client through the case for work they have already bought.
A quote stops earning its keep when the price is doing work the scope description cannot. Jonathan Stark, writing on fixed-price work, is direct about what makes a fixed price stable: strict boundaries on what is included and what is not. When the work is bespoke and those boundaries are still being found, the quote will hold the number, but the document is refusing to do the work the number is doing.
A proposal is right when the scope itself is in question, the work is bespoke, and the client has not decided what they are buying. Brennan Dunn puts it directly: if you propose only the technicals and the project details, you leave the client to imagine the connection between the work and their business result, and you have given the imagination too much room. The proposal closes that gap. It names the outcome the client is buying, traces the work back to that outcome, and carries the price as the recorded answer for the deal it just defined.
David Baker and Blair Enns add a related move on engagement structure: split the work into a paid diagnostic phase and a prescription phase that follows from the diagnosis. The proposal is where the phasing gets named. The same operators on giving the buyer real choices: present three legitimate ways to work together at different price points. The price is the same number; the document is doing different work.
Imagine a brand studio pitching a bespoke identity project for a new client who has never bought brand work before. The deliverables are negotiable. The client has read about identity work but does not yet know what an experienced studio considers in scope. A one-page quote saying "Brand identity, $18,000, please sign here" is wrong. A proposal that names the outcome the client is buying, walks the deliverables in plain language, and presents two or three ways to structure the engagement is what makes the price land.
Why the wrong document gets sent
The deal decides the document. The owner picked the template once, and the template has been answering for every deal since.
The first three months of business, the studio downloaded a template that said "Quote" in the header, or one that said "Proposal." Every deal that has gone out has used that template. The template has not been re-evaluated against the deal in front of them; it just keeps going.
A consultant whose template says "Proposal" sends a multi-section document for a returning client whose only open question is whether the engagement is the same size as last year. The client reads it as padded.
A brand studio whose template says "Quote" sends a one-paragraph quote for a bespoke identity project. The client signs the price because the price was acceptable. The kickoff call becomes the scoping call, because the document never defined the scope.
Two ways the default goes wrong
Proposal template on a quote-shaped deal. The returning client reads context for work they already agreed to. The document signals doubt where none is needed.
Quote template on a proposal-shaped deal. The price lands without the case for it. The kickoff call becomes the scoping call, because the document never defined the scope.
There is a quote-side instinct worth defending. Pricing the job by listing tasks and the time required to complete them, as Chris Do defines it, is the quote-shaped logic of fixed pricing: knowable tasks, known time, knowable price. That logic works where the task list is genuinely knowable. It fails when it gets pointed at work whose task list is not yet known. The number on the page might be correct; the document is still wrong, because it does not record what the tasks are.
The word in the header (whether it says "Quote" or "Proposal") records a decision about the deal shape, not a property inherited from a template downloaded in year one. The fix sits upstream of any writing or pricing change: re-decide the deal shape on each deal, before reaching for the template.
What ProposalKit.io ships for the acceptance moment, quote or proposal
The product does not pick the document for you. The same editor produces a tight one-page quote or a multi-section proposal, and the same branded client link carries either. When the client accepts, ProposalKit captures a typed signature, the signer's email and title, and a locked snapshot of the document at the moment of acceptance. The signed PDF accounting expects is exported on demand, with a signature page and an audit appendix attached.
The pricing decision is a separate problem, covered in our guide on how to price a creative project proposal. For the writing side, our guide on how to write a business proposal covers composition once the deal is proposal-shaped. The category this tool sits inside is covered in our guide on online proposal software; for agency-shaped operators, our guide on proposal software for agencies walks the same evaluation through an agency lens.