Making the Business Case for a Website Redesign

An approval case earns trust by showing the numbers, naming the vetoes and defining what evidence finance will accept
By Galav Bhushan · Published 6 July 2026
Making the Business Case for a Website Redesign

The strongest website redesign business case starts with four reasons to reject the redesign. Redesigns consume three scarce resources—cash, management attention and commercial time—so a case that models only upside is structurally dishonest. A case that cannot lose is not a case; it is agency sales copy.

The internal champion must force one of three decisions: approve under stated conditions, re-scope, or stop. Our position is blunt: design quality cannot rescue proposition instability, absent authority or a cash-timing mismatch.

A website redesign business case must be allowed to fail

Finance is right to distrust a deck where every assumption pushes in the same direction. A useful case identifies the commercial constraint, shows why a site-level intervention is proportionate, prices the downside and gives the approver a kill switch.

We claim that cases with named stop conditions will produce fewer post-approval scope reversals within 90 days than cases without them; equal or higher reversal counts would prove us wrong.

Four projects show what our work can evidence without pretending to prove a financial result:

  1. Lanteria required a broad HR software capability set to be routed for multiple stakeholder audiences.
  2. AfriCap Hub required an events catalogue, filtering and registration to operate as one coherent journey.
  3. Savgen required a technical, multi-industry offer to become a navigable brand and website.
  4. Lake Erie Shores required stay and ownership audiences to coexist without muddling either route.

None of those project pages publishes performance figures. The decisions demonstrate commercial reasoning, while our finished website work lets buyers inspect the resulting architecture. They do not prove traffic, conversion or revenue uplift.

The case for specialist B2B redesign support must therefore rest on the company’s own constraints and assumptions.

A credible case protects the company from the project.

Four triggers for not proceeding with a redesign

Treat any one of the four triggers as a veto until the underlying condition changes.

  1. Cash runway below 12 months. Stop a full redesign when runway is 11 months or less. At 12 months or more, evaluate it only against a risk-adjusted budget and a calendar payback deadline.
  2. Immediate revenue need. Reject redesign as the primary response when the forecast requires signed revenue within 90 days. Delivery time and the B2B sales cycle make that timing mismatch indefensible.
  3. An unsettled proposition. Pause when two or more materially different propositions remain under executive review. Resume only after one proposition statement covering the buyer, problem and buying trigger has final approval.
  4. No owner with final authority. Do not appoint an agency unless one named person can make three final calls—navigation, core copy and launch—within 48 hours. Committee attendance is not decision authority.

The version reaching us is often a website blamed for a proposition leadership has not settled. Designing through that disagreement merely converts indecision into rework.

Commercial instability turns redesign work into expensive rework.

Build the website redesign business case as a decision memo

A one-page decision memo beats a 40-slide presentation because assumptions remain visible and disagreements cannot hide behind creative language.

The memo needs five fields, in this order:

  1. Decision requested: State the approval ceiling, accountable owner and release condition.
  2. Current commercial failure: Name the buyer route that fails and the evidence available today.
  3. Intervention logic: Explain why architecture, messaging or journey design could remove that failure. Execution choices belong in the guide to building a conversion-led B2B redesign, not in approval arithmetic.
  4. Bounded scenarios: Show pessimistic, expected and optimistic outcomes using the same commercial inputs.
  5. Kill and evidence rules: Record the no-go triggers, financial hurdle and evidence finance will accept.

Do not smuggle a creative brief into the approval case. Once approval exists, translate it into a structured redesign requirements document and manage delivery through a practical redesign checklist.

Decision quality improves when approval and implementation stay separate.

A worked website redesign business case for an illustrative UK B2B firm

Numbers should expose the fragile assumption rather than decorate the recommendation.

Take an illustrative UK B2B consultancy considering a full redesign. Its ten labelled inputs are:

  1. Current monthly sessions: 4,000.
  2. Current enquiry rate: 1.50%.
  3. Qualification rate: 40% of enquiries.
  4. Close rate: 20% of qualified opportunities.
  5. Gross profit per win: £12,000.
  6. Projected enquiry rate: 1.80% versus the current 1.50%.
  7. Projected sessions: 4,000 versus the current 4,000.
  8. Delivery period: four months.
  9. Enquiry-to-gross-profit lag: two months.
  10. Investment: £46,000 base plus £4,600 contingency, creating a £50,600 approval envelope.

Every other input stays unchanged. That makes the enquiry-rate assumption visible rather than burying it among simultaneous improvements.

Current enquiries = 4,000 × 1.50% = 60
Current qualified opportunities = 60 × 40% = 24
Current expected wins = 24 × 20% = 4.8
Current monthly gross profit = 4.8 × £12,000 = £57,600

Projected enquiries = 4,000 × 1.80% = 72
Projected qualified opportunities = 72 × 40% = 28.8
Projected expected wins = 28.8 × 20% = 5.76
Projected monthly gross profit = 5.76 × £12,000 = £69,120

Incremental monthly gross profit = £69,120 − £57,600 = £11,520
Approval envelope = £46,000 + £4,600 = £50,600
Earning months required = £50,600 ÷ £11,520 = 4.39, rounded up to 5
Payback month from approval = 4 delivery months + 2 lag months + 5 earning months = month 11

The three-scenario sensitivity table shows where the case breaks:

ScenarioEnquiry rate, current vs projectedMonthly gross profit, current vs projectedIncremental gross profitEarning monthsPayback from approvalDecision
Pessimistic1.50% → 1.65%£57,600 → £63,360£5,7609Month 15Fail
Expected1.50% → 1.80%£57,600 → £69,120£11,5205Month 11Pass
Optimistic1.50% → 2.10%£57,600 → £80,640£23,0403Month 9Pass

Set the hurdle before presenting the table: payback by month 12 passes, while month 13 or later triggers rejection or re-scoping. If only the optimistic scenario passes, decline the project.

These figures are illustrative, not measured client data. The calculation also conservatively treats the entire approval envelope as exposed from approval.

A case survives only when the expected scenario clears the hurdle.

If this analysis exposes wider gaps in your site, we can turn the evidence into a focused redesign brief — book a call

What does not move the redesign decision

Five popular exhibits create activity without reducing financial uncertainty:

  1. A speculative homepage mock-up fails because it cannot test navigation, content depth, integrations or the complete buyer route.
  2. A brand-adjective workshop fails when words such as “bold” and “human” lack behavioural consequences. Work to make B2B brand personality operational belongs in execution, not financial justification.
  3. A montage of competitor websites fails because category similarity says nothing about the company’s proposition, sales motion or buying friction.
  4. An isolated PageSpeed score fails because technical improvement alone does not establish qualified demand or commercial value.
  5. A raw lead total fails because more enquiries can coincide with fewer qualified opportunities. Finance should model gross profit from wins, not form submissions.

Visual taste can influence execution after approval. It should not determine whether the investment exists.

A prettier argument remains a weak investment case.

Finance objections the redesign business case must survive

A finance stakeholder is testing downside exposure, not asking for warmer reassurance. Four objections deserve quantitative answers.

“The timing is not justified.”

Still using the illustrative firm, a three-month deferral after prerequisites are settled creates this expected opportunity exposure:

3 months × £11,520 incremental monthly gross profit = £34,560

That is modelled exposure, not a booked loss. When any stop trigger remains active, avoiding rework outweighs the expected £34,560.

“A patch could be enough.”

Patch first when at least 80% of qualified enquiries depend on five or fewer page templates and the global proposition and navigation remain sound. Build the full redesign case when the failure crosses six or more templates and also affects the global content structure.

“The budget will drift.”

Approve the £50,600 risk envelope, not the £46,000 headline. The arithmetic is explicit:

£46,000 base + 10% contingency (£4,600) = £50,600 maximum exposure

Any proposed commitment above £50,600 returns for approval. The supplier does not acquire automatic rights to contingency.

“Revenue attribution will be disputed.”

The honest limit here is that attribution of a revenue change to a redesign is contestable. Before starting, finance, marketing and sales must agree what they will accept as evidence.

Accept a comparison of 90 days before launch with 90 days after stabilisation only when four comparability controls hold: traffic-source mix, media spend and pricing each remain within ±10%, while the sales qualification definition remains unchanged.

If any control fails, classify the redesign as a contributor rather than the sole cause. That agreement cannot eliminate ambiguity, but it prevents the evidence standard changing after results appear.

Finance should approve bounded exposure, not promised certainty.

FAQ

What is a defensible UK budget range?

Use £25,000–£75,000 as an illustrative UK planning range for a substantive B2B project covering strategy, copy, design, build, QA and launch. Below £25,000, demand explicit exclusions; above £75,000, require staged approval tied to templates, integrations and governance complexity.

Can the board approve a case when attribution data is weak?

If GA4 and the CRM reconcile source and qualified status for less than 80% of enquiries across 30 days, approve a two-week data audit only. Release build funding after reconciliation reaches 80%.

Should Google Ads keep running during the redesign?

Yes. Name owners for landing-page URLs, Google Tag Manager and Consent Mode at least four weeks before launch. If an ownership gap remains seven days before release, postpone the launch rather than switching off proven campaigns.

Does a site’s age justify a redesign?

No. A five-year-old site without a persistent commercial failure should stay; a two-year-old site showing the same buyer-route failure for three consecutive months should enter review.

Clear thresholds turn subjective approval into a commercial decision.

Summary

  • Stop when cash runway is under 12 months or signed revenue is needed within 90 days.
  • Pause while two competing propositions remain or no 48-hour final approver exists.
  • Approve only when the expected scenario reaches the pre-agreed payback hurdle.
  • Patch five or fewer templates when they carry at least 80% of qualified enquiries.
  • Agree 90-day versus 90-day evidence and four comparability controls before appointment.
  • Reject any case that gives the company no reason to walk away.

Actualyse designs and rebuilds B2B websites that turn research visits into qualified pipeline. Book a call to talk through where yours stands.