Project work has a rhythm most agency owners know too well. A good quarter of launches, then a thin month while the pipeline refills, then a scramble to say yes to everything at once. The work itself may be excellent. The income is lumpy, and lumpy income makes every other decision harder: hiring, saying no to a bad-fit client, taking a week off.
Recurring revenue is the usual answer, and most agencies have tried a version of it, often a maintenance plan bolted on at launch. Some of those plans quietly work. Many fade: a handful of clients sign up, a few cancel when they cannot see what they are paying for, and the agency goes back to chasing projects. This post looks at recurring revenue as a business design question rather than a sales script: which kinds of ongoing work suit a web agency, what makes them stick, and what has to be true behind the scenes for them to be worth having.
What counts as recurring revenue, and what does not
Recurring revenue is income that arrives on a schedule because of an ongoing agreement, without a fresh sale each time. Three things distinguish it from repeat project work:
- It is agreed in advance. The client has signed up to pay on a schedule, rather than deciding job by job.
- It continues until someone ends it. Renewal is the default.
- It is tied to an ongoing outcome. The site stays secure, current, fast, or improving, rather than a single deliverable being handed over.
A client who comes back for a new landing page every few months is valuable, but that is repeat business, not recurring revenue. The difference matters because only recurring revenue lets you plan capacity with any confidence.
The menu: recurring services a WordPress agency can offer
Maintenance is the obvious starting point, but it is not the only option. Looking at the wider menu helps you choose services that match your strengths and your clients’ real needs.
Care and maintenance
Updates, backups, monitoring, security checks, small fixes. It protects the client’s investment and suits almost every site. It is also the most commoditised offer, so it needs to be clearly better or better explained than a host’s add-on or a cheap plugin subscription. Our separate guide on designing a care plan your clients will buy goes into structuring tiers.
Retained development hours
A fixed block of time each month for changes and improvements. Clients who keep asking for small updates often prefer this to individual quotes. It works best with clear rules on rollover, what counts against the hours, and how larger requests are handled.
Content and publishing support
Loading blog posts, updating product information, refreshing seasonal pages. Many clients have the words but not the time or confidence to publish them properly.
Performance and conversion work
Regular review of speed, forms, checkout and key landing pages, with a small change list each month. This suits clients who already understand that the site earns money.
Hosting management
Running hosting, domains, DNS and email on the client’s behalf. It can be recurring by nature, but brings responsibility for things you do not fully control. Decide carefully whether you want to be the person called when email stops.
Reporting and advice
A regular plain-language report on how the site is doing, with recommendations. On its own it can feel thin; combined with maintenance it often becomes the part clients value most because it makes the rest visible.
Accessibility and compliance monitoring
Periodic checks of new content and templates against accessibility guidelines, for clients who are worried about it. This needs genuine expertise and careful wording; it is general good practice, not a legal shield.
You do not need all of these. Two or three that fit together, offered well, are stronger than a long menu nobody reads.
Why recurring offers fail
When a recurring plan fades, the cause is usually one of a few patterns.
- Invisible work. The client pays every month and sees nothing change. Even when you are doing a lot, an unreported service looks like no service. Regular, readable reporting fixes this.
- Vague scope. “Unlimited small changes” sounds generous until one client treats it as a free development team. Define what is in and out, in writing.
- Delivered when convenient. Recurring work gets pushed behind project deadlines, updates slip, and the one month a backup is missed is the month the site breaks.
- Sold at launch, never discussed again. Clients forget what they bought. A short review once or twice a year keeps the plan connected to their goals.
- Wrong client fit. Some sites genuinely need very little. Selling them a heavy plan invites a cancellation later.
Design the delivery before you sell it
The most overlooked part of recurring revenue is that it creates recurring obligations. Every client who signs up adds to a stream of tasks that must happen on schedule, regardless of how busy your project team is.
Before launching or expanding a recurring service, answer these questions honestly:
- Who on the team does this work each month, and is it protected from project crunches?
- What is the written routine for each site: what is checked, updated and recorded, and when?
- How do you know when a task has been missed?
- Where are credentials, backups and notes for each site kept, so someone else can step in?
- How many more clients could you take on before quality drops, and what would you change then?
If the answers are shaky, fix them before selling more. Recurring revenue built on improvised delivery tends to become recurring stress.
Some agencies decide that the delivery is not where they add value, and hand the routine to an outside team while keeping the plan, the pricing and the client relationship. The broader options for doing that are laid out in our guide to outsourcing WordPress work as an agency.
Making it stick: retention habits
Recurring revenue is only as good as its renewal rate. A few habits help over time.
- Show the work. A short monthly summary in plain language: what was updated, what was checked, anything you caught early.
- Make one useful suggestion each period. A slow page, an outdated form, a plugin to retire. It reminds the client you are paying attention to their business, not just their software.
- Use the plan as the first port of call. When a client has a question, the plan should be the obvious channel, so they feel its value.
- Review annually. Ask what has changed in their business and whether the plan still fits. Upgrade, downgrade or adjust; a client on the right plan stays longer.
- Handle cancellations gracefully. Ask why, hand over cleanly, and leave the door open. Clients often return.
For more on how ongoing work keeps clients engaged after the launch glow fades, see our piece on keeping clients through ongoing maintenance.
Selling it without pressure
The best moment to introduce a recurring plan is during the project, not at the end. When you scope the build, describe what the site will need after launch, and include the ongoing plan as a normal part of the proposal rather than an optional extra. Clients who understand from the start that a website needs care tend to be more open to it.
For existing clients who launched without a plan, a practical approach is a short, factual message about the site’s current state: what has not been updated, any risk you can see, and what you would do about it on an ongoing basis. Our guide to explaining maintenance to clients, with sample emails has wording for both situations.
The mechanics: billing and agreements
- Automate billing. Recurring revenue that depends on someone remembering to send an invoice is not very recurring.
- Agree terms and notice periods. State how either side can end the arrangement and what happens to backups, access and files when they do.
- Separate the plan from project work. Larger requests are quoted separately. Write down where the line sits.
- Keep a record per client. Which plan, which sites, what has been done, what is due. It protects you if a dispute arises and makes handovers easier.
- Review your own pricing regularly. As your costs and the work change, plans priced long ago can drift into unprofitable territory without anyone noticing.
Testing an idea before you commit
Before adding any new ongoing service, run it past a few blunt questions:
- Would a client notice, within a few months, if this service stopped? If not, it will be the first thing cancelled when budgets tighten.
- Can you describe the monthly deliverable in one sentence a client would repeat to their accountant?
- Does it depend on one person in your team who might leave or get pulled onto projects?
- Is there a cheaper substitute the client could buy instead, and can you explain why yours is different without running anyone down?
- Does it lead naturally to project work, or does it compete with it for the same hours?
A service that survives these questions is usually worth a small pilot. One that does not is often better offered as an occasional project.
A simple starting plan
If you are starting from nothing, keep it small:
- Pick one recurring service that fits most of your existing clients, usually care and maintenance.
- Write the routine and the scope before writing the sales page.
- Offer it first to a few clients who already trust you, and ask for honest feedback after the first few months.
- Build the reporting habit from day one.
- Only then add a second service or a higher tier.
Growth in recurring revenue is slow at first and compounds quietly. That is the point: each client who stays adds to a base that makes the next lean month less frightening.
If you would like to offer a care plan under your own brand but would rather not staff the monthly routine yourself, our white-label delivery for agency care plans handles the work while you keep the client and the pricing decisions.
Next in this series: How Outsourcing Changes Agency Margins and Pricing
