Website Redesign Cost: Scope Before Price

How much does a website redesign cost?

The same tiers are listed on our pricing page, and the inputs that move a quote between them are broken down in our website cost guide.

Before comparing any two redesign quotes, check they are quoting the same project. A proposal labeled redesign that also moves you to a different CMS, a different host or a different framework is a rebuild, and it should be compared against rebuild proposals rather than redesign ones. The reverse happens too: a quote that leaves out the design system, the content work or the rollout is cheaper because it is smaller, not because it is better value.

What does it cost to update an existing website instead?

There is a genuine middle case too. Restyling a design system you already own, meaning typography, spacing, color and component states, refreshes every page at once without rebuilding any of them, and it is a fraction of a redesign. That option only exists if the current site was built on a consistent system in the first place, which is exactly what the design-system section below is about, and it is the strongest argument for building one even when it costs more upfront.

How often should a website be redesigned?

The honest version of the age argument is narrower than it sounds. Sites do decay, but usually in specific places rather than all over: a stack nobody patches, an accessibility standard that has moved on, a checkout that no longer matches how people pay. Those are repairs with names and prices. “It looks dated” is a real problem too, and it is a reason for a restyle before it is a reason for a rebuild.

"A redesign changes the experience on the platform you already have. It is not the same project as a rebuild.

The four variables to price first

• ✓
  How deep the experience work goes: researching journeys, restructuring the site, accessibility, and testing with real people.
• ✓
  Design-system depth: visual direction, components, states, responsive rules and documentation.
• ✓
  How much content work: listing what exists, rewriting it, the media, structuring it, translation, and getting it approved.
• ✓
  How much delivery work: the templates, integrations, analytics, testing, any experiments, the rollout, and training your team.

Those four variables are what carry a redesign from $1,500 to $10,000 across our own tiers, and raw page count is the weakest predictor of where it lands. Ten pages using ten templates can be more work than one hundred pages generated from a stable content model. Ask each provider to expose the templates, components, content responsibilities and review process behind the price.

Two more inputs move the number and are easy to leave off a brief. The first is how many people have to approve the design direction: one owner deciding in a single session is a different project from a marketing team, a founder and an external stakeholder each needing sign-off, because every additional approver adds review cycles and the chance of a late reversal. The second is urgency. A compressed deadline forces parallel work streams and shortened review windows, both of which cost more than the same work run at a normal pace. Be honest about the real date something has to be live, which is often later than the date first quoted to us.

Small-business and mid-market scope

A focused owner-led site may need a light journey review, a small component set and direct approval. A mid-market site may add research, stakeholder workshops, more templates, a formal design system, accessibility evidence, analytics continuity and a staged release. These are scope differences, not automatic labels based on employee count or page count.

A/B testing and staged rollout

The reason to test at all is that a redesign is not automatically an improvement. A new layout can bury an action that used to be obvious, and a navigation that looks cleaner can make the pages people actually came for harder to reach. Nielsen Norman Group reports that only one in every seven A/B tests is a winning test. That figure covers design changes in general rather than redesigns specifically, but it is the right expectation to carry into the project: plan to find out whether the new version is better, instead of treating the question as settled because it looks better.

A valid experiment needs enough eligible traffic, a defined primary outcome, guardrails, assignment logic, instrumentation and a pre-agreed decision rule. Low-traffic sites may learn more from moderated tasks, prototype tests or a staged page release. Do not promise a fixed uplift or treat bounce rate alone as proof that the new design is better.

Redesign vs rebuild vs migration

Each of those paths is costed differently, so price the one you actually need. We cover rebuild cost drivers and migration cost drivers separately, and the scope of a platform move sits on the WordPress, Webflow, Squarespace and Wix migration pages.

Hidden costs to put in the proposal

• ✓
  The URL map and 301 redirects. If any address changes, every old URL needs a destination, and this is the line most often left out of a redesign quote entirely. It is scoped by URL count rather than page count, so a 40-page site with a decade of blog archive and campaign URLs can carry thousands of them.
• ✓
  Content cleanup, missing assets, copy approval and localization.
• ✓
  Additional template, component, state and breakpoint work.
• ✓
  Accessibility review, analytics changes and regression testing.
• ✓
  Vendor licenses, third-party implementation and platform constraints.
• ✓
  Extra review rounds, delayed feedback, rework after approval and rush requests.
• ✓
  Training, launch monitoring, support and future maintenance.

What should the design system include?

Name foundations such as color, typography, spacing and layout; reusable components and their states; responsive behavior; accessibility requirements; content rules; and the source of truth handed to the client. A component screenshot without behavior and state coverage is not a complete implementation specification.

There is a real decision underneath this, and it is not a technical one. The cheapest possible redesign restyles an existing theme or page-builder preset: new palette, new type, new photography, same underlying components. It is quick, and it is also why so many sites in the same sector resemble each other. A system designed for the business costs more upfront because someone has to make deliberate decisions about type, spacing, color roles and component states instead of accepting defaults. The return arrives later, when a new page type in month eight is an application of the existing system rather than a fresh round of design. Neither route touches your platform. The question is how distinct and how durable the result needs to be.

Ask for the list of every distinct page template the system has to cover before you sign. A system scoped against a homepage and two interior pages will need extending the first time a pricing page, a resource hub or a location page needs its own layout decisions.

Fixed price vs hourly work

We quote redesigns fixed, at $1,500, $3,500 or $5,000 depending on scope, and price anything outside that scope through an approved change request. Fixed price works when deliverables, assumptions and review boundaries are defined. Hourly or weekly work fits discovery, uncertain legacy systems or client-directed changes. Neither model guarantees quality on its own, so the question is which one matches how well-defined your project actually is.

Agency, freelancer or in-house team?

Compare the people assigned, senior involvement, availability, research depth, design and engineering responsibilities, QA evidence, change handling and handoff. Provider type alone does not establish cost, quality or accountability. Our guide to what an agency should own lists the roles to check, and how to vet a low-cost developer covers the evidence to request when the quote is the deciding factor.

How to evaluate the cost of no redesign

The cost of leaving it alone is whatever the current site makes harder, measured on your own numbers rather than an industry average: support contacts, task failure, accessibility defects, the time it takes your team to publish, abandoned form steps and measured funnel loss. Quantify those. Separate observed facts from assumptions, calculate a range, and compare it with the least expensive intervention that could address the problem. Where the complaint is speed rather than design, the route-level speed diagnostics will tell you whether a redesign is even the right fix.

The problems a redesign is the right answer to tend to look like these:

• ✓
  Visitors cannot find the page that answers their question, or the action they came to take is buried below content they did not ask for.
• ✓
  The structure and copy describe an older version of the business: a retired product line, a superseded pricing model or positioning the company has moved past.
• ✓
  The design was adapted to phones rather than designed for them, and the majority of visits arrive that way.
• ✓
  The site reads as untended, which for a considered purchase becomes a question about the business rather than about the website.

Frame the case on those grounds rather than on speed. A same-platform redesign changes what visitors see and how they move through it. It does not change what the platform underneath costs, how fast it serves, or how it is maintained, so if those are the actual complaints, price a migration or a rebuild instead and read the guides linked above.

How to justify the budget internally

• ✓
  State the current problem and attach the evidence. Use findings from your own audit and analytics rather than a generic benchmark that may not describe your traffic.
• ✓
  Define the affected users, journeys and business process.
• ✓
  Compare repair, redesign, migration and rebuild options.
• ✓
  Show one-time and ongoing cost, internal effort and risk.
• ✓
  Put your current site beside the sites your buyers also consider. A side-by-side is usually the fastest way to make the positioning gap legible to people who do not read analytics.
• ✓
  Name acceptance criteria and the measurement plan. Agree which numbers you will read, and set the before and after windows in advance so the comparison is not chosen after the fact.
• ✓
  Record what will not be solved by the redesign.

How to reduce redesign cost safely

• ✓
  Assign one accountable approver and schedule feedback windows.
• ✓
  Approve the route, template and content inventory before design.
• ✓
  Resolve brand and copy decisions before implementation.
• ✓
  Reuse valid components and content rather than rebuilding by habit.
• ✓
  Consolidate thin or duplicate pages before design starts. Fewer, stronger pages cost less to redesign and less to maintain afterwards.
• ✓
  Spend the design budget on the handful of pages that carry the work, and let the rest run on shared templates.
• ✓
  Phase lower-priority templates without creating duplicate systems.
• ✓
  Defer extras such as additional languages, bespoke animation or custom dashboards until there is demand that justifies them, and scope them as a later phase rather than cutting them mid-project.
• ✓
  Freeze the launch scope and use written change requests.

Questions to ask before signing

The ownership question is the one buyers most often leave until the end. Settle it first using do you own your website.

• ✓
  Which routes, templates, components, breakpoints and states are included?
• ✓
  Who writes, migrates, approves and enters the content?
• ✓
  How many review rounds and decision-makers does the schedule assume?
• ✓
  What accessibility, browser, analytics, SEO and performance evidence is required?
• ✓
  What counts as acceptance, a defect and an out-of-scope change?
• ✓
  Who owns source files, code, accounts and third-party licenses?
• ✓
  What launch, rollback, support and termination terms apply?
• ✓
  Is this a single relaunch or a staged release, and what do visitors see during the interim?
• ✓
  Do the URLs stay as they are? Where pages are merged or renamed, who writes and tests the redirects?

PandaCodeGen offer and terms

We start with a free fit audit and use it to prepare a migration or redesign plan. Recent project pages show the scope behind each build. A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. Refund is tied to failure to deliver the signed scope, not a preference change after work starts. Starter includes 15 business days of launch defect support and Growth and Scale carry 30, where the accepted terms include it. Minor tweaks may be included when agreed, while larger changes require an approved scope change.

Frequently asked questions

Primary sources

• WCAG 2.2
• Nielsen Norman Group: A/B testing