Prospect, score leads and run outbound email sequences
An agent scans Apollo.io and job boards twice daily for ICP-matching prospects, scores leads, writes 3-email sequences with Claude, sends follow-ups, and pauses on replies with human approval. Task: Suggested implementation: An agent scans Apollo.io and job boards twice daily for prospects matching an ideal customer profile (ICP). It scores leads 0–100, filtering out low scorers. For qualified leads, Claude generates a unique 3-email sequence with follow-ups on Day 3 and Day 7. A human approves emails via Telegram or Slack before sending.; tools: Claude. Human role: Source evidence is unavailable regarding specific human roles beyond the mention of approving emails via Telegram or Slack.; limitations: Sending volume must ramp from 5 to 150 emails/day over 60 days for domain warmup, preventing immediate full-scale outreach. Source reliability is low as the original URL returned a 403 error, and no evidence proves execution. Human approval is required for all outbound emails..
Tools
Published on Agent Work Atlas:
Overview
An agent scans Apollo.io and job boards twice daily for ICP-matching prospects, scores leads, writes 3-email sequences with Claude, sends follow-ups, and pauses on replies with human approval.
Workflow
Suggested implementation: An agent scans Apollo.io and job boards twice daily for prospects matching an ideal customer profile (ICP). It scores leads 0–100, filtering out low scorers. For qualified leads, Claude generates a unique 3-email sequence with follow-ups on Day 3 and Day 7. A human approves emails via Telegram or Slack before sending.
Reported result
No actual outcomes, metrics, or user reports are available as the source is a product description without reviews or discussion data. Real-world performance is unknown. Proposed acceptance check: Measure reply rate and time-to-approval during a 1-week pilot with 10 manually selected ICP leads.
Human role
Source evidence is unavailable regarding specific human roles beyond the mention of approving emails via Telegram or Slack.
Limitations
Sending volume must ramp from 5 to 150 emails/day over 60 days for domain warmup, preventing immediate full-scale outreach. Source reliability is low as the original URL returned a 403 error, and no evidence proves execution. Human approval is required for all outbound emails.
Try it
Act as a sales operations agent. I need to set up a pilot for getSalesClaw. Inputs: [replaceable: Apollo.io API key], [replaceable: ICP criteria document], [replaceable: Telegram/Slack webhook for approvals]. Steps: 1. Scan Apollo.io and job boards for 10 leads matching the ICP. 2. Score each lead 0-100; discard those under 70. 3. Use Claude to draft a 3-email sequence for qualified leads (Day 1, 3, 7). 4. Send drafts to my Slack for approval. 5. Do not send any emails until I explicitly approve each sequence. 6. If a reply is detected, pause the sequence and notify me. Output: A JSON log of scanned leads, scores, and draft emails. Success metric: 100% of sent emails were human-approved. Handle errors by logging failed scans and skipping leads with missing contact info. Ask clarifying questions only if the ICP criteria are ambiguous.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.