Skip to content
Back to search

openoutreach

MarketplaceWorks with Claude CodeGitHub

The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/eracle/OpenOutreach with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/eracle/OpenOutreach'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/eracle--openoutreach/badge.svg)](/listings/eracle--openoutreach)

HTML

<a href="/listings/eracle--openoutreach"><img src="/api/listings/eracle--openoutreach/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

uv tool install openoutreach
openoutreach

That is the whole thing. A bare `openoutreach` onboards you if it has to, finds leads that fit, buys a verified work address for each, and emails them from your mailbox — narrating what it did as it goes. One install, one wizard, one command.

Prefer to say it out loud, or to set the size of the first run?

openoutreach run 5        # find five leads carrying an address, then send — at most 5 credits

**The verbs:**

openoutreach                  # onboard if needed, then find and send
openoutreach run 5            # ...with an explicit goal
openoutreach init             # onboard only — one flow, every answer, nothing spent
openoutreach init --product-docs product.md --target target.md   # ...the two long fields from files
openoutreach find 10          # ten more qualified leads → CSV on stdout — free, cannot spend
openoutreach find 10 emails   # ...carrying a work email (one credit each)
openoutreach find 0           # no work — print what you already have
openoutreach send             # mail what is already stored
openoutreach send 5           # ...until five conversations are open
openoutreach status           # what is configured, blocked and counted

Everything lives in `~/.openoutreach`, so stopping and starting loses nothing: the number you ask for is *more than you already have*, so running it again continues where it left off. No browser, no daemon manager, no container.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 22 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "openoutreach",
  4. "description": "The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.",
  5. "owner": {
  6. "name": "OpenOutreach",
  7. "email": "hello@openoutreach.app"
  8. },
  9. "plugins": [
  10. {
  11. "name": "openoutreach",
  12. "description": "Find qualified B2B leads from inside Claude Code — drives the OpenOutreach CLI, reads the CSV it prints, and hands the rows to whatever you send with.",
  13. "author": {
  14. "name": "OpenOutreach",
  15. "email": "hello@openoutreach.app"
  16. },
  17. "category": "productivity",
  18. "source": "./",
  19. "homepage": "https://openoutreach.app"
  20. }
  21. ]
  22. }
README.md · README · 371 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. ![OpenOutreach Logo](docs/logo.png)
  2. # OpenOutreach — open-source AI agent for B2B lead generation
  3. > **Describe your product. Define your target market. The AI finds the people who fit, tells you why each one does, and emails them.**
  4. >
  5. > Self-hosted CLI. One install, one onboarding, one command.
  6. >
  7. > Rather not run it yourself? [Get ten leads free at openoutreach.app](https://openoutreach.app/?utm_source=github&utm_medium=readme&utm_campaign=openoutreach-top), each with the reason it fits.
  8. <div align="center">
  9. [![GitHub stars](https://img.shields.io/github/stars/eracle/OpenOutreach.svg?style=flat-square&logo=github)](https://github.com/eracle/OpenOutreach/stargazers)
  10. [![GitHub forks](https://img.shields.io/github/forks/eracle/OpenOutreach.svg?style=flat-square&logo=github)](https://github.com/eracle/OpenOutreach/network/members)
  11. [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg?style=flat-square)](https://www.apache.org/licenses/LICENSE-2.0)
  12. [![Open Issues](https://img.shields.io/github/issues/eracle/OpenOutreach.svg?style=flat-square&logo=github)](https://github.com/eracle/OpenOutreach/issues)
  13. <br/>
  14. ## Demo
  15. <img src="docs/demo.gif" alt="Demo Animation" width="100%"/>
  16. </div>
  17. ---
  18. ### 🚀 What is OpenOutreach?
  19. OpenOutreach is a **self-hosted, open-source lead finder that qualifies for you — and then writes
  20. the email.** You describe your product and your target market; it discovers matching people from a
  21. **licensed data provider**, judges each one against the ICP it learned from your description, hands
  22. you the ones that fit **with the reason each was chosen written out**, and opens the conversation
  23. from your own mailbox.
  24. Two things make that different from what you may have used before:
  25. - **Unlike a cold-email sequencer, you don't bring a list.** There is nothing to upload. The input
  26. is a sentence about your product.
  27. - **Unlike a lead database, the output is not rows.** It is a verdict per person, in plain language
  28. you can read and disagree with — and correcting the description is how you correct the verdicts.
  29. It has **zero platform-ToS surface**: browserless, no social-network account, no scraping. There is
  30. no account to get banned, because there is no account.
  31. > **Rather not run it yourself?** I run it for you. Tell me what you sell and who buys it at
  32. > **[openoutreach.app](https://openoutreach.app/?utm_source=github&utm_medium=readme&utm_campaign=openoutreach)**
  33. > and I send back ten LinkedIn profiles that fit, each with the reason written out, free. After
  34. > that it's $2 a lead. Nothing to install, no keys, no account.
  35. ---
  36. ## ⚡ Quick Start
  37. ```bash
  38. uv tool install openoutreach
  39. openoutreach
  40. ```
  41. That is the whole thing. A bare `openoutreach` onboards you if it has to, finds leads that fit,
  42. buys a verified work address for each, and emails them from your mailbox — narrating what it did as
  43. it goes. One install, one wizard, one command.
  44. Prefer to say it out loud, or to set the size of the first run?
  45. ```bash
  46. openoutreach run 5 # find five leads carrying an address, then send — at most 5 credits
  47. ```
  48. **The verbs:**
  49. ```bash
  50. openoutreach # onboard if needed, then find and send
  51. openoutreach run 5 # ...with an explicit goal
  52. openoutreach init # onboard only — one flow, every answer, nothing spent
  53. openoutreach init --product-docs product.md --target target.md # ...the two long fields from files
  54. openoutreach find 10 # ten more qualified leads → CSV on stdout — free, cannot spend
  55. openoutreach find 10 emails # ...carrying a work email (one credit each)
  56. openoutreach find 0 # no work — print what you already have
  57. openoutreach send # mail what is already stored
  58. openoutreach send 5 # ...until five conversations are open
  59. openoutreach status # what is configured, blocked and counted
  60. ```
  61. Everything lives in `~/.openoutreach`, so stopping and starting loses nothing: the number you ask
  62. for is *more than you already have*, so running it again continues where it left off. No browser,
  63. no daemon manager, no container.
  64. ---
  65. ## 🤖 Use it from Claude Code
  66. This repo ships a **Claude Code plugin**, so you can pull leads without leaving your agent session:
  67. ```
  68. /plugin marketplace add eracle/OpenOutreach
  69. /plugin install openoutreach@openoutreach
  70. ```
  71. The skill (`skills/find-leads/SKILL.md`) teaches Claude when to run `find`, which flags cost credits
  72. and which cannot, how to read the CSV on stdout, and what each `error: <type>` means. It never buys
  73. an address you did not ask for, and never sends without being asked. Prefer skills to plugins? Copy `skills/find-leads/` into `~/.claude/skills/` instead.
  74. **Not on Claude Code?** The skill is a markdown file describing the CLI's own contract — nothing
  75. Claude-specific is required to use `openoutreach` itself. Codex, Cursor, or any other agent can call
  76. the same `openoutreach find` / `send` / `run` / `status` commands directly; point your agent's
  77. instructions file at `skills/find-leads/SKILL.md` and it reads the same rules.
  78. ---
  79. ## 🧩 Three packages, one product
  80. OpenOutreach is an **orchestrator**. The finding and the sending are two standalone programs, and
  81. this package installs both and hosts them in one process, one database and one onboarding:
  82. | Package | What it is | Standalone |
  83. |---|---|---|
  84. | [**OpenOutFind**](https://github.com/eracle/OpenOutFind) | discovery, qualification, enrichment, the CRM | `uvx --from openoutfind outfind find 10` |
  85. | [**OpenOutSend**](https://github.com/eracle/OpenOutSend) | the outreach agent, the mailbox, the send guards | `uvx --from openoutsend outsend send` |
  86. | **OpenOutreach** (this) | one install, one wizard, one command over both | — |
  87. **The wizard is here because the children do not have one.** Both are agent-first: they read their
  88. configuration from `OPENOUTFIND_*` / `OUTSEND_*` on every run and remember none of it, which is
  89. right for a program a script or an agent drives and wrong for a person. So this is where the
  90. questions are asked, where the answers are kept, and where they are handed to each child in its own
  91. variables.
  92. **Neither child is diminished by the bundle.** Each keeps its own console script, its own settings
  93. module and its own test suite, and the contract between them is a public one:
  94. ```bash
  95. outfind find 50 --json | outsend # anybody's producer, anybody's receiver
  96. outsend send # a separate invocation, on the mailbox's clock
  97. ```
  98. `openoutreach run` is that same pipe, in one process — the JSON Lines still cross the boundary, they
  99. just cross it in a buffer. There is no privileged in-memory hand-off, because a second, untested path
  100. between the same two programs would make the public one a lie.
  101. **Which shape is for you:** if you are an agent, a script, or a power user with your own sender,
  102. take the two CLIs and the pipe. If you want to see whether this works, take the one command.
  103. ---
  104. ## 📤 What You Get Out
  105. The finder's deliverable is a file, and it is shaped for the tools you already send with:
  106. ```bash
  107. openoutreach find 10 emails > leads.csv
  108. ```
  109. It runs until it has ten more leads carrying an address, prints **every lead you have** as CSV, and
  110. exits — so the file you just wrote is always the current truth. Exit 0 means it got what you asked
  111. for; anything short still prints its rows and says why it stopped.
  112. ```
  113. email, first_name, last_name, company, title, website, linkedin_url, reason, lead_id, qualified_at
  114. ```
  115. Those column names are **the importers', not ours**. Instantly and Smartlead both require
  116. `email`/`first_name`/`last_name` and recognise `company`/`title`/`website`/`linkedin_url` as standard
  117. fields, so an exported file imports **without column mapping**. Anything else — including `reason` —
  118. arrives as a custom variable you can merge into a template.
  119. - **`reason` is the point.** Everybody exports rows; almost nobody exports *why this lead*.
  120. - **There is no score column, on purpose.** The model's confidence is a spend gate for the paid
  121. lookup, not a quality signal. The fit verdict is the LLM's, and it is already in the file as a
  122. sentence.
  123. - **A lead with no email still exports.** If you have no email-finder credits, you still get the
  124. qualified person, their employer and the reason.
  125. - **A rejected lead never exports.** Both rejections are excluded, always.
  126. > **If you send with your own tool:** turn on its *import dedupe*. It is opt-in on Smartlead and
  127. > undocumented on Instantly, so a lead you export twice can otherwise be contacted twice.
  128. ---
  129. ## 📋 What You Need
  130. | # | What | Example |
  131. |---|------|---------|
  132. | 1 | **An LLM API key** | OpenAI, Anthropic, or any OpenAI-compatible endpoint |
  133. | 2 | **An email-finder API key** ([BetterContact](https://bettercontact.rocks?fpr=openoutreach)) | **Free account: 40 credits, no card.** Powers **both** discovery (Lead Finder, billed nothing) and enrichment (one credit per verified work email) |
  134. | 3 | **A product description + target market** | "We sell cloud cost optimization for DevOps teams at mid-market SaaS companies" |
  135. | 4 | **A mailbox to send from** | Its address and an **app password** — not your login password. Google Workspace works out of the box; any other provider names its SMTP/IMAP host and port |
  136. No keys yet? [Ask for ten leads at openoutreach.app](https://openoutreach.app/?utm_source=github&utm_medium=readme&utm_campaign=openoutreach-needs)
  137. and I'll find them for you, free.
  138. Onboarding asks for all four in one pass and **asks only once** — the answers are kept in
  139. `~/.openoutreach`, and every later run exports them into the variables the children read. A question
  140. whose variable is already exported is not asked at all, so an operator or a unit file that sets
  141. `OPENOUTFIND_*` / `OUTSEND_*` never has to repeat it into a prompt; that is what makes a headless
  142. install possible. With no TTY and something still unanswered, setup stops **naming the variables**
  143. that would have answered it rather than blocking on a question nobody is there to hear.
  144. The two long fields are read from files, not flags — a markdown paragraph shell-quoted onto a
  145. command line corrupts quietly:
  146. ```bash
  147. openoutreach init --product-docs product.md --target target.md
  148. ```
  149. The LLM key is **verified at the prompt**, and the mailbox by a real SMTP login before setup
  150. finishes: a wrong key is an answer you can retype, not a traceback halfway through a run.
  151. The BetterContact link above is an **affiliate link** — signing up through it supports OpenOutreach,
  152. at no markup to you.
  153. ---
  154. **Why choose OpenOutreach?**
  155. - 🧠 **You don't need a list** — describe your product; it finds candidates from licensed data
  156. - 📝 **A stated reason per lead** — read exactly why the agent picked someone, and fix the description when it is wrong
  157. - 🔍 **Nothing decides in the dark** — the ICP, the verdicts and the whole pipeline are on your machine and open to read
  158. - 🛡️ **Zero platform-ToS surface** — browserless, no social-network account, no scraping — nothing to get banned
  159. - 💸 **Pay only for what resolves** — searching is free; a paid lookup is rationed and billed on a verified hit
  160. - 📤 **Or export where you already work** — CSV in the shape the sequencer importers expect
  161. - ⚡ **One-command setup** — `uv tool install openoutreach && openoutreach`
  162. Every comparable tool that qualifies leads for you is paid SaaS. This one is open source under Apache 2.0, runs on your
  163. machine, and you bring your own provider keys.
  164. ---
  165. ## 💸 How OpenOutreach Stays Free
  166. **Affiliate links, and that is now the whole of it.** The one paid third-party service the tool
  167. relies on — the lead-data provider — is surfaced during onboarding through an affiliate link. Sign
  168. up through it and the project may earn a commission, **at no markup to you**. Sign up any other way
  169. if you prefer. See the **[Legal Notice](LEGAL_NOTICE.md)** (§4).
  170. ---
  171. ## 📖 How It Works
  172. **Discover → qualify → gate → resolve → write → send.**
  173. 1. **You provide** a product description and a campaign objective
  174. 2. **An LLM turns that into opening search keywords** and pages matching firmographic profiles from
  175. a **licensed discovery source** (BetterContact Lead Finder) — no emails yet, billed nothing
  176. 3. **Discovery walks the keyword index by counting**, adding one word at a time and spending its next
  177. query where the accepted-lead counts say the best ones came from
  178. 4. **An LLM qualifies each candidate** against your ICP and **writes down why**. A Gaussian Process
  179. over profile embeddings learns from those verdicts and picks who to qualify next
  180. 5. **A confidence gate rations the one paid step** — a work address is resolved for the best-fit
  181. leads only, one credit per verified hit
  182. 6. **The outreach agent writes each opener** from the same product description, and the send guards
  183. (sending window, daily cap, pacing) decide when it actually leaves your mailbox
  184. Steps 1–5 are [OpenOutFind](https://github.com/eracle/OpenOutFind)'s and step 6 is
  185. [OpenOutSend](https://github.com/eracle/OpenOutSend)'s; each repo documents its own internals.
  186. Searching the licensed source is free, so the system can afford to look at a lot and spend paid
  187. lookups only on the best fits. *(The learning loop is an active experiment — it is not yet shown to
  188. beat picking at random, and no claim is made that it does.)*
  189. ---
  190. ## 📂 Project Structure
  191. This repo is the orchestrator and holds no pipeline of its own — that is the point of it:
  192. ```
  193. ├── openoutreach/
  194. │ ├── __main__.py # the `openoutreach` console script: find · send · status · run
  195. │ ├── settings.py # one Django registry hosting both children's apps, on one database
  196. │ ├── config/ # the one model: the answers you gave, and the variables they export as
  197. │ └── wizard.py # one onboarding — ask once, keep it, hand it to both children
  198. ├── tests/ # the registry, the wizard's row and export, the CLI's own decisions
  199. ├── manage.py # checkout shim over openoutreach/__main__.py
  200. ├── pyproject.toml # package metadata, pinned children, console script
  201. ├── local.yml # Docker Compose — the server deploy only
  202. └── Makefile # Shortcuts (setup, run, find, test)
  203. ```
  204. ---
  205. ## ⚙️ Local Installation (Development)
  206. ```bash
  207. git clone https://github.com/eracle/OpenOutreach.git
  208. cd OpenOutreach
  209. make setup # install -e ".[dev]" + migrate both children's apps
  210. make run # onboard, find, send
  211. make test
  212. ```
  213. Working on the pipeline itself? It is not here — clone
  214. [OpenOutFind](https://github.com/eracle/OpenOutFind) or
  215. [OpenOutSend](https://github.com/eracle/OpenOutSend), and point this project at your checkout with
  216. `uv pip install -e ../OpenOutFind`.
  217. Running it on a server instead? A Docker image is published to GitHub Container Registry for exactly
  218. that — see the **[Docker Guide](./docs/docker.md)**.
  219. ---
  220. ## 💬 Channel
  221. Join for support and discussions:
  222. [Telegram Channel](https://t.me/openoutreach)
  223. ---
  224. ### 🗓️ Book a Free 15-Minute Call
  225. Got a specific use case, feature request, or questions about setup?
  226. Book a **free 15-minute call** — I'd love to hear your needs and improve the tool based on real feedback.
  227. <div align="center">
  228. [![Book a 15-min call](https://img.shields.io/badge/Book%20a%2015--min%20call-28A745?style=for-the-badge&logo=calendar)](https://www.cal.eu/eracle/15min)
  229. </div>
  230. ---
  231. ### ❤️ Support OpenOutreach
  232. This project is built in spare time to provide powerful, **free** open-source growth tools. Your sponsorship funds faster updates and keeps it free for everyone.
  233. <div align="center">
  234. [![Sponsor with GitHub](https://img.shields.io/badge/Sponsor-%E2%9D%A4-ff69b4?style=for-the-badge&logo=github)](https://github.com/sponsors/eracle)
  235. <br/>
  236. | Tier | Monthly | Benefits |
  237. |-------------|---------|-----------------------------------------------------------------------|
  238. | ☕ Supporter | $5 | Huge thanks + name in README supporters list |
  239. | 🚀 Booster | $25 | All above + priority feature requests + early access to new campaigns |
  240. | 🦸 Hero | $100 | All above + personal 1-on-1 support + influence roadmap |
  241. | 💎 Legend | $500+ | All above + custom feature development + shoutout in releases |
  242. </div>
  243. ---
  244. ## ⚖️ License
  245. [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) — see [LICENCE.md](LICENCE.md)
  246. ---
  247. ## 📜 Legal Notice
  248. By using this software you accept the [Legal Notice](LEGAL_NOTICE.md). It covers the third-party
  249. services you connect (data provider, email-finder), your responsibilities as data controller under
  250. data-protection law, your duties as the sender of the mail this tool writes, automatic newsletter
  251. subscription for non-opt-in jurisdictions, the central contacts store, and liability disclaimers.
  252. **Use at your own risk — no liability assumed.**
  253. ---
  254. <div align="center">
  255. <a href="https://star-history.com/#eracle/OpenOutreach&Date">
  256. <picture>
  257. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=eracle/OpenOutreach&type=Date&theme=dark" />
  258. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=eracle/OpenOutreach&type=Date" />
  259. <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=eracle/OpenOutreach&type=Date" width="400" />
  260. </picture>
  261. </a>
  262. **Made with ❤️**
  263. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.