Define the commercial goal
More enquiries, better-quality leads, easier bookings, stronger product sales and clearer positioning are different jobs. Name the primary outcome so design decisions can be judged against it.
Understand the audience
List the questions, concerns and information needs that shape a customer decision. This gives the sitemap and page structure something more useful to follow than the old website.
Protect what already works
Keep useful pages, rankings, backlinks, analytics history, testimonials and content. A redesign should improve the experience without casually discarding assets that already create value.
Prepare the essentials
- Core services, products and priorities
- Customer proof and real project examples
- Brand assets and photography
- Analytics and Search Console access
- Required integrations, forms and workflows
- Redirect and migration requirements
Plan content before production
Late content causes weak layouts and delayed launches. Agree who owns each page, what evidence is available and where new copy or imagery is required before the build reaches its final stages.
Look beyond appearance
A better-looking website is valuable, but structure, speed, editing, accessibility, search foundations and conversion paths often determine whether it becomes a better business asset.
Agree responsibilities before choosing an agency
A useful proposal states who supplies copy and images, who approves the structure, what the team can edit and which integrations are included. Ask for assumptions and exclusions as well as deliverables so the comparison is meaningful.
Discuss how changes to scope are handled and who owns domains, hosting and licences. Knowing the handover arrangements before the build helps avoid a website that depends on access your business does not control.
See our website redesign approach
Understand what changes a website quote
Define the launch checks
Test the journeys that matter: finding a service, submitting an enquiry, receiving the message and using the site on a phone. For an online store, add representative test orders and integration checks to the scope.
Agree who checks redirects, page titles, canonicals and indexability on the production site. Keep staging out of search and verify production separately; copying a site is not the same as completing a launch.
Prepare for a January kickoff
Before the holiday break, choose a decision-maker, collect brand assets and list the content that needs work. Confirm access through the appropriate account owner and identify any fixed business dates the launch must support.
Use the first project conversation to agree scope and dependencies. Confirm capacity and delivery dates with your chosen agency instead of assuming that a January enquiry guarantees a January launch.
Share your current website or workflow, the change you need and any timing or budget you have in mind.
Explore our web design services
Discuss your website