Outbound Infrastructure Checklist (2026)

Most teams treat outbound like a tool problem.

It is not.

Outbound is infrastructure. If you do not build the foundation, you will get the same failure mode every time: you scale volume, deliverability decays, reply rates die, and you start cycling domains.

This checklist is the practical version of what we build at GTM Vector: an operating system for outbound that protects deliverability, keeps routing clean, and makes attribution real.

TL;DR: The 5 Layers (in order)

1. Domains + authentication (SPF, DKIM, DMARC)
2. Inbox + routing architecture (rotation, throttles, guardrails)
3. Data quality + list management (verification, dedupe, suppression)
4. Messaging + automation (sequencing without spam signals)
5. Tracking + attribution (UTMs, tracking domains, pipeline mapping)

If layer 1 or 2 is broken, nothing above it matters.

Layer 1: Domain and authentication infrastructure

Register and separate domains

• Never send cold email from your primary corporate domain.
• Buy 1-3 parent sending domains (or use subdomains if you already have strong domain policy).
• Create sending subdomains (example: send-01.yourdomain.com through send-10.yourdomain.com).

Rule: Your sending identity is your reputation. Protect it like production.

SPF

• SPF record exists and is valid.
• SPF includes only the services that actually send mail.
• You are not exceeding the 10 DNS lookup limit.

DKIM

• DKIM is enabled for each inbox provider.
• DKIM passes alignment (the signing domain matches your From domain policy).

DMARC

• DMARC record exists and uses alignment.
• Start with p=none for monitoring, then move to quarantine or reject when stable.

Optional, but recommended

• Dedicated tracking domain (separate from sending domain), configured for your link tracking.
• Postmaster tooling (Gmail Postmaster if volume qualifies).

Layer 2: Inbox inventory and routing architecture

Inbox inventory

• You have enough inboxes for your daily volume.

Rule of thumb: 100-150 emails/day per inbox is the ceiling if you want stability.

Ramp schedules

• New inboxes warm gradually.
• New domains warm for 15-30 days before production.
• No sudden volume spikes (this is one of the fastest ways to trigger filtering).

Rotation

• Send volume is distributed across domains + inboxes.
• Rotation is deliberate, not accidental.

Guardrails (non-negotiable)

• Auto-pause rules exist for high bounce rate.
• Auto-pause rules exist for spam complaint signals.
• Suppression lists are enforced globally.

Layer 3: Data quality, list management, and suppression

Verification

• Every list is verified before sending.
• Role accounts are filtered (example: info@, sales@, support@) unless explicitly tested.

Dedupe

• Dedupe by email address.
• Dedupe by account (avoid hitting multiple people at the same company simultaneously when a conversation is already active).

Suppression

• Hard bounces are suppressed permanently.
• Spam complaints are suppressed immediately.
• Unsubscribes are honored instantly.

List decay policy

• Lists are refreshed regularly.
• Old lists are treated as higher risk.

Layer 4: Messaging and automation (without burning deliverability)

Messaging is not just conversion. It is also a deliverability signal.

• Sequences avoid repetitive, identical copy.
• CTAs are specific (not vague “let’s chat”).
• Personalization is based on real signals (not fake tokens).
• You track negative signals (spam complaints, low engagement, high bounces) and adapt.

Layer 5: Tracking, attribution, and measurement

Tracking domains + links

• Tracking links use a dedicated tracking domain.
• You do not rely on default vendor short links if you care about attribution and control.

UTM standards

• Every outbound campaign uses UTMs.
• Naming conventions are consistent.

Example:

• utm_source=outbound
• utm_medium=email
• utm_campaign=2026q1-icp1-signal1

Outcome tracking

• Replies are logged by campaign.
• Meetings booked are attributed to campaign + lead.
• Pipeline is attributed (optional but ideal).

Daily, weekly, and monthly operating model

Daily (5 minutes)

• Check bounce rate per sending domain.
• Spot-check inbox placement.
• Ensure suppression lists are being enforced.

Weekly (30 minutes)

• Verify SPF/DKIM/DMARC still pass.
• Review reply rate by campaign.
• Pause or adjust campaigns that generate negative signals.

Monthly (60 minutes)

• Run inbox placement tests.
• Rotate in fresh domains/inboxes if scaling.
• Audit routing rules and dedupe logic.

Common failure modes (and how to avoid them)

1. Scaling volume before infrastructure - fixed by ramp schedules and rotation.
2. Bad data - fixed by verification and suppression.
3. No guardrails - fixed by auto-pause rules.
4. Attribution vibes - fixed by UTMs and outcome tracking.

Next steps

If you want to go deeper:

• Start with Cold email deliverability
• Learn how we build the foundation in Outbound infrastructure
• If you are choosing tools, use comparisons in /compare

Or, if you want the fastest path to stability, book a strategy call and we will map the shortest route from your current stack to a clean operating model.