# Clay Outbound Engine

> Find 20 CEOs. Get work emails. Draft the openers. Clay’s search→enrich loop, preinstalled on Claude Code — fork it, clay login, go.

- Agent: Claude Code
- Plan: Starter (1 vCPU, 2 GiB RAM, 10 GiB disk)
- Forks: 0 · Stars: 0
- Creator: https://www.jurniti.com/creator-ca0ff2
- Tags: claude-code, clay, gtm, outbound
- Skills: clay, clay-outbound, cli, public-api, routines, search, setup, tables, workflows

**To fork:** open https://www.jurniti.com/templates/clay-outbound-engine and use the Fork action — it starts a Stripe Checkout for a new VM seeded with this template's persist disk (same flat plan price, no fork fee).

## README

# Find 20 CEOs. Get the emails. Draft the openers.

You already know the Clay motion.

ICP. Company search. People search. Waterfall work emails. Personalization. Export. Sequencer.

What you do *not* want: another afternoon wiring the [Clay agent plugin](https://github.com/clay-run/agent-plugins), hunting `PATH`, relearning Search vs Routines, and rewriting the same loop in a blank Claude chat.

This template is that loop, already on **Claude Code**.

Fork it. Log into **your** Claude. Run `clay login` with **your** Clay workspace. Then paste:

> Find 20 Series B fintech companies in New York, get each CEO's work email, and draft a first-touch cold email for each.

You get a shortlist, fill rate, CSV + markdown under `outputs/`, and **nothing auto-sends**. You own the list. You own the send.

## What you get

- **`clay` CLI** pinned under `~/.agents/bin` (survives fork — not a throwaway `/tmp` install)
- Official **Clay skills** from [clay-run/agent-plugins](https://github.com/clay-run/agent-plugins): `search`, `routines`, `setup`, `cli`, …
- **`clay-outbound` playbook** — ICP → Search → email routine → score → draft openers
- **`CLAUDE.md` + MCP wiring** so the agent knows the PATH and the job

## First five minutes

1. Fork this template → open the terminal.
2. Log into Claude Code (`claude` or your Anthropic key).
3. `export PATH="$HOME/.agents/bin:$PATH" && clay login` (browser OAuth — pick your workspace).
4. Restart Claude Code once so Clay MCP sees the session.
5. Paste the demo prompt above.

Clay **credits/actions are yours** — same as the Clay UI. No markup. No mystery keys in the snapshot.

## Who this is for

- GTM engineers and founders who already live in Clay
- People who want Claude Code to *drive* Clay, not re-implement enrichment
- Anyone tired of re-explaining “search then find work email” every session

## Who this is *not* for

- Teams that need the full Clay table UI as the control plane (use Clay’s product)
- Anyone who wants auto-send to Instantly / Outreach on day one (human gate is intentional)
- Free-tier tire-kickers with no Clay plan (searches burn real credits)

## BYOK

| You bring | Notes |
| --- | --- |
| Claude Code login / `ANTHROPIC_API_KEY` | Run-time only |
| Clay workspace (`clay login`) | Browser OAuth; session stays on *your* VM |

## Upstream

- Plugin + CLI: https://github.com/clay-run/agent-plugins  
- Product: https://www.clay.com/  
- Developer docs: https://developers.clay.com/

## The rule that keeps you safe

**Never auto-send.** This agent builds the list and the first line. You hit send in *your* sequencer.

Fork it. It’s yours.