Launch day is the loudest day of a project.
Champagne optional. Relief guaranteed. Months of work, briefings, feedback loops, rounds of corrections, lead to a single moment: go-live.
And then, the project actually begins.
The web does not wait
CHAPTER 1: THE ILLUSION
What comes after decides whether a website works, not the date it went live. User behaviour cannot be predicted in a briefing. Technical gaps only show under real conditions. And the market you built for has already moved on by launch.
Still, in most projects the launch is treated as the end point. Budget used up. Team dissolved. Responsibility handed over.
According to a study by Forrester Research, over 60 percent of all company websites measurably lose performance within 18 months of launch, not because they were built badly but because nobody looks at them any more.
The biggest mistake does not start with the wrong concept. It starts with the wrong end point.
What really happens in the first 90 days
CHAPTER 2: THE REALITY
A new website is a hypothesis. The launch is the moment you start testing it.
Real users click differently than in the usability test. Conversion paths that were conclusive in theory break off in practice. Pages that hardly anyone visits tie up resources. Pages that perform get too little attention.
In the first 90 days after go-live it is decided whether a website becomes a tool or stays a business card.
This does not require reinventing anything. It requires consistency: read the data. Recognise patterns. Adjust priorities. Sharpen content. Optimise load times. And sometimes: discard an assumption you held to be certain for a long time.
Anyone who has nobody looking in this phase loses.
The difference between handover and accompaniment
CHAPTER 3: THE RESPONSIBILITY
There are two ways to finish a web project.
The first: hand over the deliverable, send the invoice, document the closure. The agency has delivered. What comes after is the client's business.
The second: be present at the moment of launch, and even more so afterwards. Set up monitoring. Interpret the first figures. Give recommendations before they are requested. Not leave the client alone with a system they do not understand yet.
The difference is not technical. It is a question of attitude.
Whoever takes responsibility for a result does not stop when the file is uploaded. They stop when the goal is reached, and define together what that means.
What post-launch support means in practice
CHAPTER 4: THE PRACTICE
It is not about maintenance contracts. It is about continuity.
In concrete terms this means:
Monitoring – not as an end in itself but as a basis for decisions. What works? What does not? Why?
Iteration – small, targeted adjustments based on real data. No redesign every three years. Constant, calm improvement.
Communication – proactive, not reactive. Do not wait until something is on fire. Report what you see, even if nobody asked.
Development – a website that grows with the company. New requirements, new content, new goals. Not as a project. As a process.
That sounds like more effort. It is less, because problems stay smaller when you look at them early.
The launch is the beginning of the proof.
