“I don’t really know what I’m paying you for.”
That email hit my inbox five months into what I thought was a solid retainer relationship. Monthly updates. Regular backups. Uptime monitoring. The whole maintenance package.
The client wasn’t wrong.
I’d been running updates, making backups, and monitoring uptime, and none of it had any visible impact on her business. Because honestly? It didn’t. Not in any way she could see. I was selling maintenance tasks. She wanted business results. That gap almost cost me the client.
Fixing it changed how I structure every retainer since.
Why Most WordPress Maintenance Retainers Get Cancelled
The core problem is what you’re selling, not how well you’re selling it.
“We’ll keep your site updated and backed up” sounds valuable to a developer. To a business owner, it sounds like housekeeping. Housekeeping is easy to cut when budgets tighten. Nobody cancels their bookkeeper. Nobody cancels their accountant. But they cancel the person who’s running updates in the background because they can’t feel the difference.
I looked at my first two years of retainer data. My average client tenure was 4.2 months. Four of my six churn reasons were variations of the same thing: “we’re not sure we’re getting value” or “we decided to handle this in-house.” One client specifically said, “It just feels like we’re paying for insurance we never use.”
That phrase stuck with me. Insurance you never use. That’s exactly what a maintenance retainer feels like when it’s positioned around tasks instead of outcomes.
The fix isn’t doing more tasks. It’s changing what you’re actually selling.
The Four Retainer Models Worth Offering
Not every client needs the same thing. Having four distinct options lets you position the right model for the right client instead of forcing everyone into a maintenance plan.
Model 1: Maintenance + Reporting ($150-$300/month)
This is the entry-level retainer, but it’s structured around communication, not just tasks. Updates, backups, security scans, and uptime monitoring, plus a monthly one-page report that translates what all of that means for the business. “Your site had zero downtime this month. Average page load was 1.8 seconds, which puts you in the top 25% of sites in your category. We pushed 12 plugin updates including a critical security patch for WooCommerce.”
The reporting is what clients are actually paying for. It makes the invisible visible.
Model 2: Growth Retainer ($500-$1,500/month)
This is where the real value is. Monthly improvements to the site based on agreed performance goals. Conversion rate work. Page speed optimization. Content formatting. A/B tests on key pages. Every month, something gets measurably better.
This model works best for established businesses with some traffic and clear goals. A site getting 500 visitors a month with a 1% conversion rate has obvious room to grow. Show them the math. Doubling their conversion rate to 2% doubles their leads. That’s worth $500 a month. Easily.
Model 3: On-Call Priority Support ($800-$2,000/month)
For clients who have internal marketing or content teams but need a developer on standby. They get a guaranteed response time (I offer 4-hour response, same-day fix for critical issues) and a monthly bucket of hours for small changes. No surprises, no “let me check my schedule,” just fast access when they need it.
This model attracts clients who’ve been burned by slow-response developers. They pay the premium for certainty.
Model 4: Fractional CTO / Strategic Advisory ($2,000-$5,000/month)
This one is for growing businesses that need technical direction but aren’t ready to hire a full-time CTO. Monthly strategy sessions, vendor evaluation, technical roadmap planning, architecture decisions. Almost no hands-on development, mostly thinking and directing.
I fell into this model accidentally. A client asked me to review a proposal from a hosting company that wanted to charge them $800/month for “managed WordPress.” I spent 40 minutes telling them it was overpriced for their needs. They asked if I’d just handle all of their technical vendor decisions going forward. We set up a $2,500/month advisory relationship that lasted three years.
Pricing Retainers: Monthly vs Quarterly vs Annual
Monthly billing is the easiest for clients to say yes to. It’s also the easiest to cancel.
When a client is paying month-to-month, every invoice is a renewal decision. Busy month? Cancel. Tight quarter? Pause. The friction to cancel is exactly zero.
Quarterly billing changes the dynamic without making it feel like a long-term commitment. The client is committing to 90 days, which is long enough for work to produce visible results. I found that switching from monthly to quarterly billing increased my average client lifetime value by about 40%. Not because clients were trapped. Because by the time they were into month three of a quarterly commitment, they’d usually seen enough to want to continue.
For maintenance-only plans (Model 1), annual billing with a 15% discount makes sense. Updates and backups are consistent, predictable work. An annual commitment at a lower rate is good for both sides.
My standard approach: I bill Model 1 clients annually, Models 2 and 3 quarterly, and Model 4 monthly (because those relationships evolve more dynamically and the invoices are large enough that monthly makes sense for cash flow on both sides).
Always require a minimum three-month commitment regardless of billing cycle. One-month trials give clients an easy exit before they’ve seen results. Three months is enough time for growth work to show meaningful movement.
The Onboarding Process That Prevents “What Am I Paying For?”
The “I don’t know what I’m paying for” problem almost always starts at onboarding, not three months in.
If you haven’t set clear expectations upfront, you can’t manage them. So I now send a welcome document to every new retainer client before we start. Two pages. It covers:
- Exactly what’s included in their plan and what’s not
- Expected response times for different types of requests (updates: 48 hours, critical security issues: 4 hours, new feature requests: outside scope, here’s how we handle that)
- How I’ll report on the work each month and what format that takes
- How to submit requests (one email thread, not fifteen Slack messages)
- What happens if they need something outside the agreed scope
That last point is important. “Outside scope” conversations are where retainer relationships go wrong. If you don’t define the edges, every request feels like it should be included. Define the edges clearly in the welcome document, before the first request comes in.
I also schedule a 30-minute check-in call for the end of each client’s first month. Not to report on what I’ve done. To ask them how the relationship is feeling and whether my reporting is telling them what they need to know. Most of the time, everything’s fine. Occasionally, I learn something that lets me adjust before it becomes a cancellation reason.
Monthly Reports That Make Clients Feel Smart for Hiring You
The report is the retainer. Everything else is just the work that makes the report possible.
Bad report: “This month we performed 14 plugin updates, 4 theme updates, 8 security scans, and 2 database optimizations.”
Good report: “Your site’s average page load time dropped from 3.1 seconds to 1.9 seconds this month after we optimized your image delivery and updated your caching configuration. Based on industry benchmarks, this improvement typically correlates with a 10-15% reduction in bounce rate. We’ll track your actual bounce rate over the next 30 days to confirm. We also applied a critical WooCommerce security patch that addressed a known payment data vulnerability, rated CVSS 8.8.”
The same work. Completely different framing. The second version tells the client three things: what changed, why it matters, and what you’re watching to measure the impact.
I use a simple template I’ve adapted over time. It covers: site performance (load time, uptime), security (scans run, patches applied, threats blocked), updates applied (with a brief note on any significant ones), work completed that month, and one metric that’s moving in the right direction. One page, usually. Two if it was a busy month.
For Model 2 growth retainers, the report includes conversion data, A/B test results, and a forward-looking section on what we’re optimizing next month. It’s longer, but clients who are paying $1,000+/month for growth work want more detail.
For client support ticketing across multiple retainer clients, Freshdesk keeps all the communication organized without letting things slip through email. And Monday is how I track the work itself, with each retainer client getting their own project board.
Scaling Retainers Without Burning Out
After about eight or nine retainer clients, you hit a capacity ceiling. The work is manageable, but the overhead of managing eight client relationships, eight reporting cycles, and eight sets of requests adds up.
I manage twelve retainer clients now with a part-time VA and a handful of automation tools. Here’s what I delegated and what I kept:
The VA handles: scheduling check-in calls, sending monthly report reminders to me (so I don’t miss them), and fielding the initial “hey, I have a request” messages so I can batch my responses.
Automation handles: uptime monitoring alerts, automated backup confirmations, plugin update reports (I review them, automation compiles them).
I kept: all technical decisions, all reporting analysis, all client strategy conversations, and anything that requires judgment.
Batching is the other thing that makes this work. I do all plugin updates across all clients on Monday mornings. All monthly reports go out in the first week of the new month. All check-in calls happen on Thursdays. Instead of maintenance work being scattered across the week, it’s concentrated and predictable.
For the white-label commodity work like basic uptime monitoring and automated backups, there are services that handle this at scale. Worth considering if you’re managing more clients than you can comfortably touch every month.
Productivity tools for freelancers covers the automation stack in more detail. And must-have tools for freelancers has the client management and communication tools that make juggling multiple retainers possible without dropping anything.
You probably have at least one client right now who’s paying for maintenance and quietly wondering if it’s worth it. Send them a message this week. Ask what business goal they’re trying to hit in the next quarter. Then show them how your retainer can connect to that goal. You might lose the conversation. But you won’t lose it quietly over email three months from now when they cancel without warning.
Frequently Asked Questions
How many retainer clients can a solo developer handle?
8-10 is comfortable for most solo operators with a mix of maintenance and growth retainers. Above 10, you need a VA for admin overhead or a second developer for technical overflow. The limit isn’t the hours. It’s the mental load of tracking different client contexts, reporting cycles, and expectations.
Should I offer a discount for annual retainer commitments?
Yes. 10-15% for annual vs monthly is the right range. More than 15% and you’re giving away too much. Frame it as value: “An annual commitment gets you two months free and locks in the current rate for a full year.” That framing is more appealing than “I’ll charge you 12% less.”
What do I do when a retainer client’s requests exceed scope?
Address it immediately, not at the end of the month. “This is outside our current retainer scope. I can complete it as a small project for $X, or we can discuss upgrading your plan.” Don’t absorb out-of-scope work and resent the client. The welcome document defined the edges. Hold them.
How do I transition project clients into retainer clients?
Raise it at handoff, not during the project. Send a post-launch document that includes ongoing support options with two or three retainer tiers. Some clients sign immediately. Others wait until something breaks. Both are fine. The ones who sign immediately tend to be your best long-term relationships.
Is it better to offer fixed-scope retainers or hourly buckets?
Fixed-scope, always. Hourly buckets recreate the problems of hourly billing: clients count hours, hesitate to ask for small things, and every month ends with uncomfortable accounting. Fixed scope defined by outcomes removes the clock-watching and focuses both sides on results.
What’s the most common reason retainers get cancelled?
“I don’t know what I’m paying for.” This is always an onboarding and reporting problem, not a service quality problem. Fix it with a welcome document that sets clear expectations and monthly reports that frame work in terms of business impact, not tasks completed.
