Client onboarding

Onboard a client from signed contract to sequencer-ready inboxes in one workflow.

Client onboarding is a fixed sequence: isolate the workspace, take in or buy domains, pass DNS and readiness checks, prove it with a shareable report, then hand off to the sequencer.

Isolate first, provision second

Create the client workspace before any infrastructure exists. Workspace scoping is what later makes readiness reports, alerts, exports, and proof metrics client-specific, and what makes offboarding a clean handover instead of an untangling exercise.

  • Create the workspace and confirm operator access roles.
  • Record which client contacts may receive readiness reports.
  • Keep API keys scoped to the permissions the handoff actually needs.

Plan, buy, and verify domains

Run the capacity calculators against the client's real campaign volume to size domains and inboxes, then buy or import the domains and verify DNS. Imported client domains deserve extra scrutiny: age, prior use, and existing records all affect the plan.

  • Size from prospect volume, touches, and send days, not from a package default.
  • Check every domain with the DNS and domain checkers before provisioning inboxes.
  • Stagger provisioning so readiness issues surface on a small batch first.

Prove readiness, then hand off

Onboarding ends with evidence, not with mailbox creation. Run readiness checks, resolve blockers, complete seed placement for the launch gate, and share the redacted readiness report with the client. The sequencer export is the last step, after the workspace can prove it is ready.

Common questions

How long does client onboarding take end to end?

It depends on domain age strategy, DNS propagation, and how quickly readiness blockers are cleared. The workflow is evidence-driven rather than calendar-driven, so each step completes when its check passes.

What does the client see during onboarding?

The readiness report: workspace-scoped, redacted, customer-safe status for domains, inboxes, launch gates, and seed placement. Credentials, raw provider payloads, and internal operator notes are never part of it.