Skip to content

Repository files navigation

Outbound OS

A complete cold-outreach system that runs inside Claude Code. You describe your offer in a few files; Claude Code does the rest — finds the right companies, picks the right person, researches them, finds their email, writes the sequence, loads it into your email tool, and checks back later to improve it.

Instead of bouncing between a dozen tools and spreadsheets, the whole campaign lives in one folder.

New here? Two steps:

  1. Get the folder — click the green Code button above → Download ZIP (or download it directly), then unzip.
  2. Open SETUP.md and follow it. ~5 minutes if you already have Claude Code, ~20 the first time.

You bring your own API keys. You can start with zero keys, watch the whole thing work, and add keys only when you reach a step that needs one. It never spends your credits without asking.


What you actually do vs. what's built in

You provide two things, and only two:

  1. Your API keys — so it uses your tools and your credits (goes in a private .env file).
  2. Your offer and who it's for — it interviews you and writes it down for you.

Everything else — the workflow, the judgment about who to contact, the research, the writing, the safety rails — is already built in.


How to use it (first run, plain English)

  1. Install Claude Code if you don't have it — see reference/getting-started.md. One time, ~15 min.
  2. Open this folder in Claude Code:
    cd path/to/outbound-os
    claude
    
  3. Add your keys. Copy .env.example to a new file named .env and paste your keys in. Every line in .env.example says what the key is for and where to get it. (You can skip this and start with none.)
  4. Wake it up. Press Shift+Tab to turn on plan mode, then open master-build-prompt.md, copy the whole thing, paste it into Claude Code, and hit enter.
  5. Answer its questions. It asks about your offer and ICP one question at a time and fills in your campaign brain. Then it walks you through the stages, checking in with you at each one.

That's it. Want to see what "finished" looks like first? Open campaigns/_EXAMPLE/ — a complete, worked sample campaign (fictional companies, so nothing to worry about).

Plan mode is your safety net. For anything that sources at scale, spends credits, or loads a sender, Claude tells you exactly what it's about to do and waits for your "go." It never emails anyone on its own.


The pipeline at a glance

First you build the brain — the offer, ICP, personas, value prop, and a few of your best past emails. Then seven stages run on top of it:

# Stage What it does
1 Source accounts You show it good-fit and bad-fit examples; it finds and qualifies more.
2 Pick the person Weighs role and who actually owns the problem — not just "the CEO."
3 Research + patterns Studies each account so the copy is built on a real, specific problem.
4 Enrich + validate Finds emails/phones free first, spends on paid APIs only for the gaps.
5 Write sequences Copy built from the research, trained on your voice — not generic templates.
6 Push to sequencer Loads a draft into Instantly/Smartlead with your warmed inboxes and limits. Never sends without your explicit go.
7 Fetch + improve Pulls performance, shows what's landing, changes one thing at a time.

Plus a one-time Stage 0 — sending infrastructure (domains, inboxes, warmup) in playbooks/00-infrastructure-setup.md.


What's in the folder

Path What it is
CLAUDE.md The always-on rules Claude Code reads automatically. You rarely touch it.
master-build-prompt.md The one message you paste to start.
.claude/skills/ The 12 skills — type / in Claude Code to run any (/source-accounts, /pick-person, …), or just ask.
playbooks/ Step-by-step instructions for each stage, so output is consistent every time.
campaigns/_TEMPLATE/ The blank campaign. Copy it to start a new client or offer.
campaigns/_EXAMPLE/ A fully worked sample campaign (fictional) — your quality bar.
knowledge-base/ The context: how it fits together, deliverability, the copy-voice guide, a glossary, running it as a service.
reference/ Technical notes — API endpoints, install, sending setup, the workflow.
.env.example Template for your keys. Copy to .env (which is private and never shared).

The tool stack

Claude Code is the brain. The rest are optional and swappable:

  • SourcingApify (e.g. the Y Combinator directory), or free web search if you have no key.
  • EnrichmentBetterContact (a waterfall across many providers), with Findymail / Prospeo as fallbacks.
  • SequencerInstantly or Smartlead.

Adding another tool later (a phone dialer, a LinkedIn sender) is a new section in reference/apis.md plus a small skill — the pattern is documented.


Do this safely and well

  • Warm your sending domains first. A great system sending from a cold domain still lands in spam. Warmup takes ~2–3 weeks — start it early.
  • Respect the law. Cold email is regulated (CAN-SPAM in the US, GDPR/PECR in Europe). Keep an opt-out, use real sender info, and don't email where it isn't allowed.
  • Quality over volume. The entire point is sharper targeting and real personalization. Don't turn it into a spam cannon — it works because it isn't one.

FAQ

Do I need to know how to code? No. You work in plain English inside Claude Code. The most technical thing is pasting keys into a file.

Do I need all the API keys? No. You can run the whole build with zero keys and see every stage work. Add an enrichment key when you want it to find emails, and a sequencer key when you want to load leads.

Will it email people automatically? No. Loading a campaign and sending are separate steps, and it never starts sending without your explicit approval.

Can I use it for multiple clients/offers? Yes — that's the design. Each one is a new folder copied from _TEMPLATE.


Built to run entirely inside Claude Code. Bring your own keys, your own offer, and your own judgment — the system handles the rest.

About

A complete cold-outreach system that runs inside Claude Code. Build the brain, then source, pick the person, research, enrich, write, push to your sequencer, and improve — all in one folder. Bring your own API keys.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors