All posts
WebflowCMSB2B

What does a B2B website have to prove before a buyer gets in touch?

I think less than most briefs assume, and most of it has to be shown, not said. A business buyer who lands on your site has usually heard your name somewhere else first: a referral, an agent, a supplier list. They're not there to be persuaded. They're there to check four things: that you're a real company, how long you've been doing this, whether you've done it for people like them, and what exactly you sell. I go through each one below, using a site I built for a ship supplier in Uruguay as the example.

What a website can and can't do in a B2B sale

A website rarely wins a B2B deal. In most industries the relationship, the price and the referral do that. What a website can do is lose one, by making an established company look smaller or less certain than it really is. That's what I try to avoid.

So I think the job is narrower than most briefs admit. You're not building a pitch. You're building something that holds up when a purchasing manager has ten minutes to spare and three other suppliers to compare.

It also depends on how your buyers purchase. If they buy through tenders, marketplaces or a procurement portal, the website matters much less. In that case I'd put the effort into the documents they'll actually read.

First check: that you're a real company

The first thing a careful buyer looks for is boring: a legal entity, an address, a phone number, a person to write to. I'd make sure all of it is easy to reach from any page, so nobody has to hunt for it.

This is also where adjectives stop working. “Trusted”, “leading” and “world-class” don't answer the question, and they're on every competitor's homepage, so a buyer's eye just skips them. The test I use for any sentence on a B2B site is whether a stranger could verify it. A founding year can be checked. So can a client count, a list of countries, a named port or a legal entity. “Your trusted partner” can't, so when I review a page I replace that kind of line with something checkable or remove it.

For example, Seilas Ship Supplies (Nadetir S.A.) has supplied vessels at every port in Uruguay since 1921: deck and safety gear, engine-room supplies, provisions, bonded stores. They had a century of reputation and a website that carried almost none of it. The brief was a credible, international site that says “trusted since 1921” without having to use the word, so every decision below went back to the four checks.

Second check: how long you've been doing it

Age matters to a buyer because a supplier that has been around for a long time will probably still be around after the order. It's one of the few things a site can show quickly.

On Seilas the founding year isn't a tagline. It runs through the whole site, and the history has its own section. I framed that section for a buyer rather than as a family album, so it reads as a track record.

If your company is new, I wouldn't build the site around age, because it puts the focus on exactly what you don't have yet. I'd lead with the work and the people instead and let the proof build up over time. What I'd never do is inflate the age or the scale, because a buyer who checks will find out.

Third check: whether you've done it for people like them

Here the buyer is looking at scale, geography and the specific kind of work, more or less in that order. They want to know if you already serve companies like theirs, or if they'd be one of the first.

On Seilas the clients section puts the claim and its shape side by side: more than 500 clients across more than 30 countries, on a world map. I wanted the map next to the number because the number alone doesn't tell you whether the reach is regional or global, and the map shows that at a glance.

Fourth check: what exactly you sell

A buyer comparing suppliers needs the range laid out plainly, in their vocabulary and not yours. If they can't confirm quickly that you do the thing they need, they move on to the next supplier.

On Seilas the services are organized the way a ship's purchasing officer thinks about them, by category, from loading to dry dock assistance. The idea is that a buyer can confirm in seconds that what they need is something Seilas does.

The design stays restrained on purpose. I think a century-old supplier that looks like a startup sends the wrong signal to this kind of buyer. The page itself is part of the check too, because a slow or broken page is evidence and buyers read it. In Lighthouse the live site measures 100 for SEO, 100 for best practices and 90 for accessibility. Those scores don't sell anything on their own, but they mean the page isn't working against the rest of the site.

Keeping the proof accurate after launch

Proof only works while it's true. A client count that was accurate when the site launched becomes a liability the day nobody updates it. That's why the Seilas site is CMS-driven where things change: the team keeps those parts current without calling a developer, and the parts that should never move are built into the page.

The other cost is the restraint. A quiet site does less to grab attention than a loud one. For a supplier whose buyers already know who they're looking for, I think that's the right trade. For a company that needs its website to generate demand on its own, it probably isn't, and I'd design it differently.

How to check your own site

Open it the way a stranger would, on a phone, and give yourself thirty seconds.

  • Can you find the company's legal name, its address and a direct contact without hunting for them?
  • Is the company's age on the first screen, or only on an About page most visitors never open?
  • Count the adjectives in your hero section. Replace each one with a fact, a number or a place, or delete it.
  • Take your three biggest claims and ask how a buyer could verify each one. If they can't, I'd rewrite the claim or remove it.
  • Ask someone outside the company to tell you, in one sentence, what you sell. If their sentence doesn't match yours, the services page was probably written for you and not for the buyer.
start a project

Ready to build.

A few quick details so I can scope it before we even talk, or just email me directly.

hello@lucasmujica.dev
Buenos Aires · Remote worldwide

Hi Lucas, I'm from . I'm building a with a budget around . Reach me at .

The details that decide the price
Replies within a day