How to decide whether to redesign or rebuild your website
Decide which problems need a repair, redesign or rebuild. Compare two scopes using customer tasks, platform limits and maintenance requirements.
10 PRACTICAL GUIDES
Decide what to build, prepare the content and compare proposals against the same brief.
Start with the customer task, then agree the page list and responsibilities. These guides help you choose a defined project before committing to payment. Use the planning worksheet to record decisions and the quote comparison sheet to make exclusions visible.
Decide which problems need a repair, redesign or rebuild. Compare two scopes using customer tasks, platform limits and maintenance requirements.
Review service information, navigation and enquiries on your existing website. Record evidence and prioritise the fixes before asking for quotes.
Prepare a clear project brief with page purposes, content owners, features and acceptance checks so a developer can quote the actual work.
Turn a vague website goal into a customer task and a measurable outcome. Establish a useful baseline without inventing conversion claims.
Choose pages by the questions customers need answered. Map a focused route from your offer to an enquiry and identify missing content.
Organise page text, approved assets and content responsibilities. Use a content inventory to expose missing material before development starts.
Compare the project fee with domain, hosting and future-change costs. Work through an illustrative first-year total and check the exclusions.
Assess website packages against one shared brief. Check delivery limits, editing, account ownership and the handover before choosing a supplier.
Review relevant work and ask practical questions about delivery. Record evidence, supplier details and unresolved scope before commissioning a site.
Compare redesign proposals by content, migration, testing and handover. Identify assumptions that a headline price can hide.
Explore the five guide topics or review the website package scope.