Building the Business Case for a Website Redesign (With the Numbers)

"The site looks dated" is not a business case, and it is the reason most redesign proposals die in a finance review. This guide shows you how to model the return on a five-figure website investment properly, four value streams, honest confidence discounts, and a one-page template you can put in front of whoever signs.

The discipline cuts both ways. Run this model honestly and some redesigns will fail it. Those are projects worth not doing, and finding that out in an afternoon is considerably cheaper than finding it out in month four.

9–18

Months to payback for a well-targeted redesign

40%+

Confidence discount to apply to any traffic forecast

Value streams worth modelling separately

1 page

The length your business case should be

Framework

The four value streams

Model these separately, because they carry very different levels of confidence. Blending them into one optimistic number is what makes finance teams distrust marketing forecasts, and they are right to.

Stream	Confidence	Typical share of the case
Conversion improvement	High, measurable on existing traffic	30–40%
Organic traffic growth	Low, dependent on factors outside the build	10–20%
Operational hours saved	High, countable today	25–40%
Retained revenue	Medium, requires a known failure	10–25%

Stream 1

Conversion improvement

This is the strongest part of most cases, because it works on traffic you already have. You need three numbers from analytics: monthly sessions, current conversion rate to your primary action, and average value per conversion.

Worked example: 8,000 monthly sessions, 1.4% converting to a qualified enquiry, 25% of enquiries closing at an average value of $2,200. That is 112 enquiries, 28 closes, and roughly $61,600 in monthly pipeline value.

A 30% relative conversion improvement, realistic where the current site has genuine structural problems, takes the rate to 1.82%, producing 146 enquiries and about $80,300 monthly. The annual gain is roughly $224,000 before discounting.

Be strict about eligibility here. A 30% assumption is defensible only if you can point at what is broken: pages taking over four seconds on mobile, no clear primary action, a form asking eleven questions, or a checkout that fails on the payment method half your customers use. If you cannot name the defect, assume 5–10% and build the case elsewhere.

Stream 2

Organic traffic

The weakest stream, and the one most often used to inflate a business case. A redesign can improve organic performance through better information architecture, faster pages, cleaner internal linking, and structured data. It does not, by itself, create authority or content.

Model it conservatively: take current organic sessions, assume a 10–20% improvement over twelve months if the redesign includes genuine technical SEO work, and then discount that by half again. If the business case only works with an aggressive traffic assumption, the case does not work.

Model the downside too. A migration handled badly can cost 20–40% of organic traffic for a quarter or longer. That risk is worth an explicit line, and it is the strongest argument for paying properly for migration planning.

Stream 3

Operational hours saved

Frequently the most persuasive stream with a finance audience, because the numbers exist today and require no forecast. Count the repetitive work the new site would absorb:

Answering "what is the status of my order/booking/application?", count the emails, multiply by handling time.
Manually producing quotes that a configurator could generate.
Re-typing form submissions into another system.
Publishing content through a developer instead of a CMS.
Reconciling payments that arrive without reference data.

Worked example: 30 status emails weekly at 6 minutes each, plus 12 manual quotes at 25 minutes, plus 4 hours weekly of re-typing. That is roughly 12 hours a week, or 600 hours a year. At a loaded cost of $18 per hour, $10,800 annually, and that is before the capacity those hours release.

Stream 4

Retained revenue

Only include this stream when you can name a specific, evidenced failure: a checkout that fails for a payment method your customers use, a mobile booking flow that abandons at a known step, a form that silently drops submissions, or an outage pattern.

Quantify it directly from the evidence, abandonment at a specific step multiplied by average order value, or support tickets multiplied by close rate. This stream is powerful precisely because it is not a forecast; it is a leak you can point at.

Costs

The full cost side

Business cases lose credibility when the cost side is thin. Include all seven lines:

Cost	Notes
Build	The vendor's quoted fee.
Content	Writing, photography, and migration. Routinely underestimated; often 10–20% of build.
Internal hours	Your team's specification, review, and UAT time at loaded cost.
Hosting & services	Annual infrastructure, email, monitoring, third-party APIs.
Support & maintenance	15–20% of build cost per year.
Training	Getting your team genuinely capable of operating it.
Risk reserve	10–15% contingency. Its presence increases credibility rather than reducing it.

Honesty

Confidence discounts

Apply these before presenting, and say that you have. A case that discounts itself is far more persuasive than one that does not, because it signals that the person who built it was trying to be right rather than trying to win.

Conversion gains: discount 25%, measurable but subject to seasonality and traffic mix.
Organic gains: discount 50%, genuinely uncertain.
Operational savings: discount 15%, the hours are real, but recovered time is never fully redeployed.
Retained revenue: discount 20%, some of those customers were never going to convert.

The credibility move

Present the pessimistic case first

Show the discounted numbers as the headline and the undiscounted as upside. Decision-makers have seen many optimistic forecasts and discount them silently by an unknown amount. Doing the discounting yourself, explicitly, transfers that judgement back to you, and makes approval materially more likely.

Template

The one-page template

Keep it to a single page with six blocks:

The problem, in one sentence, stated as a business outcome rather than a design opinion.
Evidence, three data points: conversion rate, page speed, support volume, or abandonment.
The proposal, two sentences on what will be built and what is explicitly excluded.
The numbers, a table of the four discounted value streams against total cost, with payback in months.
The risks, named honestly with mitigations, migration risk, content capacity, internal availability.
The decision requested, a specific amount and a specific date.

If it does not fit on a page, the case is not yet clear enough to approve.

Book a 1-hour scoping consult ($100) Price your project instantly

$100 for a one-hour session, billed at $25 per 15 minutes with a one-hour minimum. You choose your time on Calendly immediately after checkout. Pay by card or M-Pesa.

FAQ

Frequently asked questions

How do I calculate the ROI of a website redesign?

Model four gains separately: conversion rate improvement on existing traffic, organic traffic change, operational hours saved through self-service or automation, and retained revenue from fixing a specific failure. Sum the annual value, subtract build and running costs, and divide by total cost. Apply a confidence discount of at least 40 percent to traffic forecasts, which are the least reliable input.

How long before a website redesign pays for itself?

For a redesign driven by conversion and operational efficiency, nine to eighteen months is a realistic target. Redesigns justified mainly by expected SEO gains take longer and carry more risk, because organic performance depends on factors outside the build.

Will a redesign hurt my search rankings?

It can, badly, if URLs change without redirects, content is thinned during migration, or page speed regresses. A redesign that preserves URL structure, redirects every changed path with a permanent redirect, and keeps or improves content depth normally holds rankings and often improves them through better performance and internal linking.

What conversion rate improvement is realistic from a redesign?

For a site with genuine structural problems, slow pages, unclear next steps, a broken mobile experience, a 20 to 50 percent relative improvement is achievable. For a site that is already well built, expect single-digit gains and justify the project on something other than conversion.