White label WordPress maintenance for agencies: how it works

Why agencies outsource maintenance

Most agencies are built to deliver projects: strategy, design, campaigns, a launch. Maintenance is a different kind of work. It is small, recurring and interrupt-driven, and it rarely fits neatly into a project schedule.

The result is familiar. A client asks for a plugin update or reports a broken form, and a designer or a project developer has to stop what they are doing. Updates get postponed because nobody owns them. After a year, the agency has a portfolio of websites at different levels of neglect, and every small request feels risky.

• No one on the team specialises in WordPress upkeep. Your people design and build well, but nobody wants to be the person who patches plugins on Friday afternoon.
• Care requests pull the team off paid projects. Each interruption is small, but together they eat into project margins.
• Clients expect ongoing care. Many clients assume the agency that built the site will keep it safe. Offering a care plan is easier than explaining why you don't.
• Hiring for it is hard to justify. One maintenance hire needs enough recurring work, holiday cover and tooling. Outsourcing lets you start with a few sites and grow.

A quick test of whether you need it: count how many hours your team spent last month on updates, small fixes and “the site looks odd” emails, and who did that work. If the answer is “several hours, spread across whoever was free”, a dedicated partner will usually be cheaper than the interruptions.

Outsourcing does not mean giving up control. Done properly, white label maintenance gives you a dependable technical back office while you keep the strategy, the pricing and the relationship.

How a white label WordPress maintenance setup works

A working setup has three parts: getting each site into maintenance safely, agreeing how the work is presented, and deciding who speaks to the client. This is how I handle each of them.

• Onboarding sites. Every site starts with a review and a full backup kept off the server, before I change anything. I check plugins, the theme, PHP version, hosting and who has access. Sites with a long update backlog or inherited problems get a clean-up first, quoted separately, so the monthly plan starts from a known state. I take over sites built by other teams too, not only those your agency built.
• Branding and reports. Work reports can carry your agency's brand, ready to forward to the client. They list what was updated, what was checked and what needs a decision. The client sees your agency's care service, not a third party.
• Who talks to the client. You do. The client relationship stays with the agency and I agree tasks with you, not directly with your client, unless we decide otherwise. If you prefer, I can join client calls as part of your team, so technical questions get answered by the person doing the work.

Agencies choose between two modes. In a fully white label setup I stay invisible: no Esumo branding, no direct contact. In a visible setup I am introduced as your technical partner. Both work; it depends on how your agency sells and how much you want to be involved in technical conversations.

I sign NDAs without any fuss. Access, credentials and client information stay between us and are used only for the agreed work.

Responsibilities and SLA

Most problems in outsourced maintenance come from unclear responsibilities rather than technical mistakes. Before the first site goes live in maintenance, write down who does what. A short table in the agreement is enough.

• Updates. Who updates WordPress core, plugins and the theme, how often, and whether updates are tested on staging first.
• Backups. Where backups are kept, how many restore points exist and who checks that a restore actually works.
• Monitoring. What is monitored (uptime, security, forms, checkout) and who responds to an alert.
• Response time versus fix time. A response time says when someone starts working on the issue. It is not a promise that the issue will be fixed by then. Keep the two separate.
• Hosting and accounts. Whose account the hosting, domain and plugin licences are on. In most cases it should be the end client's or the agency's, never the subcontractor's.
• Out of scope. New features, redesigns and large integrations are separate work, estimated before they start.
• Access. How credentials are shared and stored, who creates the maintenance account in WordPress and hosting, and how access is removed when a site leaves the arrangement. Personal named accounts are better than one shared admin login, because every change can be traced.
• Escalation. What happens when a problem is outside the website itself, for example a hosting outage or an expired domain. Agree who contacts the host or registrar and who informs the client.

In my plans the response time depends on the tier: 2 business days on Care, 1 business day on Growth and 4 hours on business days on Partner, which is the plan I recommend for agencies. Esumo is based in Poland, so I work on Central European Time (CET/CEST).

If you want to see how this works on one of your clients' sites before committing, start with a free website review. You get a report within 3 business days, with no obligation.

Pricing models for white label care

There are two common ways to price outsourced maintenance for an agency, and both are fair if the scope is clear.

• Per website. Each site has its own plan and monthly fee. This is simple to resell: you add your margin and invoice the client. It works well when sites differ a lot in complexity, for example a brochure site next to an online store.
• Shared pool of hours. The agency buys a monthly pool of hours used across all sites. This suits agencies with many smaller sites and a steady flow of change requests, because unused capacity on one site covers work on another.

For agencies, the Partner plan is the starting point: €690 a month net, including 15 hours, with further hours at €42/h. It covers weekly updates with staging and rollback, monitoring of key journeys such as checkout or course purchase, a 4-hour response on business days, and a monthly call. Whether we bill per website or as a shared pool across all your sites, we agree individually before we start. All plans run on a monthly contract with 1 month's notice, and prices exclude VAT.

The full list of plans is on the WordPress care page. For agency-specific terms, see white-label for agencies.

Getting started

Starting does not require moving your whole portfolio at once. A gradual start is safer for you and your clients.

• Pick one or two sites. Choose sites that are representative of your portfolio, ideally one simple and one more demanding. Let the client know only what your setup requires; in a white label arrangement, nothing changes from their point of view.
• Agree the basics. Branding of reports, who talks to the client, how requests are submitted and how work is billed. The way you send requests, whether by email or in your own tools, is something we agree at the start.
• Review and backup. I review each site, make an off-server backup and list what needs attention before maintenance starts.
• Run a month. After the first month you will see the report, the work log and how requests were handled. Then decide whether to add more sites.
• Plan the exit too. Agree how a site leaves maintenance if a client ends the contract with your agency: final backup, removal of my access and a short handover note. A clear exit makes the start easier to agree.

Apart from maintenance, I can also help your team turn Figma designs into WordPress builds: custom themes on Gutenberg and ACF, without page builders, so the sites you hand over are easier to maintain later.

If you are still comparing providers, the article on how to choose a white label WordPress partner lists the questions I would ask. When you are ready, get in touch and tell me how many sites you have and what they run on.