What Makes a Great Corporate Website? Lessons From Our Rebuild

For a while, the most embarrassing thing we owned was our own website.

We'd built genuinely good things for clients — fast, considered, the sort of work we were proud to put our name to. And then there was thenimaproject.com: a few years old, slow on mobile, with copy that said a lot of words without saying much at all. An agency with a dated site is its own worst advert. Every time we sent a prospective client a link, I felt it.

So we rebuilt it. Not a fresh coat of paint — a proper teardown and a new foundation. And rebuilding the thing you sell to other people is a particular kind of humbling, because you can't hide behind a brief. You are the brief.

This is what the rebuild taught us about what makes a corporate website actually work in 2026. No theory we didn't test on ourselves. Grab a coffee.

Key takeaways

• →A corporate website's real job is selling while you sleep — buyers research you long before they ever speak to you.
• →Clarity beats cleverness: say what you do in plain words, and keep the site, the sales pitch and the truth aligned.
• →Trust is designed, not claimed — visual quality, upfront pricing and contact details, and current content do the heavy lifting.
• →Performance and accessibility aren't extras any more — Core Web Vitals affect ranking, and the European Accessibility Act made access the law.
• →Build to be found by AI as well as Google: clear answers and real structure get you cited in AI search, not just listed.

Lesson 0 — Why we rebuilt our own site

There's a credibility paradox in running an agency. The work that pays the bills lives behind NDAs and on client domains, so the one site you fully control — your own — carries a disproportionate amount of your reputation. If it's dated, people quietly assume the work is too.

The research backs up that hunch harder than I'd like. Stanford's web-credibility work found that around 75% of users judge a company's credibility based on its website design. Not its case studies. Its design. We were asking people to trust us with their brand and product while ours looked tired. The rebuild wasn't vanity; it was fixing a leak.

If you're reading this because your own site has started to feel like a liability, that exact gap — between the work you do and the site that represents it — is what a rebrand and product evolution is meant to close.

Lesson 1 — A corporate website sells while you sleep

The first thing the rebuild forced us to admit: we'd been thinking of the site as a brochure, when buyers were already using it as the main event.

Gartner's research on the B2B buying journey is blunt about this. Across a typical purchase, buyers spend only about 17% of their time meeting with potential suppliers — and because they're comparing several at once, any single vendor might get around 5% of a buyer's attention. A bigger chunk, roughly 27%, goes on researching independently online. In plain terms: most of the deciding happens on your website, without you in the room.

It's gone further since. In March 2026, Gartner reported that 67% of B2B buyers now prefer a rep-free buying experience, up from 61%. People want to find the answer themselves before they talk to a human. If your site can't give it to them, they fill the gap with assumptions — or a competitor.

That reframed the whole project for us. We stopped designing a digital business card and started designing a self-service salesperson — one that works at 2am when a founder in another time zone is deciding whether we're worth an email.

Lesson 2 — Clarity beats cleverness

When I read our old homepage out loud, I winced. It was full of the sort of language that sounds impressive and means nothing. We'd written it to sound like a serious agency, not to be understood by a tired person on their phone.

The GOV.UK design principles became our north star here — particularly "start with user needs" and "do the hard work to make it simple." Plain words are not dumbing down. Plain words are respect for the reader's time. So we cut the jargon, led with what we actually do, and made every page answer one question a real buyer would ask.

There's a second, sharper reason to get this right. Gartner found that around 69% of B2B buyers report inconsistencies between a supplier's website and what its sellers tell them later. That inconsistency reads as either incompetence or spin, and both erode trust. The fix isn't more polish — it's making the site, the sales conversation, and the truth say the same thing.

Lesson 3 — Information architecture for a buying committee

The other thing we'd got wrong: we'd designed for one imaginary visitor. Real B2B decisions involve several people — a founder, a head of product, someone who'll sign off the budget, maybe an engineer kicking the tyres on whether we can actually build the thing.

They arrive with different questions and they don't read top to bottom. So the rebuild leaned hard on structure: clear navigation, scannable headings, and pages that let each person jump to the bit they care about. The engineer wants proof you can build it; the budget-holder wants to understand what an engagement looks like; the founder wants to feel understood in the first ten seconds.

Good information architecture isn't decoration — it's the difference between a site that answers a committee and one that only serves the person who happened to land on the homepage.

Lesson 4 — Trust is designed, not claimed

You cannot write "trusted partner" on a page and make it true. Trust is something the design either earns or loses, often before a word is read.

How fast? Lindgaard and colleagues found that users form a reliable judgement about a site in about 50 milliseconds — and that roughly 46% of that judgement is driven by visual appearance. Half a tenth of a second. You don't get to explain yourself first.

Nielsen Norman Group's work on trustworthy web design breaks down what earns that snap judgement into four credibility factors, and we used them as a literal checklist:

• Design quality. It has to look current and cared-for. A dated visual is read as a dated business.
• Upfront disclosure. Show your pricing approach and your contact details plainly. Hiding them signals you've got something to hide.
• Comprehensive, correct and current content. Typos, dead links and a blog that stops in 2023 quietly kill credibility.
• Connected to the rest of the web. Real links out, real proof, a presence beyond your own domain.

The humbling part of our audit: we failed three of the four. So we put our contact route and a straight description of how we work on every page, fixed the typos we'd been blind to for a year, and committed to keeping content current — this very blog is part of that promise.

Lesson 5 — Performance is part of the brand

Here's the one engineers feel in their bones and everyone else underrates: a slow site doesn't feel "a bit slow." It feels cheap. Every spinner is a tiny erosion of the trust you spent design budget building — and as we dug into the real cost of a slow website, the bill shows up in lost enquiries long before anyone complains about speed.

Google's Core Web Vitals put numbers on it: Largest Contentful Paint should land within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift below 0.1. These aren't just engineering targets — they're a confirmed ranking signal, so the slow site is also the harder-to-find site.

The usual culprit is weight: enormous hero images, autoplaying video, a stack of third-party scripts nobody audits. On our rebuild we treated every kilobyte as something that had to earn its place. We statically export the whole site, serve modern image formats, and lean on tooling like Entropy to keep heavy media from quietly wrecking load times. Fast isn't a feature you bolt on at the end. It's a decision you make on the first day and defend on every one after.

Lesson 6 — Accessibility is now the law

This one stopped being a nice-to-have on 28 June 2025. The European Accessibility Act became enforceable for products and services sold to EU consumers, and web compliance maps — via the EN 301 549 standard — to WCAG 2.1 AA. If you sell into the EU, an inaccessible site is now a legal exposure, not just a missed audience.

But honestly, the law is the least interesting reason to care. The GOV.UK principle is "this is for everyone," and that's the right frame. Good colour contrast helps someone reading in bright sun. Proper keyboard navigation helps power users. Clear labels help screen readers and the AI agents now parsing your pages. Accessibility done properly makes the site better for people who aren't disabled too — it's just good building.

We run automated accessibility checks on our own site — a real browser auditing the built pages against the WCAG rules — so a regression gets caught in testing rather than months later in a complaint. Making the check part of the process, not a good intention, is the only version that actually holds.

Lesson 7 — Build to be found by AI, not just Google

The newest lesson, and the one we're still learning. A growing share of people now start with an AI Overview or an answer engine rather than ten blue links. They ask a question and get a synthesised answer — and the game becomes being cited in that answer, not just ranked below it.

This goes by a few names — answer engine optimisation, generative engine optimisation — and the encouraging news is that it isn't a whole new discipline. Google's own position is that optimising for AI search is still SEO. The structure that gets you cited is the structure that was always good: clear questions answered directly, real statistics with sources, quotable sentences, and clean semantic markup a machine can parse without guessing.

It rhymes with the design-system thinking in our piece on using AI tools well without losing your brand — give the machine clean, structured material and it represents you faithfully; give it mush and it invents. We restructured our content so the answer to a buyer's question is the first thing on the page, not buried under three paragraphs of throat-clearing. Turns out that's better for humans too.

How we actually built it

Under the bonnet, the rebuild is deliberately boring, because boring is fast and boring is reliable.

The site is a statically exported Next.js project — every page rendered to plain HTML at build time and served from the edge, with no server doing work while a visitor waits. It runs off a design system: tokens for colour, type and spacing, a small set of components, and one button system instead of fifteen one-off buttons. That consistency is what lets us move quickly without the site drifting out of shape.

Images go through a pipeline that generates modern formats and the right sizes, so we never ship a desktop-sized photo to a phone. Metadata, sitemap and structured data are generated from the content rather than hand-maintained, so they can't fall out of sync. None of this is exotic. It's just the discipline of deciding, once, how things should work, and then not breaking your own rules.

If you're earlier on — building your first real site rather than rebuilding a tired one — the same foundations apply, and a product and brand MVP foundation is the version of this scaled to a launch rather than a relaunch.

What I'd tell my past self

If I could send one note back to the version of me who kept putting off our rebuild: your website isn't the thing you point clients to. For most of them, it is the first meeting. It sells, reassures, and qualifies while you're asleep — so the question isn't "does it look nice," it's "would I hire us based on this alone?"

For a long time our honest answer was no. Now it's yes, and the difference wasn't a bigger budget. It was clarity over cleverness, trust we designed instead of claimed, speed we refused to compromise, access we treated as standard, and structure that both people and machines can follow.

If your own site has started to feel like the weakest thing you'd show a prospect, I get it — we lived there. Have a look at how we work and the results we've shipped, and if you'd like a straight, no-sales-pitch conversation about your rebuild, get in touch. We've just been through it ourselves, so we know exactly where it hurts.