The Unglamorous Work That Keeps Websites Running

Key takeaways:

• Regular website maintenance prevents compounding technical debt that costs significantly more to fix than it does to prevent through consistent upkeep.
• Modern page builder updates like Beaver Builder 2.10 deliver meaningful improvements in build speed, content consistency, and accessibility scores — not just feature bloat.
• The best website setup for a business is one where the client’s team can manage day-to-day content without calling their developer for every small change.

The quiet weeks are when the real work gets done

Most people spend the last two weeks of December catching up with family, switching off, and eating things they’ll regret. My team at Chillybin does some of that too. But those quieter days between Christmas and the new year are also when I do the internal work I never have time for during a busy quarter. Better project templates. Tighter handover documentation. Streamlined onboarding processes. Nobody’s writing a case study about any of that. It won’t win an award. But it’s the work that makes everything else run better for the next twelve months.

I’ve been building websites since 1998. I’ve seen the industry go through enough cycles to know that the unglamorous work — maintenance, documentation, systematic improvement — is almost always where the real value lives. The flashy stuff gets the attention. The maintenance is what protects the investment.

Why do so many businesses treat website maintenance as optional?

Because the consequences are invisible until they’re not. A website that hasn’t been updated in eight months still loads. It still looks the same. The contact form still works. So the business owner assumes nothing is wrong. Then one day the PHP version gets deprecated, the plugin that handles their e-commerce checkout throws a conflict, and they’re looking at a broken site on a Friday afternoon with no one available to fix it.

I’ve seen this pattern so many times that I’ve stopped being surprised by it. A client comes to us with a site that was built three or four years ago, never touched since launch, and they’re wondering why their Google rankings have dropped, why their site is flagging security warnings, or why their images suddenly aren’t loading. The underlying cause is almost always the same: zero maintenance over a sustained period.

The comparison I always come back to is property. Nobody buys a house and assumes it will maintain itself indefinitely. You paint it. You fix the roof. You service the hot water system before it fails, not after. Websites are infrastructure. They need the same thinking applied to them.

The business case for maintenance isn’t complicated. Fixing a major issue after the fact typically costs four to ten times what it would have cost to prevent it. I’ve quoted clients $800 to resolve a cascading plugin conflict that started from an update that should have been tested and staged months earlier. The same update, handled as part of a regular maintenance cycle, takes twenty minutes.

What does a proper maintenance cycle actually include?

At minimum: WordPress core updates, theme updates, plugin updates tested in a staging environment before being pushed live, security scanning, uptime monitoring, broken link checks, database optimisation, and off-site backups verified as restorable. That last point matters more than most people realise. A backup that’s never been tested is not a backup. It’s a file that might restore your site, or might not, at the worst possible moment.

A lot of agencies sell “maintenance plans” that are essentially automated plugin updates and a weekly backup. That’s not maintenance. That’s the minimum viable effort dressed up as a service. Real maintenance involves someone who understands the site architecture reviewing what changed, understanding whether a plugin update introduces a breaking change, and making a judgment call about whether to hold, test, or push.

We’ve had clients on maintenance plans with other providers who came to us after something went wrong, and when we looked at the history, the “maintenance” had been running on autopilot. Updates applied in bulk with no staging, no testing, no one actually looking at the site. It’s the equivalent of telling someone their car has been serviced because you put petrol in it.

The clients I’ve seen get the most value from maintenance are the ones who think of it as a retained service, not a break-fix arrangement. They’re paying for peace of mind, for expertise on tap, and for someone who already knows their site when something does go wrong. That familiarity has a dollar value. A developer who’s never seen your site before is going to spend an hour just understanding the setup before they can diagnose the problem.

Does updating a page builder actually make a meaningful difference?

If it’s done well, yes. Page builder updates have a reputation for being risky, and that reputation isn’t entirely unearned. Some updates over the years have broken layouts, changed how shortcodes render, or introduced conflicts with themes in ways that weren’t obvious until a client reported something looking wrong.

Beaver Builder has generally been more conservative in how it handles updates than some of its competitors, which is a big part of why it’s become the default choice for most of our client builds at Chillybin. We’ve been rolling out Beaver Builder 2.10 across client sites since around October last year. The Components feature is the main reason.

For anyone not familiar: Components in Beaver Builder 2.10 allows you to create reusable elements where certain settings are locked and others can be customised on a per-page basis. In practice, this means we can build a call-to-action block with a fixed layout and brand-consistent styling, then deploy it across fifty pages. If the client’s marketing team needs to update the headline on that CTA globally, they update it once. It cascades everywhere. No more finding fourteen slightly different versions of the same block spread across the site, each one manually edited at some point by someone who’s no longer at the company.

For a site with a content team that logs in regularly, this is a significant change. Build time drops. Consistency improves. And the risk of someone accidentally breaking the layout while editing content is substantially reduced.

The accessibility improvements in 2.10 are worth calling out separately. In the most recent page builder comparison I’ve seen, Beaver Builder’s accessibility score jumped from 48% to 68%. That’s not a marginal improvement. For our education clients and the government-adjacent work we do, accessibility isn’t optional. WCAG compliance matters, and a 20-point jump in a comparative score is the kind of thing that actually moves the needle on whether a site passes an audit.

How do you set up a website so clients can manage it themselves?

You make decisions at the build stage specifically with that outcome in mind. This sounds obvious, but it’s not how most sites get built. The typical approach is to optimise for what looks best in the browser during the demo, and then hand over something the client’s team can’t actually navigate without calling the developer.

I’ve been building WordPress sites since 2003. Back then, the editorial interface was rough, clients needed training for almost everything, and regular support calls were just part of the model. That’s changed substantially. The tools now are good enough that a non-technical content editor should be able to update a page, add a blog post, swap out an image, or change a team member’s bio without any help. If they can’t, something went wrong in the build.

The setup that works: a well-configured page builder with locked templates for anything structural, a clear content hierarchy in the WordPress admin, user roles configured so content editors can do their jobs without accessing anything they shouldn’t, and a short documented guide specific to that site. Not a generic “how to use WordPress” manual. A one-page reference that says “here’s how you update the homepage banner, here’s how you add a team member, here’s where to find the blog.”

I had a client last year, a professional services firm with a small internal marketing team, who’d been with a previous developer for four years and never once logged into their own site. Every change, no matter how small, went through a support ticket. When we rebuilt the site and set it up properly, their team was managing content within a week. They still call us for anything structural or technical, which is appropriate. But the day-to-day content is theirs. That’s how it should work.

The business model that keeps clients dependent on their developer for minor content changes is not serving the client. It’s extracting ongoing revenue in exchange for artificial complexity. I’ve never been interested in building that kind of relationship.

Most of our Chillybin maintenance clients use Beaver Builder because it’s stable, their teams understand it, and the learning curve for a new content editor is measured in hours, not weeks. That hasn’t changed with 2.10. If anything, the Components feature makes it easier, because more of the structural decisions are locked and the editor interface for content is cleaner.

The compounding value nobody talks about

There’s a version of web development where every project starts from scratch, every site is a fresh engagement, and the relationship ends at launch. Some agencies operate exactly like that. It’s not how I’ve ever wanted to work.

The sites that perform best over time are the ones with a consistent relationship behind them. Someone who knows the history, who remembers why that plugin was chosen, who understands the client’s business well enough to make good recommendations before things break rather than after.

Twenty-five years of doing this has taught me that the maintenance conversation is usually where you find out whether a web partner is actually thinking about your business or just your next invoice. The quiet weeks at the end of December, when we’re updating documentation and refining onboarding processes for new maintenance clients, are not the glamorous part of this work. They’re the part that makes everything else hold together.

The sites that are well-maintained are the sites that keep working. That’s not a complicated idea. It just takes discipline to act on it consistently, year after year, regardless of whether anything is visibly broken.