White-label software is a product built by one company and presented to customers under another company’s name and branding. For an agency, it means clients see your name, logo and colours on the tools they use, not the vendor’s. How far that goes varies a great deal, so check exactly which parts are branded.
The phrase gets used loosely. Some vendors mean a logo upload. Others mean your own domain, your own colours, your own emails and no trace of the vendor anywhere. The difference matters, because the client-facing surfaces are where your brand is most visible.
Why agencies want it
An agency sells expertise and trust. If a client logs in to a portal, opens a report or receives an email, and every one of them carries a third party’s brand, the agency looks like a reseller. Branded surfaces reinforce that the agency is the one doing the work and make switching tools invisible to the client.
There is a practical side too. A client who is used to opening documents on your domain is less likely to wonder what the vendor does or to contact them directly.
What can be branded
Work through the surfaces a client or prospect actually touches:
- Name and logo across the workspace and in the header of documents.
- Colours and typography, so pages feel like your site.
- Sign-in page, including its wording and domain.
- Emails the system sends on your behalf: sender name, template, footer.
- Documents such as proposals, reports and invoices.
- A client portal, where clients view work, approve items and read reports.
- Your own domain, such as
clients.youragency.com, rather than a vendor subdomain.
Ask the vendor for a list of what is and is not branded today, and what is on a roadmap. A roadmap item is a promise, not a feature. Plan around what is live.
White-label compared with related terms
- Branded usually means a logo and a colour on an otherwise standard product.
- White-label means the product is presented as yours, with the vendor kept out of view.
- Reseller means you sell the vendor’s product, often with the vendor’s name still on it.
- Open source or self-hosted means you run the software yourself, which gives control and also the cost of running it.
Questions to ask a vendor
- Which client-facing screens carry my brand today, and which still show yours?
- Can I use my own domain, and is the certificate managed for me?
- Are emails sent from my domain with my sender name?
- How is my data kept apart from other agencies’ data? Ask whether it is a separate database or a shared one with filters.
- How is it priced: per seat, per client, per usage, or a flat fee? Do prices change when I add clients?
- Can I export everything if I leave?
- What is not built yet, and when is it promised?
The fourth question matters more than it looks. The usual design is multi-tenant: one running application serving many agencies. That is efficient, and the quality of the separation between tenants is what protects your clients’ data.
Pricing models
Per-seat pricing charges for each person on your team who logs in. It scales with your headcount, not your client list, which suits agencies that grow their client base faster than their team. Per-client or usage-based pricing can look cheaper at ten clients and become expensive at fifty. Work out your likely numbers a year from now and compare each model at that size.
Sign-in and access
Larger agencies and their clients sometimes ask for single sign-on, where staff log in with their existing company account. Ask early if you need it, since it is not offered by every tool. Also check roles: who can see which clients, who can approve, who can only read.
Check the claims
A vendor demo shows the best path. Ask for a trial workspace and look for the places where the vendor’s name still appears: error pages, email footers, the browser tab title, a shared link preview. Send yourself a document and open it as a client would. The gaps show up in about fifteen minutes.
An example of being specific
Kervol is an agency operating system that is open about this boundary. In Kervol 1.0, an agency gets its own name and logo across the workspace, proposals sent under its name with its details, and its own database. Brand colours and fonts from a theme screen, branded sign-in and email, branded Discovery and status reports, and your own domain for the workspace are planned for Kervol 1.5, and until then every workspace uses Kervol’s default theme. A branded client portal is planned. That is the kind of line to ask any vendor to draw.
Checklist
- A written list of every client-facing surface and whether it is branded.
- Your own domain, with certificates handled.
- Emails sent under your name.
- A clear answer on how your data is separated from other agencies’.
- A pricing model compared at your size in a year.
- Roles and, if needed, single sign-on.
- A data export you have tested.
- A trial where you opened a document as a client and looked for the vendor’s name.
Updated 21 October 2026