How To Write A Website Redesign Proposal

Don't have time to read this? Schedule a 30-minute call and we will walk you through exactly how this applies to your business. Book a call

Key Takeaways

• A proposal is not a quote. It is a structured argument for why your approach will solve the client's specific problem.
• The most common reason proposals lose is not price, it is that the agency failed to demonstrate real understanding of the client's situation.
• Proposals that mirror the client's own language and goals back to them convert significantly better than template-driven documents.
• Specificity beats length. A focused 8-page proposal outperforms a generic 20-page deck.

Is your proposal a document that explains what you will do, or does it make the case for why your approach is the right one for this specific client?

Most redesign proposals are the former. The ones that win are the latter.

Here is how to write a website redesign proposal that closes.

What a Proposal Is Not

Before writing one, it helps to understand what a proposal is not.

A proposal is not a portfolio presentation. Your past work earns attention. It does not close the project.

A proposal is not a capabilities deck. Listing what your team can do is not the same as showing what you will do for this client.

A proposal is not a quote with scope attached. A quote answers "how much." A proposal answers "why us, why this approach, why now."

The Anatomy of a Strong Redesign Proposal

Every section of the proposal should earn its place. Here is the structure that works.

1. Executive Summary

This is the first section the client reads and the one most agencies write last, or skip entirely.

Write a three-to-four paragraph summary that:

• States the client's core problem in their own language
• Outlines your recommended approach and why it fits their situation
• Notes the project timeline and investment range
• States the outcome the client should expect

This section should read like it was written specifically for this client, because it should be.

2. Understanding of the Project

This is the most important section in the proposal. It demonstrates whether you actually listened during discovery.

Summarize:

• The current website's performance problems (traffic, conversions, outdated tech, brand misalignment)
• The business context behind the redesign decision (new product line, rebranding, growth stage shift)
• The goals the client defined, in their own words where possible
• Any constraints that will shape the project (timeline, existing systems, internal approval process)

"The proposal that shows us we understood the problem is the one that earns the project."

Clients are evaluating whether you understood them before they trust you to solve anything for them.

3. Proposed Scope of Work

Break the project into phases. Each phase should be clear about what is included and what is not.

Typical phases for a website redesign:

Explicit out-of-scope items to include:

• Content writing (unless the proposal includes it)
• Photography or custom illustration
• Third-party platform licenses
• Ongoing marketing support beyond launch

Defining what is out of scope protects you as much as it informs the client.

4. Your Process

Clients are not buying deliverables. They are buying confidence that the project will be managed well.

This section answers: How will you work with us?

Include:

• How discovery is structured and who needs to be involved
• How design decisions are presented and approved
• How many revision rounds are included per phase and what they cover
• How you handle scope changes
• How you communicate status throughout the project

A client who understands your process is less likely to introduce chaos into it mid-project.

5. SEO Approach

For any client with existing organic traffic, SEO protection should be an explicit section, not a footnote.

What to include:

• Pre-redesign SEO baseline audit
• Redirect map planning and implementation
• Meta data and content migration approach
• Staging environment SEO review before launch
• Post-launch Search Console monitoring

If your proposal does not address SEO, the client asking the question "what happens to my Google rankings?" will select the agency that does.

The website redesign RFP process typically asks agencies to define their SEO approach explicitly. If they asked, your proposal must answer.

6. Team and Roles

Name the people who will work on the project. Senior teams do not make promises and hand off to junior staff without disclosure.

Include:

• Who will lead the project (project manager or account lead)
• Who will handle UX and design
• Who will handle development
• Whether any work is subcontracted, and to whom

If the team has prior experience in the client's industry, note it here. Industry-adjacent case studies mentioned here carry more weight than general portfolio pages.

7. Case Studies

Two to three case studies that are relevant to this project scope or industry.

Each case study should include:

• The client's situation before the project
• What you built and why those decisions were made
• Measurable results: traffic change, conversion rate improvement, load time, leads generated

Avoid case studies that are only visual. "We redesigned the homepage and it looks great" does not close a project. "We redesigned the homepage and demo requests increased by 34%" does.

8. Investment

Present pricing clearly. Clients who have to decode a pricing table lose confidence in the agency before they finish reading it.

Recommended format:

Follow the investment table with your payment schedule. Milestone-based payment schedules (tied to phase completion) are more client-friendly than large upfront retainers.

Note any variables that could affect the final investment (number of pages, integration complexity, content scope).

9. Timeline

A visual project timeline or a table of phases with start dates and target completion dates.

If you have a clear launch date constraint from the client, show whether the proposed timeline meets it and note any dependencies on client deliverables that could affect the schedule.

Timeline risk section: If something could delay the project, name it now. Scope changes, delayed content delivery, and approval bottlenecks are the three most common causes of missed launch dates. Naming them in the proposal sets expectations early.

10. References

Provide two to three past client references the prospect can contact. Include name, company, and the project type.

An agency that does not offer references signals something about the quality of those relationships.

11. Next Steps

Close the proposal with a specific action, not an open question.

"To move forward, the next step is a 30-minute project kickoff call where we align on timeline, confirm stakeholder availability for discovery interviews, and execute the project agreement. We are holding availability for this project through [date]. Please reach out to [name] at [contact] to schedule."

A deadline creates legitimate urgency. An open-ended "let us know if you have questions" does not.

Common Proposal Mistakes

Considerations:

• Generic language: "We are passionate about design" tells the client nothing about their project.
• No problem statement: Starting with your capabilities instead of their situation signals you did not listen.
• Vague revision terms: "Unlimited revisions" is a liability. Define what a revision round includes.
• No SEO section: Any client with organic traffic will notice this absence.
• Price without context: A number without scope justification is just a number. Clients without context compare it to the lowest bid they received.

Proposal Format: Document or Deck?

For most SMB website redesign projects, a well-structured PDF proposal converts better than a deck.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

What Separates Proposals That Win

The proposals that close share a specific quality: they make the client feel understood before the project starts.

That happens when the proposal:

1. Uses the client's language and goals from the discovery call
2. Identifies a problem the client mentioned that other agencies may have missed
3. Proposes an approach that fits their specific constraints, not a generic methodology

LOW/CODE Agency is a leading AI product team for SMBs and startups. We write proposals that address the specific problem the client is trying to solve, not just the deliverables they asked about.

For teams preparing to pitch a redesign internally or to leadership before the agency is even involved, the website redesign pitch process covers how to make the business case first.

Website projects start at $10,000+. Book a 30-minute call