How to choose a white label WordPress agency partner: 10 questions to ask

Why choosing a white label WordPress agency matters for your reputation

In a white label arrangement your client does not know who updated their plugins. They only know whether the site works. If an update breaks the checkout, the email from the client lands in your inbox, and the apology comes from you.

That is why the usual buying criteria, price per site and a list of features, are not enough. What matters is how the partner works when something goes wrong: whether they tested before updating, whether they can roll back, how quickly they respond, and whether they tell you the truth.

A good partner makes your agency look reliable. A poor one creates work you cannot bill and conversations you would rather not have. The ten questions below are designed to tell the two apart.

Before the call, decide what you need. An agency with a handful of brochure sites needs something different from one with several online stores and course platforms. Write down how many sites you would hand over, what they run on, which of them take payments and how often clients ask for changes. With that list in hand, the answers you hear become much easier to judge.

The 10 questions to ask

Ask them in a call, not by email. How a partner answers, and whether they answer at all, is part of the test.

• 1. Do you test updates on staging before applying them to live sites? What a good answer looks like: yes, at least for sites with stores, booking or custom code, with a clear description of how changes reach the live site.
• 2. How do you roll back a failed update? What a good answer looks like: a specific procedure, including how new orders or form entries are preserved on stores and dynamic sites.
• 3. Where are backups kept and how do you test restores? What a good answer looks like: off the server, several restore points, and restores actually tested, not just scheduled.
• 4. What are your response times, and how do they differ from fix times? What a good answer looks like: response times stated per plan, in business hours or days, and an honest explanation that a fix can take longer.
• 5. Who will actually work on our clients' sites? What a good answer looks like: named people you can talk to, not an anonymous pool that changes every month.
• 6. How do you communicate with us, and with our clients? What a good answer looks like: one agreed channel for requests, clarity on whether they ever contact your client directly, and the option to stay invisible.
• 7. Will you sign an NDA, and how do you handle credentials? What a good answer looks like: yes without hesitation, plus a sensible approach to storing and removing access.
• 8. What do your reports look like, and can they carry our brand? What a good answer looks like: a sample report you can see before signing, listing work done and decisions needed, available under your agency's brand.
• 9. How is work priced, and what counts as extra? What a good answer looks like: a clear monthly scope, a stated hourly rate for work beyond it and an estimate before larger tasks start.
• 10. What time zone do you work in, and what happens when you are away? What a good answer looks like: stated working hours, overlap with your day and a clear plan for holidays.

Write the answers down and compare providers side by side. A simple way to score them: for each question, note whether the answer was specific (a procedure, a number, an example), general (“we always make sure…”) or missing. Specific answers on questions 1–4 matter most, because they decide what happens on the day an update goes wrong. Questions 5–8 decide how pleasant the everyday collaboration will be, and 9–10 whether the arrangement is sustainable for your margins and your clients' expectations.

Finally, ask for one reference point you can verify yourself: a sample report, a public case study or a short trial on a single site. Claims are easy to make in a call; documents and real work are harder to fake.

Also ask for the agreement or terms before you decide, not after. The answers you heard in the call should appear there: response times, what is included, how extra work is estimated and the notice period.

If you want to see how a partner handles a real site before you sign anything, ask for a review of one of your clients' websites. I offer a free website review: a report within 3 business days, with no obligation.

Red flags

Some answers should make you slow down, whoever gives them.

• Unlimited everything for a flat fee. Unlimited fixes or changes at a low price usually means someone else's site gets priority when it matters.
• Updates without testing. Fully automatic updates with no check afterwards are fine for some sites, but not for stores or sites with custom code.
• Accounts in the partner's name. Hosting, domains or licences registered to the subcontractor create a dependency you will struggle to undo.
• No sample report. If they cannot show you what you will receive each month, you will not know what you are paying for.
• Vague answers about who does the work. A partner who cannot tell you who will touch your clients' sites cannot promise consistency either.
• Reluctance to sign an NDA. A partner working under your brand should accept confidentiality as standard.
• Pressure to move everything at once. A partner confident in their work is happy to start with one or two sites and earn the rest.
• No questions about your sites. A partner who quotes a price without asking what the sites run on, which take payments and how often they change is pricing a generic service, not your portfolio.

None of these is automatically a deal-breaker, but each deserves a follow-up question. Ask how they handled the last failed update, or what they did the last time a client site went down. A partner with a real process answers with specifics; one without it answers with reassurance.

How Esumo answers them

Here is how I would answer the same questions. I have run Esumo since 2017 and completed 80+ projects, and for agencies I work as a technical partner behind their brand.

• Staging and rollback. The Partner plan, which I recommend for agencies, includes weekly updates tested on staging, with rollback. Every new site starts with a review and an off-server backup.
• Response times. On Partner, I respond within 4 hours on business days. Esumo is based in Poland, so I work on Central European Time (CET/CEST).
• Who does the work. You talk to the person writing the code. There is no chain of project managers between you and the developer.
• Communication. The client relationship stays with your agency and I agree tasks with you. I can stay invisible or join client calls as part of your team. We agree how requests reach me at the start.
• NDA and reports. I sign NDAs without any fuss. Reports can carry your agency's brand.
• Pricing. Partner costs €690 a month net including 15 hours, then €42/h. Billing per website or as a shared pool of hours across all sites is agreed individually before we start. Monthly contract, 1 month's notice, prices exclude VAT.

I also take over sites built by other teams, not only by your agency. Each one starts with a review and a backup, and only then do updates and changes begin, so you know the state of a site before it becomes part of your care offer. Sites with a long backlog can go through a takeover and clean-up first: 2 weeks, €690 net one-off.

Response times in every plan are counted in business hours or business days, so you know exactly what to tell your client when they ask how quickly something will be looked at.

More on the setup itself is in white label WordPress maintenance for agencies and on the white-label for agencies page. If you would rather discuss your portfolio directly, get in touch.