Back to Blogs
ProcessJan 15, 20269 min readDan Winslow

Why Website Estimates Need Assumptions

A credible estimate explains what is known, what could change the effort, and how the team will handle discoveries that do not fit the original picture.

Why Website Estimates Need Assumptions

An estimate is a model built from incomplete information. Adding more digits does not make it more accurate. The useful version shows what the model assumes, which parts carry uncertainty, and what evidence would cause the number to change.

Estimate behavior, not just screens

Two pages can differ by weeks of work. A static service page, a searchable directory, and an account dashboard may each occupy one route while requiring entirely different design, data, and testing effort.

Break work into capabilities such as content management, authentication, search, payments, integrations, and migration. Then include accessibility, responsive behavior, analytics, error handling, and release preparation.

Write assumptions beside the number

An estimate might assume that the client supplies final copy, one existing API is documented, and two people provide consolidated feedback. If any of those conditions changes, the impact should not come as a surprise.

Unknown systems can be handled with a paid discovery task or an explicit allowance. Guessing low to keep a proposal attractive usually moves the same conversation to a more expensive point in the project.

Use a range that reflects the decision stage

An early budget conversation may only support a broad range. After designs, content, and technical dependencies are clearer, that range can narrow. Treating both moments as if they warrant a fixed quote creates false confidence.

Explain how changes will be evaluated before they occur. A client can make sensible tradeoffs when cost, schedule, and scope are discussed together.

In Short

  • Estimate capabilities and supporting work rather than page count.
  • Attach important assumptions and unknowns to the estimate.
  • Let precision increase as the project evidence improves.
EstimatingScopingProject Management

Related Articles

Process

What a Useful Website Scope Actually Includes

A good scope does more than count pages. It records priorities, responsibilities, open questions, and what everyone will consider finished.

Read Article
Platform Guides

WordPress vs. Duda: Which One Fits Your Website?

WordPress offers enormous flexibility. Duda trades some of that freedom for a calmer editing and maintenance experience. Here is how the choice plays out in practice.

Read Article
Process

What a Useful Website Scope Actually Includes

A good scope does more than count pages. It records priorities, responsibilities, open questions, and what everyone will consider finished.

Read Article