Your $99/Month Website Maintenance Plan Might Not Be Maintaining Anything

Website maintenance packages in New Zealand tend to sit somewhere between $99 and $249 a month. Read the plan descriptions side by side, and they’re nearly interchangeable: plugin updates, security monitoring, backups, optimisation, priority support. The same words at $99 as at $249. The same words from a provider doing the job properly as from one clicking Update All and hoping.

That’s the uncomfortable part. The quality gap between maintenance providers is real, and it is large – but it’s invisible from where you’re standing. You can’t see it in the plan description, the invoice, or a monthly email with green ticks on it. Most small business owners find out which kind of plan they bought at the exact moment maintenance was supposed to protect them: when something breaks.

There is one question that cuts through all of it. We’ll get there. It makes more sense once you know what “we update your plugins” actually involves – because that sentence describes two very different jobs.

“We update your plugins” describes two different jobs

A WordPress website is a stack of software from different makers: the WordPress core, a theme, and typically ten to thirty plugins, each releasing updates on its own schedule. A normal business site sees several plugin and theme updates a week, some of them security updates. Applying them isn’t optional: security firm Patchstack logged nearly 8,000 new WordPress vulnerabilities in 2024 – 96% of them in plugins, only seven in the WordPress core itself. Unpatched plugins are how sites get compromised, which is why most of what WordPress maintenance actually involves, in NZ as anywhere, is applying those updates without breaking anything. So far, every provider agrees.

The difference is where the update happens first.

The quick version

Update the live site. Log in to your actual website – the one your customers are on – click Update All, wait for the spinners, then load the homepage. If the homepage comes up, job done, next site. The whole thing takes a few minutes, which is precisely what makes a $99 plan profitable when you’re running it across a whole book of client sites.

The proper version

Update a staging site first. A staging site is a private, working copy of your website that visitors never see. Updates are applied there first, then the parts of the site that earn you money get checked – forms, enquiry paths, checkout if you sell online. Only after nothing is broken does the update go to your live site. If an update breaks the copy, it has broken a copy. Your real site never felt it, and the provider fixes the problem on their time instead of yours.

That’s the entire concept. Staging isn’t exotic infrastructure – it’s just testing the change before the change goes live. A mechanic test-drives your car before handing back the keys. Same idea.

In practice, careful providers run this on a sliding scale. A minor update to a well-behaved plugin might go straight to live, with a fresh backup taken and a tested way to roll back. Anything that could touch forms, checkout or integrations goes through staging first. The distinction that matters isn’t staging for its own sake – it’s whether someone decided, deliberately, how much testing each update needed, or whether everything goes straight to live because that’s cheaper.

The reason this matters more than anything else in the plan description: when a regular update goes wrong, it usually doesn’t go wrong loudly.

When updates break things, they break them quietly

People picture a broken website as a white screen with an error on it. Those are the good failures. They’re visible, someone reports them within the hour, they get fixed.

The expensive failures are the quiet ones.

A common failure pattern looks like this. An online store, busiest days Saturday and Sunday. A routine WooCommerce update changes how the checkout handles customer sessions. Nothing visibly breaks: there is no downtime, the homepage loads, product pages load, the cart works. But at the payment step, the checkout quietly fails. No error page for the customer, no PHP error in the logs, nothing for monitoring to flag – the site is “up” the whole time.

Every order across the weekend is lost, along with every customer who tried to pay, couldn’t, and bought from someone else. The business finds out on Monday morning, when someone finally rings.

A homepage check catches none of that. Uptime monitoring catches none of that – the site never went down. The only thing that catches it is a person testing the purchase flow after the update, on a copy of the site, before the update reaches production. That’s the gap between the two versions of the job, measured in a weekend of revenue.

The one question to ask your provider

“Do you test updates on a staging environment before they go to my live site?”

Send it as a one-line email. The answer tells you almost everything about what you’re paying for.

A good answer describes a process, unprompted: which updates go through staging by default – anything that could affect how the site works, and everything on an e-commerce site – which low-risk changes might be applied directly with a backup and restore behind them, what gets checked afterwards (forms, key pages, checkout for a store), and what happens when a test fails. It doesn’t have to be “every update, always” – what you’re listening for is whether anyone is making that call deliberately. Providers who work this way tend to be pleased someone finally asked.

The revealing answers are the ones that route around the question:

• “We’re careful with updates.” Careful is a temperament, not a process. It usually means: we click Update All one plugin at a time and watch the homepage.
• “We monitor the site after updating.” Read that back slowly. It means your live site is the test environment, and your customers are the QA team.
• “We’ve never had any issues.” It means no issues they noticed. The Saturday checkout failure above was invisible to a provider who wasn’t looking.
• “Staging is available on our premium plan.” This one deserves its own section.

Staging is not a premium feature

It’s worth knowing what staging actually costs a provider, because it gets positioned as an upgrade often enough that you could believe it’s expensive.

It isn’t. Most decent hosting platforms include staging environments as a standard feature – a built-in button. Where they don’t, a working copy of a site takes an hour or so to set up, once. The ongoing cost is close to zero.

What staging actually costs a provider is time: fifteen or twenty minutes of genuine checking per site, per update cycle, instead of two. Multiply that across every site on a provider’s books, and you can see exactly where the corner gets cut. Skipping the testing isn’t a smaller service – it’s the margin.

So when staging appears as a premium add-on, it’s worth translating: the base plan is we don’t test changes before making them to your live site. In most trades, that would be a strange thing to put on a price list.

What to compare in NZ website maintenance packages

If you’re comparing maintenance packages in NZ right now, this reframes the shopping list. The line items barely differ – website backups, monitoring, security patches, updates and support hours appear in every monthly maintenance plan at every price. What separates packages is the process behind the line items: whether updates happen on a regular cycle – weekly to monthly is normal – or just “as needed”, whether the provider is proactive about testing them in proportion to the risk they carry, whether anyone keeps a record of what changed and when, whether the things that earn you money get checked after every change, and what the plan is when something slips through anyway.

For website maintenance in New Zealand, that holds regardless of who’s providing it – solo specialist, small studio or agency. The process matters more than the package.

Audit the plan you’re already paying for

None of this means your provider is doing it badly – and it doesn’t mean website maintenance costs in NZ map neatly onto quality. The market has both kinds at every price: some $99 plans are run properly by small operators with good habits, and some $249 packages are automated update services with a logo on the invoice. The price doesn’t tell you. The process does – so ask about the process.

Three questions, one email

1. “Do you test updates on a staging environment before they go to my live site?” – the load-bearing question, per above.
2. “What was updated on my site last month?” – a real answer is a specific list: which plugins, from which version to which, tested where. If the answer is vague, the honest reading is that nobody kept track.
3. “What happens if an update breaks something?” – the good answer is that anything risky gets caught on staging before your live site sees it, and there’s a tested way to roll back anything that slips through. “We fix it quickly” means the plan is reactive: your customers find the problem first.

If the answers come back specific and unbothered – keep your provider, genuinely. You have one of the good ones, and this article was worth it for the peace of mind. If the answers are vague, defensive, or arrive as a phone call instead of anything in writing, then what you’ve been buying is a subscription to hope, and it’s fair to start comparing.

The same standard applies if you handle updates yourself instead of paying anyone: the question is simply whether changes get tested before your customers meet them.

Where we stand on this

For transparency, since we sell website maintenance services ourselves: every update we apply starts with a fresh backup, so there’s always a clean way back. Anything that could affect how a site works – riskier updates, and any site where a broken form or checkout costs real money – goes through a staging copy before it touches the live site, and updates are followed by checks on the things most likely to break quietly: forms, integrations, checkout. Our plans differ in how much hands-on time they include each month – not in how carefully the work is done. Testing before going live isn’t something we sell as an upgrade.

If you’d rather sanity-check your current arrangement than switch, the three questions above work on anyone – including us.