Website Estimate Request Checklist

A useful website estimate starts with enough context to identify the real work. A long wish list without goals, content, systems, or ownership creates a number that is difficult to compare or trust.

Describe the business outcome

Explain what the site should help customers do, which problem it should solve, what is not working now, and how the team will judge success. Include the audience and important departments.

List pages and workflows

Include homepage, services, locations, articles, products, inventory, booking, quote, account, payment, search, and confirmation needs. Mark must-have, useful later, and unknown items.

Share content and assets

Note existing copy, images, branding, testimonials, policies, data, downloads, translations, and who owns or approves each item. Content work can change the estimate significantly.

Document systems and constraints

List CMS, CRM, inventory, scheduling, payment, analytics, email, chat, hosting, domain, access, security, launch timing, browser support, accessibility, and required integrations.

The discovery questions and estimate preparation guide provide more prompts.

Set acceptance and budget context

Describe what must work at launch, who approves it, whether there is a target range, and what should be excluded. Ask for assumptions, phases, hours, and ongoing costs separately.