New website or website redesign: how to make the B2B decision

The question “Do we need a new website?” often comes up when a site generates few enquiries, the sales team keeps explaining the same basics in calls, or marketing cannot launch a new campaign quickly. A redesign can look like the obvious answer: start again and fix everything at once. For a B2B company, though, it is not always the best first move.

Do not decide based on the age of the design or the team’s taste. First, find where the buyer journey breaks down. A visitor may not reach a key page, may not understand the offer, may not have enough reason to trust the site, may be unable to submit a form, or may have their enquiry lost after submission. Comparing analytics, CRM records, and the material used by the sales team is what separates a website problem from a traffic, offer, or enquiry-handling problem.

This guide offers a practical way to choose between Fix, Upgrade, and Rebuild. Its purpose is to make the scope of change proportionate to a problem you can verify.

New website or website redesign: start by finding what is not working

Before discussing the platform, template, or visual style, state the business question. For example: “Why do people who visit this service page not send an enquiry?” or “Why does sales receive contacts without a clear need?”

A practical check has six steps:

1. Choose one priority audience and one action you want that audience to take: request a meeting, a quote, or a demonstration.
2. Review the pages this audience lands on and the pages it should see before making contact.
3. Compare that path with analytics. Events, page transitions, form submissions, and technical errors only matter in relation to a specific scenario.
4. Complete the scenario yourself on mobile and desktop. Find the offer, evidence, contact details, and submit a test form.
5. Check the CRM: do enquiries arrive, do they contain enough context, and who receives the notification?
6. Compare the findings with sales conversations. What questions do buyers ask before a deal, and what information is missing from the website?

A low number of enquiries does not prove that you need a new website. Visitors may be landing on the wrong page. The form may submit but fail to pass data to the CRM. Or the page may describe the service too broadly. Each cause calls for a different response.

The Nexinlab matrix: Fix, Upgrade, or Rebuild

The matrix below helps marketing, sales, and technical teams discuss the decision using evidence from their systems rather than assumptions.

Criterion	Fix — targeted improvement	Upgrade — develop the existing website	Rebuild — new architecture and implementation
Main issue	Isolated obstacles on an understood buyer journey	Several connected limitations in structure, content, or lead handling	The website’s core logic does not support the current sales model, or cannot be managed safely from a technical perspective
What supports the choice	Specific pages, forms, or CTAs can be linked to the issue	Diagnosis shows recurring breaks between sections and scenarios	Required changes, preservation of important content, or integration maintenance cannot be implemented safely
Typical work	Clarify the offer, simplify a form, repair a journey, add evidence, remove a technical fault	Rework page priorities, navigation, templates, content model, and measurement	Design a new information architecture, migration, components, and integrations
Risk of the wrong choice	Treating a symptom without checking nearby journey stages	Extending a project with no clear boundaries	Spending resources on a new interface without addressing demand or enquiry handling
What to measure after launch	Completion of the target action and enquiry quality	Key-scenario completion, data quality, and the team’s ability to work with content	Migration accuracy, availability of key scenarios, and enquiry quality after stabilisation

If the first column is not supported by evidence, a Fix may be only cosmetic. If there are no technical constraints, a Rebuild may be premature. A useful website does not have to be new. It needs to help the right person understand the next step and take it with minimal friction.

Fix: when resolving 5–7 issues is enough

A Fix is appropriate when the website broadly performs its role and losses are concentrated in a few verifiable places. The issue may be a page that does not make clear who a service is for; a form that asks for unnecessary information; a CTA that does not explain what happens after the click; or an error in passing an enquiry on.

For example, a B2B company sends a campaign to a service page. The visitor sees a list of activities but does not understand which business problem the team solves or what to prepare for the first conversation. The first change may not be a new design. It may be a clear page structure: the client’s problem, the scope of work, limitations, evidence of fit, and a specific action such as “Request a situation review.” If the enquiry does not reach the responsible sales representative after form submission, connecting the form and CRM is the priority, not a new visual style.

State a hypothesis, make the change, confirm that the scenario works technically, and watch the data you agreed to assess in advance. Do not attribute an outcome to a single element if traffic channels, the offer, or sales activity changed at the same time.

Upgrade: when the website needs development, not patches

An Upgrade is needed when individual fixes do not form a coherent buyer journey. Common signs include no consistent way of presenting services, important material that is hard to find, marketing having to ask developers for every simple change, forms, pages, and CRM using different definitions of the same enquiry, or the team being unable to tell which scenario is actually working.

Start with the structure: which segments and tasks should the B2B website support, which pages answer early questions, where should evidence sit, and how should content connect to an action? Then review templates, navigation, components, and analytics. The business value of an Upgrade is manageability: the team knows where to place new material and how not to lose the context of an enquiry.

Set boundaries for the project. Not every page affects the commercial journey equally. Start with priority segments and scenarios; record what belongs in this phase and what remains in the backlog. This prevents the work from turning into an endless redesign driven by new aesthetic preferences.

Rebuild: when a new website is genuinely justified

Consider a Rebuild when confirmed needs cannot be met on the existing foundation without unacceptable risk. The current architecture may not support the required content types, critical scenarios may repeatedly fail because of outdated dependencies, or migration and development may have become unpredictable for the team. Another reason can be a substantial change in the business model: the company is addressing a different audience, changing its offer, or changing its route to sale while the old website still reflects the previous logic.

In that situation, “build a new website” does not mean only drawing new screens. The project includes a content inventory; decisions about what to migrate and archive; a redirect map; requirements for forms and CRM; editor roles; acceptance criteria; and a launch plan. Without these, a new website can carry old problems into a more contemporary appearance.

Before starting, write down the business task the current system cannot solve, the technical constraints that support that conclusion, and what must be tested after launch. This makes it possible to assess options without blaming the previous team or web agency.

Choosing a route in a working session

Bring together the website owner, marketing, sales, and the people responsible for the technical side for a short working session. Do not vote on the design. You need a list of observable facts: key scenarios, pages, errors, CRM data, platform constraints, and business changes.

Then use this simple decision rule:

Is there a confirmed local obstacle in one or more scenarios?
├─ Yes → can it be removed without rebuilding the website foundation?
│  ├─ Yes → Fix
│  └─ No → check the signals for Upgrade or Rebuild
└─ No → first clarify traffic, the offer, and enquiry handling

Are there recurring problems in structure, content, and website management?
├─ Yes → Upgrade
└─ No → is there a technical or business constraint that prevents website development?
   ├─ Yes → Rebuild
   └─ No → do not start a project before further diagnosis

The result of the meeting should not be the label “old website”. It should be a next step that can be checked: a list of fixes, a defined Upgrade scope, or a case for a Rebuild. Assign an owner to each action and agree in advance which signals would mean the decision needs to be revisited.

What to measure after the change

Measurement should correspond to the problem you selected. For a Fix, that could be successful completion of a specific scenario and correct data transfer. For an Upgrade, it could be the team’s ability to maintain key pages promptly, consistency across scenarios, and completeness of the enquiry context. For a Rebuild, it could be preservation of critical routes, working integrations, and no loss of necessary data during launch.

Do not rely only on a count of submitted forms. A contact without details, topic, or required consent may not help sales, while a good enquiry may come after several visits and pieces of content. CRM data and feedback from sales representatives help you assess enquiry quality, not just a click.

Limitations: when a Rescue Sprint and this framework do not fit

A short Rescue Sprint is useful only for a limited diagnosis and the most urgent changes. It does not replace audience research, a full technical migration, development of a complex integration, or work on an offer when the business model itself is not yet defined. It is not the right way to urgently “fix conversion” when there is no access to analytics, CRM, and the people who understand the sales process.

This framework also does not answer how to attract more relevant traffic. If the right audience is not reaching the website, the issue may be in channels, campaign messaging, or the market offer. If enquiries arrive but receive no response, improve enquiry handling first. The website is an important part of the buyer journey, but not the only one.

If you are choosing between a new website and improving the existing one, begin with a Lead Loss Review: map the key buyer journey, check the data, and name the constraints. The discussion about Fix, Upgrade, or Rebuild can then rely on observable causes rather than the feeling that the website is simply “old”.