Practical business guide

How to write a project estimate clients can actually use

Updated November 4, 2026 · General educational information

A useful project estimate helps a client make a decision without pretending uncertain work is perfectly predictable. The goal is not just a number: it is a shared understanding of what the number covers and what happens if the project changes.

Use this as a general workflow, then adapt it to your client, contract, industry, and local rules.

Start with the outcome and scope

Summarize the client’s goal, the work you will perform, and the deliverables they will receive. Break large projects into stages or milestones. Describe boundaries too: number of revisions, formats, meetings, locations, or items included can all matter.

Show how you arrived at the price

Itemize meaningful work packages, hours, quantities, rates, third-party costs, and any applicable tax. A client should be able to see the logic without needing to reverse-engineer a lump sum. Do not itemize sensitive internal cost data unless you intend to disclose it.

Make uncertainty and assumptions visible

For time-and-materials projects, explain how actual hours will be reported and whether you will use a not-to-exceed limit. For a fixed-fee proposal, make sure the scope is sufficiently defined to support that commitment.

  • List information you are relying on, such as supplied content or access to a site.
  • Identify excluded work and external costs.
  • Explain what could change the price or timeline.
  • Say how you will notify the client and obtain approval for extra work.
  • If appropriate, give a range and explain what would place the project at the low or high end.

Set validity and approval terms

Include an issue date and a reasonable date for the estimate to be reviewed or accepted. Explain whether acceptance requires a signature, written email approval, deposit, or a separate agreement. State when work is scheduled to begin and whether the estimate itself is intended to be binding; get qualified advice for legal language where needed.

Follow through consistently

Once approved, keep the estimate as the baseline. Record scope changes in writing, update price and timing before doing additional work, and issue an invoice that ties back to the approved project or milestone. This discipline protects the client relationship as much as it protects your time.

Worked example

Example: estimating a launch package

Suppose a client wants brand direction, a small set of web graphics, and social assets, but has not finalized the number of pages. Separate the known work from the uncertain page count. State the assumed asset count, revision limit, supplied materials, and what additional pages would cost. If a range is used, explain what makes the lower and upper ends different. Ask the client to approve the scope and budget approach before production begins.

Use before you send or file

Quick checklist

  • Name the outcome, deliverables, quantities, and exclusions.
  • Show the basis of the price: fixed fee, hours, rates, or range.
  • List assumptions, third-party costs, and uncertainty drivers.
  • Set a review/validity date and a clear approval method.
  • Define how scope changes affect price and delivery dates.

Common mistakes to avoid

  • Giving a low number to win the work while hiding likely extras.
  • Presenting a range without explaining what changes the cost.
  • Starting out-of-scope work based only on a vague verbal request.

Related guides

This guide is general educational information, not legal, tax, accounting, or financial advice. Rules vary by location and business circumstances. Check current local requirements or consult a qualified professional.