A website isn't finished when it launches

There's a moment near the end of every website project that feels like the finish line: the site goes live. It's the natural place to celebrate, and it should be. But launching a website isn't the last step. Over time, software is updated, browsers change, security standards evolve, and businesses grow. Periodic maintenance helps keep a website secure, compatible, and aligned with your current needs.

This isn't a sales point dressed up as advice. It's just how software behaves — and understanding it changes how you think about what you're commissioning.

Why a finished site doesn't stay finished

A website sits on top of software that keeps moving underneath it — the systems that run it, the browsers that display it, the security landscape it lives in. All of that changes constantly. A site that was correct and secure on launch day is, a year later, running on foundations that have shifted beneath it. Nothing dramatic happens on any single day. But left long enough, the small drift adds up: a security hole opens that wasn't there before, a browser update breaks something that used to work, a form quietly stops sending and no one notices until a customer mentions they never heard back.

The site didn't fail because it was built badly. It failed because it was left alone in a world that didn't hold still.

What "keeping it running" actually involves

Ongoing care isn't a vague retainer. It's a set of specific, unglamorous jobs. Security updates applied before a hole becomes an incident. A watch kept on whether the site is actually up and working. Small fixes when something drifts. The occasional content change you need made. And, over time, the steady work of staying findable — search visibility isn't won once at launch and held forever; it's maintained.

Most of this is invisible when it's done well. That's rather the point. The absence of problems is the product. You notice ongoing care mainly by never having the bad afternoon where the site is down, a customer can't reach you, and no one's quite sure who to call.

What this means for how you buy

The practical upshot is that when you commission a website, you're really commissioning two things: the build, and the life of the site afterward. It's worth being clear with yourself about both, and clear with whoever you hire about who handles the second.

Some arrangements hand you a finished site and consider the job done — which is fine, so long as you know the upkeep is now yours to arrange. Others treat launch as the beginning of the relationship rather than the end of a transaction, and stay responsible for the site's continued health. Neither is wrong. But they're different things, and the difference matters more than it appears to on launch day.

For most businesses, a website isn't something you want to own the maintenance of. It's something you want to work, reliably, while you get on with your actual business. That's worth saying out loud when you hire — because "what happens after launch?" isn't a detail. For the years that follow, it's most of the story.