From WFW to Your Brand in 24 Hours

When a new partner signs with Workforce Wave, the first question is almost always: "How long until our clients see our logo?"

The answer is 24 hours — often less. Here's the full picture of how that works, what moves during the deployment, and what partners are actually responsible for.

The Deployment Model in Plain English

Workforce Wave's white-label system is not a theme switcher bolted onto a shared app. Each partner gets their own Vercel deployment — a fully isolated front end that points at the same underlying API infrastructure but presents entirely under the partner's brand.

The separation is clean by design. Partners own the experience their clients see. WFW owns the infrastructure beneath it.

The key that makes it work is a single environment variable: PARTNER_SLUG.

# Vercel project settings for "Meridian Staffing"
PARTNER_SLUG=meridian-staffing

When the Next.js app boots, it reads PARTNERSLUG and fetches the partner's full configuration from partnersite_configs. Every color, logo URL, product name, pricing display preference, and VIL template set is loaded at startup and applied globally. The same codebase powers every partner's deployment — the slug is the only thing that changes.

What Lives in partnersiteconfigs

The partnersiteconfigs table is the source of truth for everything a partner can control. A typical record looks like this:

{
  "partner_slug": "meridian-staffing",
  "brand": {
    "logo_url": "https://cdn.meridian.com/logo.svg",
    "primary_color": "#1A4C8B",
    "accent_color": "#F5A623",
    "font_family": "Inter",
    "product_name": "Meridian AI",
    "tagline": "Your workforce, always available"
  },
  "domain": "ai.meridianstaffing.com",
  "vil_template_set": "staffing_v2",
  "pricing_display": {
    "show_pricing": true,
    "tier_labels": ["Starter", "Growth", "Enterprise"],
    "currency": "USD"
  },
  "feature_flags": {
    "show_compliance_profile": true,
    "allow_brand_voice_editing": true,
    "enable_fleet_view": true
  }
}

Partners configure this through the WFW admin panel. Changes propagate on the next deployment — typically under a minute via Vercel's build pipeline.

The Custom Domain Step

Pointing a custom domain at a partner's Vercel deployment is a 15-minute operation, not a 15-day one.

Partner adds a CNAME record in their DNS: ai.theirbrand.com → cname.vercel-dns.com
WFW adds the domain in Vercel project settings
Vercel issues a TLS cert automatically via Let's Encrypt
The deployment updates partnersiteconfigs.domain

Once the CNAME propagates, clients visiting ai.theirbrand.com see the partner's brand with no Workforce Wave branding anywhere in the UI.

The 24-hour timeline is mostly DNS TTL. The actual setup takes less than an hour.

What Partners Control

Partners have full control over the experience layer:

Brand identity — logo, colors, fonts, product name, tagline, favicon
VIL template selection — which Vertical Intelligence Library templates are available to their clients, and which are the defaults for each industry vertical
Pricing display — whether pricing is shown, tier labels, any custom packaging names
Feature visibility — which admin features are surfaced to their clients (fleet view, brand voice editor, compliance profile, etc.)
Onboarding copy — the welcome emails and in-app onboarding messages clients see when they first provision an agent

What they don't control — and shouldn't need to — is everything below the experience layer.

What WFW Manages

Compliance rules, API infrastructure, and the Workforce Wave provisioning pipeline are WFW-managed and are not configurable by partners. This is intentional.

Compliance rules — HIPAA guardrails, TCPA time windows, Fair Housing phrase filters, PCI masking — are determined by vertical and jurisdiction, not by partner preference. A partner cannot disable HIPAA guardrails for a healthcare client even if they wanted to. The rules run at the infrastructure layer before any tool call is executed.

API infrastructure — the ElevenLabs integration, phone number provisioning, Twilio subaccounts, KB sync jobs — all run on WFW infrastructure regardless of which partner's branding is in the UI.

Workforce Wave provisioning — when a partner's client provisions an agent, the 5-step Workforce Wave pipeline runs identically to how it would on the WFW-branded platform. Partners can select which VIL template set Workforce Wave uses, but they don't control the crawl logic, LLM call chain, or prompt construction.

This split matters for partners. It means they can go to market immediately with a polished product without building compliance infrastructure, maintaining LLM integrations, or managing phone carrier relationships. They're building a business on top of the platform, not rebuilding the platform.

The Deployment Checklist

Here's what actually happens during a partner onboarding:

WFW creates the Vercel project, forks the environment, and sets PARTNER_SLUG
Partner uploads brand assets and fills out the configuration form in the WFW admin panel
WFW pushes the initial partnersiteconfigs record
Partner configures DNS; WFW adds the custom domain in Vercel
First test deployment — partner reviews the live URL, confirms brand rendering
Partner's Twilio subaccount is provisioned (phone number pool ready)
Partner runs a test agent provisioning — one real client URL through Workforce Wave
Sign-off; partner goes live

Steps 1–5 typically complete in a few hours. Steps 6–8 add another few hours, mostly waiting on DNS and making any final brand tweaks.

Total time from "signed contract" to "live with first client" is reliably under 24 hours for partners who come prepared with brand assets.

Why Isolation Matters

Every partner deployment being isolated means a configuration change for one partner cannot affect any other. A bad partnersiteconfigs write doesn't propagate platform-wide — it affects exactly one deployment and is trivially rolled back.

It also means partners can test changes in a staging environment before pushing to their clients. Each partner has a _staging slug variant that points at the same backend but with a separate Vercel deployment. Partners use this to preview UI changes, new VIL template sets, or onboarding copy before their clients see it.

The 24-hour number isn't a marketing claim — it's an operational one. The system is designed so that setup is configuration, not construction.

Next in this series: Vertical Intelligence: Give Your Agents Domain Expertise — how VIL docs become agent system prompts, and why 150-line prompts outperform 20-line ones in complex service industries.