Macro.com White Label CRM Buyer's Guide

What White Label CRM Actually Means

White label CRM is not simply giving your clients access to software under a different name. It involves three distinct technical and business layers that each need separate evaluation. First, the platform must accept your agency's branding (logo, domain, colour scheme) so clients see your name throughout, not the vendor's. Second, each client account must be completely isolated, so one client cannot see another's data, and you can charge and control permissions independently for each. Third, you need clarity on who owns the client relationship for support and invoicing. Understanding these three layers separately is the only way to evaluate whether a platform will actually work for your model.

Many agencies assume all three layers are automatic. They are not. Some platforms apply branding at the interface level only, leaving backend systems and billing pages unbranded. Others isolate data but require you to handle support directly, which can overwhelm a small team. A third category gives you billing control but hands support to the vendor, creating awkward handoffs when a client reports a problem. Knowing which model a platform offers is the difference between a smooth resale channel and a source of client complaints you did not budget for.

Condition One: Complete Branding Coverage

Branding starts with the obvious: your logo on the login screen and your domain in the URL. But it extends to every customer-facing surface: email notifications, help articles, API documentation, invoice headers, and automated alerts. If your logo appears in the interface but invoices still show the vendor's branding, your client will experience a fractured identity. Test this by requesting a full trial account as if you were an end customer, not an agency partner. Log in, change a password, receive a password-reset email, run a report, check the PDF download, and look at the invoice or billing page. Take screenshots of every screen. The ones that still carry the vendor's branding are support friction points you will inherit.

Verify in writing which specific surfaces are customisable and which are not. Ask whether custom domain setup is included or a paid add-on, and whether it covers email notifications and invoice generation. Some platforms let you rebrand the UI but still send emails from their domain, creating confusion. Others support full domain customisation but require you to host DNS records or handle SSL certificates. Confirm whether you or the vendor maintains the SSL certificate, and what happens if it expires. A vendor-managed certificate is simpler; a vendor that expects you to manage it without clear documentation will create downtime during renewal. Ask for their documentation on custom domain setup and read it yourself before purchasing. If they won't share it, that is a red flag that the process is undocumented or difficult.

Condition Two: Account Isolation and Multi-Tenancy

Data isolation is the non-negotiable technical foundation of white label CRM. Each client's account must be completely separate at the database level, so a bug in one client's account cannot affect another, and a vendor security update does not risk exposing one client's data to another. Test this by creating two trial accounts under the same white label instance. Log into Account A and verify you cannot see, access, or modify any data from Account B. Check the URL structure: does it change between accounts, or is all data accessed through the same endpoint? Do permission changes in one account affect the other? Can you set custom fields, automation rules, or retention policies separately for each client? The more independence each account has, the easier your support team's job.

Ask the vendor about their multi-tenancy architecture: whether each client is in a separate database, a shared database with row-level security, or a hybrid. Each has trade-offs. Separate databases are most secure and allow independent scaling, but are expensive and slow to provision. Shared databases with row-level security are cheaper and faster to deploy, but a bug in the security layer could breach isolation. Understand which model they use and what their testing and audit process is for confirming isolation is maintained. If they hesitate or give vague answers, the isolation layer is likely underdeveloped. Ask for their security documentation and white papers on their multi-tenancy model.

Condition Three: Support and Billing Ownership

The support model you choose determines whether white label CRM is profitable or a support drain. Three models exist: first-line support, where your team handles all client issues and escalates technical problems to the vendor; co-support, where your team handles some issues and the vendor handles others, with a defined handoff; and full delegation, where the vendor handles support directly but under your brand. Each has different skill requirements, cost implications, and client satisfaction profiles.

First-line support requires you to hire or train someone who understands the platform deeply enough to troubleshoot login problems, lost data, integration issues, and permission errors. If you are a two-person agency, this is often impossible. Co-support requires clear documentation of what your team is responsible for and what the vendor covers, with a formal escalation process so clients do not experience finger-pointing when something breaks. Full delegation means the vendor talks directly to your clients, which kills your relationship with them and usually violates the white label model. Ask the vendor which model they support, and get their tier-one support SLA in writing: how long before first response, and what counts as resolution. For co-support, ask for their escalation policy and request a copy of their technical documentation your team would be expected to master. If they do not have written escalation procedures, expect chaos when your first client has a data problem at 11 p.m.

Billing ownership is equally critical. Ask whether you invoice the client and pay the vendor, or whether the vendor invoices the client directly. If you invoice the client, you control pricing, payment timing, and the relationship. If the vendor invoices, you lose control of renewal timing and client payment defaults become your vendor's problem, not yours. Verify that the vendor's billing system supports per-client configuration of features, users, and custom pricing tiers. Some white label platforms lock you into a fixed per-client cost, leaving no margin for your own pricing strategy.

Condition Four: Integration and API Stability

Your clients may expect the CRM to integrate with their existing tools: email, calendar, accounting software, or marketing automation. As a reseller, you cannot ask every client to integrate manually. Ask whether the platform offers an integration marketplace, and which integrations are included in your white label package. Some vendors charge per integration or limit free integrations to a tier, which adds friction to your sales process. Request their roadmap for new integrations and their SLA for integration uptime. A broken Mailbox integration could disable half your clients' workflows, and you will be the one fielding complaints.

Test the API documentation by building a small integration yourself during the trial. Request an API key, read their documentation, and try to list contacts or create a record. If the documentation is vague, outdated, or requires contacting support for clarification, integration support will consume time you did not budget for. Ask whether they have an API sandbox environment where you can test changes without affecting live client data. A vendor without a sandbox expects you to test changes in production, which is unacceptable for any integration touching client data.

Testing in a Trial: The Concrete Checklist

A good white label trial lasts at least 14 days and includes a dedicated account manager or onboarding specialist who can answer technical questions. During your trial, work through this sequence. First, set up your agency branding: upload your logo, configure your domain, and customise colours. Create a test client account and verify your branding appears throughout: login screen, emails, invoices, and reports. Take screenshots. Second, test account isolation by creating a second test client account, logging in as that client, and confirming they see no data from the first account. Third, attempt a realistic integration: connect an email inbox or import a CSV of contacts and verify the data appears only in the intended client account. Fourth, test the support process by submitting a ticket with a non-technical question (e.g., "How do I change the invoice logo?") and measure response time. Fifth, ask for a cost breakdown showing the per-client cost, any per-user fees, integration costs, and support charges if you opt for co-support.

As an illustration, imagine a five-person marketing agency that resells CRM to its own clients. They need to support three initial clients with growth to ten within a year. In a trial, they discover the platform charges £49 per client per month for unlimited users, but integrations with email and accounting software cost an additional £15 each, and first-line support requires a vendor fee of £200 per month for a support SLA. They estimate they will sell the CRM for £149 per client per month. With three clients at full integration, their margin per month would be: (£149 × 3) - (£49 × 3) - (£15 × 2 × 3) - £200 = £447 - £147 - £90 - £200 = £10 per month. That is barely a viable product for a five-person agency to maintain. If the vendor's model requires cheaper clients or higher volumes to work, the trial should reveal that early, before you commit to the partnership.

When White Label CRM Is the Wrong Choice

White label CRM is not suitable for every agency. If you have only one or two clients, or if your clients are price-sensitive and unlikely to pay £50 or more per month for a CRM, the resale economics do not work. The vendor's minimum cost per client, combined with your time to support, onboard, and maintain accounts, means you need a minimum client base to justify the effort. If your clients demand integration with obscure or proprietary software, evaluate whether the vendor's integration marketplace covers those tools before committing. A common failure point is agencies that sell white label CRM to clients, then discover their clients need an integration the platform does not offer and cannot build. You then become the liaison between your client and the vendor's product team, which is unpaid support.

If your team lacks technical support capability, or if you are unwilling to invest in training someone, do not pursue first-line support. Delegation to the vendor typically breaks the white label model. If you need to differentiate your CRM offering with custom fields, workflows, or reporting that differs by client, confirm the platform supports that level of per-client customisation. Some white label platforms force all clients into the same feature set, leaving no room for your own competitive advantage. Finally, if your business model depends on owning and controlling all client data independently of the vendor, traditional CRM licensing is likely better than white label resale. White label is a convenience play for agencies that want to offer CRM without building or licensing individual instances.

Your Next Steps: Comparing Platforms Fairly

When evaluating any white label CRM platform, use this framework consistently. Request a 14-day trial from at least two vendors. During the trial, work through every test on the checklist, and compare the results side by side. Create a spreadsheet with rows for each condition: branding coverage, account isolation, support model, billing control, integration options, and cost per client. This removes emotion from the decision and makes the trade-offs visible. For a more detailed comparison of how different platforms approach white label, compare Sysevo and Macro.com directly to see the specific differences in their models.

Before signing a contract, request the vendor's SLA documentation, support escalation procedures, and integration roadmap in writing. Clarify who is responsible for maintaining custom branding, SSL certificates, and backups. Confirm the process for adding or removing client accounts and what the lead time is for provisioning a new account. Some vendors require manual setup by a technical team, adding weeks to your sales cycle. Request references from at least two other agencies who resell the platform, and ask them about support response times and whether the economics actually worked for their business. An honest peer reference is worth more than any vendor promise.

If you are ready to explore options, review Sysevo's white label and agency partner plans, which include a built-in CRM with branching and multi-client isolation, or book a call with our team to discuss your specific agency model.

Frequently Asked Questions

Can I use the same white label CRM instance for multiple client brands, or do I need separate instances for each?

Most white label platforms use a single instance with per-client branding, so your logo and domain change when a client logs in, but the underlying infrastructure is shared. This is cheaper and simpler than separate instances. However, confirm the platform truly isolates each client's data at the database level. Some platforms share the database but use row-level security, which is adequate if tested thoroughly, but not as robust as separate instances.

What happens to my client accounts if the vendor shuts down or I want to switch platforms?

This is critical. Ask for a data export procedure in writing, and test it during your trial. Verify that you can export all client data in a standard format (CSV, JSON) without vendor permission or delay. Confirm there are no export fees or usage restrictions on exported data. If a vendor makes data export difficult or charges for it, that is a warning sign about their commitment to your independence.

How do I handle clients who want custom fields or workflows that differ from other clients?

Confirm the platform supports per-client field and workflow configuration. Some white label platforms lock you into a single schema across all clients, forcing all your resold instances to be identical. Others allow custom fields and automation at the individual account level. The latter is much more flexible and lets you serve clients with different needs without building workarounds.

Is first-line support really necessary, or can I rely on the vendor to handle everything?

Full vendor support breaks the white label model in most cases, because the vendor's team will contact your clients directly, undermining your agency's position. First-line support (your team handling initial contact) keeps your clients engaged with you. You only escalate technical problems to the vendor. This requires training someone on the platform, but it protects your relationship and brand.

What is a realistic margin on white label CRM, and how many clients do I need before it becomes profitable?

Margins depend entirely on your vendor's pricing, your resale pricing, and your support costs. If the vendor costs £50 per client and you resell for £150, your gross margin is £100 per client per month. Subtract support costs, training, and your own time. With one support person covering ten to fifteen clients and spending roughly two hours per month per client on average, the work is distributed enough to be profitable. Below ten clients, the overhead of maintaining the relationship often exceeds the margin. Calculate this for your own situation using the vendor's actual pricing before committing.

How often do I need to communicate with the vendor about platform updates and new features?

This depends on your support model, but plan for regular communication. Ask the vendor about their release schedule, feature rollout process, and whether updates affect all white label instances simultaneously or can be staged. A vendor that pushes major updates without notice to your clients will make you look unreliable. Request a changelog and a way to communicate upcoming changes to your clients in advance.

Independent buyer's guide published by Sysevo. Sysevo is not affiliated with, endorsed by, or partnered with Macro.com, and Macro.com is the trademark of its owner. Product details change often, so confirm anything that matters to your decision with the vendor directly before you buy.