Website governance: who owns the site inside your company?

Who inside your company owns the website? If you cannot immediately put a name to it, that is exactly the problem that makes so many sites stall after launch. Website governance is about the organizational gap after go-live: who gets to decide, who keeps the content current and who watches over tech and security. In this article you will learn which roles to assign, how to lock down decision rights and which maintenance agreements to make so your website stays a working business asset instead of a project that was once “done”.

Why does a website stall after launch?

A website rarely stalls because of a technical fault. It stalls because, after launch, no one is clearly responsible for it anymore. The build project had a deadline, a budget and a point of contact. As soon as the site goes live, that structure disappears. The project lead moves on to the next thing, the agency delivers, and management ends up with “everyone”, which in practice comes down to no one.

You probably recognize the consequences: texts go out of date, a job posting stays up for months too long, a form stops working and no one notices, updates get postponed. Not out of unwillingness, but because it is not on anyone’s task list. This is an organizational problem, not a technical problem, so you solve it organizationally too. The guide on building a B2B website covers the build process itself, but governance is about everything that comes after.

The core of website governance is simple: make it explicit who is responsible for what, before the buzz of the launch is over and attention fades.

Who is the owner of the website?

The owner of the website is one person who is ultimately responsible for the direction and the priorities of the site, not the one who carries out every task themselves. This is the most important role to assign, because decision rights have to sit somewhere. Without a clear owner, every change becomes an endless discussion, and what belongs to everyone gets priority from no one.

That owner usually sits in marketing or on the commercial side, because the website is first and foremost an instrument to turn visitors into leads, not an IT system. He or she decides what is on the roadmap, assesses proposals, guards the coherence of the site and is the point of contact for the agency or the internal developers.

Important: ownership is not a title but a mandate. The owner must actually be allowed to decide and must have time in their calendar. An owner without a mandate or without hours is a name on a chart, and then you are back to square one.

Which roles do you need besides the owner?

Besides the owner, you ideally assign three kinds of responsibility: content, tech and decision. At a small company those roles can sit with the same person or with two people, but the responsibilities themselves must be named separately, otherwise they quietly disappear.

• Content management. Who keeps texts, case studies, job postings, prices and news current? This person makes sure the site matches the reality of the company. Out-of-date content costs trust, and trust is exactly what a B2B website has to inspire to generate leads.
• Technical management. Who watches over updates, backups, security, hosting, speed and the working of forms and integrations? Whether that is an internal developer or a fixed contract with your agency, it has to be assigned. This also covers keeping an eye on Core Web Vitals and fixing common accessibility mistakes in good time.
• Decision rights. Who approves changes and who sets the priorities when there are more wishes than time? That is usually the owner, but lock it down explicitly so a change does not get stuck because it is unclear who is allowed to say yes.

The mistake we often see is that a company does appoint a person to “do the website”, but without any distinction between these roles. Later it turns out the content manager does not do security and the IT person does not touch texts, and everything falls through the cracks.

Manage internally or outsource to an agency?

It is not a question of internal or external, but of which responsibility you place where. Many B2B companies keep content management in-house, because only the company itself knows what is correct and what the priorities are, and outsource technical management to the agency that built the site.

That split works well, on one condition: put the agreements in a maintenance contract or a service agreement. What falls under it, what falls outside it, within what timeframe is a problem picked up, and who pays for larger changes? Without those agreements, friction arises at exactly the moment something goes wrong. We are platform-independent and build in Webflow, WordPress and custom or headless. Per platform, what you can realistically manage yourself and what you are better off outsourcing differs, so tune the governance to the tech you have, not the other way around. A well-chosen content management system or headless setup helps determine how much an editor can do independently, and therefore how you split up the management.

Also be honest about internal capacity. Managing a website structurally costs time. If you do not free up those hours, outsourcing is not a luxury but the only way the management gets done at all.

Which maintenance agreements do you lock down?

Good maintenance agreements turn the vague “we keep the site up to date” into a concrete rhythm with names attached. It is not about a thick document, but about a few agreements that everyone knows.

Lock down at least these points. A fixed maintenance rhythm: for example a monthly content check and a fixed moment for technical updates, so it does not depend on whoever happens to have time. An owner per type of task, tied to the roles above. An escalation path: who do you call if the form or the site goes down, and within what timeframe? A change process: how do you request a change, who approves it, who carries it out? And finally measurement points: periodically look at what the site delivers in leads and requests, not just visitor numbers, so that management is about results and not about maintenance for the sake of maintenance.

That last agreement fits how we look at websites: a site is not a business card that is finished, but a business asset you steer on leads and revenue. Management is the mechanism that lets you keep adjusting. Whoever keeps sharpening their forms and conversion points gets more out of the same site year after year.

When is the best time to arrange this?

The best moment to lock down governance is before launch, as part of the build or redesign process. At that point attention is high, the right people are involved and you can take roles and agreements straight into the project. Arranging governance afterwards is possible too, but then you are fighting the habit that the site is now simply “just there”.

If your site has been live for a while and you recognize the symptoms of neglect, then start small. First appoint an owner with a mandate and time. Let that person assign the three responsibilities and agree on one maintenance rhythm. From that foundation you build out the rest. You do not have to nail everything down in one go, you mainly have to stop assuming that someone else is taking care of it.

The short summary

Websites stall after go-live because of an organizational gap, not because of tech. Fill that gap by appointing one owner with a mandate, assigning responsibility for content, tech and decision separately, and locking down maintenance agreements with a fixed rhythm. Do that preferably before launch and steer on leads, not on maintenance for the sake of maintenance. Want your new or existing site to stay a working business asset? In our web design approach, we think along about management and ownership from the very start.

Book your free intake