How to Identify Prospects Facing Low Reply Rates, Personalization, and Deliverability Challenges in Outbound Outreach | Clay

How to Identify Prospects Facing Low Reply Rates, Personalization, and Deliverability Challenges in Outbound Outreach | Clay

Aaron J.
·
·
Those are common outbound issues, almost everyone doing outbound will be solving for them in some way, and still struggling with them in others. Potentially looking for companies actively hiring cold-calling AEs or SDRs (job search enrichments) will help identify those that are willing to spend money on more/better Outbound.
1
Md R.
·
·
Deliverability is the easiest of the three to detect from outside. Public DNS lookups show everything. SPF over 10 lookups, DMARC at p=none with no reporting endpoint, missing DKIM alignment across their sending tools - all visible from a Kitterman or MXToolbox check. A company running outbound from a domain with broken DMARC is your textbook ICP.
Slava M.
·
·
Riaz makes a great point about DNS technicalities, but there's a catch: detecting the "real" outbound domains is the bottleneck. Clay will give you the primary company.com, but experienced teams run outbound from dozens of look-alike domains. You won't see their SPF/DMARC issues because you don't know their secondary domains. My advice for finding "struggling" prospects: Look for "Tech Stack Decay" and "Hiring Friction" signals:
1.
Job Posting Specifics: Don’t just look for "SDR." Look for companies hiring SDRs with "experience in deliverability" or "domain management." If those keywords appear in the job description, it's a clear signal they’ve recently been hit by spam filters or are struggling to scale their infrastructure.
2.
The "Ghosting" Signal: If a company is actively hiring for sales but their headcount growth in sales is stagnant or negative over the last 6 months (LinkedIn Headcount data), it often means their current outbound engine is broken, and they are trying to "hire their way out" of a low-reply-rate problem.
Slava M.
·
·
For the last one, combine LinkedIn Sales Headcount growth (to see if the team is actually expanding) with a tool like PredictLeads (via Clay enrichment) to check job posting history. If the data shows they've had 5+ open SDR roles for 180 days, but their Sales headcount is flat or down — that’s the 'Smoking Gun.' It means their churn is high because their outbound engine isn't providing enough pipeline for the reps to hit quota. That's your entry point.
1
Viky G.
·
·
Really interested what will be the results of your enrichment. I had a similar alarm approach, trying to narrow my target base by researching their pains, and it appeared to be quite narrow. Where are you able to create a significantly meaningful audience size?
Slava M.
·
·
The narrowness is actually the point!.. I’d rather spend 80% of my time on the 20% of the market that is clearly 'bleeding.' It’s about effort management. If the 'Smoking Gun' list feels too small to keep the engine humming, you just look one step upstream. Instead of only targeting the teams that are already broken (high churn/flat headcount), you look for the ones about to break. A company hiring their first 3-5 SDRs or a new VP of Sales is an 'effort' signal. They aren't in a death spiral yet, but they’re at the exact moment where they’re deciding between building a generic spam machine or something that actually scales. I treat the 'broken' teams as 1:1 manual priority and the 'scaling' teams as signal-based automation. That way, you aren't sacrificing meaningful audience size, you’re just making sure your manual effort isn't wasted on companies that are 'doing just fine' with their current setup. Have you found that narrowing the criteria actually killed your volume, or did it just make the manual research feel too heavy?
Viky G.
·
·
Yes, I had a very specific narrowing point which researched them expressing pain points related to our product in social accounts. Since this is a developer oriented audience not many of them actually talk about their pains openly, so the end audience was not that wide. I still think it is good for the initial run for the experimentation.
🎯1