Product pages use the language of the product team. Service pages use the language of the service. The about page tells the history of the company to people who don't know the company and don't yet care about its history.
The people who need the website most are the ones it's least equipped to help: the prospective buyer who isn't sure yet, the committee member doing pre-meeting research, the CFO being asked to approve a vendor they've never heard of.
It gets treated as a web design problem. It's a clarity problem, handed to the web team to solve on their own.
Think about what the website actually is. It's the one salesperson in the business who is always available, never off-message, and never has a bad day. It's also, for most companies, the one that would be fired fastest if it were a person.
The reason is simple. The website can't fix a brand problem. It can only reflect one. If the brand hasn't answered the question, why this company and not the one with the same homepage in a different shade of blue, the website has nothing to work with. It will describe the company accurately and say nothing useful. A website redesign without a brand rethink is an expensive way to produce a prettier version of the same confusion.
And it keeps happening for a reason that has nothing to do with talent. Websites are built by web teams. Web teams think in pages and user journeys. They're very good at making content findable. Deciding what to say isn't their job.
So the content comes from the people who know the business: the product team, the marketing team, the leadership team. Those people describe the business from the inside out. They know every feature, every service, every point of difference. They write about it in the language that makes the most sense to them. Which is usually the language of people who already understand the business.
But the customer arrives with a problem they're trying to solve and a shortlist they're building. They need to understand quickly: is this company for people like me, and is it clearly better than the alternative? Most B2B websites answer neither question on the homepage.
So the website needs a point of view before it needs a design. A point of view on who the customer is and what they need to believe before they'll buy. Not a tagline, a point of view.
It's not a web brief. It's a brand brief. And it has to be written before anyone talks to a web agency, picks a CMS, or debates the navigation structure.
The businesses whose websites work, the ones that convert and shorten the sales cycle and help buying committees agree, have usually done this work first. Not explicitly, often. Not always through a formal brand process. But someone, at some point, forced the clarity: this is who we're for, this is the one thing we need them to understand, this is why they should trust us enough to have a conversation. Everything else is design.
There's a simple test for whether you've got it. Ask someone who's never heard of the company to spend 60 seconds on the homepage. Then ask them two questions: who is this for, and what do they get from it?
If they can answer both, clearly, without prompting, the website is working. If they can't, the problem isn't the website.