Website design starts with what your customers need to do.
What should someone do when they reach your site: call, request a quote, book or buy? Use that answer to decide which pages and functions belong in the project.
A new site, a rebuild or specific changes?
Improve an existing site
List the pages and functions you want to keep. Point to the changes you need rather than assuming everything needs replacing.
Rebuild an existing site
Save a list of current pages, forms and connected accounts. Mark what should move, change or be retired.
Start a new site
List the services or products to explain, the content you already have and the action each page should support.
Put the website scope in writing
Pages and customer actions
Name each required page and the next action you want it to support. A service overview, quote request and booking flow are different requirements.
Forms and connected systems
What information should each form collect, and where should it go? If you need booking or checkout, include that in the requirements rather than assuming it comes with a website.
Content and account access
Who will supply and approve the copy, brand files and images? Identify who controls the domain, hosting and any accounts the site needs to connect to.
Ownership and ongoing work
Ask which website files are delivered, which reusable components are licensed, and whether updates, hosting and maintenance are included. Confirm those items in the proposal.
Changing the addresses of existing pages?
Add current URLs to the brief and ask how changed or removed pages will be handled. Google's site-move guide recommends a URL map, redirects and post-move monitoring when addresses change. Rankings can fluctuate during a move.
Google's guide to moving a siteQuestions before you choose a website project
How much will a website cost?
Describe the required pages, functions and content before comparing quotes. Ask the proposal to separate the initial build from hosting, maintenance and later changes.
What if I already have a site?
List what works, what is missing and what must stay, including existing URLs and forms. You can use this scope checklist for a focused change or a rebuild.
Who owns the website after launch?
Ask what you will receive and when ownership transfers. Website files, your content and reusable frameworks can have different terms; read those parts of the agreement together.
Does a rebuild guarantee more leads or better rankings?
No. Treat rankings, traffic and inquiries as things to measure, not promised results. Ask which outcomes will be measured and how results will be reviewed.
How do I plan for future changes?
List who will update copy, test forms and manage hosting. Ask which work is included after launch and how additional requests are scoped.
AI-assisted planning guide.
Have a website project in mind?
Bring the current site, the pages you need and the customer action you want to support.