The thing that makes a redesign quote different from a new-site quote is the site you already have. A new build starts from an empty folder. A redesign starts from an accumulation — URLs, content, search history, forms, domains, integrations, licensed assets, analytics, and a pile of operating knowledge nobody ever wrote down. Some of that accumulation is valuable and saves you money. Some of it is wired to a former employee's inbox and will cost you money the week after launch. Either way, it is the hidden variable in the price, and it moves the number more than the count of new pages does.

That is also why no honest provider can name a redesign price from the title alone. "Redesign" is one word for at least four different projects, and they don't cost the same:

  1. a visual reskin;
  2. a restructuring of pages and content;
  3. a migration to another platform; or
  4. a rebuild that changes the site, its integrations, and the way inquiries are handled.

The question worth answering before you collect quotes is which of those four you're actually buying, and what the existing site forces the project to preserve. Everything below is in service of answering it.

The four projects that share one name

A visual reskin keeps most of the content, structure, platform, URLs, and functionality and concentrates on presentation — type, color, spacing, components, imagery. It's the narrowest version and often the right one when the information is sound and only the look is dated. It stops being narrow when the existing templates fight every change or the mobile behavior needs rebuilding underneath.

A content and structure redesign changes what the site says and how visitors move through it. Services get split or combined, pages get rewritten, navigation and proof and calls to action shift. Even on the same platform, you've now bought strategy, information architecture, content production, review, and usually some URL decisions. The expensive part isn't moving boxes around a page; it's deciding which business facts matter, how to organize them, and who has the authority to approve them.

A platform migration moves the site to a different content-management system, builder, host, or architecture. The front end can look identical while nearly everything underneath changes: templates, content fields, forms, integrations, redirects, analytics, permissions, backups, deployment. Google's site-move guidance treats this as a project with real steps — map old URLs to new, use permanent redirects, update internal links and canonicals, test, and monitor the move — not a switch flipped at the end. The redesign-and-search article walks that migration in full.

A business-system rebuild is the deepest version, because it changes the path from visitor to inquiry, not just the presentation. It may add or replace forms, saved submission records, notifications, analytics events, scheduling, call tracking, or CRM handoffs, and it usually has to define where the website's record ends and your human follow-up begins. Two proposals can both say "website redesign" while one prices a new coat of paint and the other prices an observable lead path. They should not carry the same number.

What the old site gives you, and what it hides

An existing site is not automatically a liability. It often holds material that reduces the work: accurate service content, strong photography, real customer questions, pages already earning search traffic, working integrations, reusable brand assets, and a structure that mostly makes sense. A good provider mines that before rebuilding it.

The same site can also hide work you'll pay for whether or not anyone predicted it: duplicate or obsolete pages, changed URLs with no redirect history, forms wired to people who left, domains and software living in a vendor's account, analytics nobody can administer, undocumented code, expired licenses, inaccessible components, and old ad campaigns still pointing traffic at forgotten pages. This is why an inventory improves an estimate — it replaces the vague promise "we'll migrate the site" with a countable set of decisions, and countable decisions are what a dependable price is built on.

The nine drivers that actually move the number

Unique page types, not raw page count. Twenty location pages built from one approved pattern can be less work than eight pages that each need a different structure, proof model, and review. Ask how many distinct templates the project requires, which pages reuse them, and who enters the content.

Content condition. Content can be kept, lightly edited, rewritten, freshly researched, or retired — each a different amount of work. Even "reuse everything" still requires someone to inventory it, check it, and fit it to the new structure. Content responsibility is also a schedule driver: a lower estimate that quietly assigns all the writing and approvals to you is an honest option, but it is not the same product as one that supplies interviews, drafts, and editing.

URL and search preservation. An established site can carry years of URLs, links, and indexed pages. When URLs change, a responsible redesign needs a map from old to new, permanent server-side redirects to the most relevant destination, updated internal links, and monitoring afterward. The project doesn't need to preserve every weak page — it needs to decide on purpose what happens to the important ones. The larger and messier the inventory, the more work lands in discovery, migration, and post-launch monitoring.

Platform and hosting change. Staying put can reduce migration work but doesn't guarantee a simple project; a broken theme still needs a rebuild. Changing platforms introduces new content models, account structures, form systems, redirect tools, and transfer rules — some features move cleanly, others must be recreated. Price the platform decision together with the exit plan, because a cheap migration is not cheap if you cannot operate or leave the result later. Ownership and exit terms deserve their own review, with qualified legal advice when the stakes warrant it.

Forms and lead handling. A single form with one email alert is a smaller scope than a lead path with a saved record, routing rules, status evidence, spam handling, attribution, and a defined handoff. For each form, settle the fields and validation, where the submission is stored, who is notified, what happens if the notification fails, which marketing context is retained, what data you deliberately don't collect, and which later steps belong to you rather than the provider. The goal isn't to make every form complicated — it's to stop calling fundamentally different systems "a contact form."

Third-party integrations. Scheduling, payments, reviews, maps, email marketing, call tracking, CRM, chat, and portals each add a dependency. An integration line should say whether it's an embed, an official connector, an automation, or custom work — "integrate CRM" can mean ten minutes of configuration or a small software project, and the proposal shouldn't make you guess which one is priced.

Design originality and interaction. A well-used component system isn't inferior to a one-off design; reuse is often how a site stays consistent and maintainable. Cost rises with multiple original directions, custom illustration, photography, animation, and uncommon interaction. Motion and novelty have a way of charging rent across design, development, testing, and maintenance, so it's worth asking which flourishes improve the visitor's task and which are decoration.

Accessibility and quality remediation. A redesign is a chance to fix headings, keyboard use, focus, contrast, text alternatives, and responsive behavior. Remediation gets more expensive when the project drags along inaccessible third-party tools, large media libraries, PDFs, or content the team can't change. The scope should state what practices guide the work, what's tested, and what stays outside the provider's responsibility.

Approval complexity. The number of decision-makers can matter as much as the number of pages. An owner who can decide moves faster than a committee that sees the homepage for the first time at final approval. That complexity shows up as meetings, revision rounds, rework, and waiting — so a good proposal names the reviewers, the milestones, the included revision rounds, and the cost of late approvals.

The cost-driver matrix

Use this before you request estimates. It won't calculate a quote; it tells you whether two quotes are even describing the same problem.

Cost driver Lower-complexity condition Higher-complexity condition What to inventory
Page system Few reusable page types Many unique templates and interactions Pages grouped by type
Content Accurate and reusable New research, interviews, rewrites Keep / edit / create / retire status
URLs Most stay unchanged Many important URLs change Sitemap, analytics, links, redirects
Platform Same system and accounts New CMS, host, or workspace Current stack and transfer limits
Lead paths One simple, observable form Multiple forms, routing, records, integrations Every conversion path
Integrations Standard embeds / connectors Custom logic or unclear dependencies Tools, owners, credentials, data flow
Design Reusable component system Original systems, illustration, complex motion Unique states and assets
Accessibility Simple pages, owned components Complex tools, documents, remediation Important tasks and known issues
Approvals One empowered reviewer Many stakeholders, regulated claims Reviewers and decision rights

An audit is worth it when it changes the project

A pre-redesign audit adds work before the build, so it looks like added cost. Its job is to remove expensive uncertainty — to find which pages earn traffic, which have external links, which URLs live in ads and email signatures and printed material, which accounts are actually business-controlled, and whether a redesign is even the right response instead of a focused repair. The test is simple: an audit earns its fee when it changes what you build. If it only turns a predetermined rebuild into a longer PDF, it's sales collateral. The pre-redesign audit article is the method; the point here is only that the audit is a cost lever, not a formality.

Read the price in three layers

Don't compare totals. Compare three layers, because a low total can simply be a total with a layer missing.

The build cost is discovery, content, design, development, migration, integrations, testing, and launch. The infrastructure cost is domain, hosting, platform, plugins, form and call-tracking tools, analytics, fonts, images, and other subscriptions. The stewardship cost is updates, monitoring, backups, restore work, support, content changes, and ownership when something breaks. A redesign with a low build price and an undefined stewardship layer isn't cheaper — it's partly unpriced, and the unpriced part tends to arrive as a surprise. The small-business website cost article breaks down the general pricing model these layers sit inside.

Where a cheap redesign gets expensive later

A low price can be the right choice. It becomes a problem when the scope quietly pushes the missing work into next quarter: important old pages disappear and have to be rebuilt after traffic drops; excluded content leaves a finished design waiting months on unwritten copy; forms send email but keep no source record, so failures are impossible to diagnose; platform accounts stay under the provider's login and have to be untangled later; analytics gets replaced instead of carried forward, breaking useful history; and "maintenance" starts at launch without anyone defining monitoring, restore, or response. Google explicitly suggests changing one major thing at a time during a site move when you can — a project that swaps CMS, URLs, design, and content all at once may still be justified, but the estimate should own the extra testing and monitoring that all-at-once creates.

What a dependable estimate states

Before you treat a number as firm, ask the provider to put in writing which of the four redesign types the project is; the included pages, templates, and content work; what's kept, rewritten, migrated, or retired; the old-URL inventory and redirect responsibility; the forms, notifications, records, and integrations; the analytics and Search Console work; account ownership and required access; the accessibility and testing scope; your inputs and approval deadlines; launch and post-launch verification; ongoing costs and support; and the process for handling discoveries and changes. The estimate should also reveal its own uncertainty. "Price assumes no custom CRM integration" is useful. "Integrations included" is a disagreement waiting for a calendar invite.

Where RP fits, and where it doesn't

For a current, real-world reference point: as of July 15, 2026, RP Marketing Group publicly prices two new lead-generation builds — a Lead Website at $6,500 plus $79 per month and a Connected Lead System at $13,500 plus $199 per month, first 90 days of the monthly included, paid half to start and half on delivery. Those are new-build prices, and RP's own pricing page is explicit that a redesign is a separate conversation rather than a menu item — its monthly fee covers hosting, monitoring, the receipt-and-alert infrastructure, and a couple of small edits like new hours or a swapped photo, not a rebuild. That is how redesign pricing actually works: it is scoped to what the specific project must preserve and change, which is exactly why it does not reduce to a package number on anyone's page. Treat those figures as one provider's current new-build scope, not a market average or a redesign quote, and recheck the live page before relying on them.

Start with the inventory

A redesign costs more when it has to preserve more value, resolve more ambiguity, change more systems, and produce stronger evidence at launch. That is not an argument for turning every small-business site into a large project — sometimes the right answer is a reskin, a focused repair, or no redesign at all. It is an argument for doing the inventory first. Decide which of the four projects you're buying, list what the current site must not lose, and then ask every provider to price the same preserved-and-changed responsibilities. Until you've done that, you're comparing confidence, not cost.

Sources