A solid redesign proposal spells out goals and success metrics, a sitemap and page count, scope of design and development work, content and migration responsibilities, a 301 redirect plan, technology and hosting, timeline with milestones, a line-itemed price, and exactly who owns the finished site, code, and accounts.
- A complete proposal defines a sitemap and exact page count up front — vague scope like "approximately 8–12 pages" is the single biggest source of mid-project budget disputes.
- A 301 redirect map should be named as a launch deliverable; redesigns that change URLs without redirects routinely lose a large share of organic traffic to sudden 404s.
- Content responsibility must be assigned explicitly — who writes the copy is the most common gap that stalls projects, since a built-but-empty site can't launch.
- In Canada, a templated or WordPress redesign typically runs $5,000–$15,000 CAD, while a custom build on a modern stack like Next.js runs $15,000–$50,000+ CAD.
- The proposal should state plainly that you own the finished site, the code, the domain, the hosting, and the CMS logins — not the agency.
The Sections Every Real Proposal Contains
A website redesign proposal should read like a contract you could hand to a stranger and have them build the right thing. At minimum it contains nine parts: goals and success metrics, scope, a sitemap, content ownership, an SEO and redirect plan, technology and hosting, timeline, price, and ownership terms. If a quote is missing several of these, it isn't a proposal — it's a number with a logo on it.
Goals and metrics come first because they justify everything else. A redesign should name what it's trying to move — more qualified leads, a faster mobile experience, the ability to edit your own pages, a layout that converts paid traffic. "Make it look modern" is a preference, not a goal, and it's how businesses spend a five-figure budget and land at the same rankings and the same conversion rate.
Scope is the heart of the document. It lists what's being designed and built, page by page, and just as importantly what isn't — so nobody discovers in week six that the booking integration or the multilingual version was never included. The remaining sections exist to remove ambiguity from scope: the sitemap turns it into a concrete page count, content ownership says who fills those pages, the redirect plan protects what you already rank for, and the technology section says what it's built on.
Read a proposal looking for what it leaves unsaid. The expensive surprises in a redesign almost never come from the work that's described — they come from the work everyone assumed someone else was doing. A good proposal's job is to make those assumptions explicit before a single pixel is designed.
Scope, Sitemap, and Who Writes the Content
The three places redesigns go over budget are scope creep, an undefined page count, and unwritten content — so a strong proposal nails all three before you sign.
Scope and sitemap. The proposal should include a sitemap: a named list of every page the new site will have — Home, each service page, each location page, About, Contact, blog, and so on — with an exact count. "Roughly 10 pages" is the phrasing that ends in arguments; "these 14 specific pages" is the phrasing that ends in a finished site. The count drives the price, so vagueness here is vagueness in the bill. The proposal should also state how many design concepts and revision rounds are included, because "unlimited revisions" rarely is, and "two rounds" at least tells you where the meter starts.
Content ownership. This is the gap that stalls more projects than any other. Someone has to write the words for every page, and a beautifully built site with no copy cannot launch. The proposal must say plainly whether the agency is writing the content, you are, or it's split — and if you're writing it, that you understand the build pauses until the words arrive. Copywriting is real work; if it's included, it should be a line item, not an assumption.
Watch for scope written to flatter the quote: a low price that quietly excludes content, image sourcing, third-party integrations, or post-launch fixes isn't cheaper, it's incomplete. Ask directly what happens to the price if you add a page, need a form integrated, or want the copy written for you. The answers tell you whether you're reading a real plan or an opening bid.
The SEO and Redirect Plan — The Part Most Quotes Skip
If a redesign proposal doesn't mention 301 redirects, keep shopping — that omission alone can cost you months of traffic. Your current site, however dated, has accumulated equity: indexed URLs, backlinks, and ranking history. A redesign that changes URLs without mapping them forward turns every ranking page into a 404, and Google quietly drops them.
A competent proposal names a redirect map as a launch deliverable: every old URL that earns traffic or has links pointing at it gets mapped to its new equivalent and 301-redirected before go-live. It should also commit to content parity — pages that rank today survive the redesign with equal or better content, rather than getting "cleaned up" out of existence during a navigation tidy.
Beyond redirects, the technical section should cover the SEO fundamentals that are far cheaper to build in than to retrofit: clean titles and metadata per page, proper heading structure, fast mobile performance (Google indexes the mobile version first, and its Core Web Vitals guidance asks for the main content to paint within about 2.5 seconds), structured data where it applies, and an XML sitemap. None of this is exotic — it's table stakes — but it's routinely absent from design-led quotes because the designer is thinking about layout, not rankings.
The proposal should also be honest about the launch window: expect a few weeks of ranking fluctuation while Google recrawls the new structure. That's normal. A cliff that doesn't recover signals a redirect or parity mistake. A proposal that treats search visibility as something to handle "later, separately" is one that's planning to hand you a prettier site that fewer people find — which is the opposite of why most businesses redesign.
Timeline, Price, and Who Owns the Result
The last three sections are where you find out whether you'll get the site on time, what it truly costs, and whether it's actually yours when it's done.
Timeline with milestones. A real proposal breaks the project into stages — discovery, sitemap and wireframes, design concepts, build, content load, QA, launch — each with a date and a clear sign-off point. This matters because most redesign delays are caused by the client, not the agency: feedback that takes three weeks, copy that never arrives. Milestones make those dependencies visible, so a stalled project has an obvious cause instead of a vague sense that it's late.
Price, line-itemed. The number should be broken down — design, development, content, integrations, migration, post-launch support — not a single lump sum. In Canada, a templated or WordPress redesign typically runs $5,000–$15,000 CAD; a custom build on a modern stack like Next.js runs $15,000–$50,000+ CAD depending on page count and functionality. The proposal should also state payment terms, what hosting and maintenance cost ongoing, and what's covered in the post-launch period if something breaks.
Ownership — the clause people forget to check. The proposal should say in plain language that when the project is paid for, you own the finished website, the source code, the domain, the hosting account, and every CMS and analytics login. Some agencies build on proprietary platforms you can never export, or register the domain in their own name, which quietly locks you in. At SearchPod, client ownership is the default and the work is month-to-month — your site and your accounts are yours to take anywhere. A proposal that's silent on ownership is one to ask about before, not after, you sign.
Related questions
Length matters less than coverage. A clear two-to-four-page proposal that nails scope, sitemap, content responsibility, redirects, timeline, price, and ownership beats a twenty-page document padded with stock photography and mission statements. Judge it by whether a stranger could build the right site from it, not by page count.
A quote is a price. A proposal is the price plus everything that justifies it — defined scope, a sitemap, who writes the content, the redirect plan, the timeline, and ownership terms. A bare quote leaves all the expensive assumptions unwritten, which is exactly where redesigns blow their budgets. Always ask for the proposal behind the number.
Yes — and its absence is a red flag. Changing URLs without 301 redirects turns your ranking pages into 404s and can lose a large share of organic traffic overnight. A competent proposal names the redirect map and content parity as launch deliverables. If yours doesn't mention them, ask, or keep shopping.
You should — assuming the project is paid for. A good proposal states plainly that you own the finished site, the source code, the domain, the hosting, and the CMS logins. Watch for agencies that build on proprietary platforms you can't export or register the domain in their own name; that's lock-in, and it should be settled in writing before you sign.
A templated or WordPress redesign typically runs $5,000–$15,000 CAD, and a custom build on a modern stack like Next.js runs $15,000–$50,000+ CAD, depending on page count, custom functionality, and whether copywriting is included. Quotes well below these ranges usually exclude content, migration, or post-launch support — read the scope, not just the total.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get Free Proposal →