Buyer guide

Website redesign scope and cost factors

Two quotes for “a new website” can differ several times over because they describe different projects. Here is what drives the cost, what to decide first and how to compare proposals fairly.

Who this guide is for

Owners, marketing managers and operations leads budgeting a redesign, writing a clear request for proposals and comparing quotes like for like.

We publish no price ranges: without your scope they are guesses, and "average website cost" figures mix very different projects. This guide shows what moves the number, so you can control it.

First, check a redesign is what you need

Site works but few enquiries? Read why a website gets visits but few enquiries first: fixing a broken form, vague headline or hidden call to action costs far less than a rebuild.

The main cost drivers

DriverWhy it costs, and how to control it
Distinct page templatesEach layout is designed, built and tested: group pages into a few templates
ContentOften the slowest, costliest part: decide who writes, start early, migrate only what is useful
Migration and redirectsProtects search visibility and bookmarks: inventory pages early, remove outdated content deliberately
IntegrationsCRM, bookings, payments and syncing add build and testing: list systems, mark launch essentials
Custom functionalityCalculators, portals, member areas and complex search are software projects: launch or later?
Design depthA new brand identity is a separate project: say what brand assets you have
Accessibility and approvalsAdd review cycles: one decision-maker, target agreed upfront
Platform and licencesThemes, plugins and hosting recur: list every paid component and renewal
Care after launchUpdates, backups and fixes continue: budget for it, ask what is included
More detail: each driver in full
DriverWhy it mattersHow to keep it under control
Distinct page templatesEach unique layout needs design, build and testing. Twenty service pages on one template cost far less than five pages that all look different.Group pages into a small set of templates.
ContentWriting, rewriting and approving content is often the slowest and most expensive part.Decide who writes what, and start early. Migrate only what is still useful.
Migration and redirectsMoving old content and mapping old URLs to new ones protects existing search visibility and bookmarks.Inventory current pages early. Remove outdated content deliberately.
IntegrationsSending enquiries to a CRM, taking bookings or payments, or syncing with other systems adds build and testing work.List every system the site must connect to, and which are essential for launch.
Custom functionalityCalculators, portals, member areas and complex search are software projects in their own right.Separate "must have at launch" from "later".
Design depthA new brand identity is a separate project from designing web pages with an existing brand.Be clear whether you have brand assets to use.
Accessibility and approvalsFormal accessibility requirements and multi-person approval add review cycles.Name one decision-maker and agree the accessibility target upfront.
Platform and licencesPremium themes, plugins and hosting are recurring costs, separate from the build.Ask for a list of every paid component and its renewal cost.
Care after launchUpdates, backups and fixes continue for as long as the site exists.Budget for ongoing care, and ask what is and is not included.

Decisions to make before asking for quotes

  1. The site's job: enquiries, customer support, recruiting? Rank the goals.
  2. Audiences: who must find what, and their next step.
  3. Page list and templates, even roughly.
  4. Content ownership: who writes, approves, by when.
  5. Launch integrations and must-have features.
  6. Accessibility target. If your Ontario organization has 50 or more employees, Ontario's accessibility rules set a minimum standard for your public website. Many organizations aim for WCAG 2.2 AA regardless.
  7. Ownership: domain, hosting and every account in your name.
  8. Maintenance: who, and with what budget.

How to compare proposals

Check each proposal for:

  • Specific deliverables, not "a new website"
  • Stated exclusions
  • Who provides content; migration included
  • URL inventory and redirect plan
  • Testing: forms, mobile, accessibility, performance
  • Licences and hosting listed, with renewals
  • You own the site, code and accounts
  • Ongoing care priced and scoped separately
  • No promises it cannot keep

Distrust promised first-page rankings: Google's own guide says no secrets will automatically rank a site first. A lower quote that omits content migration, redirects and testing is not cheaper; it moves the cost to you.

Requirements worksheet

Fill this in and send the same version to every provider you ask to quote: it makes proposals comparable.

Organization and goals

  • Organization name and what you do (two sentences):
  • The website's top three goals, in order:
  • How you will judge success six months after launch:

Audiences

  • Main audiences, and what each needs to do on the site:

Current site

  • Current web address and platform (if known):
  • Approximate number of pages, and which ones get the most useful visits:
  • Content to keep, rewrite or remove:

Pages and templates

  • Planned page list (or sections):
  • Distinct page types you expect (for example: home, service, article, team, contact):

Content

  • Who writes new content, and who approves it:
  • Existing brand assets (logo, colours, fonts, photography you own):

Features and integrations

  • Forms and where their submissions must go:
  • Systems to connect (CRM, booking, payments, email marketing):
  • Must have at launch / can wait:

Standards

  • Accessibility target (for example, WCAG 2.2 AA):
  • Languages:
  • Any industry or privacy requirements:

Ownership, hosting and care

  • Who owns the domain and hosting today:
  • Who will maintain the site after launch:
  • Budget range for build and yearly care (optional; helps realistic proposals):

Timing

  • Any genuinely fixed dates, and why:

What happens next

With the worksheet filled in, any competent provider can give a meaningful estimate. For ours, send it with your enquiry: we reply with questions or a written scope.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Web Content Accessibility Guidelines (WCAG) 2.2, W3C
  2. How to make websites accessible, Government of Ontario
  3. SEO Starter Guide, Google Search Central

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in CAD before any work starts