In this guide 23 sections
A professional website redesign proposal should define the business objectives, page scope, content responsibilities, design deliverables, technical requirements, SEO migration, lead integrations, testing, timeline, price, ownership and post-launch support. It should tell you exactly what will be built and how the work will be accepted—not simply show attractive mockups and a total fee.
For service businesses, the proposal also needs to protect existing enquiries and search traffic while making the new site easier for customers to use. The checklist below explains what to look for before approving a redesign.
A redesign proposal should start with the business problem
A useful proposal explains why the website needs work before describing colors, fonts or software. It should summarize the current challenges, intended audience and the actions visitors need to take. For a service business, those actions might include understanding a service, viewing completed projects, booking a consultation or submitting a qualified enquiry. Ask the agency to distinguish observed problems from assumptions. An old visual style is not, by itself, evidence that the website is failing. Review existing analytics, contact forms, mobile behavior, search visibility and customer feedback where available. A proposal should explain what the agency will investigate and which decisions depend on discovery. This makes the work more defensible than a list of design trends.
Define measurable objectives without guaranteeing results
The proposal should state what success looks like and how it will be evaluated. Possible objectives include clearer navigation, accessible forms, more reliable lead routing, improved mobile usability and easier content editing. Conversion metrics may be included, but an agency cannot responsibly guarantee a specific increase without knowing traffic quality, offer competitiveness and the sales process. Ask for a measurement plan that identifies baseline data, analytics events, CRM outcomes and the review period. Separate outputs under the agency’s control from outcomes influenced by advertising, demand and follow-up. A new website can support business performance, but the proposal should not present speculative future revenue as certain. The strongest goals are understandable and testable.
Inventory existing pages, content and URLs
Before rebuilding an established website, list the important pages, their purposes and the content worth retaining. A proposal should explain who performs the audit and how pages will be kept, merged, rewritten or retired. Include existing blog posts, service pages, projects, location pages and forms. Clarify who supplies new copy, who approves claims, and whether image selection or original photography is included. If a URL changes, identify the redirect responsibility. Existing pages may have search visibility or inbound links that deserve careful handling. The proposal should not assume that every old page is valuable, nor that deleting most pages is harmless. A documented content map reduces surprises during development and helps estimate the real work.
Describe the sitemap and information architecture
A sitemap shows how users will navigate the new site. It should identify main navigation items, service categories, company information, case studies, educational content and contact routes. For a business offering multiple services, explain whether each needs a dedicated page and how related content will be linked. A proposal may include a preliminary sitemap that is refined after discovery. Avoid treating the sitemap as an arbitrary page count; ten generic pages are not necessarily more useful than six well-structured ones. Ask how the design accommodates future services and new case studies. The goal is to help visitors find relevant information and understand what to do next without navigating a maze of menus.

Specify design deliverables and review milestones
The proposal should name the design artifacts the client will review: wireframes, visual mockups, a component system, responsive layouts or an interactive prototype. Identify which unique page templates are included and how many rounds of feedback apply. A homepage, service page, article page and contact page may have different requirements. Clarify whether mobile layouts are designed deliberately or adapted later. Define who signs off on each milestone and how requests beyond the approved scope are handled. A clear review process avoids both rushed approval and endless revisions. The proposal should describe the intended brand direction without promising that a particular visual style alone will increase leads.
Explain the content and copywriting responsibilities
Strong visual design cannot compensate for inaccurate or vague content. The proposal should identify who writes headlines, service descriptions, project summaries, FAQs, metadata and calls to action. If the client provides text, specify the format, deadlines and editing support. If the agency writes copy, explain its research process and how subject-matter claims will be checked. Authentic client testimonials and project results must be supplied or approved, not invented. Photography should be clearly categorized as client-provided, commissioned or appropriately licensed editorial imagery. Avoid treating stock photos as evidence of completed work. Content responsibilities should appear in the timeline and budget because late copy decisions often delay launch.
Include mobile design and accessibility expectations
A professional redesign should be tested on more than a desktop mockup. Ask how menus, service cards, images, sticky CTAs, forms and booking tools behave on smaller screens. The proposal should mention readable text, touch targets, clear labels, keyboard navigation and accessible error messages. W3C’s Web Content Accessibility Guidelines provide a reference for accessibility criteria, although a proposal should specify which checks are included rather than making an unsupported claim of perfect compliance. Consider motion preferences and avoid effects that obscure content or make forms hard to use. A mobile acceptance test should cover the entire customer journey from a landing page to a successful enquiry.
Define development scope and integrations
The technical section should identify the CMS or framework, page templates, reusable components, content editing workflow and required integrations. If the business uses WordPress, Next.js or a headless combination, explain why that setup fits its needs. List contact forms, CRM routing, analytics, booking tools, email notifications, third-party services and any payment functionality. Distinguish configuration of existing services from custom development. Clarify where API credentials will be stored and who controls accounts. If an integration is dependent on a third-party provider, note that dependency and its costs. The client should understand what functionality will be delivered, not merely which technologies the agency plans to use.

Plan technical SEO and search migration
For an existing website, the proposal should include an SEO migration approach. Important elements are a URL inventory, redirect mapping, canonical tags, metadata, internal links, sitemap updates, robots directives and post-launch indexing checks. Explain who will monitor Google Search Console and address errors. A redesign should not casually discard useful content or replace established URLs without considering consequences. Search performance may fluctuate even when migrations are planned carefully, so guaranteed rankings are not a credible deliverable. The proposal should distinguish technical launch SEO from ongoing keyword research, content publishing and link development. These may be separate services with separate budgets.
Explain performance and quality assurance
Ask what the team will test before launch. This should cover browser behavior, responsive layouts, form submissions, links, images, keyboard access, analytics events and integrations. Performance checks should consider real mobile conditions, not only desktop development machines. Google’s Core Web Vitals are useful indicators for loading, responsiveness and visual stability, but they do not replace functional testing. The proposal should define how bugs are reported, prioritized and resolved. It should also clarify whether QA is included in the base price. A site that looks polished but loses contact requests has failed an essential business requirement.
Document the lead generation workflow
For service companies, the contact process deserves a dedicated acceptance checklist. The proposal should show where visitors encounter CTAs, what information forms collect, what happens after submission, and which team receives the enquiry. If a CRM is used, clarify field mapping, lead ownership, duplicate handling and notifications. Test both valid and invalid submissions, including mobile behavior and temporary connection problems. Avoid recording personal contact information in analytics systems that are not intended to receive it. A thank-you page alone does not prove delivery. Ask for a live test demonstrating the stored record and the staff notification. This reduces the risk of a beautiful website that silently loses business opportunities.

Set a realistic timeline with dependencies
A redesign timeline should show discovery, content, design, development, testing, launch and handover. Each phase needs an owner, expected deliverables and approval requirements. Note dependencies such as client feedback, access to existing systems, copy approval, photography and third-party integrations. Dates should be realistic rather than artificially compressed to win the project. Explain how delays and scope changes will be communicated. A timeline that only lists a final launch date hides the decisions that determine whether the project can finish. The client should know which tasks can happen in parallel and which must wait for approval.
Show an itemized price and payment schedule
The financial section should identify design, development, content, integrations, SEO migration, testing and support costs as appropriate. State what is included, excluded and optional. Clarify hosting, domains, premium plugins, licenses, photography, ongoing maintenance and transaction fees. A deposit and milestone schedule should correspond to defined work and approvals. Describe how additional requests are estimated and authorized before they begin. Comparing two proposals is difficult when one includes content migration and testing while another includes only page layouts. Request a consistent breakdown and consider the total cost of ownership, not merely the initial build price.
Clarify ownership, access and licensing
The proposal should explain who owns the domain, hosting, repository, custom code, design source files, content and relevant accounts. Third-party software and templates may carry separate licenses that cannot simply be transferred. Make sure the business will have appropriate administrator access and a documented handover. Clarify whether the agency retains reusable components and whether the client can hire another developer later. Do not assume a hosted platform offers unrestricted export. Ownership terms are legal matters, and significant projects may warrant contract review by qualified counsel. The goal is to avoid unnecessary dependence on a single supplier after the project is complete.

Describe launch, rollback and handover
The proposal should define a launch checklist: backups, redirects, forms, analytics, SEO settings, DNS or hosting changes and final content checks. If the website already receives enquiries, identify a rollback plan in case a critical function fails. Clarify who monitors the site immediately after launch and who resolves unexpected issues. Handover may include administrator access, CMS training, design files where agreed, documentation, backup procedures and an inventory of recurring services. A website is not fully delivered merely because it is visible online. The business should know how to publish updates, respond to enquiries and request support after launch.
Explain the post-launch support arrangement
The proposal should state whether bug fixes, maintenance, backups, content changes, security updates and performance monitoring are included after launch. Define the support period, response process and any service fees. Distinguish correcting a defect from adding a new feature. If ongoing SEO or conversion optimization is offered, describe it separately with deliverables and reporting expectations. Ask what happens when the initial support period expires and how the client can transfer maintenance to another provider. A clear support arrangement protects the investment and prevents avoidable downtime. Do not assume that a hosting subscription includes hands-on website care.
How to evaluate competing redesign proposals
Compare proposals against the same business requirements. Review scope completeness, evidence of relevant work, communication, content responsibility, mobile QA, SEO protection, lead routing, ownership, timeline and support. A higher price can be justified by meaningful additional deliverables, but vague promises are not a substitute for detail. Ask each agency to explain how it would handle a broken contact form or a migration issue. Their answers may reveal the quality of the operating process. Choose a partner who can clearly explain trade-offs and provide realistic commitments. The cheapest quote is not always the lowest total cost, and the most elaborate presentation is not necessarily the strongest implementation plan.
Redesign proposal comparison checklist
| Proposal component | What to verify |
|---|---|
| Business goals | Clear problems, audiences and success measures |
| Content and sitemap | Page inventory, new structure and copy ownership |
| Design | Unique templates, responsive layouts and review rounds |
| Development | Platform, features, CMS and integrations |
| SEO | Redirects, metadata, indexing and migration checks |
| Lead generation | Working forms, CRM routing and notifications |
| Testing | Mobile, accessibility, performance and functional QA |
| Commercial terms | Itemized price, milestones and exclusions |
| Ownership | Accounts, code, files and license responsibilities |
| After launch | Handover, support and maintenance boundaries |
Questions to ask before accepting the proposal
- Which pages and templates are included in the price?
- Who writes and approves the content?
- What happens to existing search-ranking URLs?
- Who tests and receives contact-form submissions?
- How are additional requests estimated?
- What are the design approval milestones?
- Who owns the domain, hosting and website assets?
- What happens if the launch causes a critical problem?
- What training and documentation will we receive?
- Which services continue after the initial project ends?
Frequently asked questions
How detailed should a redesign proposal be?
Detailed enough that both parties understand deliverables, exclusions, responsibilities, acceptance criteria and commercial terms.
Should copywriting be included?
It may be included or separate, but the proposal must clearly state who writes, reviews and supplies each type of content.
Does a redesign proposal need an SEO plan?
For a site with existing search visibility, a migration and redirect plan is important. Ongoing SEO services may be scoped separately.
How many page designs are included?
The number depends on the project. Clarify unique templates versus pages populated from reusable templates.
Should I pay for the entire project upfront?
Payment arrangements vary. A clear milestone-based schedule tied to defined deliverables can make expectations easier to manage.
What is the difference between a proposal and a contract?
A proposal describes the suggested work and commercial offer; the signed agreement governs obligations, ownership and remedies. Seek legal advice where needed.
Can I change requirements after approval?
Usually, but the proposal should define how changes affect cost and schedule and who authorizes them.
Who should test the website before launch?
The development team should perform QA, and the client should complete agreed acceptance checks for real business workflows.
Should ongoing maintenance be part of the redesign?
It can be included or offered separately. Either way, responsibilities and fees should be explicit.
Related website planning resources
Review our questions for a website developer, redesign timeline guide, website redesign budgeting guide, content migration checklist, and SEO-safe redesign guidance.
Make the scope clear before work begins
The most useful proposal is not the longest document. It is the one that lets a business owner understand what will be delivered, how the project will proceed, what the client must provide, and how the new website will be tested and maintained.
Avenzo Digital provides website design, development and redesign services for businesses. Request a consultation to discuss your requirements and ask about a free homepage mockup.




