Redesign clients are not greenfield clients. They have a site. They’ve been running it for years. They mostly suspect it’s underperforming but they have not done the math. Your proposal does the math for them.
A redesign proposal that opens with “we’ll build you a beautiful new site” is competing on craft. A redesign proposal that opens with “your current site is leaking roughly 80 leads a month” is competing on math. Math wins.
Honestly, this is the part most freelancers I see get wrong. They sweat the portfolio screenshots and the case studies, then bury the only sentence the client actually needed to read. Put the leak number on page one. Everything else is supporting evidence.
Why the standard redesign proposal underperforms
Most freelancers structure a proposal for a website redesign project the same way they structure a greenfield build. Cover page, about us, scope, timeline, price. The client opens it, scrolls to the price, and either accepts, ghosts, or asks for a discount.
The problem is that nothing in that proposal explains why they should spend money on a site that already works well enough to keep their business running. They’ve been paying their hosting bill for years and the world has not ended. So the entire conversation defaults to comparing your number against doing nothing, and doing nothing always feels cheaper.
Reframing fixes this. Doing nothing is not free. Doing nothing has a monthly cost. Your job is to surface that cost.
Open with a one-page diagnostic
Before you talk scope or price, open with what’s wrong. One page, four bullets, plain language.
A typical diagnostic looks like:
- Current load time: 4.8 seconds on mobile (industry benchmark: under 2.5s)
- Estimated mobile bounce rate: 62 percent (industry median for your space: 45 percent)
- Visible conversion paths: 1 (homepage contact form, buried below the fold)
- Trust signals on key pages: none above the fold
You don’t need a 40-page audit. You need four lines that make the client uncomfortable. The discomfort is what justifies the rest of the proposal.
Translate the diagnostic into money
This is the part most freelancers skip and it’s the single biggest lever in any proposal for a website redesign project.
Take the numbers you have (their traffic, their conversion rate, their average deal size) and write a single paragraph that translates the diagnostic into monthly revenue lost. You don’t need precision. You need a defensible range.
Example phrasing the client should be able to read in 30 seconds:
Your site is doing roughly 4,200 monthly visits with what looks like a 1.1 percent contact-form conversion. That’s 46 leads a month. Your average deal sits around 3,200 dollars and your close rate on form leads is about 22 percent. Moving conversion to the industry median of 2.8 percent (achievable with the changes outlined below) would put you at 117 leads, closing 25, adding roughly 80k in monthly revenue.
That paragraph does more work than 20 pages of design rationale. The redesign fee now reads as small.
The scope section that prevents scope creep
After the diagnostic and the money paragraph, the scope section is where most redesign projects go wrong six months later. Be specific.
For a typical mid-sized redesign, you want explicit line items for:
- Sitemap definition (how many pages, named)
- Wireframes (how many rounds)
- Visual design (how many concepts, how many revision rounds)
- Development (CMS, framework, hosting target)
- Content migration (number of pages, who writes net-new copy)
- 301 redirect map for every URL that changes
- Third-party reconnection (analytics, CRM, marketing automation, forms, chat, payment)
- QA across browsers and screen sizes
- Launch and post-launch monitoring window
Each line gets a one-sentence definition of done. “Done” for wireframes is not the same as “done” for visual design and not knowing the difference is how proposals turn into 14-month projects.
Price anchoring with three tiers
A single price in a proposal for a website redesign project asks the client to compare your number against zero. Three tiers ask them to compare your numbers against each other, which is the comparison you want.
A clean three-tier structure:
| Tier | What’s included | Price |
|---|---|---|
| Core | Sitemap, design, build, migration of top 10 pages | Base |
| Recommended | Core plus copy rewrite, full content migration, 90-day post-launch optimization | Base + 40% |
| Full | Recommended plus phase 2 SEO foundations and conversion testing setup | Base + 90% |
Most clients pick the middle. That’s the point. The Core option exists to make the middle look reasonable. The Full option exists to make the middle look modest.
Address the awkward questions in writing
Every redesign client has the same three unspoken questions. Answer them in the proposal so they don’t have to ask.
- What happens to our SEO? (Answer: redirect map covers every changed URL; rankings typically dip for 2-4 weeks then recover.)
- What if we hate the design? (Answer: revision rounds are bounded; concept stage has a kill switch; you have not committed to the build until concept signoff.)
- What if it’s late? (Answer: timeline assumes client feedback within X business days; if feedback runs longer, dates shift accordingly; here’s the exact dependency map.)
Putting these in writing positions you as someone who has done this before. The client relaxes. Relaxed clients sign.
The “what your current site costs you” sidebar
A small visual element worth adding: a sidebar or callout that restates the monthly loss number from the diagnostic. Something the eye lands on while the brain is reading the price.
Example callout text:
Estimated monthly revenue impact of current site issues: 65k to 90k. Redesign investment: 22k one-time. Payback window at the low end of projected gains: under 60 days.
You’re not promising the payback window. You’re framing the relative scale of the numbers. The client’s brain finishes the comparison on its own.
Timeline and dependencies, not just a Gantt chart
Most redesign proposals show a generic timeline like “8 weeks.” Real projects break that promise by week three.
Instead, show a dependency-aware timeline. List each client-side dependency (content delivery, brand asset handoff, stakeholder review windows) with the date by which it must arrive for the launch date to hold. Then put a single sentence under the timeline: “If any dependency slips, downstream dates shift accordingly. We will flag in writing within 24 hours.”
This protects you when things slip (they always slip) and makes you look organized in the proposal.
Close with the smallest possible next step
End the proposal with one question, not a contract.
If the diagnostic feels right, the next step is a 30-minute call to align on sitemap and pick a tier. After that call I’ll send a finalized SOW and a deposit invoice.
You’re not asking them to sign a 22k contract from a PDF. You’re asking them to book a 30-minute call. The call is easy to say yes to. The signature happens at the end of the call when you’ve already agreed on tier and scope live.
A note on engagement tracking
A proposal you send and never hear back on is not necessarily a dead proposal. It’s a proposal you have no information about. Sending it through something that tells you when it was opened, which sections got the most time, and whether the price tier table got scrolled to changes how you follow up. If they spent four minutes on the diagnostic and twelve seconds on the price page, the follow-up is about the diagnostic. If they spent two minutes on the tier table, the follow-up is “did you have questions about what’s in the middle tier?”
That information is the difference between a follow-up that lands and one that gets ignored.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
