Agency workspace planning

Model client cold email capacity before provisioning a workspace.

Estimate the inboxes, domains, SMTP capacity, and warmup assumptions needed for a client workspace or campaign pod.

Calculator

Model the send load.

Agency capacity should stay workspace-scoped so readiness, proof metrics, blocked exports, and alerts remain attributable to the right client.

Reset defaults

Capacity recommendation

Dedicated SMTP infrastructure

Dedicated server/IP planning for customers that need stronger infrastructure isolation.

Estimated monthly cost

$982.50

Planning estimate only.

Monthly emails

36,000

12,000 prospects x 3 touches.

Daily send requirement

1,662

Spread across 5 send days/week.

Recommended inboxes

67

25 emails/inbox/day cap.

Recommended domains

23

3 inboxes/domain by default.

Infrastructure caps

SMTP IP capacity
3
Domain daily cap
100
IP daily cap
3,000
Warmup assumption
30 days

Per-IP utilization should stay below 80 percent before adding traffic. Scale horizontally with more IPs or domains before raising inbox caps.

Cost assumptions

Dedicated SMTP infrastructure platform planning baseline$249
67 inboxes$402
23 managed domains$34.50
3 SMTP IP capacity units$297

Domain registration, taxes, discounts, support tiers, and real Microsoft/Google reseller SKUs can change the final quote.

Readiness notes

  • Treat this as a planning estimate, not a quote or deliverability guarantee.
  • Readiness gates, seed-placement evidence, and fresh SMTP/IMAP smoke tests still decide exportability.
  • Dedicated SMTP IP capacity should be reserved before raising inbox caps.

Common questions

Should each client get a separate workspace?

For operational clarity, yes. Workspace-scoped readiness and proof reports make it easier to isolate domains, inboxes, alerts, and exportability by client.

Can this estimate be shared with a client as a final quote?

No. It is a planning estimate. Final pricing can change with package terms, support needs, domain registration, provider costs, and operational requirements.