B2B Website Redesign
Redesign vs. Conversion Optimization: How to Make the Right Call
Most companies reach for a redesign before they've looked hard enough at the data. Here's how to tell which investment your situation actually justifies.
A redesign is a large bet. Conversion rate optimization is a series of small bets. The question is not which one is better. The question is which one the evidence supports, right now, for your specific site.
Most B2B marketing teams choose redesign by default. Not because the evidence points there, but because a new website feels like progress. It looks like action. It is something you can point to in a board meeting.
That instinct costs companies a lot of money. And, more often than not, it does not fix the actual problem.
Why this comparison matters
The cost difference is not trivial.
A B2B website redesign typically runs $75,000 to $250,000 in agency fees alone. That number does not include internal time, content production, QA, redirects, the months of lost momentum while the site is in development, or the risk that launch is delayed.
The timeline is just as significant. From kickoff to launch, a full redesign typically takes 6 to 12 months. Some take longer. The site you brief in January may not be live until September, and the market does not pause while you rebuild.
Conversion rate optimization looks different. You start with the site you have. You identify specific friction points, run targeted changes, measure the result, and iterate. The feedback loop is weeks, not months. The cost is ongoing but manageable. And if a test does not work, you learn something. Nothing is lost.
What you gain with a redesign: a chance to fix structural problems that incremental work cannot reach, a new platform if the old one is the constraint, and a visual identity reset if the brand has changed. What you lose: time, money, and six months of compounding optimization work you could have done instead.
What you gain with CRO: fast feedback, lower spend, and the ability to double down on what is working rather than starting over. What you lose: the ability to fix structural problems that live below the surface, at the information architecture or positioning level.
Neither is always right. But one of them is right for your situation, and the difference is diagnosable.
When conversion optimization is the right answer
If any of the following are true, start with optimization. Do not brief a redesign until you have exhausted what CRO can tell you.
The problem is specific and traceable. You know the page. You can see the drop-off in the data. You have a hypothesis about what is causing it. That is a CRO problem, not a redesign problem. If you can point to the leak, you can fix it without rebuilding the whole pipe.
The tech stack is not the constraint. If your CMS lets you make changes, run tests, update copy, and connect your forms to your CRM without a developer ticket queue, you have what you need. CRO requires the ability to experiment. If that ability exists, use it.
The brand is solid. If your visual identity, messaging, and positioning are still accurate and aligned with your current ICP, a redesign adds risk without adding signal. Visual changes are not the same as conversion changes. You can have a very good-looking site that still loses people at the same places.
The structure is sound but the execution has drifted. This is the most common scenario. The bones of the site are fine. The navigation makes sense. The page inventory is reasonable. But the homepage copy is stale, the CTA placement is inconsistent, and the demo form has eight fields. Those are CRO problems.
If you are not sure whether your site has diagnosable CRO problems, read How to Diagnose Why Your B2B Website Isn’t Converting. That framework will tell you whether you have a behavioral problem you can test your way out of, or something more structural.
When a redesign is the right answer
A redesign is the right call when the problems on your site cannot be solved incrementally. Here is what that actually looks like.
The information architecture is broken. If the way the site is organized does not match how buyers navigate, you cannot fix that with copy tests. Buyers are landing on the wrong pages, bouncing because they cannot find what they need, or encountering a menu structure that made sense three years ago and has not kept up with how the business has grown. That requires restructuring, not tweaking.
The tech stack is blocking you. If your current CMS requires developer involvement for every content change, cannot support A/B testing, or is not compatible with your current marketing stack, the platform itself is the constraint. Optimization requires speed and flexibility. If the infrastructure cannot provide that, a rebuild is the prerequisite.
The positioning or brand has changed significantly. If the company has shifted upmarket, changed its ICP, rebranded, or gone through a merger or acquisition, the current site may be signaling the wrong thing to the right buyers. No amount of copy editing will fix a site that is fundamentally aimed at a buyer you are no longer trying to reach.
The performance gap is too large to close incrementally. If you are booking five qualified meetings per month and the goal is thirty, CRO can move the number but probably not enough, fast enough. Incremental improvement compounds over time, but it cannot leapfrog a site that is structurally misaligned with the goal. In that case, a redesign is the vehicle for the kind of structural changes that optimization cannot make.
The most common mistake
Companies choose redesign because it feels like a fresh start. Not because the evidence points there.
A new website looks like a solution. It has visible deliverables and a launch date. Everyone can point at it and say something happened. That is psychologically satisfying in a way that “we changed three form fields and improved conversion by 18%” is not.
But here is the problem: redesigns do not automatically fix conversion problems. Most conversion problems survive a redesign intact.
The team rewrites the homepage headline. Okay. But the demo form still has eleven fields. The pricing page still buries the CTA. The case studies are still abstract and credentialless. The new design is cleaner, but the same buyers are still bouncing at the same places, because the underlying friction was never diagnosed. It just got new clothes.
I have seen this play out many times. Companies spend six figures on a new site, launch with a lot of internal fanfare, and then watch the metrics return to baseline within 60 days. Not because the agency did bad work. Because the brief never defined what “better” looked like in measurable terms, and no one tracked what the old site was actually producing.
If you go into a redesign without a conversion baseline, a specific hypothesis about why performance is low, and a measurement plan for the new site, you are building a beautiful object, not a revenue channel.
How to decide
Work through this in order. Do not skip steps.
Establish a conversion baseline first. Before you can evaluate any investment in the site, you need to know what the site produces today. Qualified sessions, form completions, booked meetings, conversion rate by page. If you do not have this, get it. Every decision after this depends on it.
Identify the actual problem. Is the problem structural, meaning the architecture, platform, or positioning is wrong? Or is it behavioral, meaning specific pages have specific friction that can be diagnosed and tested? These require different solutions. Do not conflate them.
Ask whether the structural problems can be fixed without a full rebuild. Sometimes the answer is partial: the homepage and pricing page need structural work, but the rest of the site is fine. That is a scoped redesign, not a full one. Partial rebuilds are faster and cheaper than starting from scratch.
Price out both options honestly. A CRO program for six months costs a fraction of a full redesign. If CRO has a reasonable path to the goal, compare what six months of optimization would cost versus what a redesign would cost and how long it would take. Then decide based on the comparison, not on which option sounds more impressive.
Make the call based on evidence, not preference. If the evidence points to CRO, do CRO. If it points to redesign, do the redesign with a clear brief and a conversion baseline. If the evidence is unclear, get more evidence before committing either budget.
The audit-first argument
The fastest way to get to the right answer is a structured audit of the current site.
An audit does not tell you what looks bad. It tells you what is actually broken, where the conversion drop-offs are, what is causing them, and which path, optimization or redesign, is the right response to the specific problems it surfaces.
That matters because the two most common ways companies make this decision are both wrong. Option one: they ask the agency who also builds websites. The agency recommends a redesign. Incentive structure, not diagnosis. Option two: they look at the site subjectively and decide it feels dated. “Feeling dated” is not a conversion problem. It is a preference.
An audit replaces both of those processes with evidence. It tells you the actual problem. Then the decision follows from the evidence, not from what anyone wants it to be.
Before you commit to either path, get a Web Experience Audit. It will tell you exactly what is broken and which investment is warranted.
FAQ
Common questions
Can we do CRO and a redesign at the same time?
How long does a CRO program take to show results?
What if we just redesigned last year and conversion is still weak?
Is there a situation where neither is the right first step?
How do we know if the problem is positioning, not design or UX?
Takeaway
The redesign versus CRO decision is not a preference. It is a diagnosis. If the problems on your site are structural, a redesign is right. If they are behavioral and traceable, CRO is right. And if you are not sure which it is, an audit will tell you before you commit the budget to find out the hard way.
Who is this guy?
25+ years on the web. Numbers to show for it.
I led web strategy and conversion optimization for Tableau at Salesforce. I worked across engineering, marketing, and product to ship changes that moved the business. Here's what that looked like.