Begin with the business job
A restaurant needs menus, accurate hours, and simple navigation. A service business needs proof, helpful descriptions, and reliable inquiries. A recruiting firm needs pathways for both candidates and employers.
Write down what visitors must understand and do before counting pages. A website that looks modern but leaves buyers guessing hasn't solved the most important problem.
Content requires real ownership
Headlines, service explanations, photographs, FAQs, project evidence, and calls to action all need to come from somewhere. Decide who writes, supplies, and approves each asset.
Many pages can share a carefully designed template. Custom calculators, portals, complicated databases, and unusual integrations should be budgeted separately from simple informational content.
Don't forget forms, SEO, and migration
Define what the site connects to: CRM, email, payments, scheduling, analytics, or existing tools. Forms need actual delivery testing and spam protection, not just a successful-looking button.
For a rebuild, plan old-to-new URL redirects, metadata, sitemaps, indexability, and content migration. Google's documentation explains technical practices, but a redesign alone cannot guarantee a ranking change.
Plan for the first month after launch
Check the experience on phones, large screens, and keyboards. Test real inquiry pathways and the admin's ability to edit the content. Agree what blocks launch and what can be improved afterward.
Hosting, security, maintenance, content updates, and ongoing SEO need named owners. Ask proposals to separate the build from recurring services so you know what you're buying.
Compare the deliverables, not just the total
Request separate lines for discovery, strategy, copy, design, development, integrations, testing, launch, and support. You should be able to tell which work creates value and which is optional.
The best scope is the one that supports the customer journey and your team's capacity after launch—not the proposal with the most pages.