Website redesign cost depends on more than page count, design polish, or the hourly rate on a proposal. One of the biggest cost decisions is how you buy the work: as a defined project with a finish line, or as ongoing retainer capacity that keeps improving the site over time.
The short version: if you can clearly define what “done” means, a project usually fits better. If the work is valuable because the site will keep changing, testing, integrating, and evolving, a retainer can make more sense. The expensive mistake is buying the wrong operating model for the problem.
TL;DR: Project or retainer?
- Choose a project when the redesign has a defined outcome, a reasonably stable scope, acceptance criteria, and someone who can own the site after launch.
- Choose a retainer when the business needs ongoing design/development capacity, frequent changes, continuous optimization, or an external team that stays responsible after launch.
- Use a hybrid when you need a serious rebuild first and ongoing support afterward.
- Do not compare the models using monthly price alone. Compare the total ownership burden, change frequency, risk, and cost of waiting.
- Before deciding how to pay for a redesign, make sure you actually need one. Our website redesign checklist is designed for that decision.
The Finish-Line Test: the simplest way to choose
At Scope Design, we think the useful question is not “Which pricing model is cheaper?” It is:
Can you define a credible finish line?
That gives you the Finish-Line Test.
Ask four questions:
- Can we define done? Can you describe the deliverables and acceptance criteria without using phrases like “we’ll know it when we see it”?
- How fast will the requirements change? Are products, offers, content, integrations, campaigns, regulations, or internal processes likely to change while the work is underway?
- Who owns the website after launch? Do you have someone internally who can manage updates, vendors, analytics, security, content, and future requests?
- What does waiting cost? If every new request has to become a separate quote, approval, and mini-project, does that slow the business down enough to matter?
If the finish line is stable and post-launch ownership is clear, project pricing is usually easier to control. If the finish line keeps moving because the business itself keeps moving, ongoing capacity is often the more honest model.
That does not mean a retainer is automatically better. Paying every month for capacity you barely use is not strategy. It is a subscription to guilt.
What actually drives website redesign cost?
A redesign quote is rarely just payment for “making the site look better.” Cost is usually created by the amount of uncertainty, migration work, decision-making, custom functionality, content, and post-launch responsibility hidden inside the phrase website redesign.
Common cost drivers include:
- number and complexity of page templates;
- content rewriting, editing, migration, or restructuring;
- ecommerce, membership, booking, CRM, payment, or other integrations;
- custom functionality and business logic;
- analytics and conversion tracking;
- SEO preservation and URL migration;
- accessibility requirements;
- performance work;
- photography, illustration, video, or other creative production;
- stakeholder reviews and approval complexity;
- training and documentation;
- post-launch maintenance and improvement.
For a broader look at total website budgets and the differences between DIY, professional, and custom work, see our small business website cost guide. This article is narrower: it focuses on how the commercial relationship itself changes the cost and risk of the redesign.
Project-based website redesign pricing
A project agreement buys a defined outcome. The agency and client agree on what is being built, what is included, what counts as complete, and how changes will be handled.
That structure works well when uncertainty can be reduced before the build begins.
What a good redesign project should define
A solid project scope should make the following explicit:
- business goals and priority users;
- sitemap or page inventory;
- required page templates;
- content responsibilities;
- functionality and integrations;
- migration requirements;
- design review and revision process;
- technical requirements;
- launch responsibilities;
- acceptance criteria;
- warranty or post-launch correction period;
- what happens when scope changes.
If those items are fuzzy, the fixed project price may only be pretending to be fixed.
The real advantage of project pricing
The main benefit is not simply “lower cost.” It is a defined commitment.
You can approve a budget for a specific outcome. The agency can plan staffing around that outcome. Both sides have a shared definition of completion. Once the project is accepted and launched, the engagement can end cleanly.
That is especially useful when:
- the redesign is a one-time strategic change;
- the website will be relatively stable afterward;
- internal staff or an existing vendor can own maintenance;
- procurement requires a defined budget and deliverable;
- leadership wants a clear launch date and handoff.
Where project pricing gets expensive
Project pricing becomes painful when the business keeps changing faster than the scope can keep up.
Typical pressure points include:
- a new service gets added halfway through the build;
- sales changes the offer after pages are approved;
- an integration turns out to have undocumented limitations;
- the client discovers missing content late;
- stakeholders request major structural changes after design approval;
- launch reveals a stream of follow-up work that was never part of the project.
None of those automatically mean the agency did something wrong. They may simply mean the work was never truly bounded.
This is why project governance matters. If you choose a project model, our guide to managing a website project without losing the plot covers requirements, decisions, changes, acceptance, and handoff.
Retainer-based website redesign pricing
A retainer buys ongoing access to capacity and continuity, not one frozen deliverable.
The exact structure can vary. Some retainers reserve a set number of hours or points. Others cover a defined service band. Some combine strategy, design, development, maintenance, and optimization. What matters is that the relationship is intentionally ongoing.
What you are paying for in a retainer
A useful website retainer may include some combination of:
- design and development capacity;
- content changes;
- landing pages and campaign support;
- technical maintenance;
- performance improvements;
- analytics review;
- conversion experiments;
- integration work;
- ongoing UX improvements;
- priority scheduling;
- strategic planning;
- retained knowledge of the site and business.
The last item is easy to underestimate. Every time a new vendor touches a complex website, somebody has to relearn the architecture, plugins, integrations, business rules, hosting, analytics, and history. Continuity can reduce that repeated discovery burden.
The real advantage of a retainer
A retainer works best when change itself is the requirement.
The site is not a finished brochure. It is an operating system for marketing, sales, service, ecommerce, or internal workflows. New work will keep arriving, and the business benefits from having a team that already understands the environment.
That tends to fit businesses that:
- launch campaigns or offers regularly;
- rely heavily on the website for leads or revenue;
- have ongoing development or integration needs;
- lack internal website ownership;
- want continuous testing and improvement;
- would lose money or momentum waiting for a new quote every time something changes.
Where retainers waste money
A retainer is a bad fit when the client has no meaningful ongoing backlog, cannot make decisions fast enough to use the capacity, or expects “unlimited everything” from a finite team.
Warning signs include:
- no one internally owns priorities;
- work requests arrive randomly with no business value attached;
- the retainer exists only because canceling feels awkward;
- most months are quiet;
- the agency cannot explain what capacity is reserved or how work is prioritized;
- the client expects every large new initiative to fit inside the same monthly fee.
A retainer should create leverage, not fog.
Project vs. retainer: cost comparison
The useful comparison is not “$X project versus $Y per month.” The useful comparison is what each model makes you responsible for.
| Decision factor | Project | Retainer |
|---|---|---|
| Best when | Outcome has a clear finish line | Work is continuous or requirements change often |
| Budget structure | Defined project budget | Recurring budget for ongoing capacity |
| Scope | More fixed and acceptance-driven | Prioritized and continuously managed |
| Change handling | Often requires change orders or added scope | Smaller changes may flow through the ongoing backlog |
| Team continuity | May decline after launch | Usually stronger by design |
| Post-launch ownership | Must transfer somewhere | Can remain with the retained team |
| Procurement simplicity | Easier for one-time capital-style approval | Easier for predictable operating spend when ongoing work is expected |
| Main risk | Scope was not actually stable | Paying for capacity without enough valuable work |
Neither model removes risk. It changes where the risk lives.
A project pushes more risk into scoping and change control. A retainer pushes more risk into prioritization, utilization, and relationship management.
The hidden cost most redesign budgets miss: ownership after launch
A website does not become maintenance-free because somebody sent a “launch complete” email.
After launch, someone still needs to own things such as:
- WordPress, plugins, hosting, backups, and security;
- new content and page changes;
- broken integrations;
- form and email delivery issues;
- analytics and tracking changes;
- accessibility improvements;
- performance regressions;
- campaign pages;
- product, pricing, or service changes;
- vendor coordination.
If your project proposal ends at launch, ask who owns that list next.
This is where a cheap-looking project can become expensive operationally. The business may save on the initial agreement but then spend staff time coordinating freelancers, opening new tickets, approving small proposals, or rediscovering how the site works every few months.
Conversely, a retainer can be wasteful when internal staff already handles those responsibilities well.
The right cost comparison includes who owns the next 12 to 24 months, not just who builds the next 12 pages.
A hybrid model is often the least stupid answer
Many businesses do not need to choose one model forever.
A practical hybrid can look like this:
- Discovery and redesign project: define the strategy, architecture, design system, content, migration, integrations, launch, and acceptance criteria.
- Handoff decision: determine what the internal team can realistically own.
- Ongoing support: move only the recurring work into a care plan or retainer.
This preserves the accountability of a project while acknowledging that some websites are too important to throw over the wall after launch.
It also makes the retainer easier to size because the agency is no longer guessing what the rebuild will uncover. The large transformation is handled as a project; the recurring operational work becomes the ongoing relationship.
How SEO, URL migration, and accessibility affect redesign cost
Some redesign costs are not visible in a mockup.
SEO and URL changes
If the redesign changes URLs, the project needs migration work: redirect mapping, canonical checks, controlled internal-link updates, sitemap behavior, and post-launch verification. Google publishes specific guidance for site moves with URL changes, which is a good reminder that “we changed the slug and hoped for the best” is not a migration plan.
If there is no compelling reason to change an established URL, preserving it is often the cleaner choice.
Accessibility
Accessibility is another scope item that should be explicit rather than assumed. The W3C Web Content Accessibility Guidelines 2.2 cover a broad set of requirements that can affect design systems, navigation, forms, contrast, keyboard behavior, media, content, and testing.
If accessibility matters to the project, define the expected standard and testing responsibility before the build is priced.
How to compare two redesign proposals without getting fooled by the totals
When two agencies quote different amounts, ask what each number actually owns.
Compare:
- discovery and strategy;
- content responsibility;
- number of unique templates, not just pages;
- migration work;
- integrations;
- SEO preservation;
- accessibility scope;
- analytics implementation;
- testing and QA;
- revisions;
- change-control rules;
- training;
- launch support;
- warranty period;
- maintenance after launch;
- response expectations;
- who owns unresolved issues.
A proposal that is 30% cheaper because it excludes migration, content, QA, and post-launch ownership is not necessarily cheaper. It may simply move those costs into your staff calendar.
Likewise, a large retainer is not automatically more sophisticated. If nobody can explain what work will actually be prioritized each month, you are buying capacity without a plan.
Which model should a small business choose?
Use the project model when all of these are mostly true:
- the desired redesign outcome is clear;
- the scope can be documented with reasonable confidence;
- major business changes are unlikely during the build;
- someone can own the site after launch;
- follow-up changes will be occasional;
- a defined budget and handoff matter more than continuous access.
Use a retainer when several of these are true:
- the website supports ongoing marketing or sales operations;
- requirements change frequently;
- integrations or technical work continue after launch;
- internal ownership is weak or intentionally outsourced;
- speed of iteration matters;
- there is a meaningful, prioritized backlog every month.
Use a hybrid when the site needs a major reset and ongoing ownership afterward.
Frequently asked questions
What is a website retainer fee?
A website retainer is a recurring fee paid for ongoing access to a defined level of website strategy, design, development, maintenance, or optimization capacity. The agreement should explain what capacity is reserved, what is included, how priorities are handled, and what happens when work exceeds the agreed level.
Is a website retainer cheaper than a redesign project?
Not inherently. A retainer can cost more over a year because it buys ongoing capacity rather than one deliverable. It can also reduce repeated quoting, onboarding, and handoff friction when the business genuinely has continuous work. Compare the models based on the amount and frequency of work you actually expect.
What are the disadvantages of a retainer?
The main risks are underusing the capacity, unclear prioritization, fuzzy boundaries, and staying in an ongoing agreement after the business need has disappeared. A good retainer should make capacity, responsibilities, and review points visible.
What are the disadvantages of project pricing?
Project pricing can become rigid when requirements change. If the original scope is incomplete or the business changes during the build, change orders and follow-up projects can add cost and delay. Project pricing works best when discovery creates a credible definition of done.
What is a reasonable website redesign cost?
There is no universal number that is useful without scope. Page templates, content, custom functionality, integrations, ecommerce, migration, SEO, accessibility, stakeholder complexity, and post-launch ownership can change the budget dramatically. For broader budget ranges and buying routes, use our small business website cost guide.
How long should a website redesign take?
Timeline depends on scope, content readiness, decision speed, integrations, review cycles, and technical complexity. A smaller, well-defined project can move quickly; a complex redesign with multiple stakeholders and integrations can take much longer. A retainer does not automatically make the rebuild faster, but it can make ongoing post-launch work easier to prioritize.
Can I start with a project and move to a retainer later?
Yes. In many cases that is the cleanest structure: complete the defined redesign as a project, then decide what recurring work is valuable enough to retain. The post-launch agreement can be sized using a real backlog instead of guesses made before the redesign begins.
Should maintenance be included in the redesign cost?
The proposal should at least state what post-launch maintenance is and is not included. Whether it is bundled into the project, sold as a separate care plan, or handled through a retainer matters less than making ownership explicit before launch.
The decision is not project versus retainer. It is finish line versus continuous ownership.
A website redesign project is a good buying model when you can define the outcome, control the scope, and hand the site to a capable owner afterward.
A retainer is a good buying model when the business needs ongoing website capacity and continuity because the work will keep changing.
If you are not sure which one you need, start one level earlier: identify the actual constraint. Sometimes the problem is design. Sometimes it is content, technology, ownership, conversion friction, maintenance, or a business process wearing a website costume.
Scope Design works across website development and ongoing management, so we can help you decide whether the right next move is a defined redesign project, ongoing support, or a hybrid. The goal is not to sell you the longer agreement. The goal is to put the finish line in the right place.
