Outreach Sending Deliverability
A reply rate of zero is almost always read as a pitch problem, so the team rewrites the email repeatedly while nothing is reaching an inbox. Sending cold outreach at volume from the primary company domain is worse than ineffective: once its reputation is damaged, invoices, password resets and sales replies start landing in spam and take months to recover. This is infrastructure work and it has to be done before the first campaign, not diagnosed after the third.
CATEGORY
Links & authority
FORMAT
outreach-sending-deliverability.md
WHEN TO REACH FOR THIS
Use when an outreach campaign is about to send, or when reply rates are near zero and the team has started rewriting the pitch.
The skill file
outreach-sending-deliverability.md
---
name: outreach-sending-deliverability
description: Use when an outreach campaign is about to send, or when reply rates are near zero and the team has started rewriting the pitch.
---
# Outreach Sending Deliverability
A reply rate of zero is almost always read as a pitch problem, so the team rewrites the email repeatedly while nothing is reaching an inbox. Sending cold outreach at volume from the primary company domain is worse than ineffective: once its reputation is damaged, invoices, password resets and sales replies start landing in spam and take months to recover. This is infrastructure work and it has to be done before the first campaign, not diagnosed after the third.
## What you need first
- a separate sending domain, close to the main brand but not the main domain, registered several weeks before first use
- DNS access on that domain for SPF, DKIM and DMARC records
- a verified prospect list with the bounce rate measured before sending
- a lawful basis for contacting the list in the jurisdictions it covers
## Method
1. Register a separate sending domain and never send cold outreach from the primary. The primary carries transactional and sales mail, and its reputation is the expensive thing to lose.
2. Configure SPF, DKIM and DMARC on the sending domain and confirm alignment with a test send before any campaign. Unaligned mail is dropped or foldered at the gateway and often never appears as a bounce.
3. Warm the mailboxes over several weeks at low daily volume with genuine two way replies. A domain registered on Monday sending 200 cold emails on Tuesday is the clearest spam signal available.
4. Verify the list and delete anything unverifiable. A hard bounce rate of a few percent damages sender reputation faster than anything you could write in the message.
5. Cap volume well below the provider limit per mailbox and add mailboxes rather than raising the cap, because per-mailbox behaviour is what the filters score.
6. Strip open tracking pixels and shared link redirect domains. A shared tracking domain inherits the reputation of every other sender using it, and the open rate it buys you was not going to change any decision.
7. Seed two or three of your own addresses on different providers into every send and check placement. Without that, a filtering failure and a weak pitch produce identical reporting and you will fix the wrong one.
## What this produces
A warmed, authenticated sending domain with per-mailbox caps documented and a per-campaign inbox placement figure recorded alongside reply rate.
## Where this goes wrong
- sending cold outreach from the primary domain and putting invoices and receipts at risk
- rewriting the pitch for months when the actual problem is that nothing was delivered
- sending to a bought or unverified list, where the bounce rate alone ends the domain
- treating outreach as exempt from marketing email law, when unsolicited business contact still needs a lawful basis and a working opt out in most jurisdictions
---
From the QuQi skill library - https://www.quqi.io/skills/outreach-sending-deliverability
Free to download · no account, no email
What you need first
-
a separate sending domain, close to the main brand but not the main domain, registered several weeks before first use
-
DNS access on that domain for SPF, DKIM and DMARC records
-
a verified prospect list with the bounce rate measured before sending
-
a lawful basis for contacting the list in the jurisdictions it covers
Method
-
01
Register a separate sending domain and never send cold outreach from the primary. The primary carries transactional and sales mail, and its reputation is the expensive thing to lose.
-
02
Configure SPF, DKIM and DMARC on the sending domain and confirm alignment with a test send before any campaign. Unaligned mail is dropped or foldered at the gateway and often never appears as a bounce.
-
03
Warm the mailboxes over several weeks at low daily volume with genuine two way replies. A domain registered on Monday sending 200 cold emails on Tuesday is the clearest spam signal available.
-
04
Verify the list and delete anything unverifiable. A hard bounce rate of a few percent damages sender reputation faster than anything you could write in the message.
-
05
Cap volume well below the provider limit per mailbox and add mailboxes rather than raising the cap, because per-mailbox behaviour is what the filters score.
-
06
Strip open tracking pixels and shared link redirect domains. A shared tracking domain inherits the reputation of every other sender using it, and the open rate it buys you was not going to change any decision.
-
07
Seed two or three of your own addresses on different providers into every send and check placement. Without that, a filtering failure and a weak pitch produce identical reporting and you will fix the wrong one.
What this produces
A warmed, authenticated sending domain with per-mailbox caps documented and a per-campaign inbox placement figure recorded alongside reply rate.
Where this goes wrong
-
sending cold outreach from the primary domain and putting invoices and receipts at risk
-
rewriting the pitch for months when the actual problem is that nothing was delivered
-
sending to a bought or unverified list, where the bounce rate alone ends the domain
-
treating outreach as exempt from marketing email law, when unsolicited business contact still needs a lawful basis and a working opt out in most jurisdictions
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Claude Code
Save it as ~/.claude/skills/outreach-sending-deliverability/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude
Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT
There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else
Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.
Questions about this skill
When do I look at sending setup rather than rewrite the pitch?
Before the first campaign goes out, and immediately when reply rates sit near zero. A dead campaign reads as a copy problem, so teams rewrite the email for months while nothing is reaching an inbox at all. Seeded addresses settle which it is within a day. This is infrastructure work and diagnosing it after the third campaign is the expensive order.
What do I need in hand before starting?
A separate sending domain registered several weeks before first use, DNS access on it for SPF, DKIM and DMARC, a verified list with the bounce rate measured beforehand, and a lawful basis for contacting it. Send from the primary domain instead and you put invoices, password resets and sales replies at risk, and that reputation takes months to rebuild.
What do I end up with, and which part gets used?
A warmed, authenticated sending domain with per mailbox caps documented, and an inbox placement figure recorded per campaign next to the reply rate. The placement figure is the number that changes decisions. Without it a filtering failure and a weak pitch produce identical reporting, and the team fixes whichever one it happened to guess at.
What most often ruins this, and what does it cost?
Warming too fast or not at all. A domain registered on Monday sending 200 cold emails on Tuesday is the clearest spam signal available, and a hard bounce rate of a few percent from an unverified list damages reputation faster than any wording could. Add mailboxes rather than raising the cap, because filters score per mailbox behaviour.
More in Links & authority