Proposal vs quote vs estimate: which one to send and when

An estimate is an approximate price used early to check whether a budget fits. A quote is a fixed price for a clearly defined job. A proposal is a persuasive document that combines scope, timeline, price and terms, and asks the client to approve the project. For most website work you will send an estimate first and a proposal second; a bare quote is only right when the work is small and fully specified.

Using the wrong document is a common source of disputes. This article explains each one, when to use it, and how they fit together on a typical web project.

The estimate: a range to test the budget

An estimate answers one question: is this project roughly affordable? It is based on limited information and should be presented as a range, such as "between $6,000 and $9,000 depending on the number of templates and whether you need e-commerce".

Send an estimate when a lead asks "how much does a website cost?" before you have had a discovery call, or when the client is comparing options internally. Keep it short: the range, the two or three factors that move the price, and an invitation to talk.

The main risk is that clients remember the lowest number. Always write the range and the assumptions, and say clearly that it is not a fixed price. Never present a single figure as an estimate; it will be treated as a quote.

The quote: a fixed price for defined work

A quote is a commitment. If the client accepts it, you deliver the described work for that price. Quotes work well for small, repeatable jobs where the scope is obvious: installing an SSL certificate, adding a page to an existing site, a fixed monthly maintenance plan.

A good quote lists the work, the price, what is included, how long the price is valid and the payment terms. It does not need to persuade, because the client has usually decided they want the work and is checking the price.

The risk with quotes is using them for work that is not fully defined. If you quote a fixed price for "a new website" without a clear scope, every unclear point becomes an argument about whether it was included.

The proposal: scope, price and a reason to say yes

A proposal includes everything in a quote, plus the context the client needs to approve a larger decision: their goal in their own words, your approach, a phased timeline, deliverables, assumptions, optional add-ons and a clear acceptance step.

Send a proposal for any project where the client is choosing between providers or approaches, where the budget needs internal approval, or where the scope has several parts. For freelancers and agencies that build websites, that is almost every new project.

A proposal is not longer for the sake of it. Two or three screens are enough. Its job is to make the decision easy, not to impress. See how to write a website proposal that gets approved for the process.

How they fit together on a web project

A typical sequence looks like this:

1. A lead asks about pricing. You reply with an estimate range and suggest a call.
2. On the discovery call you confirm the goal, scope and budget.
3. Within 48 hours you send a proposal with a fixed base price and optional add-ons.
4. After launch, small changes are handled with quick quotes.

Each document has a different level of commitment. The estimate is a conversation starter, the proposal is the agreement for the main project, and quotes handle the small pieces of work that follow.

A comparison with numbers

Take a law firm that wants a new website.

Estimate, sent after the first email: "Sites like this usually cost $7,000 to $11,000. The main factors are the number of practice area pages and whether you need a client portal." No commitment, no detailed scope.

Proposal, sent after the discovery call: discovery $1,500, design $3,000, build for ten pages $4,000, launch and training $500, for a base of $9,000. Optional client portal integration $2,200 and optional copywriting $1,400. Timeline of seven weeks, 50% to start and 50% at launch, two revision rounds included. The firm accepts the base plus copywriting: $10,400, inside the original estimate range.

Quote, three months later: "Add an attorney profile page using the existing template: $350, delivered within five business days, valid for 30 days." Accepted by reply.

Because each document matched its purpose, there was no confusion about whether the $10,400 was firm or whether the profile page was included.

Mistakes to avoid

Do not call a document an estimate and then refuse to adjust when scope changes; equally, do not call it a quote if you expect the price to move. Do not send a quote for a large project to avoid writing a proposal; the time you save is lost in later disputes. And do not let an estimate become the price by default: when you send the proposal, refer back to the range and explain where the final number landed and why.

Put a validity period on quotes and proposals, such as 30 days, so old prices do not come back months later.

Send the right document in minutes

ProposalKit is built for the proposal step: scope, timeline, pricing with optional add-ons and typed-name acceptance on one link. Start from a template in the gallery or create a free account.