What happens after a website launches — and who should own it?
The website launches. The project team moves on. Somebody has the logins, somebody looks after the hosting, and marketing can update the content. But who is responsible for noticing whether it still does the job the business needs?
That question is easy to leave unanswered because several people already look after parts of the site. The developer handles technical issues. Marketing adds pages. Sales mentions that something needs changing. An agency sends a report.
Each of those contributions can be useful. They don’t automatically add up to someone keeping hold of the whole picture.
A website can be running perfectly while becoming less useful to the business. The offer changes. Customers ask different questions. New material accumulates. Important pages slip behind newer priorities. Nothing breaks, but the site gradually stops reflecting what matters.
Maintenance and usefulness need different attention
Technical maintenance matters. Hosting, security, software updates, backups and working integrations need appropriate ownership for the platform you use.
Someone also needs to keep basic information accurate and make sure enquiries reach the right people.
But those responsibilities don’t answer every question. Are we attracting suitable visitors? Does the website explain the work we now want more of? Can customers find the evidence they need? Is the team making changes because they help, or because someone asked for them?
Those questions require context and judgement as well as technical care. Keeping the website available is one responsibility. Keeping it aligned with the business is another. The same person might handle both, or the work might be shared.
The important thing is that somebody knows where those responsibilities sit.
Someone needs to notice what has changed
A useful website review starts with what is happening in the business and with its customers, rather than looking for a fresh list of things to change.
Sales might be hearing the same misunderstanding repeatedly. A service that used to lead the offer might have become less important. Search data might reveal questions the site doesn’t answer. The marketing team might be spending hours working around an editing constraint.
These are different kinds of evidence. They become more useful when someone can connect them.
At Locale, the work continued beyond a website rebrand and rebuild into content, search, design and optimisation. As the product and marketing evolved, search performance and user behaviour helped guide what deserved attention next.
The continuity meant later work could build on the existing platform and context. Every question didn’t have to become a separate project with a new starting point.
Launch data is the beginning of a conversation
A report can show that traffic has changed, a page is being found or a particular route is rarely used. It doesn’t always tell you why, or what response would be worthwhile.
More traffic might be welcome, or it might be arriving for something you no longer want to sell. A low enquiry count might reflect a broken route, unsuitable visitors or a long buying process. A quiet page might be unimportant, or it might be exactly the page your best prospects need after a referral.
Interpret the evidence against what the website is supposed to do. Combine it with customer questions and what the team is experiencing. If you don’t yet understand the cause, investigate before choosing the fix.
For a smaller business, the evidence may be modest. A few customer conversations, a tested enquiry route and a clear view of relevant search activity can be more useful than a dashboard nobody acts on. Avoid treating small fluctuations as a reason to change direction every week.
Continuing improvement doesn’t mean constant change
There is no virtue in manufacturing a monthly list of website jobs. Sometimes the useful decision is to leave something alone.
The purpose of paying attention is to distinguish between an issue that matters, an opportunity worth exploring and something that can wait. That includes deciding what not to prioritise.
Sometimes the next step is a small content change. Sometimes it is a more substantial piece of work. Sometimes a supplier needs a clearer brief, or a business decision needs to be made before anyone touches the website.
The EV decision-support tools evolved over several years as customers faced new questions about electric vehicles. Existing products were refined while new capabilities were introduced across markets and partner channels. The platform’s usefulness depended on responding to a changing situation, rather than treating release as the point at which the thinking ended.
That doesn’t mean every website needs a growing collection of features. It means the decision to add, change or retain something should follow what people need.
Give ownership something concrete to mean
“Marketing owns the website” can sound clear while leaving several practical questions unresolved.
It helps to agree:
- Who notices? Who brings customer feedback, business changes and performance questions into view?
- Who decides? Who can say what matters, what can wait and what needs more investigation?
- Who acts? Who makes the change, or gives the right supplier a useful brief?
- Who checks afterwards? Who looks at whether the change helped and records what was learned?
One person doesn’t have to do all the work. They do need enough context and authority to keep the responsibilities connected.
Agree how often to look together and which events deserve attention sooner: a changed offer, a recurring customer problem, a significant performance shift or an important new initiative. The rhythm should fit the business, its capacity and the rate of change.
A short record of the decision, its reason and the intended outcome is often enough to stop the same question being reopened without remembering why it was settled.
When does outside help make sense?
If your team already has the context, capacity and authority to do this, outside involvement may add little. A technical support arrangement may also be entirely adequate if the website’s role is stable and someone inside the business keeps it accurate and useful.
If there is one clear problem, deal with it as a defined piece of work. A recurring need should not be invented around a finite project.
Outside continuity becomes more useful when the same questions keep returning, several suppliers see different parts of the situation, or important changes drift because nobody quite owns the decision.
That is the kind of need Stewardship is designed around: keeping enough of the business context to help judge what matters and make sure an appropriate response follows. The value is in useful attention over time, rather than a quota of activity.
Who will notice the next thing?
A good launch can give a business a much better foundation. It cannot anticipate every service change, customer question or decision that follows.
Before commissioning another project, ask who will notice when the next thing starts drifting, who can decide whether it matters and who will see the response through.
If there is already a clear answer, you may have what you need. If there isn’t, the website’s next problem may be an ownership question before it becomes another redesign brief.