How to Write an Estimate for a Client (Step by Step, 2026)

A client emails: "Roughly what would this cost?" You don't have the full scope yet, you can't commit to a number, but you also can't say "I don't know" and expect to win the job. This is the moment an estimate exists for — a careful, professional way to put a figure on the table without locking yourself into a price you'll regret.

Done well, an estimate keeps the conversation moving, protects your margin, and converts smoothly into a binding quote and then an invoice. Done badly, it becomes a number the client treats as a promise. Here's how to write one that works for you.

What an estimate actually is

An estimate is an approximate, non-binding forecast of cost, based on what you currently know about a project. It says: "Given the information I have today, this will likely cost around X." It is not a commitment, and that distinction is the whole point.

It helps to see where the estimate sits among the documents freelancers use:

• Estimate — an educated guess. Non-binding. The scope is still fuzzy.
• Quote — a fixed offer: this exact scope for this exact price, valid until a date. Binding once accepted.
• Invoice — a request for payment, issued after the work or a milestone is delivered.

If those distinctions feel blurry, the full breakdown is here: estimate vs quote vs invoice. The short version: an estimate explores, a quote commits, an invoice collects.

When to send an estimate vs a quote

Use this as your default rule.

The trap to avoid: sending an estimate when you should be sending a quote. If your number is precise enough that a client could reasonably treat it as fixed, skip the estimate and write a proper quotation instead. Estimates are for genuine uncertainty, not for dodging the commitment.

How to write an estimate, step by step

A good estimate is structured like a quote — just clearly labelled as non-binding. Here's the anatomy.

Write a scope summary first

Before any numbers, write two or three sentences describing the project as you understand it. This does two jobs: it shows the client you listened, and it surfaces mismatches early ("oh, I also need the mobile version") before they blow up your figure.

Itemize the work

A single number invites haggling because the client can't see what they're paying for. Break it into lines — "Discovery & wireframes," "Design," "Build," "Testing" — each with a cost. Itemizing makes the total feel fair and gives you room to adjust scope line by line if the budget is tight. If you price by the hour, anchor your line items to a defensible rate; our hourly rate calculator helps you set one that covers your real costs.

Use ranges carefully

Ranges are the honest way to handle uncertainty — but they carry a psychological risk: clients remember the bottom of a range as the price. Quote "$2,000–$3,000" and land at $3,000, and some clients feel overcharged. So keep ranges tight, and only use them where the uncertainty is real. If you're guessing at the duration too, estimating how long a project will take is half the battle.

Spell out your assumptions

Assumptions are where estimates protect you. "Assumes you provide final copy" or "assumes hosting is already in place" means that when those things turn out to be untrue, you have a written basis to revise the figure — not an awkward conversation about why it cost more.

Add a validity period and a clear disclaimer

End with something explicit: "This is an estimate based on the information available today. Final pricing will be confirmed in a fixed quote once scope is agreed. Valid for 14 days." That one sentence is the difference between a flexible forecast and a number you're trapped by.

How estimates protect you — and convert

An estimate isn't a weaker version of a quote; it's a different tool with a different job. It lets you engage seriously with a lead before you've done the unpaid work of fully scoping the project. It anchors the client's budget expectations early. And it gives you a documented starting point, so when scope grows, the price growing with it feels logical rather than like a surprise bill.

It also gives you a natural next step. Once the client reacts to the estimate and the scope firms up, you convert it into a fixed quote — and once that's accepted, into an invoice. The estimate did the exploring; the quote and invoice do the committing and collecting.

A note on language: some clients and corporate buyers expect a formal document before any invoice — that's often a pro forma invoice, which behaves much like a quote. And if your estimate comes back with "that's too much," don't drop the number on reflex — here's how to respond when a client says your price is too high. For the bigger picture on setting figures you can defend, see how to price freelance projects.

The takeaway

An estimate is a forecast, not a promise. Write it like a quote — scoped, itemized, with assumptions — but label it clearly as approximate and add a validity window. Get that right and your estimate does its real job: keeping the deal alive while protecting your price, then handing off cleanly to the quote and invoice that get you paid.

The good news is you don't need separate tools for any of this. In Tuplify, estimates and quotes are produced the same way — same generator, same clean layout — so turning an approved estimate into a binding quote (and then an invoice) takes seconds.