White-Label SaaS for Resellers: How the Model Actually Works

Overview

White-label SaaS lets a reseller sell someone else's software under their own brand. The mechanics are widely described and the commercials rarely are, which is unfortunate, because the commercials are what determine whether the model makes you money. How white-label software actually works is less a question about logo uploads than about who contracts with the end client, who carries support, who sets the price, and what happens to the client list when the partnership ends.

This is a companion to our buyer's guide to white-label HR and operations software, which covers branding depth and tenancy. Here the subject is the deal.

1. Decide whether you want commission, margin, or a platform business — they are three different companies.
2. Price support explicitly, because it is the cost that surprises resellers.
3. Settle the exit terms while the vendor still wants your signature.

How does white-label software work?

Structurally, a vendor builds and operates a multi-tenant platform. A partner is given a tenant — or the ability to create tenants — and a branding layer: their logo, colours, domain, and sender identity applied to the interface and to outbound artefacts like emails and exported documents. The partner then sells access to end clients as their own product. The vendor keeps running infrastructure, releases, and security; the partner keeps the customer relationship, the configuration, and usually the first line of support.

What varies between deals is not that description. It is who invoices the client, at what price, under whose terms, and what each side is contractually obliged to do when something breaks.

The three commercial models

Referral. You introduce the client; the vendor contracts and bills them; you take a commission, typically for a bounded period. It costs you nothing to set up and it is not really white-label at all, because the client meets the vendor at signature and the brand on the invoice is not yours. Sensible if software is adjacent to your business rather than part of it. Recognise it for what it is: an affiliate arrangement with better paperwork.

Reseller. You buy at a partner rate and sell at your own. You issue the invoice, you set the price, and the client's contract is with you. This is the tier where white-labelling starts to mean something, and it is also where the obligations arrive. You are the support desk. You are the party the client escalates to at 5pm on a Friday, including for issues you cannot fix yourself because they sit in the vendor's platform. Your margin is the gap between the partner rate and your price minus the cost of that obligation, and the third term is the one nobody models.

Wholesale or platform. You commit to volume — a block of tenants or seats — at a committed rate, and allocate it as you win business. Best unit economics, real balance-sheet risk, and usually the only tier where deep branding and self-service tenant provisioning are on the table. It is the right structure once demand is proven and an expensive way to find out whether demand exists.

A useful sanity check: if the vendor offers full white-labelling at referral-tier commitment, ask what "full" means. Either the branding is thinner than the word implies, or the vendor has a reason to want your brand in front of the client that you should understand before you agree.

Where the margin actually goes

Reseller margin looks generous on the first spreadsheet and thins in three predictable places.

The first is support. Once your logo is on the login screen, every password reset, permission question, and "why is this report empty" is yours. That cost scales with end users, not with clients, so a single 400-seat client can cost more to support than eight 40-seat ones at the same revenue. Either price a support tier explicitly, or negotiate a response-time commitment and an escalation path from the vendor and price for that.

The second is onboarding. Configuring a tenant, importing data, and training administrators is real delivery work. If it is manual it does not get cheaper with the tenth client. Ask whether configuration can be saved as a template and applied to new tenants, and whether you can provision a tenant yourself without raising a ticket — the answer moves your marginal cost more than the partner discount does.

The third is pricing shape mismatch. Vendors usually charge per seat. Resellers often want to charge per client, per project, or as part of a bundled retainer. Those two shapes diverge as clients grow, and the divergence runs against you. Model your third year at your largest plausible client, not your first quarter at your smallest.

1. Terms to settle before signature:
   • Who owns the end-client relationship and the data in it, stated explicitly rather than implied.
   • Whether the vendor may market to, or contract directly with, clients you introduced — a non-solicitation clause covering your book.
   • What happens to your tenants if the agreement terminates, and how much notice each side gives.
2. Operational commitments:
   • Support tiers: what you handle, what the vendor handles, and the response time attached to each.
   • Release notice, so an interface change your clients will notice does not arrive unannounced.
   • Whether an update can be deferred for a tenant, and for how long.
3. Commercial protections:
   • Price-change notice on the partner rate, and whether existing tenants are grandfathered.
   • Minimum commitments and what happens if you miss them.
   • Whether the discount tier ratchets with volume, and whether it can ratchet back down.

White-label SaaS marketplaces

A second route exists: marketplaces that aggregate white-label products and let a reseller assemble a catalogue. The appeal is breadth — you can offer eight categories without eight partner agreements. The trade-off is depth and control. Branding tends to sit at the cosmetic tier because it is applied uniformly across many products; you are one tier removed from the people who build the software, so escalations are slower; and the catalogue changes when the marketplace's supplier relationships change, not when you decide.

Marketplaces suit resellers selling breadth as the proposition. If a single product is central to your service, a direct agreement with its vendor is almost always the better structure, because the terms you will need to negotiate are exactly the ones a marketplace cannot vary for you.

Suite or single product?

One decision resellers underweight is how many products they want under one agreement. Selling an HR system this year and a time-tracking system next year through two vendors means two partner agreements, two support escalation paths, two release calendars, two branding configurations, and a client who now has two logins with your logo on both and no shared employee directory between them.

A vendor whose products already share a tenant, a directory, and a permission model collapses that overhead. It also constrains you: you are betting on one roadmap. That trade-off is the same one your clients face when choosing between a suite and a set of specialists, and it plays out the same way — we covered the reasoning in all-in-one versus best-of-breed operations software. As a reseller you feel it twice, once in your own operations and once in what you can credibly promise.

Where to go next

If you are evaluating platforms rather than terms, start with branding depth and tenancy — our buyer's guide covers both, and it is the diligence to do before commercials. If you are a recruitment business specifically, the ATS case has its own set of checks, which we set out in what agencies should check before signing a private-label ATS deal.

For what we offer partners — per-tenant logos, colours, and domains, with the client relationship staying yours — see the Workefy white-label page, or browse the products you would be putting your brand on. Partner terms are quoted rather than published; ask and we will send them.