Explain what changes the scope before quoting a website

Two websites with ten pages can require very different work. One uses approved copy and a simple inquiry. Another needs a catalog import, two language journeys and an account portal. A useful initial brief explains the moving parts.

Separate content and behavior

List the pages people read and the tasks they perform. A service description is content; a quotation form that calculates and stores a revision is behavior. Both need design, but they create different implementation and testing work.

Name external dependencies

For a Colombian business, include payment-provider access, Spanish review, product photography and any invoicing connection. Say who approves each one. An unfinished dependency may change sequencing even when the website code is ready.

Choose a complete first release

A first release should let someone finish a useful task. It can be narrower than the eventual vision, provided the omitted features are deliberate. Agree what will be tested and what remains for later rather than compressing every idea into an unclear promise.

The W3C accessibility planning resource illustrates why responsibilities need attention early. Use the project worksheet to organize your own responsibilities, then discuss whether discovery, a staged redesign or a new build is the sensible next step.