A Client Portal That Looks Like Your Agency, Not Ours
White-Label Client Portal is part of HubWho. When a client logs in to pay you, the page they land on is part of your brand — or it's a reminder that you're reselling someone else's software. HubWho is built so every client gets a portal on your agency's own domain, with your logo, your colors, and your support email, where they sign in with a magic link, see their invoices, pay by bank or card, and manage their payment methods. No HubWho logo, no separate vendor login. HubWho is pre-launch — currently being built with a small founding cohort of agencies through early access, so this describes the white-label client portal the founding cohort is shaping, not a generally available product.
The problem: your client login gives away the game
You position yourself as the marketing partner running a client's growth. Then billing time comes and you send them to a login screen branded with some other company's name — or a generic invoice tool that has nothing to do with your agency. The whole illusion that you're one seamless team breaks the moment they have to pay you.
Most agencies end up choosing between two bad options. Either they stitch payments onto a third-party portal that puts a vendor's brand in front of their client, or they email PDF invoices and chase payment by hand because there's no client-facing place to send people at all. Neither makes the agency look like the established, buttoned-up operation it's trying to be.
The cost isn't just aesthetic. A client who logs in to an unfamiliar, off-brand system is a client who's slightly less sure who they're paying and slightly more likely to question the relationship at renewal. Every touchpoint that doesn't look like you is a small crack in the partnership you're charging a retainer for.
- Clients pay you through a login branded with a vendor's name instead of yours
- The only on-brand alternative is emailing PDFs and chasing payment by hand
- No single client-facing place to send people for invoices, statements, and payment methods
- An off-brand portal quietly undercuts the premium-partner positioning your retainer depends on
- Routine 'how do I pay' and 'where's my invoice' questions land back in your inbox because there's nowhere to point clients
- The more clients you add, the more these off-brand touchpoints multiply
How the white-label portal works
HubWho is built so the portal runs on your agency's own domain. You point a subdomain — billing.youragency.com, portal.youragency.com, whatever you choose — at HubWho with a CNAME record, and HubWho is designed to resolve that hostname to your agency and serve your client's portal from it. The intent is that the address bar shows your domain, not ours, so as far as the client is concerned they're logging in to your agency.
The look matches. HubWho carries your agency's brand name, logo, primary color, and support email through the portal and the emails it sends, so a client sees your mark on the login screen, on their invoices, and on the receipts and reminders that go out. There's no HubWho badge in front of your client — the platform is designed to stay invisible behind your brand.
Sign-in is passwordless by design. A client enters their email and HubWho emails them a magic link; clicking it drops them straight into their portal, with no password to set, forget, or reset. The link requests are rate-limited and the flow is built not to reveal whether a given email is on file, so the convenience doesn't come at the cost of leaking who your clients are.
- Built to run on your own domain via a CNAME — the goal is that the client never sees a hubwho.com address
- Your brand name, logo, and primary color carried through the portal and its emails
- Your support email on the sign-in and notifications, so replies come back to your agency
- Magic-link sign-in — clients log in from an emailed link, with no password to manage
- Sign-in requests rate-limited and built not to leak which emails are on file
- Multi-location clients can land on a locations command-center; a single-location client lands on their own dashboard
What's included
Once a client is in, the portal is built to be the one place they handle the money side of working with you. Their dashboard surfaces open invoices with a live pay link, paid history, their autopay status, and a KPI snapshot, with dedicated pages for invoices, a running statement (downloadable as a PDF), and their payment methods. They can link a business bank account through Plaid, add a card, and set which method is the default — so the routine 'how do I update my card' email is designed never to reach you.
You can also brand the emails clients receive. HubWho is built with an email-template editor for your invoice and dunning (past-due) emails, so the messages that go out match your agency's voice and look rather than a generic system default. Automated past-due dunning is on HubWho's roadmap rather than a shipped, running sequence today — but the template editor lets founding agencies shape that copy now. The editor covers invoice and dunning emails; it does not template quote or proposal emails.
Because HubWho is pre-launch and being built with a small founding cohort, the way your portal looks and behaves — branding, domain, which surfaces clients see, how the emails read — is exactly the kind of thing founding agencies help shape before public launch. Agencies can also preview the portal as a client sees it in a read-only mode, so you can check the experience before sending a client in. Availability is early-access by request; the public contact is info@roffik.com.
- Client dashboard — open invoices with a live pay link, paid history, autopay status, and a KPI snapshot
- Invoices, a downloadable PDF statement, and a self-service payment-methods page in one branded place
- Plaid bank-link, card, and default-method management so clients handle payment setup themselves
- Editable invoice and dunning email templates in your agency's brand (automated dunning sends are on the roadmap, not running today)
- Read-only 'view as the client sees it' preview so you can check the portal before sending anyone in
- Early-access by request — the founding cohort helps shape branding, domain, and portal surfaces before public launch
Frequently asked questions
Does the portal run on my own domain or a HubWho URL?
It's built to run on your own domain. You add a CNAME record pointing a subdomain like portal.youragency.com at HubWho, and HubWho is designed to resolve that hostname to your agency and serve your client's portal from it — so the client sees your domain, your logo, and your colors rather than a hubwho.com address. HubWho is pre-launch and being built with a founding cohort, so this is the white-label experience that cohort is shaping.
How do clients sign in?
Passwordless, by magic link. A client enters their email and HubWho emails them a link that drops them straight into their portal — no password to set or reset. Sign-in requests are rate-limited and the flow is built not to reveal whether a given email is on file, so it stays convenient without leaking who your clients are.
Can I brand the emails clients receive, and does that include automated past-due reminders?
You can edit the invoice and dunning (past-due) email templates so they match your agency's voice and look — that editor covers invoice and dunning emails only, not quote or proposal emails. Automated past-due dunning sends are on HubWho's roadmap rather than a running sequence today, but founding agencies can shape that copy now. For early access, contact info@roffik.com.