Break the deliverable into tasks, include review and handoff, add an explicit uncertainty allowance, then apply your rate. Keep exclusions beside the number.
Start with a deliverable
“Build a website” leaves almost everything open. A useful estimate starts with a result another person can inspect: a five-page website, one contact form, a mobile layout, and a handoff document. The pages, content ownership, review rounds, and completion check belong in the scope before an amount does.
Write two lists. The first describes what the project includes. The second names requests that would change the estimate. This does not need to become a long contract; it needs to make the shared expectation visible.
A small example: refresh a service business website using supplied copy. Include five pages and one consolidated review round. Treat new branding, copywriting, additional languages, and ongoing updates as separate decisions.
Break it into work
Count more than implementation. Discovery, checking the supplied material, design decisions, testing, review, and handoff all use time. A task list makes these costs easier to discuss and easier to compare with what actually happened later.
| Work | Example hours |
|---|---|
| Discovery and scope | 2 |
| Design decisions | 4 |
| Implementation | 12 |
| Review and checks | 3 |
| Handoff | 1 |
These 22 hours are a worked example, not a benchmark. Replace them with estimates for your actual deliverables. Keep a large uncertain task separate until you can describe it well enough to estimate.
Make uncertainty visible
An allowance is easier to understand when its purpose is explicit. It might cover uncertainty within the agreed scope, such as integrating with an unfamiliar existing system. It should not silently stand in for unlimited revisions or new requirements.
Our estimator multiplies base hours by a buffer percentage, then adds that allowance before applying your hourly rate. With 22 base hours, a 15% allowance, and a rate of 35 in your chosen currency, the calculation is 25.3 × 35 = 885.50. No tax, hosting, subcontractor, or other expense is included unless you account for it separately.
Changing a rate or buffer does not make an estimate more accurate by itself. Keep the assumptions alongside the result and discuss the uncertain parts directly.
Review the estimate
Before sharing the result, check the task names, quantities, exclusions, review rounds, and handoff. Ask whether someone else could tell what completion means from the same description. Export the task list so that the estimate remains understandable after the conversation.
After delivery, compare estimated and actual effort by task. A repeat pattern is more useful than a vague feeling that a project took too long. Revise the next estimate using that evidence, rather than treating a single successful job as a universal rule.
Download the editable scope worksheet or calculate your own estimate.