outreach-icp

Solid

Turn a vague outbound brief such as 'sell our tool to SaaS companies' into a targeting spec that a data source can actually execute: job titles with their real per-country variants, industries with NAF, NAICS and SIC codes, headcount band, geography, technographics, buying signals, and the exclusions that keep customers, competitors and unpayable prospects out of the list. Estimates the addressable market with free count calls before a single credit is spent, and splits the brief into separate campaigns when it covers too many audiences. Reads a brief in plain language, writes outreach/icp.json. Triggers on: ICP, ideal customer profile, targeting, target audience, who should I target, define my market, segment, segmentation, persona, buyer persona, job titles, NAF code, NAICS, SIC, headcount, firmographics, technographics, buying signals, exclusion list, TAM, addressable market, market sizing.

Data & Documents 12 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
37
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Define the ICP ## What this does Takes a one line brief and turns it into `outreach/icp.json`, a targeting spec precise enough that [outreach-leads](../outreach-leads/SKILL.md) can run it against Basile, LinkedIn or a CSV without guessing. It writes down the titles, the industry codes, the size band, the geography, the signals and, above all, the exclusions. It counts the market for free before anything is extracted, and it refuses to hide three audiences inside one campaign. No credits are spent here. Counting is free on every source this repository uses. ## When to use it Use it at the start of every campaign, and again whenever a campaign underperforms and you suspect the list rather than the copy. A 1% reply rate with good deliverability is almost always a targeting problem. Use a different skill when: - You already have `outreach/icp.json` and want contacts: go to [outreach-leads](../outreach-leads/SKILL.md). - You already have a list and want it cleaned: go to [outreach-filter](../outreach-filter/SKILL.md). - You know exactly who you want by name (a named account list): skip the ICP, write the account list straight into the leads step, and come back here only if it stops scaling. ## Inputs | Input | Required | If missing | |---|---|---| | The brief, in plain language | yes | Ask for it in one question: what do you sell, to whom, and what does a deal cost you? | | What the product costs | yes | Ask. Price sets the headcount floor. Without it the list wil...

Details

Author
emelia-io
Repository
emelia-io/claude-outreach
Created
3 days ago
Last Updated
2 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Featured

outreach-icp-finder

Find your PROVEN ideal customer profile from your own outreach data — who actually replies, accepts and shows interest — then find more like them. Reads La Growth Machine via its MCP, or a CSV export from any outreach tool (lemlist, Instantly, Smartlead, HeyReach, Apollo, Waalaxy…). Use when someone asks which job titles, seniorities, industries, company sizes or countries reply to their cold outreach, wants reply or positive-reply rate by segment, the ICP behind their replies, who to stop contacting, or a data-driven lookalike from engagement. Triggers: 'who replies to my outreach', 'ICP from my campaigns', 'analyze my replies', 'reply rate by job title', 'who should I target next', 'what's my real ICP', 'qui répond à mes campagnes', 'profil des leads qui répondent'. For SDRs, Heads of Sales/Growth, RevOps, GTM engineers, founders, agencies. Statistically guarded (confidence intervals, minimum volumes, confounding check). Hands off to sales-nav-search-builder. Maintained by La Growth Machine.

37 Updated today
LaGrowthMachine
Data & Documents Solid

outreach-leads

Build the lead list by actually querying the sources this repository supports: the Basile API for French B2B, where an ICP becomes a plan of several queries (adjacent job titles, size bands, zones, sources), each counted for free with countOnly before a single record is extracted, then merged, deduplicated and cut of what is obviously off target before any enrichment credit is spent; a LinkedIn Sales Navigator search collected through the Emelia LinkedIn scraper; or a CSV the user already has (encoding, separator and column mapping handled). Writes outreach/leads.csv with a fixed 26 column schema that every other skill in this repository reads, including a source and a source_url column on every row. Reads outreach/icp.json, a Sales Navigator URL or a file path. Triggers on: build a list, lead list, source leads, find companies, find prospects, Basile, api.basile.cc, docs.basile.cc, French companies, SIREN, NAF, activity filter, count before extracting, Sales Navigator, LinkedIn search, LinkedIn scraper, scra

12 Updated 2 days ago
emelia-io
DevOps & Infrastructure Listed

account-sourcing

Turn an ICP into a ranked target-account list with receipts. Takes the account-level ICP (ideally produced by icp-research), translates its criteria into queries against public sources (job postings, press, funding databases, registries, tech lookups), builds the account universe, scores and visibly disqualifies against the ICP rubric, and tags each surviving account with a dated why-now signal. Every account carries public evidence; no account is invented. Use whenever the user says "build a target account list", "account sourcing", "TAM list", "list building", "find companies to sell to", "who should we go after", "turn our ICP into a list", "prospect list", "account universe", or "lead sourcing". Ships with three key-free scripts: a deterministic account scorer, a live hiring-signal detector for public ATS job boards, and an executive briefing renderer. For products bought by organizations; consumes icp-research output and feeds outbound-engine.

0 Updated 6 days ago
esmefong