Quote, proposal or estimate: what's the difference, and which should you send?

The short answer:

• An estimate is your best guess at what a job will cost. It can change.
• A quote is a firm price for a defined scope of work. If the client accepts, that's the price, unless the scope changes.
• A proposal explains how you'll approach the job and why you're the right choice, usually with a quote inside it.

People use these words loosely, and that's where problems start. If you call something a quote and then charge more, your client is entitled to be annoyed.

Estimates

An estimate is useful when you can't know the full cost up front. Maybe the scope isn't settled, you're relying on information you haven't seen yet, or the job could uncover surprises.

A good estimate:

• is clearly labelled as an estimate
• explains what it's based on
• says what could change it
• often gives a range rather than a single number

The risk with estimates is that clients hear the lowest number and treat it as a promise. Be clear about what's uncertain, and update the client early if the cost is heading up.

Quotes

A quote is a fixed price for a specific scope. Once accepted, it's generally treated as an agreement to do that work for that price.

A good quote:

• describes exactly what's included, and ideally what isn't
• states the price and whether it includes GST
• includes timeframes where relevant
• has an expiry date, since prices and availability change
• sets out payment terms, such as deposits and when invoices are issued

If the client later asks for more than the quoted scope, that's a variation. Agree the extra cost in writing before you do the work.

Australian Consumer Law doesn't define "quote" and "estimate" word for word, but it does prohibit misleading conduct and pricing. If you present something as a fixed price and then charge more without a genuine change in scope, you're on shaky ground. When in doubt, be clear, and get advice for your situation.

Proposals

A proposal does more than state a price. It's a sales document. It typically covers:

• your understanding of the client's problem or goal
• how you'll approach the work
• what you'll deliver, and when
• why you're a good fit
• the price, often broken into required items and optional extras
• terms and next steps

Proposals suit larger or more competitive jobs, especially where the client is comparing providers on more than price. For smaller, routine work, a clear quote is usually enough. Nobody wants a twelve-page proposal for a two-hour job.

Which should you send?

Send an estimate when you genuinely can't price the job yet, and you want to give the client a ballpark so they can decide whether to proceed.

Send a quote when the scope is clear and you're confident in the price. This is the right choice for most routine service work.

Send a proposal when the job is larger, the client is weighing several options, or you need to explain your approach to win it.

Many businesses use a hybrid: a quote with a short scope description and a few optional extras. It's quick to put together, clear to read, and gives the client choices. See Optional extras on quotes for how to do that well.

Whatever you call it, make it clear

The labels matter less than clarity. The client should be able to read your document and know what they're getting, what it costs, what might change, and how to say yes.

cyrenRPM handles quotes and proposals in the same place, with required items, optional extras, revisions and client approval. Clients can ask questions on the quote, and once it's accepted it flows into a project and invoice.