Your domain reputation is grazing land.
Every mailbox provider maintains a shared ledger of trust between senders and inboxes, and every message you send draws on it. So does every message your competitors send, and every message their agents send. In 2026 the herd got very large very fast: agents that write, sequence, and send without a human touching the workflow, each one grazing the same pasture your deals have to cross.
Economists have a name for what happens next. In a commons, each grazer captures the whole benefit of one more animal and pays only a fraction of the cost, so everyone adds one more animal until the field is dirt. Nobody intended the dirt. The incentives did it.
That is not a metaphor stretched over email. It is a literal description of how inbox trust works: a finite, shared resource, drawn down fastest by whoever sends most, with the damage billed to everyone on the channel.
The 90-day pattern
On Tuesday, Chris wrote about Ramp: a company that shut down the AI SDR program behind a meaningful share of its pipeline and spent four years rebuilding outbound around selection, bounded action, and a record. Ramp is the famous case. The pattern underneath it is bigger, and it runs on a schedule.
Most fully autonomous AI SDR pilots get pulled inside 90 days. Digital Applied's 2026 aggregation of AI SDR benchmarks puts a number on the leading cause: 47% of attempted deployments hit a domain-reputation wall inside their first 90 days, and roughly a fifth never recover the inbox placement they started with. The 47% is that one aggregation's figure, drawn from sender-platform data, so hold it loosely. The 90-day shape it describes, volume up fast, reputation down faster, pilot pulled, repeats across the independent 2026 summaries of the same benchmark set.
The cycle is almost boring in its regularity. A pilot launches. Volume multiplies, because volume is the one thing the new tooling makes free. Complaint rates creep. The provider throttles. Reply rates fall, which the dashboard misreads as a copy problem, so the pilot sends more. And somewhere around day 90, someone with a title pulls the plug on a program that was killed by its own throughput.
Warmup tricks, domain pools, and clever openers move the wall a few weeks. They do not remove it, because the wall is not a filter to outsmart. It is the pasture running out.
The fence line
The fence exists, and it is public.
Since February 2024, Google's sender guidelines require senders to keep spam-complaint rates reported in Postmaster Tools below 0.3%, with bulk senders held to the same 0.30% line. The same page tells you where Google actually wants you: keep spam rates below 0.10%, and avoid ever reaching 0.30% at all. Yahoo's sender requirements hold the identical line: keep your spam rate below 0.3%.
Read that number the way it is written. Three complaints per thousand delivered messages is the enforcement threshold. One per thousand is the comfort zone. The distance between a healthy channel and a burned one is two annoyed recipients per thousand, and a fully autonomous sender can close that distance in an afternoon.
The asymmetry is the part most teams learn the expensive way. Damage is fast and recovery is not. Google's guidance says plainly that it can take time for improvements in spam rate to reflect positively on spam classification. The same aggregation reports post-incident reputation recovery measured in weeks: roughly three at Google, closer to seven at Microsoft 365. The over-grazing took days. The regrowth takes a quarter.
Sends this month against the published spam-rate lines. Only the two dashed thresholds are sourced; the curve is the shape of the story, not your data.
| Sends vs addressable audience | Illustrative complaint rate | Zone |
|---|---|---|
| 100% (1x) | 0.05% | Inside Google's recommended 0.10% ceiling |
| 200% (2x) | 0.13% | Above the recommendation, drifting toward the fence |
| 350% (3.5x) | 0.31% | At the 0.30% enforcement threshold Google and Yahoo publish |
| 500% (5x) | 0.57% | Past the threshold; recovery measured in weeks |
Curve values illustrative, not a benchmark. Thresholds sourced to Google's sender guidelines and Yahoo's sender requirements.
At 100% of your addressable audience touched this month, the illustrative complaint rate is 0.05%. Inside Google's recommended 0.10% ceiling. Room to breathe. (Curve illustrative, not a benchmark; thresholds sourced.)
Drag the slider, or use arrow keys. Only the two dashed lines are sourced: Google enforces at a 0.30% spam rate and recommends staying below 0.10%; Yahoo requires below 0.3%. The curve shape and all rate values along it are illustrative, not a benchmark. Damage is faster than recovery: post-incident reputation rebuilds are reported in weeks, not days.
