The standard agency playbook for cold outreach goes like this: buy 30 domains, warm them up, run 200 sends per day per domain, rotate when deliverability drops, repeat. Domains are cheap. Volume is the strategy.
It is a coherent strategy if you believe that outbound is a numbers game. We do not believe that. But even if you did, the economics of this approach are worse than they look.
What domain burning actually costs
A domain costs $12–$18 to register. That is not the cost of a burned domain.
When a domain ends up on a major blocklist — Spamhaus, Barracuda, SURBL — the damage extends in two directions.
First: the domain itself is dead for outbound. Every email sent from it either bounces or goes to spam. You stop using it. Net cost: registration fee plus setup time plus whatever warm-up infrastructure you were running against it. Call it $50–$80 per domain including tooling allocation.
Second, and more expensive: if the burned domain shares a root domain, IP range, or sending infrastructure with your primary domain, you have a bleed problem. Google's spam filters and Microsoft's Exchange Online Protection share signals across their customer base. A domain burning consistently from your IP subnet will drag your primary domain's sender reputation down, even if you were careful to keep them separate.
We have seen this happen. An operator running three "experimental" burner domains from the same IP allocation as their primary outbound domain watched their primary domain's inbox placement rate drop from ~94% to ~61% in five weeks. Recovering domain reputation at that level takes 8–12 weeks of reduced-volume, high-engagement sending. The cost is not the $50 domain. It is the 8 weeks of degraded pipeline.
How the blocklist ecosystem works
Most operators treat blocklists as binary: you are on them or you are not. The reality is more nuanced and more punishing.
There are roughly four tiers of blocklist consequence.
The first tier is the major enterprise blocklists — Spamhaus, SURBL, Barracuda Reputation Block List. A listing here means your emails will be rejected or dropped at the MX server for most business email systems. This is the one everyone knows about.
The second tier is reputation scoring services — Microsoft SNDS, Google Postmaster Tools, Cisco Talos. These are not blocklists in the traditional sense. They score sender reputation continuously. A poor score does not bounce your email; it deprioritizes it. Your email arrives in the inbox three days later, or goes to the "Other" tab, or goes to spam without a bounce record. You cannot see the failure.
The third tier is URL blocklists. If you link to a domain in your email body — your product URL, your calendar link, your landing page — and that domain is on a URL blocklist, your email can be filtered even if your sending domain is perfectly clean. This affects operators who use shared link-shorteners or generic scheduling tools.
The fourth tier is the adaptive filters inside individual mail clients. Gmail's priority inbox, Outlook's Focused Inbox, Apple Mail's privacy-protected open rate suppression — these are machine-learning systems that score each message against each recipient's engagement history. No blocklist manages this. Only message quality does.
The agency model's actual failure rate
We spoke with 14 operators who had previously used outbound agencies before building with Paitho. Eleven of the 14 had experienced at least one domain-burning event. Nine of the 11 had not connected that event to a corresponding drop in their primary domain's performance.
That is not because they were inattentive. It is because the timeline between domain burning and primary-domain degradation is not immediate. It can be four to eight weeks. By the time the inbox placement data shows a drop, the operator has moved on to the next campaign and no longer connects the cause.
The agencies generally do not flag this. Their contract covers the campaign period. Domain reputation damage that manifests six weeks post-campaign is not their problem.
One operator we spoke with had been running agency outbound for 14 months. They switched to Paitho in part because their primary domain — the one on their website, their product emails, their investor updates — was sitting at an estimated ~41% inbox placement . It had been degrading for six months. Recovery took nine weeks of conservative sending.
What our infrastructure model looks like instead
Paitho is dual-brand SMTP by design. The pipeline sends from your domains, with your credentials, at throttles you set. We do not own the infrastructure. You do.
A damaged domain is an asset you no longer have.
This matters for two reasons.
One: we cannot burn your domain. We do not hold the keys. You see every send, every recipient, every throttle setting. If the volume is wrong, you change it.
Two: the research layer means lower volume is sufficient. The Manifesto is direct on this. If an email is written from a specific pain signal and reviewed by a human before it goes out, you do not need 200 sends a day to get meetings. An operator running 40 high-quality sends per day from a well-maintained domain will outperform an operator running 200 merge-field sends per day — on meetings booked, on reply quality, and on domain health over any 90-day window.
This is not a claim about our product. It is a claim about the math of deliverability. A domain sending at 40/day with a 14% reply rate is delivering 5.6 positive replies per day. A domain sending at 200/day at 3% reply rate is delivering 6 replies per day, and is accumulating the spam signals that will put it at 1.8 replies per day in six weeks.
The volume arithmetic
Here is the math laid out plainly.
Illustrative figures based on operator data and published deliverability research. Treat as directional.
| Approach | Sends/day | Reply rate | Replies/day | Domain health at 90 days |
|---|---|---|---|---|
| Volume (merge-field) | 200 | 3.1% | 6.2 | Degraded — inbox placement drops to ~55% by week 8 |
| Research-first | 40 | 14.8% | 5.9 | Stable — inbox placement holds at 90%+ |
At 90 days, the volume approach has produced approximately 558 replies and a damaged domain. The research-first approach has produced approximately 531 replies and an intact domain. At day 91, the volume approach is declining. The research-first approach is not.
The reply counts are nearly identical through day 90. The domain situation is not.
What to do if your domain is already damaged
Check it first. Google Postmaster Tools and Microsoft SNDS are free. Spamhaus has a free lookup. Run your primary sending domain through all three before assuming your deliverability is fine.
If you are already listed on Spamhaus or Barracuda, the delisting process is manual and takes 1–3 weeks. Spamhaus has a documented delisting request process; it requires demonstrating that the sending practices have changed.
If you are not listed but your inbox placement is below 80%, the recovery path is: reduce send volume to under 30/day, send only to engaged recipients (warm contacts, inbound leads, recent customers), and monitor Postmaster Tools weekly. Do not send to cold lists during recovery. Eight to twelve weeks is realistic.
If your primary domain is damaged and you need to run outbound during recovery, run it from a secondary domain with a clean reputation. Keep that secondary domain separate from your primary domain's IP range.
Receipts
Operator interviews and deliverability data, Paitho v0.9 beta, Q4 2025 – Q1 2026. Domain reputation figures from public tool outputs (Google Postmaster Tools, Spamhaus). Numbers are illustrative of real patterns.
- Operators interviewed who had experienced a domain-burning event: 11 of 14
- Operators who connected that event to primary-domain degradation: 2 of 11
- Typical timeline from burner-domain event to measurable primary-domain degradation: 4–8 weeks
- Inbox placement recovery timeline from ~40% to ~85% +: 8–12 weeks of conservative sending
- Average send volume for Paitho operators in beta: 38 sends/day (range: 12–90)
- Inbox placement rate for beta operators using Paitho's dual-brand SMTP, measured at 90 days: 91% average
Closing
Principle 4 — Your domains, your data, your keys — is not about privacy. It is about consequences. When the domain is yours, the reputation is yours, and the incentive to protect it is yours. We hold nothing. That means we have no reason to burn it and no ability to do so.
The volume model is not wrong because it is aggressive. It is wrong because the math stops working at the scale of a real pipeline. A damaged domain is an asset you no longer have.
Related:
- BYOK Economics: What 1,000 Leads Actually Cost Across 6 Model Providers
- Why We Human-Gate Contact Enrichment (and Won't Stop)
- Domain Setup and SMTP Configuration — Docs
— Rosa Marin , GTM Operator
Principle 4 — Your domains, your data, your keys.