The Definition of Outreach Decay
Outreach decay is the measurable decline in the performance of a recruiting outreach program as a mandate progresses — typically manifesting as falling response rates, declining open rates, and deteriorating pipeline conversion from outreach activity. It is caused by some combination of pool exhaustion (the reachable candidates have been contacted), message fatigue (repetition without response reduces future response probability), and deliverability degradation (email domain reputation declining from high send volumes).
Outreach decay is distinct from response decay: response decay measures the outcome (fewer candidates responding); outreach decay measures the broader program performance, including email deliverability, open rates, and sequence engagement at each stage. Both are signals; outreach decay is the earlier and more comprehensive one.
The Three Causes of Outreach Decay
Pool exhaustion
The defined candidate pool — the segment of the market that matches the brief and is reachable through the recruiter's channels — has been contacted. The people who were going to respond have responded. Continued outreach to the same pool will produce diminishing returns regardless of message quality.
Message fatigue
Candidates in a niche market who receive repeated outreach from recruiters — whether the same recruiter or different ones running similar searches — develop fatigue responses: lower open rates, lower click rates, and lower response rates even to genuinely relevant opportunities.
Deliverability degradation
High-volume outreach from a domain that lacks proper DNS/MX authentication degrades email deliverability — increasing spam filter interception rates and reducing the proportion of outreach that actually reaches the intended recipient. This is a technical cause that is often mistaken for a message quality problem.
"Reply rate improvement from 14% to 35% required two changes: DNS/MX verification to fix deliverability (technical, not copy), and outreach decay detection that triggered a pool refresh and sequence reset at the right moment. Neither change required better writing. Both required better infrastructure."