Maintenance
The maintenance conversation clients avoid, and why it costs them
The day it goes live is the day it starts to rot.
Not dramatically. A plugin author stops shipping updates. A library picks up a known vulnerability. A contact form starts failing silently because an API on the other end changed shape.
The site looks identical. It works fine, right up until the morning it does not. The real maintenance conversation is about ownership, and it is the one that always gets skipped. The build is exciting, the launch has a date and a party. Maintenance has neither, so it falls into the gap between departments.
Marketing owns the campaigns and the copy, and assumes someone technical is watching the rest. Dev owns the build, then moves to the next build; the site was a project, not a standing responsibility. IT owns the network and the laptops, and the website was never on their list, and nobody put it there.
The one box that matters is empty. When a plugin needs updating at 9pm on a Tuesday, no phone buzzes, because it belongs to nobody.
Everybody owns a piece. Nobody owns the site.
When nobody owns it, the knowledge evaporates.
The agency moves on. The marketing manager who knew where everything lived takes a new job. Six months later someone is staring at a WordPress admin full of plugins they have never heard of, afraid to touch anything in case one is load-bearing. The site enters defensive paralysis, and paralysis is exactly what lets the rot pile up.
Then the content goes stale, which is the symptom leadership finally notices. The events page lists last spring's conference. The team page has two people who left. Together they tell every visitor this organization does not look after its own front door.
An ownership problem in a budget problem's clothes.
Most compromised sites were not outsmarted. They had a door left open because the person whose job it was to close it did not exist. The fix was sitting right there, and there was no somebody to apply it.
The short, uncomfortable conversation.
Who owns this site on Monday morning? Not the team. A person. We push clients through this before launch because the honest answer is usually a pause, and a pause is not a maintenance plan. When a plugin needs updating at 9pm on a Tuesday, whose phone buzzes? If you cannot name them, you do not have a plan. You have a hope, and hope is what leaves the door open for the automated scripts that check it every night.
The conversation costs an hour before launch. Skipping it costs a rebuild. It's why naming an owner is step one of every Keystone engagement, not an afterthought bolted on later.