Turn a marketing phrase into observable questions
White-label can mean a logo change, a custom hostname or a much wider collection of client-facing changes. The phrase is useful as a starting point, but it does not provide a reproducible acceptance test. Ask the vendor to show the exact plan and configuration you would buy.
Write down the surface where your brand matters and the people who see it. A client opening a request, a reviewer following a proof link and an administrator receiving an invoice can encounter different identities within the same product.
Give all eight surfaces their own row
A branded portal can still send vendor-addressed mail, keep a provider footer or use an unbranded receipt. Record each surface separately for the exact plan and add-on. An item can be unnecessary for your agency without being described as included.
The three email rows answer different questions. From is the identity a recipient sees, Reply-To is where a reply goes, and sending infrastructure is the service that delivers the message. A custom From address does not establish your own SMTP provider. None proves that an ordinary reply becomes a project comment.
- Custom domain: the actual client-facing hostname and destinations.
- Interface logo and colours: what clients see in the working screens.
- Provider attribution: remaining footers, help links and system marks.
- Email From identity: display name and address on received messages.
- Email Reply-To identity: where replies are routed.
- Email sending infrastructure: vendor delivery, your own SMTP or another configured provider.
- Billing identity: receipts, invoices and payment notices seen by clients.
- Mobile app branding: a browser-installed PWA and a native app-store app are separate scopes.
Plan boundaries can change the budget
Markup.io describes branding and a vanity domain on a different tier from its Pro review allowance. Ziflow distinguishes higher-tier white-label viewer and domain capabilities from other proofing features. Those official pages illustrate why a generic product-level checkbox is too broad.
Do not move a capability from one tier into another because a screenshot looks similar. Store the plan, billing period, source and checking date with the claim. Where the official page is ambiguous, leave the exact surface unknown.
Compare the requirement, not the white-label headline
Suppose a three-person web agency only needs its own logo and From domain for collecting copy. Content Snare documents those branding settings on Plus and above; its mail help explains replies going to the configured address. That does not establish a custom request hostname, agency-owned SMTP or reply ingestion. Those rows remain open.
For a subscription-design agency that contractually needs provider attribution removed, ManyRequests Core is a different case: the official comparison reserves Powered by removal for Scale. A custom domain alone does not satisfy that requirement. SuiteDash documents a branded PWA and explicitly says it is not a separately branded native app in the app stores. A native-app requirement would need a different answer.
Do not confuse branding with participation
A client can receive your branded email and still need a separate account to act. A magic link removes a password step but does not necessarily turn an ordinary reply into a structured work record. Branding and participation are two axes of the same buying decision.
Test a realistic client journey using a separate external identity. Follow an invitation, send a reply, open an attachment and approve a revision. Record what actually happens instead of using your administrator session as evidence of the client experience.
Make the acceptance record portable
Take notes on the exact settings and plan used during a trial. Store examples that contain no client confidential information. If a vendor change later removes a required surface, the record gives you a specific correction or renewal question rather than a dispute over the word white-label.
The result can be conditional: acceptable if the outgoing sender is confirmed, unnecessary if clients never see the vendor interface, or unsuitable if provider attribution is contractually prohibited for this engagement. A universal white-label score hides those differences.
Sources & editorial notes
Source checked: 2026-11-13. Vendor statements are not hands-on product tests. OpSift editorial method and service policies describe our own process.
- Markup.io official pricing
- Ziflow official pricing
- OpSift research method
- Content Snare branding setup
- Content Snare sending and reply destination
- ManyRequests plan comparison
- SuiteDash PWA scope

