Skip to content
OutboundIntel
Request the audit
Back to Sending Infrastructure

Sending infrastructure specification

This page states exactly what the product is, in the detail an operator would want before buying. No positioning, just the specification.

Fleet composition

  • Starter: 2 sending domains, 100 Microsoft inboxes each, sized for 500 emails a day.
  • Growth: 5 active sending domains plus 1 warm reserve, 100 inboxes each, sized for 1,500 emails a day.
  • Scale: 14 active sending domains plus 3 warm reserves, 100 inboxes each, sized for 5,000 emails a day, on a rotation calendar we operate.

Authentication

  • Every domain is configured with SPF, DKIM, and DMARC before any inbox sends.
  • Nameservers are managed so records stay correct through replacements.

Send capacity

  • A warmed Microsoft inbox sends 3 to 5 cold emails a day. We plan on the low end.
  • One domain of 100 inboxes therefore carries roughly 300 to 500 sends a day.
  • Fresh inboxes hold a short cooldown after provisioning before they enter rotation.

Burn and replacement

  • Sending domains degrade with use. Expect 10 to 20 percent to need replacing each month.
  • When a domain is flagged, we provision a replacement, you approve the name, and sending moves across. This is included.

Rotation

  • Growth and Scale hold warm reserve domains so a swap does not drop your capacity.
  • Scale runs on a rotation calendar we operate, cycling domains to hold placement over time.

Credentials and data

  • Every inbox has a name, address, and password. We deliver them into your sequencer or as a CSV.
  • We show inbox passwords in the portal on request and record each time they are viewed.

Cancellation

  • Month to month. Cancel any time and your fleet runs to the end of the billing cycle.
  • If we cannot deliver working inboxes, you do not pay for that block.