What is actually being white-labeled?
White labeling can cover different layers: logo and colors, login domain, emails, client portal, mobile app, billing experience, support resources and sometimes the product name itself. Never assume a platform's 'white label' label includes every layer. Some capabilities are plan-gated or sold separately.The reseller model
The agency buys access to a platform, configures a repeatable client experience, then sells that experience as part of a recurring package. The value comes from packaging, implementation, niche expertise and ongoing support—not merely putting a new logo on generic software.The core evaluation checklist
Evaluate account separation, branding depth, client billing, usage-based cost, automation, integration needs, reporting, support tooling, permissions, mobile experience and migration. Then test the actual workflows your clients will use.Avoid the feature-count trap
A platform can list hundreds of features and still be a poor reseller product if onboarding is confusing or the client cannot understand what they are buying. Start from a defined client outcome, then select the smallest coherent feature bundle that supports it.White labeling does not remove platform dependence
Even when the client never sees the underlying vendor, the reseller still depends on that vendor's infrastructure, pricing and product roadmap. Build vendor change into your operating process: monitor release notes, re-check plan requirements before updating sales copy, and avoid promising permanent access to features that can be repriced or moved.
A healthy reseller offer therefore combines platform leverage with portable assets you control—your brand, onboarding process, niche documentation, templates, client relationships and support knowledge. Those assets preserve more of the business value if the underlying software changes.