Last updated: 5 June 2026
Launch feels like the finish line. After weeks or months of work the site is finally live, and it is tempting to think the job is done. But a website is not a painting you hang on the wall. It is more like a car: it works best when someone looks after it, and worst when it is left untouched until something breaks.
Software rots
It sounds odd — code does not change by itself. But everything around it does. Browsers are updated, security holes are found in the libraries the site is built on, and dependencies go out of date. A site that was perfectly safe and fast at launch can a year later have known vulnerabilities simply because the world around it has moved on.
Security is perishable
This is closely tied to the previous point. Most attacks exploit known, old vulnerabilities — holes that were patched long ago in newer versions, but which are still open on sites nobody has updated. Maintenance is in practice what keeps that door closed over time. Security built in at launch is good, but it is not a one-off job.
Content that goes out of date
The least technical, but often most visible form of decay: prices that no longer hold, employees who have left, services you no longer offer, a "news" page where the latest post is two years old. Outdated content damages trust with visitors and weakens visibility in search. A living site signals a living business.
What maintenance actually is
It is rarely dramatic. It is the sum of small, regular things:
- Updating dependencies and applying security fixes
- Backups that are actually tested, not just taken
- Monitoring uptime and performance
- Small fixes and adjustments as needs come up
- Updating content that has become outdated
None of it is big on its own. It is the absence of it over time that becomes a problem.
The cost of not doing it
"We will deal with it later" is the most expensive sentence in this industry. A site that is maintained regularly costs little and predictably. A site that is neglected until it breaks — hacked, down, or so outdated that it has to be rebuilt — costs far more, and usually at exactly the worst moment.
It is the same logic as with a car: an oil change is cheap, a blown engine is not.
You decide who does the job
The important thing is not who maintains the site — it is that someone does. If you own your code, you have the freedom to choose: let us run it for you, or take it with you and do it yourself or with someone else. The point is that the choice is yours, and that someone actually takes responsibility before it becomes urgent.
A website built to last but never maintained is like a house with no upkeep. It looks fine for a while. Then it starts to leak.