Your Website Isn't Done at Launch: What Ongoing Maintenance Actually Covers

Most website projects end the same way. The site goes live, everyone breathes out, the final invoice gets paid, and the relationship winds down. Six months later something breaks, and the client emails whoever built it with the words "is this something you can fix?"

It is. And at that point the fix usually costs more than it would have, because six months of drift happened in the dark. Nobody updated anything, nobody checked anything, and the first sign of trouble is a broken contact form or a page that redirects somewhere wrong.

What actually drifts

A site that just sits there isn't standing still. The world around it moves:

Dependencies collect CVEs. The frontend build, the server runtime, the database engine — all of them get security patches you never applied.
Certificates and DNS records expire. SSL renewal is automated when someone is watching. When nobody is, it fails at 2am on a weekend.
Integrations rot silently. A payment provider deprecates an API version. The site keeps working until the day it doesn't, and the error lands in an inbox nobody reads.
Content goes stale. Prices from three years ago, a team page with people who left, a blog whose last post is old enough to be embarrassing. Search engines notice this even if you don't.
The hosting itself changes. OS updates, PHP version bumps, disk filling up with logs. All fine until one of them takes the site down.

None of this announces itself. That's what makes maintenance hard to sell: everything looks okay right up until it isn't.

What a maintenance arrangement covers

When we keep a site on after launch, the work splits into two tiers. The boring tier is scheduled and cheap: updates applied on a regular cadence on a staging copy first, uptime and certificate monitoring with alerts that go to a human, backups tested by actually restoring one, and a short monthly report of what changed.

The second tier is hands-on time: content edits, small layout tweaks, a new landing section, an extra field on a form. This is what most clients actually want, and it's worth pricing explicitly instead of pretending it's free. When every small change becomes a mini negotiation, clients stop asking, the site calcifies, and in a year it doesn't represent the business anymore.

How to check whether your site is cared for

If a maintenance quote lands in front of you, or you're auditing what your current arrangement gets you, the honest questions are short:

When was the last dependency update applied, and was it tested on staging before production?
Do backups exist, and has anyone restored one in the last quarter?
Who gets the alert if the site goes down at 3am, and do they have access to fix it?
Is there a report of any kind, monthly or quarterly, that shows what was done?

If the answers are vague, you don't have maintenance. You have hosting.

The part clients underestimate

Maintenance isn't only about preventing disasters. It's also what keeps iteration possible. A site whose owner trusts that a change won't break production gets updated constantly: new services, better copy, seasonal campaigns. A site nobody dares touch freezes. The frozen one loses more business over a year than a single outage ever costs, because it slowly stops saying anything true about the company behind it.

So when a studio quotes you a monthly fee after launch, read it as insurance plus momentum, not as a tax. Ask what exactly it covers, ask for the boring tier in writing, and make sure the hands-on hours are priced so that small improvements stay small.