Rebrand Depth Audit Before Client Launch (Delivery)

Rebrand Depth Audit Before Client Launch (Delivery)

1. 01

   Walk every client-facing surface and log what still carries the vendor's name

   Check login screens, password reset emails, invoice PDFs, error pages, and mobile app splash screens. Most white-label tiers cover the dashboard but leave transactional email footers untouched.

2. 02

   Confirm the custom domain resolves on both apex and www with a valid certificate

   Agencies routinely launch on a subdomain of the vendor and lose the brand impression on the first client login. Test in an incognito window before announcing the URL.

3. 03

   Verify the platform's own support channel is not exposed to the client

   If a client can open a ticket directly with the underlying vendor, your retainer relationship gets bypassed. Route help links to your agency inbox instead.

4. 04

   Test the full billing path with a live card at the client's actual price point

   Run one real transaction, confirm the descriptor on the statement shows your agency name, then refund it. Statement descriptors are a common leak that surfaces only after the first invoice dispute.

5. 05

   Document which features are gated behind the vendor's higher tier before promising them

   White-label rights, custom SMTP, and API access are frequently tier-locked. Map each promised capability to the plan you actually purchased.

6. 06

   Capture a screenshot set of the branded experience for the client handoff deck

   Six to ten screens covering login, core workflow, and a sample report give the client something concrete to approve and give your team a reference for future QA.

7. 07

   Record the vendor's branding limits in the client's account file

   Note any surface you cannot rebrand, such as a required footer credit or a co-branded mobile app store listing, so no one promises full removal later.