How to build a business case for a B2B website redesign

Then a stakeholders asks for a number: what’s the ROI?

This is where most redesign projects either get parked indefinitely or move forward on shaky ground that collapses six months in.

I’m a web agency founder so I’ve seen this play out enough times to know the pattern. Most B2B website redesigns fail because they’re missing a clear business objective. The site got prettier but the pipeline stayed empty.

This article is a practical framework for building the business case – getting internal buy-in and justifying the spend. These things will set up your redesign to deliver a measurable return.

1. Start with the commercial problem, not the website

If you walk into the CFO’s office and say “our website looks dated,” the conversation is over. If you walk in and say “our website is not generating enough MQLs to hit the growth target, and here’s what I think it would take to fix that,” now you’re talking.

The commercial problems we’ve seen at NerdCow play out in different shapes:

• Strong PPC spend that converts at half the rate it should – money is reaching the site, the site isn’t doing its job. That was the situation at Courier Exchange.
• Zero leads from a website that was getting traffic. Repositive had never run paid acquisition. The inbound came from the CEO’s industry network and from investors sending prospects to look them up. The website’s job was to convert that warm traffic into qualified meetings. A small commercial team of one salesperson and one marketer was depending on the website, but it wasn’t generating leads. After a redesign aligned to a real commercial objective, the site went from zero to three qualified calls a week.
• A product pivot or repositioning that isn’t reflected on the current website. Doddle is a good example. When the business moved into software, the website had to do something fundamentally different than it had been designed to do initially.

In every case, the redesign starts with the commercial question, not the visual one. If you can’t write your problem as a single sentence about revenue, pipeline, or cost, you don’t have a business case yet. You have a feeling.

2. Audit your current baseline

Most teams skip this part, and it’s the part that makes the whole exercise possible. You just can’t prove ROI without a point of reference. Before you do anything else, get the numbers on the table:

• MQLs per month
• Demo requests
• Form completions across primary and secondary CTAs
• Organic sessions
• Bounce rate on key pages
• Conversion rate on the primary CTA

The distinction between primary and secondary conversions matters. The primary conversion is the action that maps directly to pipeline – usually a demo request or a qualified contact form. You’ll use it to prove the ROI. The secondary, or micro, conversions are everything else: newsletter signups, content downloads, video plays, scroll depth on a pricing page. They’re not as exciting, but they’re required to troubleshoot your current situation.

If you don’t have this data, that’s a finding in its own right. “We don’t even know what our website is currently doing for us” is a strong argument for spending money to create something that tracks it.

The baseline is what you take to the decision-maker. It’s also what you compare against six months after launch. Without it, you’ll have nothing to point at when the next quarterly review asks whether the investment paid off.

3. Map the specific failure points

The business case has to be specific. “The website feels old” won’t get you a budget, and it won’t get stakeholders engaged either. “Our homepage bounce rate is 74% and our demo page gets 12 visits a month” will.

Look at heatmaps and session recordings. Spot areas where users hesitate, where they click on things that aren’t clickable, where they leave. Check Google Search Console for queries you rank for but don’t convert on – these are intent signals you’re failing to capture. Finally, check drop-off points in GA4.

Some of the patterns we find again and again:

• The user journey is built for a first-time visitor when most of the traffic already knows the brand. Returning visitors don’t need re-educating on what you do, they need moving closer to a decision. Courier Exchange’s site fell into this trap.
• The site doesn’t bridge the gap between awareness and demo-ready. There’s content for someone who’s never heard of you, and there’s a demo form for someone ready to buy, but nothing in between. The buyer journey has a missing middle.
• Dead clicks, broken CTAs, navigation that confuses rather than guides – all of this is quantifiable now. There’s no excuse for opinion-based diagnosis.

You don’t need a 60-page audit. You need three or four specific, evidenced failure points that anyone reading the document sees as an issue. Don’t be discouraged if you’re missing specific numbers. Assumptions are fair game as well. “I think we’re not getting enough demo requests” is a good starting point. A web agency can help you validate your hypothesis.

4. Define a specific objective

Not “improve conversions.” Look for something specific, e.g. “increase demo requests from organic traffic from X to Y within six months of launch”. If your baseline is still missing numbers at this point, look up industry benchmarks and use them as your target.

The objective has to be tied to a commercial metric the business already cares about. If your team measures pipeline contribution, the objective is pipeline contribution. If it’s MQLs, it’s MQLs. Don’t invent a new metric for the redesign – borrow the one finance is already watching.

Our approach is to force this clarity in a stakeholder workshop before any design work starts. Instead of starting with creativity, we kick off projects with an alignment session. Everyone in the room has to agree on what success looks like in a measurable way. If they can’t, that’s the problem to solve before going further.

One objective, or at most two. More than that, and the redesign tries to do everything and ends up doing nothing well. The site has to be optimised for something specific, so pick one.

5. Estimate the financial upside

This is the number the CFO actually wants. The simplest model is as follows:

Current conversion rate × current traffic × average deal value = current website revenue contribution

Then ask: what is a 1% lift in conversion rate worth at our current traffic level? What about a 3% lift? At what point does the redesign pay for itself in a quarter? Two quarters? A year?

You’re not building a precise forecast. You’re building a plausible range that makes the investment look rational.

Real-world anchors help. Courier Exchange roughly doubled its leads after our redesign. Repositive went from zero to three calls a week. If your case looks similar to one of those in shape, you can argue for an outcome in a similar range. If it doesn’t, find a closer comparison.

The point of this section isn’t to promise the CFO a specific number. It’s to show that you’ve done the research, that the upside is meaningful, and that doing nothing is more expensive than it looks.

6. Account for the cost of doing it wrong (or not doing it at all)

What does another 12 months of the current site cost you in lost leads?

That number is usually larger than the cost of the redesign itself, which is a useful framing when the conversation gets stuck on the price tag.

But the other risk is doing the redesign badly. The pattern I’ve seen too many times: a six-month project that runs over budget and over time, lands a shinier site, and three months later the conversion rate is exactly the same. It’s the “if you build it, they will come” mistake – and it’s the most expensive way to learn that design isn’t the bottleneck.

Prototyping changes the calculus here. By validating the new design against real users before you commit to a full build, you reduce the risk of the investment substantially. You find out what works and what doesn’t on a prototype, not on the live site that’s costing you leads while it’s being rebuilt.

7. The stakeholder problem (and how to solve it)

A business case is only half the battle. The other half is internal alignment and engagement.

The classic failure mode: the CMO builds the case. IT has a different priority list. Sales wants different things on the homepage. Product wants the new feature highlighted. The project stalls in committee, gets re-scoped into uselessness, or launches with a homepage that’s clearly the result of a vote rather than a strategy.

The fix is the alignment workshop. Everyone’s agenda gets surfaced and addressed in one room. It happens the very first time we meet, not in a six-week email chain or a series of design reviews. The workshop output isn’t a Figma file. It’s a prototype: something you can put in front of real users and test before committing to build.

There’s a question that comes up often at this point in the conversation, usually from the CFO or the CEO: How do we know we’ll actually get a website in three months and not just a hero banner? It’s a fair question. Here’s the answer I give:

You can’t be sure. But you stand the best chance with a process designed to tame the uncertainty – detect mistakes early, correct them, move on. We align stakeholders from the start, find the direction in workshops, then deliver in weekly iterations everyone can see. We run four-week cycles where the time is fixed and the scope is open: we hammer down each feature to fit the timeline, which removes the risk of domino effects and scope creep. If we agree we have three months, we’ll make it work. I can’t guarantee the website we deliver will be exactly what you imagined on day one – it might be 80% there, or we might learn halfway through that the MVP we agreed isn’t feasible. But it’s better to learn that with us than anyone else.

If you’re building the business case internally, build the workshop into your proposal as the first stage. It’s where the redesign stops being one person’s project and becomes the company’s project.

8. Don’t forget the intangibles

While we advocate for extreme focus when picking your metrics, forgetting the intangibles can also skew your calculations. Things like operational efficiency can often bring massive savings. We helped our clients move from manual copy edits across different campaigns to using efficient patterns. We implemented global variables to edit stats and facts in a single place, rather than across 100+ pages. Another example is a centralised pricing setting – not uncommon, but we built an external API on top of that, allowing it to be displayed outside of the website as well.

Some companies go as far as making an intangible their focus. It’s harder to build the business case around them, but it’s not impossible. In most cases, it’s still worth including a few intangibles as a footnote in your business case.

9. What a strong business case looks like

You can replicate this on one page. Don’t overproduce it. A clean one-page document is more credible than a 30-slide deck. Cover these areas:

1. The commercial problem – one sentence.
2. Current baseline metrics – five to seven numbers, with a focus on one or two – no more.
3. Specific failure points – three or four, ideally backed by evidence.
4. Objective – measurable, with a target and a deadline.
5. Estimated financial upside – the simple calculation from section #5.
6. Investment required and timeline – what it costs and how long.
7. Risk mitigation – how the project will be validated before full build.

That’s the document. If you can’t fit it on one page, the case isn’t tight enough yet.

Need a second opinion?

If you need a second opinion on what your website is actually doing for you – and what a credible business case for changing it looks like – book a process demo with me. We’ll go through your current baseline, your commercial objective, and whether a redesign is the right answer at all. Sometimes it isn’t – and that’s also useful to know too.