White-label WordPress management that never mentions us
Your clients should experience your agency, not your vendor. Reports, portal, emails and the connector plugin all carry your brand, with no WPCentrify logo anywhere the client can see.
Free during early access. No credit card required.
Vendor branding undermines the service you are selling
Agencies selling care plans are selling expertise and attention. Every time a client sees a third-party logo on a maintenance report, it invites a question the agency does not want asked: what exactly am I paying you for, if a tool is doing this?
The question is unfair, because the tool is not doing the judgement, the prioritisation, the client relationship or the accountability. But it gets asked, and once it is asked the client can go and price the tool directly, which is a conversation that ends badly regardless of how it is answered.
The other cost is subtler. White-labeling that is partial — a branded report but a vendor-branded email sender, or a branded portal at a vendor domain — reads as a cheaper version of proper white-labeling, which is worse than not attempting it.
What carries your brand
- Client reports, with your logo, colours and typography
- The client portal, on your own domain
- Email notifications, from your sending domain
- The connector plugin as it appears in the client's plugin list
- PDF exports and shared documents
- Status and incident communications to clients
How white-labeling is configured
Set up once at the account level, applied everywhere a client might see it. Per-client overrides are available if you operate under more than one brand.
Brand assets
Upload your logo, set brand colours and choose typography. These apply to reports, the portal and every client-facing document without further configuration.
Your domain
Point a subdomain of your own domain at the client portal. Clients log in at your address, and the browser address bar carries your brand rather than ours.
Your sending domain
Configure email authentication so notifications and reports come from your domain. This improves deliverability as well as branding, because authenticated mail from a known domain is less likely to be filtered.
The connector plugin
The plugin as it appears in the client's WordPress plugin list carries your agency name and description, so a client browsing their own admin does not find a vendor they have never heard of.
Where white-labeling applies
Reports
Monthly maintenance reports in your brand, with your commentary, delivered from your domain on your schedule.
Client portal
Your clients see their sites, requests, reports and entitlements at your own web address.
Connector plugin
Renamed and re-described in the client's plugin list so your stack is not visible from their admin.
Notifications
Incident and maintenance emails sent from your domain, in your voice, with your escalation contacts.
Documents
Exported PDFs, proposals and audit summaries carry your brand rather than ours.
Multiple brands
Per-client brand overrides for agencies operating several trading names or servicing other agencies.
White-label website maintenance for resellers and other agencies
A meaningful proportion of WordPress maintenance is delivered by one agency on behalf of another. A design studio sells a care plan, a specialist agency delivers it, and the end client never knows the second agency exists.
That arrangement only works if white-labeling holds up under scrutiny, including in the places people forget: the email headers, the plugin list, the portal certificate, the PDF metadata. A single unbranded touchpoint undoes the whole arrangement, usually at the worst possible moment.
Per-client brand configuration means the delivering agency can service multiple reselling partners from one account, with each partner's clients seeing only that partner's brand. Reports, portals and notifications stay separate without maintaining separate accounts.
Where white-labeling commonly leaks
- Email sent from a vendor domain despite branded content
- A portal on a vendor subdomain rather than your own
- Vendor name visible in the client's WordPress plugin list
- PDF metadata carrying the vendor's name
- Support replies signed by the vendor rather than the agency
Related capabilities
Questions about white-labeling
Not from anything you present to them. Reports, portal, emails and the connector plugin all carry your brand. A determined technical client inspecting network requests could identify the underlying service, as with any white-labeled platform, but nothing in the normal client experience surfaces it.
To get the full benefit, yes: a subdomain of a domain you already own is enough, and setup takes one DNS record. Without it the portal works but sits at our address, which undercuts most of the point.
Yes. Per-client brand overrides exist specifically for agencies operating multiple trading names or delivering white-labeled work for other agencies. Each client sees only the brand assigned to their account.
No. It is included rather than sold as an add-on, which is deliberate, because several competitors charge per site for it and that pricing makes white-labeling a decision rather than a default.
No. The plugin continues to receive updates normally. Only the name and description shown in the WordPress plugin list change.
Deliver under your own brand
Your logo, your domain, your reports. Set up once and every client touchpoint carries your agency rather than ours.
Free during early access. No credit card required.