Why “Launched and Left” Is the Most Expensive Thing You Can Do to a Website

There’s a moment, a few weeks after a new website goes live, when the excitement settles and the project gets mentally filed under “done.” The emails slow down. The client moves on to the next thing. The site just… sits there.

This is the most common way a good website becomes a problem.

It doesn’t happen dramatically. It happens in slow accumulation: a security plugin stops being updated. A form stops sending to the right email because someone changed inboxes. A page about an event that happened two years ago stays at the top of the site because nobody got around to taking it down. A new staff member joins but never appears on the About page. A board member tries to share the church website with a donor and realizes the sermon player stopped working sometime last winter.

None of this is catastrophic on its own. Together, it quietly tells every visitor: nobody’s home.

The actual cost

An outdated website doesn’t just look bad — it creates work. When something finally breaks enough to notice, it usually costs more to fix than regular maintenance would have. Security vulnerabilities compound. Hosting configurations drift. The person who built the site is gone and nobody knows the passwords. What would have been a ten-minute fix becomes a half-day project.

More than the money, there’s the cost to trust. For a nonprofit or a church, a website that looks abandoned signals an organization that may be too — even when that’s completely false. A visitor who can’t tell if you’re still active isn’t going to reach out to find out. They’ll move on.

What a care plan actually does

Ongoing maintenance isn’t glamorous, but it’s specific: security patches applied on schedule, content edits made when things change, broken links caught before visitors find them, a quarterly look at what’s working and what needs attention, and someone on the other end of an email who knows the site well enough to fix things quickly.

The difference between a maintained site and an abandoned one isn’t dramatic month to month. Over two or three years, it’s enormous — both in the quality of the site and in the time the organization doesn’t have to spend on it.

A note on “we’ll just update it ourselves”

This works sometimes, for some organizations. It tends to work when there’s a specific person whose job includes the website, when they have time protected for it, and when they have the confidence to make changes without breaking things.

It tends not to work for the same reason most good intentions don’t: not because the people aren’t capable, but because the website always loses the priority battle against everything else that needs doing.

That’s not a failure. It’s just honest about how small organizations run.

If you have someone who wants to manage content — a volunteer, a staff member, a junior admin — the best arrangement is usually one where they handle the words and photos, and someone else handles the security, structure, and technical layer. That way the site actually stays current without any one person carrying the whole burden.