Outbound
No reason? Delete it from Salesforce
Clay pre-qualifies about 200 accounts. Claude Code researches each one. A hiring signal, a stack change, or something on the site. No reason → delete. Wrong persona → remove. Then Outreach plus LinkedIn.
The loop
- 01Start from a Clay-qualified listAbout 200 accounts this week. Pre-qualified in Clay, but there is still a margin of error. Bad-fit rows clog Salesforce.
- 02Pull the contact, then researchClaude Code takes each contact from Salesforce and researches the company. ICP fit is table stakes. It is looking for a specific reason.
- 03Draft only if there is a reasonA hiring signal. A tech-stack change. Something on the site that says they are thinking about the problem. No reason → do not write.
- 04Human reviews, then Outreach plus LinkedInYou read the draft. Send through Outreach. Go engage on LinkedIn. Judgment stays on every account.
- 05Delete or remove as you goSAP consulting shop that only looked like ICP? Delete it from Salesforce. CFO sitting there for air coverage? Remove the contact. Claude reads markdown ICP, winning templates, and DQ criteria every run.
Most Outreach days are processing. Benyamin’s version is a reason-or-delete loop. Claude does the research. A person still decides.
The interesting constraint is the delete, not the draft. No specific reason means the account leaves Salesforce. The CRM gets cleaner as a byproduct.
