Is a custom domain the same as white-labelling?

It is one piece of it, not the whole thing. A custom domain hides the vendor's URL. A client can still see the vendor's name in emails, the login screen or a 'powered by' footer if the rest of the branding was not replaced too.

Why does data separation belong on a white-label checklist at all?

Branding and tenancy are usually unrelated decisions made by the vendor. It is easy to assume a white-labelled product also isolates each client's data, when the two are independent features. A CRM can look fully rebranded per client while every client's rows still sit in the same shared database.

Do white-label CRMs usually let me set my own pricing to clients?

Often yes for the retail price a client pays you, because that is your business relationship with them. Whether the vendor offers wholesale or partner pricing to you is a separate, less consistent feature. Confirm it before you plan margin around it.

How do I white-label a CRM?

Four things are visible: your domain, your brand, no vendor mention, and a way to clone a setup. The fifth, which most vendors skip, is keeping each client's data separate.

app.salescrew.io/inbox

The unified reply inbox with classified threads

The short answer

White-labelling a CRM means four visible things. Your own domain. Your brand in the interface and in outgoing emails. No vendor 'powered by' mention anywhere a client can see. And a way to clone a working setup onto the next client without rebuilding it.
A fifth requirement, which most vendors leave out of their white-label pitch, is keeping each client's data separate from every other client's. Branding and data isolation are unrelated features that a vendor may or may not have both built.
White-label pricing tiers commonly gate the custom domain and the 'powered by' removal behind the vendor's top plan. Check which tier includes full branding before assuming a lower tier covers it.
Cloning a finished setup, meaning stages, cadences, dispositions and integrations, onto a new client account is the feature that decides how fast an agency can onboard. It is offered less often than basic branding.

Why branding alone is not the full checklist

Most vendors that advertise "white-label" mean the visible layer. Replace the logo, pick a color, put it on a subdomain or a custom domain. That is real and it matters. A client seeing the vendor's brand undermines the agency relationship. But it is also the easiest part to build, and vendors tend to stop there.

The harder, less advertised piece is repeatability. Can you take a setup that works, stages, cadences, dispositions, agent policy, and apply it to the next client without starting over? A white-label product without a cloning mechanism still requires an agency to rebuild each client's configuration by hand. That caps how many clients one person can onboard in a week.

The piece that is almost never part of the white-label pitch is whether each client's data sits in a separate place. It is an architecture decision rather than a UI setting. A product can look fully white-labelled per client, different logo, different domain, different color, while every client's rows still live in one shared database underneath. Branding and data separation are independent features. Confirming one does not confirm the other.

What 'white-label' covers, vendor by vendor

Named vendors are cited from their own pricing, help and developer pages. Verify before quoting a specific plan or price.

Element	GoHighLevel	Vendasta	SalesCrew
Custom domain	Yes. You point a CNAME at HighLevel and set it in the agency account; the branded desktop app with custom domains is listed on the Unlimited plan at $297/mo	Yes. Vendasta lists customized Business App domains on its Premium plan; the white-label client portal starts on Professional	On the roadmap, not available today
Brand in UI and emails	Yes. You upload your logo, colors and fonts, and a separate API domain brands the links inside outgoing emails and texts	Yes for logos, colors and product names, set per market or per product	On the roadmap, not available today
No vendor mention visible to clients	Yes on the white-label setup, which replaces HighLevel branding across the platform	Yes, and Vendasta requires it: its developer docs say there must be no mention of Vendasta in your content, including dashboards, UI, cookies, redirects and error messages	On the roadmap, not available today
Clone a setup per client	Yes. Snapshots are listed from the $97/mo Starter plan and can be attached to a plan in the SaaS configurator	Not described as a snapshot feature in the white-label documentation	On the roadmap (snapshot export/apply); today configuration is repeatable through MCP tools, not one click
Each client's data kept separate	Clients are sub-accounts inside your agency account; the documentation describes sub-accounts, not a database per client	Clients are accounts under a partner and market hierarchy; the documentation describes accounts, not a database per client	Available today, one Supabase project per client

Figures checked on vendor pricing, help and developer pages, September 2026.

What to check before you commit to a white-label plan

Ask which tier removes the vendor's name everywhere a client can see it. Login screens. Outgoing email footers. Browser tab titles. Any in-app help links. Custom domain and full brand removal are commonly two separate features on two separate tiers. A vendor's marketing page usually shows the fully branded version, whichever tier you are pricing.

Then ask about the two things that decide how the product works for you day to day. Can you clone a working setup onto a new client? Is each client's data separated at the database level, or only by a filter in the interface? Neither question is answered by seeing a rebranded login screen in a demo.

Disclosure: SalesCrew is our product. Branding, meaning your name, logo, theme and a client subdomain, and snapshot export and apply are both on the roadmap, not available today. This page says so rather than describing them as shipped. What is available today is the data-separation half. Each client gets a dedicated Supabase project, so nothing is shared between two clients whatever the interface looks like.

Custom domains are commonly gated behind the top plan

White-label pricing tiers often reserve the custom domain and full brand removal for the highest tier. A lower tier looks white-labelled in a demo but still shows the vendor's name somewhere a client will eventually see. Ask which tier includes full removal before you price a plan around it.

Questions

Is a custom domain the same as white-labelling?: It is one piece of it, not the whole thing. A custom domain hides the vendor's URL. A client can still see the vendor's name in emails, the login screen or a 'powered by' footer if the rest of the branding was not replaced too.
Why does data separation belong on a white-label checklist at all?: Branding and tenancy are usually unrelated decisions made by the vendor. It is easy to assume a white-labelled product also isolates each client's data, when the two are independent features. A CRM can look fully rebranded per client while every client's rows still sit in the same shared database.
Do white-label CRMs usually let me set my own pricing to clients?: Often yes for the retail price a client pays you, because that is your business relationship with them. Whether the vendor offers wholesale or partner pricing to you is a separate, less consistent feature. Confirm it before you plan margin around it.