What a B2B Website Redesign Really Involves

Why a new design can leave the old problem intact

Most redesigns start from something visible: a dated look, pages that no longer match one another, a menu that has outgrown its space. Those are real, but they are rarely the root cause. Check first whether pages follow the org chart instead of buyer questions, whether content has piled up without anyone deciding what leads, and whether the company description still fits the business.

In a meeting, a salesperson supplies the missing order. They recognize the audience, choose the relevant explanation and bring in evidence when a question arises. A website needs to provide that guidance through its messages, navigation and page relationships.

Giving every audience the same introduction can make that difficult. A prospective buyer, technical evaluator and existing customer may need different information from the same organization. The site needs to make those routes understandable while keeping the company story consistent.

Run the explanation test

Choose a page your sales team regularly shares. Ask someone unfamiliar with the business to use it to answer three questions: What does this company help me do? Why should I consider its approach? Where would I go to evaluate it further?

Listen without filling in the gaps. Record the explanation you wanted to add, then identify where it belongs. A missing central idea is a messaging problem. Evidence that exists but cannot be found points toward structure. An unclear next step points toward the journey.

Repeat the exercise for another important audience. If the useful route changes, the redesign needs to account for that difference.

Review the site as five connected parts

Each part answers a different planning question:

• Brand. Would a new visitor recognize the company you are today from this site?
• Message. What should a visitor take away first, and which evidence follows it?
• Experience. Can each audience reach what it needs and tell what to do next without help?
• Content. Who decides what gets published, and how does one fact stay consistent across pages?
• Technical. Which integrations, performance and accessibility needs must the platform meet from day one, and who looks after them?

Use the answers to set priorities. If the company cannot agree on its central message, resolve that before asking a homepage layout to carry it. If editors repeatedly duplicate information, examine the content model before adding more page templates.

Turn the strategy into a maintainable website

Start with the audiences and decisions the site needs to support. For each priority audience, write down what it needs to understand, what evidence it needs and what a useful next step looks like.

Next, inventory the content you already have. Decide which material to retain, revise, combine or remove. Build the sitemap and page hierarchy around audience questions, then define how recurring content such as resources, services and case studies relates.

Use real content to test wireframes and components. A layout that works with a short sample headline may fail with the information your team actually publishes. Include the people who maintain the site when reviewing the CMS and publishing workflow.

Before launch, test the complete journeys alongside content, responsive behavior, accessibility and integrations. Assign ownership for the updates that follow. A redesign needs a practical maintenance plan as well as an agreed launch state.

Set rules editors can work within

A CMS works best when editors can build the pages they need without making design decisions each time. Define the page types and components up front, decide what editors may change and what stays fixed, and write down why. The aim is a site your team can keep adding to for years without it drifting apart.

Test that balance with a likely future request, such as a new service or resource collection. Can the team publish it using the existing content types and components? If every new request requires a custom layout, the system may be too narrow. If routine publishing requires editors to invent typography and spacing, too many design decisions remain unresolved.

AdaCore: communication strategy and UX/UI

For AdaCore, Suits & Sandals handled website communication strategy and UX/UI. Development was by a partner agency.

The project is a useful example of the scope distinction within a redesign: communication strategy and UX/UI are part of the website work, even when another team implements it. When planning your own project, make the relationship between those decisions and development explicit.

When to bring in outside help for a redesign

Outside help pays off when messaging, audience needs, content structure and technical requirements have to be settled together, especially when internal stakeholders have competing priorities. Those decisions need to be agreed before design and development can proceed coherently. See how S&S approaches website strategy, UX and development.