Website project scope describes what will be delivered and where the project ends. Page count is only one part. A simple contact page and a product configurator may each occupy one URL but require very different work. Define functionality, content and acceptance criteria separately.

A practical approach

Agree how new requests will be handled before development starts. A change should describe its effect on price, timing and testing, even when it sounds small. Keep a version of the approved scope that both the client and delivery team can reference.

Your checklist

  • List page templates and the number of pages using each.
  • Name integrations and which party supplies their accounts.
  • Document what launch support and training include.

For example

A ten-page site might use four layouts: home, service, article and contact. A later request for customer accounts introduces authentication and account management, rather than simply adding an eleventh page.

Planning a project? Explore our website design or tell us what you need.