Agencies and IT service providers keep running into the same calculation. Clients ask for something that already exists off the shelf, just not under someone else's name. Resell it and you become the reseller of a foreign logo and hand the client relationship to the vendor. Build it yourself and you spend two years on groundwork that has nothing to do with your actual business.
The third option
Between those two sits the route larger providers have taken for years: running a finished platform under your own brand. Your clients see your domain, your logo, your colours and your prices. They see no indication of who built the software. Operations, updates and further development sit elsewhere; the client relationship sits with you.
This is not a label stuck over a standard interface. Brand, pricing, permissions and even the layout of the screens are set per level and inherit downwards. What you configure as a reseller applies to your clients. What a client adjusts for themselves applies to their users, without overwriting your defaults.
Why the levels matter more than the logo
The visible part of white labelling is quickly explained. The load-bearing part is how many tiers fit underneath. An agency rarely looks after end clients only. It looks after clients who in turn have sites, franchisees or their own customers. If the platform knows one level only, you end up with separate installations, separate updates and separate invoices.
aYOUne models the whole chain: platform operator, reseller, agency, client and their sub-clients. Each level sees its own data, can issue its own logins and set its own prices. The separation is not a setting somebody can forget, it sits in the data model. For you that means looking after a hundred clients without operating a hundred systems.
What you are actually selling
The common mistake is assuming the product is the software. It is not, because software is available everywhere. What you sell is the setup, the fit to an industry and the ongoing support, which is exactly what you are best at anyway. The platform is the base that makes this possible without a development department.
Commercially it shifts the shape of the business. One-off project revenue becomes recurring revenue, and the margin lives in the spread between what you pay and the price you set. A project business with gaps in utilisation becomes a book of recurring accounts.
The questions worth settling first
Three points decide whether the model suits you. First, the brand: do you genuinely want to appear as the provider, with everything that means for being first in line on support? Second, the depth: is your logo enough, or do you need your own terminology, your own workflows and your own domain? Third, billing: who invoices your clients, you or the vendor?
If the answer to the third question is not “me”, it is not white labelling, it is referral. The difference becomes visible at the latest when a client wants to move.
Frequently asked questions
Does it run on our own domain?
Yes. Your own domain including its certificate is part of white labelling, otherwise someone else's brand sits in the address bar.
Will our clients see that the software comes from someone else?
No. The interface, the sender of notifications and the address all carry your brand.
Can we set our own prices and packages?
Yes, that is the core of the model. You buy on your terms and sell on yours.
You can read how the tier model works under multi-tenancy. Partner terms are in the reseller section, and a worked example under your own brand.