A website redesign should improve how visitors complete important tasks. A modern appearance can help, but the project also needs a plan for content, accessibility, search visibility and ongoing ownership. Preparing these details makes agency quotes easier to compare and reduces avoidable surprises near launch.
Define the problem before choosing a style
List what customers struggle to do today. Can they understand your offer, find coverage information, compare options and contact the right person? Use evidence from inquiries, site behavior and customer conversations. ‘The site feels old’ is a starting observation, not a complete project goal.
Choose a few measurable outcomes. These could include fewer failed forms, easier mobile navigation or more suitable quote requests. Document the current baseline so the new design can be evaluated against something more useful than personal taste.
Inventory the content and URLs
Identify pages that must be kept, improved, combined or retired. Record valuable URLs, downloads, forms and integrations. A redesign that removes important information or changes addresses without a migration plan can create avoidable search and customer problems.
Assign an owner to each piece of content. Decide who will supply copy, approve claims, provide images and obtain permissions. Missing content is a delivery risk; it should appear in the project plan rather than emerging during final design.
Put accessibility into the brief
Ask how the agency will test navigation, form labels, keyboard use, focus visibility, readable contrast and meaningful alternatives for images. Include real tasks, such as requesting a quote without a mouse. The W3C introduction to web accessibility provides a useful foundation for these discussions.
An automated score can reveal some problems, but it cannot establish that every visitor can use the site. Agree on the scope of manual testing and who is responsible for addressing issues after content changes.
Agree on performance and integrations
- What forms, CRM connections, booking systems or payment services must continue working?
- Which pages and devices will be tested for speed?
- How will images be sized and compressed?
- Who controls the domain, hosting, analytics and administrator access?
- Which licenses or subscriptions will require renewal?
Create a launch acceptance checklist
Test the primary journeys on phones and computers. Submit controlled test forms, check confirmation messages and verify that notifications reach the intended destination. Review redirects, important links, indexing settings, backup and the plan for returning to the previous version if necessary.
Agree who can authorize launch and when the site will be watched closely afterward. Schedule a follow-up review rather than treating launch day as the end of the project.
Compare scope, not only price
Ask agencies to identify what is included in discovery, copywriting, design, development, migration, testing, training and support. A lower quote may exclude work another proposal includes. Make the comparison explicit before discussing whether the price is reasonable.
Request examples of decisions the team made on similar projects, including constraints and tradeoffs. Attractive screenshots alone do not explain whether a project solved the customer’s problem.
Explore web design providers with your brief in hand. Confirm their responsibilities, ownership terms and acceptance criteria directly before committing.
