outreach — Contacts: who to write to, and where — openbash

Companies matching a description, the people at them, and their addresses — derived from the company's format, found by a finder, or verified against a mail server.

outreach

outreach is a command on the openbash shell, reachable over HTTP, SSH and MCP with one key. It composes with the other programs through pipes; there is no per-program endpoint and no schema for the join.

outreach email list argenx

help

outreach: building a list of people to write to, as JSON.

RETURNS
  One JSON object on stdout. `outreach` with no arguments prints every study
  and what it takes.

FOUR STUDIES, ONE PIPELINE
  `companies find` turns a description of a market into companies with their
  mail domains — every name checked against a directory, so a company nobody
  has a record of is dropped rather than reported. The domain is what the rest
  of this command takes.

  `email list` is who works there: people from the directory, each with a
  name, a position and a department, and an address where the company's
  format is already on file — learned from a real address or a probe, never
  guessed. With no format on file the people come back without addresses.

  `email search` places ONE named person — by the filed format, a probe, or a
  finder that charges only when it finds an address — which is how it answers
  for a new joiner or anybody the directory does not list.

  `contacts expand` goes furthest: colleagues from the directory, addresses
  derived from the format, and each one checked against a mail server before
  it comes back. It is the only study that verifies.

  `email person` runs the other way: from an address you already have — a
  signup, a reply — to who it belongs to, with their name, position, company
  and LinkedIn, from the people directory. `found: false` is an answer, not a
  failure: the directory was asked and knows nobody, and a miss is not billed.

WHAT TO GIVE IT
  A company name is enough. A domain is surer. Surest of all is one address
  you already have there — it names the domain outright, so there is no lookup
  to land on the wrong firm.

NOTES
  A CONFIDENCE IS NOT A DELIVERY CHECK. It says the address follows the
  company's format; only `contacts expand` opens a mailbox, and that is on
  unless you turn it off. A company that accepts mail to any local part comes
  back with `accept_all`, which is worth reading before anybody counts a
  delivery as proof the person exists.

  Role addresses — info@, sales@ — are MARKED, not dropped. They are the right
  address for some jobs and the wrong one for outreach, and only the caller
  knows which.

  `companies find` reports how many names were PROPOSED before checking. The
  gap between that and what came back is the invention rate: two of twenty
  means the description is wrong, not that the market is empty.

Studies:
  companies find  <prompt>
      a description of a market, and the companies that match it — each one checked to exist
  email list      <company_name>
      every address a company has published, with positions and the format
  email verify    <email>
      whether one address you already have reaches a mailbox
  email person    <email>
      who is behind one address you already have: their name, job, company and profile
  email search    <company_name> <name>
      one named person's address — published on the web (with the pages), from the company's format, accepted by its mail server, or from a directory; `basis` says which and `confirmed` whether the server accepted it. `risk` says how far to trust it: confirmed, published, format, unchecked or guess — treat `guess` as no address before sending
  contacts expand <company_name>
      colleagues at a company with their addresses derived and checked — the one study that verifies
  people role     <company>
      who holds a role at a company now, from public profile pages, each with the page — a tenth of a cent where a directory charges a third of a dollar; pass the name to `email search` next
  people find     <titles>
      people who describe themselves this way — a title, skills, a place — with no company named, from public profile pages, each with the page: the sourcer's search for candidates, reps or experts

JSON to stdout, so it composes: pipe to `jq` to pick a field, or `> /tmp/…` to keep it.
Run a study with no arguments — `outreach companies find` — to see what it takes.

What it answers

outreach companies find — a description of a market, and the companies that match it — each one checked to exist
outreach email list — every address a company has published, with positions and the format
outreach email verify — whether one address you already have reaches a mailbox
outreach email person — who is behind one address you already have: their name, job, company and profile
outreach email search — one named person's address — published on the web (with the pages), from the company's format, accepted by its mail server, or from a directory; `basis` says which and `confirmed` whether the server accepted it. `risk` says how far to trust it: confirmed, published, format, unchecked or guess — treat `guess` as no address before sending
outreach contacts expand — colleagues at a company with their addresses derived and checked — the one study that verifies
outreach people role — who holds a role at a company now, from public profile pages, each with the page — a tenth of a cent where a directory charges a third of a dollar; pass the name to `email search` next
outreach people find — people who describe themselves this way — a title, skills, a place — with no company named, from public profile pages, each with the page: the sourcer's search for candidates, reps or experts

• This program as JSON, with its full help text
• Every program in the catalog
• llms.txt — how to call it