workflow
White-label (per-client)
Rendering an artifact in a client's branding so the agency's own brand stays invisible unless the client wants it visible.
What it is#
White-labeling in agency reporting means the rendered brief carries the client's brand identity, not the agency's. The client's logo, typography, color palette, and ideally their domain — not the agency's.
For a marketing agency serving 30 clients, this means 30 different visual treatments for the same template. The agency's brand lives in the audit log and the email signature; the deliverable belongs to the client.
Why it matters#
Three reasons agencies care about this:
- Client politics. When a brief gets forwarded internally at the client's company, it should look like their deliverable to the executive team — not like a third-party marketing report. The agency name on the cover undermines that.
- Reseller positioning. Some agencies operate as fractional CMO / fractional ops shops where the entire pitch is "we're an extension of your team." A visible third-party brand contradicts the value prop.
- Discretion. Many clients work with multiple agencies; explicit agency branding can create awkward conversations about "why are you using THEM, I thought you were using US?"
What good white-labeling looks like#
- Per-client brand kit: logo (light/dark), typography stack, color palette, header style
- Custom subdomain per client (
briefs.theirdomain.comvia DNS) - Email-sender display name matching the client's brand
- ICS calendar invites that don't say "SendBriefs"
- Audit log retains agency identity for legal/operational reasons but isn't visible to the end-reader by default
In SendBriefs specifically#
Per-client white-label is included on every paid plan. Custom subdomains require DNS setup during onboarding (we'll walk you through it).
See White-label (per-client) in the product →
See branding featuresRelated terms
Connected ideas.
See White-label (per-client) in action.