Most B2B websites are built as brochures: a description of the company, a list of services, a contact form. The site gets approved because everyone recognises their own department in it, and then it sits there for four years doing very little. The problem is not the design. The problem is that nobody ever wrote down what the site was supposed to do.
A serious B2B website is a working part of the business.
It is often the first place a potential client forms a judgment about how you think, how you communicate and whether a conversation with you is likely to be worth their time. That judgment happens before anyone fills in a form, and usually before you know the visit occurred.
So the useful question is not “does the site look current?” but “what decision is the site supposed to help someone make, and does it actually help them make it?” Everything else—structure, copy, design, measurement—follows from the answer.
A website is decision support, not a portfolio
In most B2B purchases the person on your site is already mid-decision. They have a problem, some internal pressure to solve it, and a shortlist forming in their head. They are not browsing; they are evaluating. What they need from your site is material for that evaluation: what you do, for whom, under what conditions, and what working with you actually looks like.
This is why vague positioning is so expensive. A page that says the company “delivers innovative solutions across industries” forces the visitor to do the qualification work themselves—and most will not. The visitors you lose this way are precisely the careful ones: people who read properly, compare options and take decisions seriously. Those tend to be the clients worth having.
Decision support also means being willing to say what you do not do. A clear boundary reads as competence. When a firm states plainly which problems it takes on and which it refers elsewhere, the visitor can locate themselves quickly—and the enquiries that arrive are better matched to the work.
The four jobs of a B2B website
Stripped of everything decorative, a B2B website has four jobs. If a page does not serve at least one of them, it is a candidate for removal.
- Position. State who the firm is for, what it does and what it deliberately does not do—specifically enough that the wrong visitor can rule you out quickly. Ruling people out is a feature, not a leak.
- Qualify. Help the right visitor recognise their own situation: the problems described should sound like their problems, in their language, at their scale.
- Reassure. Reduce the perceived risk of starting a conversation. Show how you work, what an engagement involves, who is accountable and what happens after the first contact.
- Route. Give a qualified visitor one obvious, low-friction next step—and make sure something reliable happens on the other side of it.
These four jobs are sequential from the visitor’s point of view. Someone who is not positioned to will not qualify themselves; someone who is not reassured will not follow a route, however prominent the button. Most website problems can be traced to one of the four jobs being skipped—usually reassurance, because it is the hardest to write.
Why rebuilds fail before design begins
When a company decides its website “no longer represents the business,” the instinct is to start with visuals: a new look, a new template, a moodboard. Design matters—a dated site quietly undermines everything on it—but starting there inverts the work. The visual layer is the last decision that should be made, because it depends on all the earlier ones.
The earlier decisions are less glamorous. Who is the primary audience for this site, when there are several candidates? Which offer leads? What happens, operationally, when an enquiry arrives—who responds, how fast, with what? Who owns the site after launch, with the authority to change it? A rebuild that skips these questions produces a better-looking version of the same ambiguity.
The other predictable failure is scope. Website projects attract additions: a careers section, a portal idea, a blog nobody is resourced to write. Each addition sounds reasonable and each one delays the part of the site that earns money. Scope discipline here is simple to state and hard to hold: build the pages that serve the four jobs for the primary audience, launch, and let evidence from real visitors justify everything else.
Measurement that respects how B2B buying works
B2B sites produce few conversions over long cycles, which makes them easy to measure badly. Traffic dashboards reward volume, but a professional-services site does not need volume; it needs a small number of well-matched enquiries. A month with nine hundred visits and two strong enquiries is a better month than one with four thousand visits and none.
The more honest measures are closer to the sales conversation. Are enquiries arriving from the kind of company the site was aimed at? Do first calls start further along—because the prospect has already read how you work and roughly understands the engagement? Do the wrong-fit enquiries decline? None of this shows up neatly in an analytics tool, which is exactly why it requires a human review: a short, regular look at what actually came in, judged by the people who took the calls.
What this means in practice
If you are responsible for a B2B website—building one, or deciding whether the current one deserves investment—the practical version of this argument looks like this:
- Write the site’s job description before anything else: one primary audience, one primary decision the site supports, one primary next step. If the team cannot agree on those three lines, the disagreement is strategic, not a website problem—resolve it first.
- Audit each existing page against the four jobs. Pages that serve none of them are removed or merged, however attached anyone is to them.
- Write the reassurance content deliberately: how engagements work, what the first conversation involves, who the visitor will deal with. This is usually the missing layer, and it cannot be delegated to a template.
- Define the operational side of the route before launch. An enquiry that waits three days for a reply undoes everything the site did well.
- Assign one owner with the authority and budget to change the site, and review real enquiries—not just traffic—on a fixed rhythm.
None of this requires a large team or a long timeline. It requires the discipline to treat the website as infrastructure with a job, and to judge it—continuously, by human review—on whether the job is being done. Companies that hold that line end up with smaller, plainer sites that quietly do more commercial work than the elaborate ones they replaced.
Related capability: Web Platforms & Digital Experiences