Most web agencies leave significant recurring revenue on the table the moment a site goes live. They hand over the login credentials, send a final invoice, and move on — then spend the next six months chasing the next project while that same client’s WordPress installation accumulates outdated plugins, a lapsed SSL certificate, and an uptime incident no one notices for three days.
WordPress maintenance packages — sometimes called care plans or retainers — change that dynamic completely. Done well, they create a predictable monthly revenue stream, deepen client relationships, and give you a legitimate reason to stay in your clients’ inboxes every month. The challenge is that most agencies either underprice them (and create servicing headaches) or over-engineer them (and create selling headaches). This guide is about getting both right.
Why WordPress Maintenance Packages Are One of the Best Agency Products
Of all the recurring revenue products a web agency can sell, maintenance packages have an unusually good profile. The work is systematisable — once you have the right tools and processes, servicing 30 maintenance clients doesn’t take 30 times the effort of servicing one. Much of it can be automated. The value to the client is real and tangible. And churn is naturally low because the cost of leaving (migrating hosting, finding a new agency to hand things over to, re-establishing trust) is high relative to the monthly fee.
Consider the maths. If you charge £99/month per site and sign up 40 clients, that’s £3,960/month — nearly £48,000/year — largely from work your tooling is doing automatically. Your actual human time per client per month, once the system is running, might be 30–60 minutes on average. At that volume, you’re looking at margins well above 70%. Those economics don’t exist in project work.
The demand side also works in your favour. WordPress powers roughly 43% of all websites globally, and the vast majority of small and mid-sized businesses running WordPress have neither the skills nor the time to maintain it themselves. They know the risk is there — they’ve heard the horror stories about hacked sites and broken updates — but they lack the capacity to address it. You’re not selling a nice-to-have. You’re selling peace of mind to someone who genuinely needs it.
The average UK web agency’s opportunity
A 10-person agency that has built 150 WordPress sites over five years and is actively maintaining only 20 of them on paid plans is leaving roughly £13,000/month in potential recurring revenue untouched. Even converting 40% of that backlog at a modest £99/month would add £5,940 to monthly revenue — without winning a single new client.
What to Include in Each Tier: Building the Package Stack
The most common mistake is building a single maintenance offering. One package forces you to either price too high (losing budget-conscious clients) or too low (losing margin on high-complexity sites). Three tiers — sometimes four — let you capture the full spectrum of client budgets and site complexity while protecting your margins at each level.
Here’s a framework that works well for UK agencies in 2024:
Essential (£49–£79/month)
This is your entry-level offer — positioned as the minimum any responsible site owner should have. It’s designed to be highly automated and low-touch. What to include: weekly WordPress core, theme, and plugin updates; daily off-site backups with 30-day retention; uptime monitoring (5-minute check intervals, email and SMS alerts); SSL certificate monitoring and renewal; a monthly summary report. What not to include: hands-on development work, content updates, or priority support response times.
This tier should be almost entirely automated. The right tooling handles updates, backups, and monitoring without human intervention. Your main human touchpoints are the monthly report (which a template makes quick) and responding to any alerts that fire. Budget 20–30 minutes per client per month at this tier.
Professional (£99–£149/month)
This is your mainstream offer — where most clients should land. It adds meaningful human oversight on top of the automation. Include everything in Essential, plus: daily WordPress core, theme, and plugin updates with pre-update staging tests; uptime and performance monitoring (response time tracking, Core Web Vitals baseline); a dedicated support ticket allowance (typically 1–2 hours per month for minor content updates and bug fixes); monthly WordPress security scan; a more detailed monthly report with performance metrics and any issues resolved. Response time SLA of 1 business day.
At this tier you’re spending 45–75 minutes per client per month in a well-run operation. The staging-before-update step adds time but dramatically reduces the risk of a plugin update breaking the site — which matters both for client trust and for your own remediation time if something goes wrong.
Premium (£199–£299/month)
This is your high-touch offering for business-critical sites — e-commerce stores, high-traffic publishers, or clients in regulated industries. Everything in Professional, plus: dedicated account management; 4-hour emergency response SLA for downtime or security incidents; monthly performance optimisation (caching audit, image optimisation, database cleanup); WooCommerce or membership plugin specialist attention where applicable; proactive security hardening and quarterly security audit; access to your team for small ad-hoc development tasks (2–4 hours/month).
At Premium, you’re looking at 2–4 hours per client per month, including the relationship management overhead. Price accordingly — and be selective about which clients go on this tier. Not every client needs Premium; overselling it creates servicing pressure and resentment when the 4-hour development allowance gets consumed in week one.
Optional: Agency tier for other agencies
Some agencies white-label their maintenance operation and sell to other small agencies or freelancers who don’t want to run the infrastructure themselves. If you have the volume, this can be a high-margin wholesale product — typically priced at 40–50% of your retail rate, with minimum commitments of 10–20 sites. This is worth considering once you have the process properly systematised.
Pricing Your Packages: The Maths You Need to Do Before Publishing a Number
There are two failure modes in maintenance pricing. Pricing too low means you’re effectively subsidising clients’ infrastructure at your own expense — and because the pain is distributed across many clients in small amounts, it’s hard to see until you do a proper time audit and realise you’re earning £12/hour on your “£99/month” accounts. Pricing too high means you lose the deal or the client doesn’t renew after the first year because they’ve convinced themselves they can muddle through without you.
The right approach is to work backwards from your actual costs, not forwards from what “sounds reasonable”.
Step 1: Calculate your true cost per client per month. This means tooling costs (your monitoring platform, backup service, staging environment, security scanner — divide the monthly cost by the number of sites you’re managing or planning to manage), plus your team’s fully loaded hourly rate multiplied by the average time you’ll spend per client at each tier. For a UK agency with a £50/hour fully loaded rate (salary + NI + overhead):
These numbers will vary based on your tooling choices and actual hourly costs, but the principle holds: price to at least 55–60% gross margin once you account for all costs. Anything below 50% gross margin on a maintenance product is a warning sign that you’re either underpriced or your processes aren’t efficient enough yet.
Step 2: Account for incident time. Maintenance work isn’t entirely predictable. Occasionally a plugin update will break something, a site will get hacked, or a hosting issue will require investigation. Budget roughly 15–20% of your estimated monthly time as an incident buffer when calculating your pricing. Agencies that don’t do this consistently find their “profitable” maintenance portfolio turns loss-making every time there’s a WordPress major version release.
Step 3: Consider annual vs monthly billing. Offering a 10% discount for annual upfront payment benefits both parties — the client saves money and you get 12 months of revenue secured. Many agencies find that 30–40% of their maintenance clients will take the annual option if offered, which materially improves cash flow and reduces the admin of monthly invoicing. Build this into your pricing conversation from day one, not as an afterthought.
Selling Maintenance to Existing Clients: The Conversation That Works
Your best prospects for maintenance packages are the clients you built sites for over the last three years who are not currently on a plan. They already trust you, you know their sites, and you have a legitimate reason to reach out. The challenge is having the conversation in a way that doesn’t feel like you’re pitching them something they don’t need.
The most effective approach is the audit-led conversation. Run a quick audit of their existing site — plugin versions, uptime history, SSL status, security headers — and use the findings as the opener. Something like: “We ran a health check on your site this week and noticed a few things worth discussing.” You’re not selling; you’re reporting on what you found. The problems do the selling for you.
What you’ll typically find when auditing a live site that isn’t on a maintenance plan: 8–15 outdated plugins (at least two of which have known vulnerabilities), a PHP version that’s end-of-life, no off-site backups, an SSL certificate that’s auto-renewing but has never been verified, and uptime monitoring that doesn’t exist. These aren’t hypothetical risks — the first thing a client says when you show them this list is usually some version of “why didn’t anyone tell me about this sooner?”
Frame the conversation around what they’re currently exposed to, not what you’re offering. “If this plugin vulnerability were exploited, you’re looking at a minimum of £800–£1,500 in recovery work, plus however long the site is down during cleanup. Our £99/month plan means that risk is managed every week, and if something does go wrong, we’re on it within a business day.” The maths land themselves.
One tactic that consistently converts: offer a complimentary 30-day trial of your Essential package to any client who hasn’t heard from you in 90+ days. The rationale is simple — once they’re receiving your monthly report, seeing the plugin updates you’ve applied, and getting uptime alerts resolved before they noticed anything was wrong, the £79/month feels like very good value. Churn from trial-to-paid conversion at this point is typically very low (under 15%).
Tooling and Automation: What You Actually Need to Run This at Scale
A maintenance operation that relies on someone manually logging into each client’s WordPress admin every week will never scale profitably. The economics only work when you have the right tooling automating the repetitive work and centralising the monitoring signals.
You need four categories of tooling:
WordPress management platform. Tools like ManageWP, MainWP, or WP Umbrella let you manage dozens of WordPress installations from a single dashboard — applying updates in bulk, running security scans, generating reports, and managing backups. At scale, the cost is typically £0.50–£1.50 per site per month, which is negligible relative to what you’re charging. The time savings are transformative: what would take 10–15 minutes per site manually takes 30 seconds per site with bulk updates.
Uptime and performance monitoring. You need something checking each client’s site every few minutes and alerting you immediately if it goes down or responds slowly. At the Professional and Premium tiers, you want performance trend data too — not just “is the site up” but “is it slower than it was last month.” Marque CRM’s built-in site monitoring module covers uptime, SSL certificate expiry, and WordPress plugin version tracking across your entire client portfolio from within your agency management dashboard — without bolting on a separate tool.
Off-site backup solution. Hosting provider backups are not sufficient. If the hosting account is compromised, the backups stored on the same account are compromised too. You need backups going to a separate location — typically S3 or Google Cloud Storage via your WordPress management platform. For most clients, daily backups with 30-day retention is the right configuration. For e-commerce clients processing transactions, twice-daily is more appropriate.
Reporting templates. Monthly reports are one of the highest-value touches in a maintenance relationship — they make invisible work visible. A good report includes: uptime percentage for the month, number of updates applied (with plugin names), any security scan findings, backup status, and a short “next month” section. Build a template once; the generation time drops to 5–10 minutes per client. Clients who receive consistent reports churn at noticeably lower rates than those who don’t — because the report is a monthly reminder of the value you’re delivering.
One thing to be careful about: resist the temptation to build this stack from five separate tools. Each additional tool adds login overhead, billing complexity, and surface area for things to go wrong. Where possible, consolidate — a WordPress management platform that handles updates, backups, and basic monitoring, combined with an agency management platform that handles the client-facing work (reports, tickets, invoicing), keeps the operational complexity manageable.
Handling Support Requests and SLAs Without Destroying Your Margin
The area where WordPress maintenance packages most commonly go wrong is support scope. A client on a £99/month plan who treats that as “unlimited access to your team for anything WordPress-related” will consume your margin within the first week of each month. You need clear, written boundaries — and a support system robust enough to enforce them graciously.
The most important thing to define upfront is what “support” means in the context of your maintenance package. Maintenance support covers: broken functionality caused by an update you applied, security incidents, and the specific ad-hoc allowance (if any) in the client’s tier. It does not cover: new feature development, design changes, content population, third-party integrations, or anything that requires more than the monthly allowance without a separate agreement.
A formal ticketing system — even a simple one — changes the dynamic entirely. When a client has to submit a request through a support portal rather than emailing a named person directly, they automatically frame the request more carefully. They ask themselves whether it’s a maintenance issue or a development request. Response SLAs become visible and accountable — the client can see when they submitted the ticket and how long it took to respond. This is professionally healthier for everyone.
For clients on your Professional and Premium tiers, a white-label client portal where they can raise tickets, see the status of their support requests, and access their monthly reports creates a genuinely premium experience. It positions you as a professional operation rather than a freelancer with a website. Marque CRM’s client portal and support ticketing module handles this — clients get their own branded portal, you get a structured inbox with SLA tracking, and the whole thing sits inside your CRM so the conversation history lives alongside the client record.
On the SLA side: only commit to response times you can genuinely guarantee. A 4-hour response SLA on a 2-person agency is unsustainable unless you have out-of-hours cover. Better to offer 1 business day and reliably deliver in 2–4 hours than promise 4 hours and miss it regularly. Missed SLAs erode trust; exceeded SLAs build it.
Monitoring Dozens of Sites Without Losing the Signal in the Noise
When you’re maintaining 5 sites, an email alert for every uptime event is fine. When you’re maintaining 50 sites, your inbox becomes unusable and alert fatigue kicks in — which means the one real emergency gets lost in a sea of false positives from sites that were momentarily unreachable and then recovered automatically.
Mature maintenance operations typically follow a few principles to keep monitoring signal clean. First, tune your uptime alert thresholds. A site that’s unreachable for 30 seconds before recovering doesn’t warrant an immediate alarm — configure your monitoring to alert only after 3–5 consecutive failed checks (typically 3–5 minutes of genuine downtime). This reduces noise by 60–70% for most agencies while still catching real incidents quickly.
Second, categorise your sites by priority. A WooCommerce store doing £50,000/month in transactions warrants a different alert profile than a local estate agent’s five-page brochure site. For high-priority sites, alert immediately by SMS. For standard sites, batch low-urgency alerts into a daily digest. The client’s agreed SLA (which should vary by tier) should directly inform which alert profile their site gets.
Third, keep a centralised view rather than checking individual dashboards. When a client calls to say their site is down, you should be able to pull up their monitoring history in seconds — not log into three different platforms. This is where an integrated agency management tool pays dividends: Marque CRM’s site monitoring dashboard shows uptime status, SSL certificate health, and WordPress plugin versions for every client site in one view, flagging issues that need attention rather than making you check each one manually.
Finally, use monitoring data proactively rather than reactively. If you can show a client a graph of their site’s response times trending upward over three months, that’s a compelling argument for a hosting upgrade or a performance optimisation engagement — both of which are additional revenue opportunities that monitoring data surfaces naturally.
Getting Your First 10 Maintenance Clients: A Realistic 90-Day Plan
The theory is one thing; the first 90 days are where most agencies stall. Here’s a practical sequence that works.
Month 1: Build the infrastructure. Set up your WordPress management platform and connect every client site you currently have. Configure backup schedules and monitoring. Create your three-tier package documentation and pricing page. Draft your report template. Build a simple maintenance service agreement (have a solicitor review it — £200 spent once is worth it). Create the support channels clients will use.
Month 2: Convert existing clients. Run site audits on your 10–15 best client relationships and email them with findings. Prioritise clients whose sites you built (you know the codebase), who have come back to you before (evidence of trust and ongoing need), and who are in commercial sectors where downtime has a real cost. Aim for 6–8 conversations. A 50–60% close rate at this stage is realistic.
Month 3: Systemise and start prospecting. With 3–5 maintenance clients live, you’ll learn what takes longer than expected and what takes less. Adjust your pricing and processes based on real data. Then begin proactive outreach to clients from 2–3 years ago who aren’t currently active — and start including maintenance in every new project proposal as a natural next step.
Most agencies that commit to this sequence reach 15–20 maintenance clients within six months and £1,500–£3,000/month in maintenance MRR. It’s not dramatic growth, but it’s extremely reliable — and it compounds. By month 18, agencies that started this process consistently tend to have maintenance MRR covering a meaningful portion of their fixed costs, which changes every other commercial decision they make.
For more on building the recurring revenue foundation this sits within, see The Agency Owner’s Complete Guide to Monthly Recurring Revenue, or explore how retainer vs project pricing affects your agency’s long-term stability. The Marque CRM features page covers the site monitoring, client portal, and ticketing modules in detail.