Disclosure
We sell white-label HR software, so read this as a guide written by someone with an interest in the answer. It is written to be useful whichever vendor you choose, and the questions at the end are ones you should put to us as readily as to anyone else.
Short answer
White-label HR software is a finished product built by one company and supplied by another under its own name: your logo, your product name and your web address, with the engineering, hosting and updates staying with the vendor. The three arrangements vendors mean by it (reseller, white-label and private label) differ on whose brand the user sees, who holds the client contract and who the client pays. We sell white-label HR software, so this guide is written by an interested party.
Written by
Subhan Khan, Founder
·
·
White-Label
What white-label HR software is
White-label HR software is a finished product, built and maintained by one company, that another company supplies under its own name. The people using it see your logo, your product name and your web address. The engineering, hosting and updates stay with the vendor.
It exists because building HR software is slow and expensive, and because the firms best placed to sell it — the ones already advising on employment, running payroll or managing a client’s IT — have no wish to become software companies. White-label lets them offer the product without building it.
The phrase gets used loosely, which is where most of the confusion starts. Three quite different arrangements are all called white-label, and they differ on who the client contracts with, who they pay, and whose name is on the screen.
Reseller, white-label, private label
Vendors use these terms inconsistently, so the label matters less than the answers to three questions: whose brand the user sees, who holds the contract with the end client, and who that client pays.
Reseller
You sell the vendor’s product under the vendor’s name and take a margin. The client knows whose software it is. Fastest to start, least control, and your client can usually go direct later.
White-label
The product carries your brand — logo, product name, colours, domain, emails — but it is the vendor’s platform underneath, maintained by them. You hold the client relationship. This is what most vendors mean.
Private label
Usually a deeper arrangement: a dedicated deployment, sometimes with changes made for you. More control, more commitment, normally a longer contract. Ask what actually differs from white-label before paying for the word.
If a vendor cannot say plainly which of the three it is selling, that is itself an answer. Ask them to describe what your client sees at the login screen, and what happens if you stop working together.
Who actually buys it
White-label HR software is bought by firms that already hold the client relationship and want to add software to it rather than refer it away.
- HR consultancies that advise on policy and need somewhere for the client’s records to live.
- Payroll bureaus adding HR, leave and attendance around the payroll they already run.
- PEOs and employer-of-record firms that need one system across many client companies.
- Managed service providers already supplying IT to small businesses, for whom HR is an adjacent sale.
- Franchise groups and business networks that want one branded system across their members.
The common thread is trust that already exists. White-label works when the client is buying from you because they buy from you. It works badly as a way to acquire strangers, because you are then competing on a product you did not build and cannot change.
What “your brand” should cover — and what it will not
This is where to be specific, because “fully branded” means different things to different vendors. Get the list in writing, element by element. A reasonable arrangement puts your brand everywhere the client looks and leaves the machinery with the vendor.
Should be yours
- Logo and favicon, in the app and on client-facing documents.
- The product name, wherever the interface shows it.
- The colour scheme.
- The login page — the first thing every user sees, every day.
- A web address you choose, not a subdomain of the vendor’s own site.
- System emails — invitations, reminders, payslip notifications — sent from your address and under your name.
- Error pages, which are easy to forget and are exactly where somebody else’s name appears at the worst moment.
Usually stays the vendor’s
- The infrastructure: servers, backups, monitoring.
- Security patching and framework upgrades.
- The product roadmap — what gets built next, and when.
- The underlying code, which you are licensing rather than buying.
Ask specifically about the places branding tends to leak: the login screen, transactional emails, error pages, and any in-product help or assistant. A vendor that has thought about it will answer without checking. One that has not will tell you it is on the roadmap.
Hosting and data — the questions that matter later
Where the software runs and who holds the data decide what you can promise your own clients. If you sell to businesses that must answer questions about where employee records are stored, you need these answers before you sign, not after a client asks.
Establish whether your installation is separate or a tenant inside a shared system, and where it is physically hosted. A separate installation is easier to reason about for data residency and easier to move; shared tenancy is usually cheaper and updates faster. Neither is wrong, but they are different answers on a client’s due-diligence questionnaire.
Then establish who is the data controller and who is the processor, and get the processing terms in writing. You are the one your client will ask.
Who answers your client
Support is the part partners most often underestimate. There are three usual shapes: the vendor supports your clients directly under your name; you provide first-line support and escalate; or you handle everything and the vendor supports only you.
Each is defensible. What is not defensible is discovering which one you bought when a client’s payroll run fails on a Friday afternoon. Ask which hours are covered, in which languages, and what happens outside them.
What to settle before you sign
Put these to any vendor, including us. They are questions rather than promises on purpose: the answers are what you should be comparing.
- Which arrangement is this — reseller, white-label or private label — and what specifically differs?
- Exactly which screens, documents and emails carry my brand, and which do not?
- Is my installation separate or shared, and where is it hosted?
- Who is the data controller, who is the processor, and what do the processing terms say?
- Who supports my clients, during which hours, and in which languages?
- What uptime does the contract commit to, and what happens when it is missed?
- If we part company, what do I get back, in what format, and how long do I have to take it?
How HRMZY does it
We run one separate installation per partner, on a domain you choose, deployed, hosted, updated and supported by our team. Your clients are companies inside your installation rather than tenants of ours. We sell this, so read it as an interested party describing its own arrangement — the detail, including anything that still carries our name, is on our white-label page.