Last week I was on a call with a client running a seasonal tourism business. About ten minutes in, we hit a moment I’ve seen many times before.
She wanted a WordPress maintenance retainer. But she’d been burned by one already – locked into flat monthly fees that made zero sense when her site traffic drops 80% over winter and her team is barely checking email.
“We paid the same in February as we did during peak season,” she said. “For what?”
Honestly? Fair question. And one most WordPress agencies would rather dodge.
Here’s the thing most agencies won’t say out loud: flat monthly retainers exist because they’re easy for the agency. Predictable revenue. Clean invoicing. No awkward conversations.
But for a business that makes 70% of its revenue between May and September? That structure is completely backwards. You’re overpaying during your slow months and probably undercovered when things actually break during your busiest weeks.
We’ve been providing WordPress maintenance services for different websites and built over 437 sites since 2008. Somewhere around year five, we stopped pretending that one pricing model fits every kind of business.
When a client pushes back on flat retainers, most agencies respond with one of two options: commit to a monthly retainer you’ll resent for half the year, or go fully ad-hoc and pay emergency rates every time something urgent comes up. Neither is good. The first punishes you for having a slow season. The second punishes you for not having a safety net.
We proposed a third path.
Six-month retainers with quarterly reconciliation.
Here’s what that means in practice: we agree on a block of support hours covering a six-month period. We track time monthly, but we settle up quarterly. If Q1 – your slow season – uses fewer hours, those carry into Q2 when you’re slammed and things actually need attention. If we go over, we flag it before it becomes a surprise on your invoice.
The minimum still matters. We set a floor – a baseline number of hours per quarter – because WordPress maintenance isn’t optional even when business is quiet. Plugin updates, WordPress core updates, security patches, small performance fixes: these need to happen whether you’re in peak season or not. But the floor is reasonable. It’s there to keep your site healthy, not to pad our revenue.
For this particular client, we landed on a structure where winter quarters carry a lower minimum and summer quarters carry a higher one. The total annual cost is roughly the same as a flat retainer would be – but the cash flow finally matches how her business actually operates.
The other piece we sorted out on that call: how changes actually get made to the site.
“How do we handle deployments?” sounds like a boring operational question. It isn’t. It’s where WordPress support relationships break down at 11pm the night before a client’s busiest weekend.
Our standard process: test locally, push to staging, validate, then deploy to production. We require staging environment access before agreeing to any maintenance arrangement. Not as a box-ticking exercise – because trying to patch something directly in production on a live WooCommerce store during peak season is how you cause a three-hour outage. If there’s no staging environment in place, we scope creating one into the initial setup. It’s not optional. You can read more about how we handle WordPress site performance and server setup for clients across different hosting configurations.
We also talked about something clients rarely bring up but nearly always want: a focused review of the site before the engagement starts.
Not a full code audit. Those are expensive, slow, and usually produce a 40-page document that never gets acted on. A focused WordPress site health review means: are there critical security vulnerabilities? Plugin conflicts that could break things? Performance issues that are actively costing conversions right now? That’s the scope. An hour or two of targeted investigation, documented findings, and a prioritised action list. According to WPScan’s WordPress Vulnerability Database, outdated plugins are responsible for the majority of WordPress site compromises – which is exactly the kind of thing a quick initial review catches before it becomes a problem. You go into the engagement knowing what you’re actually working with.
For anyone mapping out what a solid website maintenance retainer should cover, here’s what we consider the baseline: regular WordPress core, theme, and plugin updates; security monitoring and malware scanning; uptime monitoring with alert response; monthly performance checks; a staging environment for all non-trivial changes; transparent hours tracking so there are no surprise invoices; and a named point of contact who already knows your site. The WordPress security and maintenance best practices documented by Sucuri align closely with how we’ve approached this over the years – particularly around update cadence and access control.
Most website maintenance relationships don’t fail because the work is bad. They fail because the contract never matched how the business actually operates. Misaligned payment structure. No staging environment. Vague scope with no tracking. A support agreement written for a generic client, not for a seasonal tourism business with specific peak periods and a team that goes quiet in winter.
If your current maintenance retainer doesn’t fit how you actually work, it won’t survive the first stressful month. The frustration builds quietly until something breaks and suddenly everyone’s unhappy.
We’ve helped businesses move from reactive, ad-hoc WordPress support to structured retainers that actually make sense for their model. You can see more about how we approach ongoing website care and long-term client relationships at Green Wire Media. The Clutch report on web maintenance agency relationships notes that clear scope definition and transparent billing are the two biggest factors clients cite when ending a maintenance contract early – which tracks with what we see firsthand.
The right retainer is the one you don’t have to fight.
A good WordPress maintenance retainer should feel invisible most of the time. Updates happen. Security stays clean. Performance stays solid. And when something does break, there’s a clear process and a team who already knows your site.
If you have a good base for the WordPress website – maintenance work will be small and issues less likely to happen. We have seen some of the projects that we have built 3-4 years ago that never signed up for active maintenance still working fine. And when we push the update – nothing goes bad. It’s still suggested in most cases to update your website more often, but it really depends on how your site was built.
If yours doesn’t feel that way, it’s worth having an honest conversation about why. We’ve had this one before. Get in touch.
