Corporate Web Design: Beyond a Digital Brochure

A digital brochure describes the company. A corporate website has to survive being checked — by a buyer building a shortlist, a candidate deciding whether to apply, a journalist confirming you exist, and a search engine deciding whether to show you. Those four are looking for different things, and none of them is looking for adjectives.

That is the whole difference, and almost every corporate site that underperforms fails it in the same way: it asserts things nobody can verify.

The visitor arrives suspicious

By the time someone reaches your site, they have usually already decided you are a candidate rather than a choice. They are not reading to be persuaded; they are reading to eliminate. The questions they are answering, roughly in order:

• What exactly does this company do — specifically enough that I could describe it to a colleague?
• Who runs it, and have they done this before?
• Who else has bought it?
• What does it cost, or what determines the cost?
• What happens when something goes wrong?

A brochure site answers the first vaguely and the rest not at all. Then it adds a paragraph about passion and innovation, which is the part the visitor skips.

The practical test: can a stranger verify three claims on your site without contacting you? Not believe — verify. If the answer is no, the site is a brochure regardless of how it looks.

The pages where trust is actually decided

Not the homepage. The homepage gets scanned; these get read.

The About page. Google's quality rater guidelines devote whole sections to finding who is responsible for a website and who created its content, and to finding About Us, contact and customer service information — which tells you that "who are these people" is a signal the search ecosystem treats as meaningful. We wrote about what that implies in what Google actually rewards. Three sentences and a stock photo is a wasted page on the one page where trust is settled.

The work or case pages. Specific beats impressive. What the problem was, what you decided and why, what changed. A case study with no decisions in it is a testimonial with extra pictures.

The pricing or scoping page. If you can publish numbers, publish them. Most companies can publish more than they do — a range, a starting point, the variables that move it. A buyer who cannot estimate assumes the worst and leaves, and you never hear about it.

The contact page. It should say what happens next and when. "We'll be in touch" is the least informative sentence on most corporate sites.

The three measurable floors

Everything above is judgement. These are not, which makes them the right place to start an argument about quality:

1. Core Web Vitals, in the field. Not a Lighthouse score from a laptop — the field data that describes real visitors. A corporate site has no excuse for failing this; it is mostly text and images.
2. WCAG 2.2 AA. Keyboard operation, contrast, focus visibility, form labels, alt text. This is a legal and practical requirement, not a preference, and it overlaps almost entirely with being usable.
3. Readable without JavaScript. If the main content only exists after client-side rendering, you are gambling on the renderer of every crawler, assistant and reader-mode tool that visits.

Meeting all three does not make a site good. Failing any of them caps how good it can be, which is why we treat them as entry conditions rather than achievements.

What actually distinguishes the good ones

Having removed the excuses, what is left is specificity and restraint.

Say one thing clearly. A corporate homepage that lists nine capabilities communicates none. The site that wins the shortlist is usually the one a buyer can summarise in a sentence afterwards.

Show the reasoning, not just the result. A screenshot proves a thing exists. An explanation of why it is that way proves someone thought about it — and thinking is what a buyer is actually purchasing.

Publish something only you could write. A position, a measurement, a method, a thing you refuse to do. This is the same property that makes a page quotable by AI systems, which is a useful coincidence rather than the reason to do it.

Design for the second visit. Nobody buys on the first. The navigation should make it easy to come back and find the specific page that mattered, which argues for clear structure over a scroll-driven narrative that has to be replayed.

Where we say no

We do not build sites whose central claim is a superlative. "Leading", "innovative" and "world-class" are checkable by nobody and therefore worth nothing, and they occupy the space where a specific claim could have gone.

We do not put a stock photograph of a handshake on a page about people. If a company cannot show its own people, the honest move is to say why rather than to substitute a stranger.

And we will say when the problem is the offer rather than the site. A company that cannot explain what it sells to its own team will not get a website that explains it to strangers — and that is a positioning conversation, not a redesign.

The audit you can run this afternoon

1. Pick three claims on your homepage. Can a stranger verify each one without emailing you? If not, replace them with claims they can.
2. Read your About page as a candidate. Would you apply? Would you believe this company employs anyone?
3. Open a case study and count the decisions. Zero means it is a testimonial.
4. Check field Core Web Vitals and keyboard navigation. Both are free to check and neither is a matter of opinion.
5. Ask five people what the company does after thirty seconds on the site. If you get five answers, the site says nine things and communicates none.

If you want that read done from outside, send us the site — or see how we approach a build on the custom web development page.