Isolated sending infrastructure
Cold email infrastructure
Outbound never runs from your main domain. It runs from a subdomain built for it.
The first rule is isolation. Your invoices, your support replies and your payroll notices leave from your main domain, and nothing about outbound should be able to touch them.
So we set up a separate subdomain with its own 5 to 10 mailboxes, its own DNS records and its own reputation. If a campaign goes wrong, the damage stays on the subdomain. The mailboxes are function mailboxes, named for a role the company has, never an invented person.
Each mailbox is warmed, capped and monitored on its own. Together a full set sends 300 to 600 messages a day, and the total is the sum of individual caps, never a number we pick.
This is the layer that most cold email skips, and it is the reason most cold email lands in spam. In outbound engineering it is the third stage, and the one the other six depend on.
Questions
How many mailboxes does a program need?
It is sized from the profile: how many companies fit it and how many conversations a month you want. A set of 5 to 10 mailboxes covers most first programs, and the number is on the plan before the first send.
Who owns the subdomain?
You do. It is created under your domain, the mailbox subscriptions are in your name, and on the way out it is handed over with its records and readings.
This page is part of outbound engineering, the practice of running B2B outbound as a measured system.
Bring your ideal customer profile. Leave with a plan for the first eight weeks.
Three screens, then thirty minutes with the person who builds the system. If outbound is not worth running for you, you hear that too.
Get your planAlready running outbound? Say so and we start from your deliverability numbers.