Agency operating model

Build client cold email infrastructure around readiness proof, not spreadsheet promises.

Agencies need repeatable infrastructure that separates clients, catches broken DNS or mailbox auth early, and proves when inboxes are ready to export.

Start with workspace isolation

A cold email agency should not manage every client from one shared operational bucket. GTM Inboxes models client work through organization-scoped workspaces so domains, inboxes, alerts, readiness reports, and proof metrics stay attributable to the right account.

  • Create one workspace per client or operating unit.
  • Keep domain and inbox inventory tied to that workspace.
  • Use readiness reports as the redacted customer-shareable status artifact.

Plan capacity before provisioning

Capacity planning should happen before domains and mailboxes are created. The inbox and domain calculators translate prospect volume, touches, send days, and conservative risk profiles into a starting plan. That plan is not launch approval; it only prevents obvious under-sizing.

  • Estimate inboxes and domains from real campaign volume.
  • Avoid overloading a small domain pool just because mailboxes are available.
  • Revisit assumptions when a client changes cadence or sequence length.

Gate exports on readiness

Sequencer exports should fail closed for inboxes that are not ready. GTM's workflow separates ready inboxes from blocked rows with redacted reasons, so an operator can fix DNS, SMTP, IMAP, or launch-gate issues without exposing secrets or raw upstream errors.

  • Require SMTP and IMAP readiness before export.
  • Require fresh seed-placement evidence before first prospect traffic.
  • Return redacted blocked-row reasons instead of provider secrets or raw payloads.

Common questions

Can an agency use the same readiness report for multiple clients?

No. Readiness is workspace-specific because domains, inboxes, alerts, seed-placement evidence, and proof metrics belong to one operating context.

Does capacity planning prove deliverability?

No. Capacity planning estimates infrastructure needs. Deliverability and inbox placement still depend on authentication, reputation, targeting, content, suppression policy, and seed-placement evidence.