Infrastructure inventory
Every domain, inbox, DNS record, tracking domain and platform connection in one place.
Outbound infrastructure
Build the sending foundations before increasing the volume.
Cold outbound belongs on dedicated domains and inboxes, authenticated, warmed within provider limits and monitored, so the corporate domain is never exposed to it. We run our own outbound estate this way and build the same for clients, with everything owned by you and written down.
- What is outbound infrastructure?
- Outbound infrastructure is the set of domains, mailboxes, DNS records, sending platforms, tracking domains, reply routes, suppression lists and operating rules that cold email runs on. Done properly it is documented, owned by the client, kept inside the sending providers’ limits and terms, and separated from the corporate domain so that ordinary business email is not affected by prospecting volume.
The problem
The corporate domain should never carry cold volume.
When sequences share a domain with invoices, proposals, HR and customer support, every complaint and every filter decision lands on the same reputation. A bad month for prospecting becomes a bad month for everything. Microsoft 365 and Google Workspace both say plainly that bulk email is not what standard mailboxes are for, and both apply recipient limits and restrictions that will catch a rep long before they hit a sensible volume.
The answer is not a loophole. It is operational separation: dedicated outreach domains and inboxes with their own authentication, limits and monitoring, run within the rules, so the risk is contained and visible. Separation reduces the exposure of the main brand. It does not make outreach risk-free, and we will not describe it that way.
Two ways to buy
- Built for your team: set up, tested, documented and handed over with training, then run by you
- Run by Neotiqa: the same setup operated as part of managed outreach
Architecture
What separation looks like.
One side protected and monitored, the other built for the traffic it carries. Replies flow back to the people who own the conversation.
Corporate domain: yourcompany.com
Ordinary business email, customer conversations, invoices, HR, security notices. Reputation protected by keeping cold volume off it.
- SPF, DKIM, DMARC at enforcement
- Sequencer sends only for one-to-one replies, if at all
- Monitored through DMARC reports
Dedicated outreach domains: yourcompany-team.com and similar
Cold outbound runs here, on inboxes bought for the purpose, warmed and ramped within provider limits, with replies routed back to the people who own the conversation.
- Own authentication, tracking domain and monitoring
- Sending limits and ramp rules per inbox
- Owned by you, documented, rotated by policy
Corporate domain kept for business email; dedicated domains carry cold outbound, within provider limits.Illustrative
Scope
What a proper setup includes
Every item below is agreed in the written scope, built to a specification, and recorded in the handover pack.
Domains and identity
- Domain architecture and sensible naming that a recipient can recognise as yours, not deceptive lookalikes
- Authorised domain and mailbox procurement in your name, with the registrar and provider accounts owned by you
- Provider selection checked against acceptable-use rules, sending limits and the markets you sell into
- Sender identity, display names and signatures that hold up when a recipient looks you up
Authentication and DNS
- SPF with the lookup count kept in check, DKIM signing per platform, and DMARC with reporting turned on
- Custom tracking domains per outreach domain, so links are not shared with strangers
- Reverse DNS and TLS where the sending route allows it
- A record of every DNS entry, what it is for and who can change it
Mailboxes and security
- Mailbox security, access control and multi-factor authentication on every account
- Sales-engagement connections set up with the limits the platform and provider allow
- Reply routing and forwarding so interested replies reach a person quickly
- Suppression handling that stops opted-out and bounced addresses re-entering sequences
Sending rules and monitoring
- Sending schedules, per-inbox limits and a controlled ramp-up plan, with warm-up treated as a readiness process rather than a fixed calendar
- Recipient-environment matching, so Microsoft-hosted and Google-hosted prospects are sent from the side that reaches them
- Monitoring of bounces, blocklists, DMARC reports and placement, with a rotation policy for domains and inboxes that are no longer healthy
- Launch checks before the first real send, and operating instructions for the people who will run it
Readiness
Warm-up without the folklore.
New domains and inboxes need time and a gradual ramp before they carry real volume. How much depends on the provider, the recipient mix, the content and the evidence from the first sends. We treat warm-up as a readiness process with checks, not as a promise that a fixed number of days makes every inbox safe.
We do not market manufactured engagement, purchased reputation, disposable identities or constant domain replacement as a strategy. Those approaches trade a short-term lift for a longer-term problem, and they put the people running the campaign on the wrong side of provider terms.
Ownership and handover
- Domains, inboxes, tools and data are held in your accounts, not ours
- An access and ownership register lists every asset and who controls it
- The handover pack lets your team, or another provider, run the setup without us
Deliverables
What you receive
Concrete, written and yours to keep.
Configuration record
What was configured, why, and the values used, so changes can be reviewed later.
Access and ownership register
Who owns and who can change each asset, with credentials handled through your own password management.
Approved sending plan
Limits, schedules, ramp rules and the recipient-environment split, agreed before launch.
Reply and suppression workflow
Where replies go, who answers them, and how opt-outs and bounces are kept out of future sends.
Launch checks and operating instructions
A checklist for the first send and plain instructions for running and monitoring the setup.
Options
Three ways to engage.
Each option is quoted after scoping. No arbitrary domain counts or daily volumes are promised; the plan is built around your team, your market and the providers’ limits.
| Option | What it includes | Best for |
|---|---|---|
| Setup only | Design, procurement in your name, configuration, authentication, launch checks and the handover pack. | Teams with an operator who will run and monitor the setup themselves. |
| Setup with handover and training | Everything in setup only, plus working sessions with the people who will run it, a sending standard for the team and a follow-up review after the first weeks of sending. | Teams that want to own outbound but have not run dedicated infrastructure before. |
| Setup with ongoing management | The same setup, operated and monitored by Neotiqa as part of a managed outreach programme, with an agreed reporting cadence. | Teams that want outbound run for them and would rather deal only with interested replies. |
Boundaries we keep
- We do not present Microsoft 365 or Google Workspace as suitable for unrestricted bulk prospecting. Both providers prohibit unsolicited bulk email from standard mailboxes, and the setup respects that.
- We do not promise inbox placement, sending volumes or that separation makes the corporate domain immune.
- We do not recommend weakening security controls or blanket allowlisting to get mail through.
- Who may lawfully be emailed, and on what basis, is scoped with you. Recipient type, jurisdiction, transparency and opt-outs are part of the plan, not an afterthought.
Questions about outbound infrastructure
Do we always need dedicated domains for outreach?
For cold, sequenced email at any real volume, yes. For one-to-one follow-up with people who know you, the corporate domain is usually the right place. The scoping conversation looks at what you send, to whom and how often, and says which traffic belongs where.
How many domains and inboxes will we need?
It depends on your volume, your market and the providers’ limits, so we do not publish a formula. The sending plan sets the number, the per-inbox limits and the ramp, and it is reviewed against the evidence once sending starts.
Which sequencer do you set up?
Yours, if you already have one that supports what the plan needs. Otherwise we scope one with you. We have built on the common sales-engagement and outbound platforms, and we check each platform’s limits, tracking and unsubscribe handling before recommending it.
Who owns the domains and accounts afterwards?
You do, from the start. Registrar, provider and tool accounts are opened in your name, and the ownership register records who controls each one. There is no lock-in, and the handover pack lets another provider take over if you choose.
How long before we can send at volume?
New inboxes need a gradual ramp, and the length depends on the provider, the recipient mix and what the early sends show. We give you a plan with checkpoints rather than a promise that a fixed number of days makes every inbox safe.
Can you fix an existing setup instead of building a new one?
Often, yes. That usually starts with a short review of what is there, using the same evidence-led approach as a deliverability assessment, followed by a specification for what to change, retire or add.
Last reviewed September 2026. Service descriptions are general; every engagement has a written scope.
Planning to scale outbound, or cleaning up a setup that grew by accident?
Tell us what you send, from where, and what you want the setup to do. We reply within two working days with the questions we need to scope it.