Website Redesign Planning: Scope, Budget & Timeline

Here's the uncomfortable truth about website redesigns: most of them go sideways. Only 29% of projects finish on time and on budget, according to the Standish Group CHAOS Report. That's not a rounding error—it means roughly seven out of ten website projects blow past their deadline, their budget, or both. And the people writing the checks rarely see it coming until they're already deep into the build.

The fix isn't a better designer or a fancier platform. It's better planning. This article walks through every phase of a website redesign—from deciding whether you even need one, to scoping the project, setting realistic budgets, building timelines that won't collapse, picking the right partner, and protecting your SEO through the transition. If you're about to spend $15K to $50K on a redesign, the next 19 minutes could save you from the mistakes that sink most projects.

For a tactical execution companion, pair this planning guide with our 25-point redesign checklist that covers the build and launch phases step by step.

Do You Need a Redesign, a Refresh, or a Rebuild?

Most redesigns start with the same complaint: "our site looks old." But looking dated isn't always a reason to tear everything down. A GoodFirms survey found that 80.8% of redesigns are triggered by low conversion rates, not aesthetics. Before you write a check, figure out which category your project actually falls into.

Refresh: New Paint, Same Structure

A refresh updates colors, fonts, imagery, and minor layout tweaks without changing the underlying architecture. Think of it as repainting a house instead of rebuilding it. Cost: $3,000 to $10,000. Timeline: 4–6 weeks. This is the right move when your brand is strong, your content works, and the site just feels visually dated.

Redesign: New UX, Content, and Structure

A redesign rethinks the user experience, information architecture, and content strategy. You're rearranging rooms and possibly adding new ones. Cost: $15,000 to $50,000. Timeline: 3–6 months. Choose this when conversions are poor, the mobile experience is broken, or your business model has shifted since the site was built.

Rebuild: New Platform and Architecture

A rebuild means moving to an entirely new platform or tech stack. You're demolishing the house and starting from foundation. Cost: $50,000 to $250,000 or more. Timeline: 6–12 months. Only do this when your current platform genuinely can't support your needs—for example, migrating from a page builder to a custom React application because you need dynamic functionality the old system can't handle.

Start with data, not feelings. Pull your Google Analytics conversion data, check your mobile usability reports, and audit your page speed. If the structure works but the design doesn't, you probably need a refresh. If the structure itself is the problem, that's a redesign.

How Much Does a Website Redesign Cost in 2026?

The average B2B website redesign costs $42,500 according to a 2025 survey by Rick Whittington Associates. But averages mask wide variation. A 15-page small business site costs a fraction of what a 100-page enterprise portal requires. Here's what to expect based on your project scope.

Cost Ranges by Business Size

Small business redesigns (10–20 pages) typically run $15,000 to $40,000. Mid-market projects (30–75 pages) fall in the $40,000 to $100,000 range. Enterprise sites with 100 or more pages start at $100,000 and can exceed $250,000 when custom integrations, multilingual support, or complex application features are involved.

Where the Budget Actually Goes

Most clients are surprised by how much of the budget goes to content. "Nobody told us we'd need to write all the content ourselves" is one of the most common complaints in post-project surveys. Content and copywriting account for 15–20% of a typical redesign budget. Skipping the content budget doesn't save money—it just delays the project by weeks while someone scrambles to write page copy at the last minute.

Large IT projects run 45% over budget on average, according to McKinsey research. Website redesigns are no exception. Build a 15–20% contingency into your budget from day one. If you don't use it, great. If you do, you won't be scrambling for approval mid-project.

For a deeper breakdown of what websites cost across different project types, see our website cost breakdown covering everything from templates to custom builds.

What's a Realistic Timeline for a Website Redesign?

Small sites (10–20 pages) take 8–12 weeks. Mid-sized sites (30–75 pages) take 12–16 weeks. Enterprise sites (100+ pages) take 16–24 weeks or more, according to timeline benchmarks from Webstacks, based on hundreds of B2B redesigns. Here's what a typical 16-week project looks like.

Content Is Always the Bottleneck

Notice how content production starts in Week 3, not Week 10. That's intentional. Content delays are the number one reason redesigns miss deadlines. Most teams treat copywriting as an afterthought—something to "fill in later" once the designs are approved. Then Week 10 arrives, the design is ready for development, and nobody has written a single page.

Start writing content the same week you begin wireframes. Assign specific pages to specific people with hard deadlines. If your internal team can't produce the content, budget for a copywriter from day one. We've seen more projects slip on content than on any technical challenge. For help building your content strategy, plan it before the redesign kicks off.

How Long Before the Next Redesign?

The average website lifespan is 2.5 years, and top marketing brands redesign every 2 years and 1 month, according to Orbit Media Studios. But calendar-based redesigns waste money. Redesign when your data tells you to—declining conversions, rising bounce rates, or a broken mobile experience—not because two years have passed.

How Do You Prevent Scope Creep?

Scope creep affects 52% of projects and ranks as the third leading cause of project failure, according to the Project Management Institute (PMI). It usually doesn't start with a big ask. It starts with "can we just add one thing?" repeated a dozen times.

Use MoSCoW to Lock Down Priorities

MoSCoW stands for Must-Have, Should-Have, Could-Have, and Won't-Have. Before development starts, categorize every feature and page into one of those buckets. Must-Haves ship at launch. Should-Haves are next-sprint items if there's time. Could-Haves go on the post-launch roadmap. Won't-Haves get officially killed. The power of MoSCoW isn't the framework itself—it's that everyone agrees in writing before a single line of code is written.

What Your Scope Document Must Include

A proper scope document lists every page, every feature, every integration, and every content responsibility. Who writes the homepage copy? Who provides product photos? Who approves final designs? Ambiguity here is where scope creep breeds. If it's not in the document, it's not in the project.

The Change Order Process That Saves Projects

Every addition after scope sign-off requires a written change order. The change order documents what's being added, the estimated cost, the timeline impact, and requires sign-off before work begins. No exceptions. This isn't about being difficult—it's about making the true cost of "just one more thing" visible before anyone commits.

How Do You Protect Your SEO During a Redesign?

Site owners frequently report losing 30–60% of their organic traffic after a redesign when redirects are missed. That's months or years of search authority wiped out in a single deployment. The most common cause isn't a technical mystery—it's simply failing to redirect old URLs to new ones.

301 Redirect Mapping Is Non-Negotiable

Before you launch, build a spreadsheet that maps every existing URL to its new URL. Every single one. If a page changes its slug, gets merged with another page, or moves to a different section, it needs a 301 redirect. If a page is being removed entirely, redirect it to the most relevant remaining page. Our SEO migration checklist walks through this process step by step.

Migrate Your Metadata

Title tags, meta descriptions, canonical URLs, and schema markup all need to transfer to the new site. Don't assume your CMS will handle this automatically. Export your metadata from the old site before you touch anything, then verify each page after launch. Missing a canonical tag can create duplicate content problems that take months to untangle.

Audit Internal Links Before and After Launch

Broken internal links hurt your crawl efficiency and pass zero authority. Run a full crawl before launch to establish a baseline, then run it again within 24 hours of going live. Tools like Screaming Frog make this painless. Fix any broken links immediately—don't add them to a backlog. For ongoing monitoring, set up Google Search Console alerts and check coverage reports daily for 30 days post-launch.

Don't forget Core Web Vitals. If your new site is slower than the old one, you could lose rankings even with perfect redirects. Run Lighthouse tests on staging before launch and set performance baselines for LCP, FID, and CLS.

How Do You Choose the Right Redesign Partner?

The partner decision affects budget, timeline, and quality more than any other single variable. A great designer with poor project management will still deliver a late, over-budget project. Your choice between a freelancer, an agency, and an in-house team changes the risk profile of the entire engagement.

Freelancer vs Agency vs In-House

Freelancers cost $2,000 to $10,000 and work well for simple sites. But there's a real risk of ghosting mid-project—we've inherited projects where "our developer ghosted us halfway through." Agencies cost $10,000 to $50,000 or more but bring a full team, established processes, and accountability structures. In-house hiring costs a full-time salary but makes sense when you need ongoing iteration, not a one-time project.

Five Questions to Ask in Discovery

First, ask to see portfolios of similar projects—not just their best work, but work for businesses like yours. Second, get timeline commitments in writing, not verbal estimates. Third, ask who will actually do the work. Some agencies sell with senior talent and deliver with juniors. Fourth, ask what happens when scope changes—do they have a formal change order process? Fifth, clarify post-launch support. Who fixes bugs on Day 2?

Red Flags to Watch For

Walk away from any partner who skips a discovery phase. If they're quoting a price without understanding your business, they're guessing. Other red flags: no content plan in the proposal, unwillingness to share a detailed timeline, and requesting 100% payment upfront. A reasonable payment structure is 30–40% to start, milestones tied to deliverables, and 10–20% held until 30 days post-launch.

For a deeper evaluation framework with scoring templates, read our guide to choosing an agency.

Your Post-Launch 90-Day Roadmap

Launch day isn't the finish line—it's the starting line for optimization. Every $1 invested in UX returns $100, according to Forrester Research. But that ROI only materializes if you monitor, measure, and iterate after the site goes live. Most teams celebrate launch and then neglect the site for months. Don't be that team.

Days 1–7: Fix What's Broken

Monitor your 301 redirects, hunt for 404 errors, and verify that analytics tracking is firing correctly on every page. Check form submissions, payment flows, and third-party integrations. This is triage week. Conversion rates drop 4.42% per additional second of load time, according to Portent. If your new site is slower than the old one, fix performance issues before anything else.

Days 8–30: Baseline and Quick Wins

Establish your conversion baseline with the new design. Compare against pre-launch data. Look for pages with high traffic but low conversions—these are your first CRO targets. Quick wins like adjusting CTA button placement, simplifying form fields, or improving above-the-fold messaging can move the needle within weeks.

Days 31–90: Optimize and Test

By Day 30, you should have enough data to identify underperforming pages. Update content based on real analytics, not assumptions. By Day 60, start A/B testing headlines, CTAs, and page layouts. By Day 90, you should have a clear picture of what's working and a roadmap for continuous improvement. Check out our ongoing maintenance guide for what comes next.

Pair your post-launch monitoring with proper GA4 setup to make sure you're tracking the right events from Day 1. And if UX drives revenue at a 100:1 ratio, every week you delay optimization is money left on the table.

Frequently Asked Questions

Planning Is the Cheapest Part of a Redesign

Every dollar you spend on planning saves five to ten dollars on execution. The teams that blow their budget and timeline almost always share the same problem: they started building before they finished thinking. Scope creep, content delays, and missed SEO migration steps are all planning failures, not execution failures.

Here's your action list. First, decide if you need a refresh, redesign, or rebuild—based on data, not gut feelings. Second, build a realistic budget with a 15–20% contingency. Third, create a timeline that starts content production in Week 3, not Week 10. Fourth, write a scope document with MoSCoW priorities and a change order process. Fifth, map every URL redirect before launch. Do those five things and you'll already be ahead of 70% of projects.

Your redesign doesn't have to be one of the 71% that misses its targets. Plan it right, and it won't be. For the step-by-step execution checklist, grab our redesign checklist and pair it with the accessibility compliance guide to cover all your bases.