← all systems
buildingPersonal / agencyOutbound2026 — present

Founder outreach engine

A Claude Code + Clay + Python system that scores startups against an ICP, enriches founder contacts, and runs A/B-tested sequences tracked all the way to booked meetings.

Builder
ClaudeClayClayPythonApolloApolloInstantlyInstantlyHubSpot
~/systems/founder-outreach
running
  1. ApolloStartup listfunding · hiring
  2. Research agentclaude · ICP fit
  3. ClayFounder enrichclay · waterfall
  4. Personalizewhy-now line
  5. InstantlySequencesinstantly · A/B
  6. Meetingscrm · booked
tool agent gate / human record in flight
ICP
agent-scored accounts
A/B
tested sequences
→ mtg
tracked to meetings
Live
in build
Problem

Generic founder outreach gets ignored. The goal is outbound where every email has a researched reason to exist, and where the system learns which reasons work.

Architecture
  1. 01

    Source

    Startups filtered by stage, funding and hiring signals.

  2. 02

    Research

    A Claude Code agent reads each company's site and signals and scores fit against an explicit ICP rubric.

  3. 03

    Enrich

    Clay waterfall for founder emails and roles.

  4. 04

    Personalize

    An agent writes one specific why-now line per founder; the rest of the email stays tested and fixed.

  5. 05

    Sequence + track

    A/B-tested sequences, with every reply and meeting tied back to the variant and ICP score that produced it.

Design decisions
  • →Personalize one line, not the whole email, so A/B tests still measure something.
  • →The ICP rubric is written down and versioned, so the agent's scoring can be audited.
Results

In active development. Results will be published here as the first batches complete.

What I'd build next
  • +First 200-founder batch
  • +Publish reply-rate breakdown by ICP score band
Next system
Momnt: Retention + discovery loop
→