This is a preview card so the review deck can be styled and tested before real feedback exists. The kit went into a fresh sub-account, the load sheet listed every custom value in order, and the build was finished before lunch.
White-Label Sub-Account Setup
Clients do not read your invoice for the brand. They read the login screen, the notification email and the app icon on their phone. Those are the three we get right.
What you get back
- Login domain configured on your own hostname with certificates verified in a real browser
- Dashboard, menu labels and help links reworded so no page names the underlying platform
- Notification and system emails sending from your domain, with SPF, DKIM and DMARC passing
- Mobile app branding submitted and tracked, with the realistic timeline stated up front
- Support links pointed at your desk rather than the platform's, on every surface that carries one
- A leak checklist run against a live client login, listing anything still showing through
How it runs
- 01
Map the surfaces
White-labelling is not one switch. It is a login domain, a dashboard, a set of transactional emails, an app, and a scattering of help links. We list every surface a client can reach before configuring any of them.
- 02
Domain and certificate
The login hostname is set up on your domain and then checked from outside — a certificate that resolves for you and warns for your client is worse than no white-labelling at all.
- 03
Email authentication
Rebranded notification email that lands in spam has made things worse. SPF, DKIM and DMARC are configured and verified with real test sends before we call it done.
- 04
The app
Mobile app branding runs on a submission and review cycle we do not control. We submit it, track it, and tell you the honest timeline rather than a comfortable one.
- 05
Leak check
We log in as a client would and walk the account looking for the platform's own name. Whatever is still showing goes on a written list, because some of it cannot be removed and you should know which.
What a client actually sees
Three surfaces decide whether an agency looks like the software or looks like a business: the page they log into, the emails they get at seven in the morning, and the icon on their phone. Everything else in a white-label configuration is secondary to those three.
The part that goes wrong
Rebranded email that does not authenticate. It is the most common failure and the most expensive, because the client’s notifications quietly stop arriving and nobody reports a missing email. SPF, DKIM and DMARC get verified with live sends, not assumed from a green tick in a settings panel.
What cannot be hidden
Some of the platform’s surface stays visible, and the boundary moves as the platform changes. We hand back the list rather than implying it is empty. An agency that knows where the seams are can answer a client’s question in one sentence.
Related work
Rolling this out across a batch of new accounts at once is bulk sub-account provisioning.
Reviews
Reviews of this service
These are sample entries. SubaccountKit is new, so rather than invent testimonials we are showing clearly-labelled placeholders while the deck waits for real customers. Nothing here is published as review or rating markup either — search engines see no ratings from this site until the words are real.
Placeholder copy standing in for a real review. The point being illustrated here is the follow-up ladder stopping the moment someone books, which is the thing most sequences get wrong.
A preview entry, not a customer quote. It exists so the deck renders with a realistic length of text and the shuffle animation can be judged honestly before launch.
Sample text. Deliberately four stars rather than five, so the star row is tested at more than one value and the layout is proven before real reviews arrive.
Another preview card. Real reviews will replace every entry in this file, and the same change that swaps them in also switches the review structured data on.
Questions
No. Parts of the platform's own surface cannot be rebranded, and the terms change from time to time. You get a written list of what is still visible after the work, which is more useful than a claim that nothing is.
The domain, emails and app are configured once at agency level. The per-sub-account part is the finishing: support links, menu wording and anything client-specific. That is why the price has two parts.
The submission is quick; the review is not, and it is outside anyone's control here. Plan for weeks rather than days and do not promise a client a date you were given by us or anyone else.
Related services
Next step
Get white-label work scoped this week
Send what you are trying to ship. You get a scope and a fixed number back, or an honest reason why this is not the right engagement.
No call required to buy a kit · replies within one business day