audience-icp-filter

Featured

Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants to know who is worth contacting. Triggers on: 'filter this audience against my ICP', 'who in this list matches my ICP', 'clean up this lead list', 'score these leads', 'qualify my signups', 'segment this audience', 'is my audience on-ICP', 'filter my webinar attendees', 'split this audience by ICP fit', 'remove the bad leads'. For SDRs, BDRs, RevOps, growth, demand gen and founders doing list qualification, ICP refinement, post-event follow-up or audience cleanup. Checks whether the data can support the ICP before filtering, sorts every lead into ICP match / needs review / no match, strips out your own team and competitors, and never silently drops anyone. Maintained by La Growth Machine.

Data & Documents 37 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

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

Skill Content

# Audience ICP Filter Takes an audience that already exists and splits it into **ICP match**, **needs review** and **no match** — with the user's own team and competitors stripped out, and a reason attached to every decision. ## Authority — read this first - **Inlined below:** the coverage gate, the ICP question set, the seniority and function tiers, the exclusion doctrine, the two-pass rule, the naming convention, the anti-patterns, and the **fixed result UI**. This covers the common ~90% of lists. Work from these tables. - **In `references/title-taxonomy.json`:** the full regex patterns behind seniority/function detection. **You do not need to read it** — `scripts/build.py` loads it. Consult it only if a user disputes a classification or wants to extend the taxonomy. - **Never classify a list by hand.** Run the script, then run your own review pass over its output. Both passes are mandatory. ## Scope This skill starts from a list that **already exists**: an audience in the user's sales tool, or a CSV. It does not import or scrape — importing is a separate job with its own timing and prerequisites, and folding it in here would make the skill slower and less reliable for no gain. If the user hasn't imported yet, tell them to do that first, then come back with the audience. ## What it does Any audience is mostly noise: the user's own colleagues are in it, competitors are watching, and a third of the job titles are unreadable. This skill checks whether the data can supp...

Details

Author
LaGrowthMachine
Repository
LaGrowthMachine/gtm-system
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

outreach-icp

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.

12 Updated 2 days ago
emelia-io
Data & Documents Solid

outreach-filter

Clean and segment a lead list before a single credit is spent on it. Deduplicates by email, by company domain and by LinkedIn profile, handling the awkward cases (subdomains, plus aliases, apostrophes and accents in names, Sales Navigator URLs that never string match a public profile), excludes existing customers, competitors and blacklisted addresses using find_contact and the Emelia blacklist endpoints, drops generic mailboxes such as contact@ and info@ and the junior roles that cannot buy, checks that geography and headcount match the ICP, and splits what survives into segments that each deserve a different message. Reads outreach/leads.csv and outreach/icp.json, writes a smaller leads.csv plus a report of every row removed and why. Triggers on: filter, clean the list, dedupe, deduplicate, duplicates, remove customers, exclusion list, blacklist, suppression list, generic emails, contact@, role address, segment the list, segmentation, list hygiene, data quality, before enrichment.

12 Updated 2 days ago
emelia-io
AI & Automation Listed

icp-definition

Define an ideal customer profile precise enough to build a lead list from, including buying triggers and disqualifiers. Use whenever the user mentions ICP, ideal customer profile, target market, buyer persona, target accounts, account list, who to sell to, market segmentation, or says their outbound isn't working and they aren't sure who to target. Also use before any lead sourcing or cold email work, because a list built from a vague ICP wastes every downstream step.

0 Updated 3 days ago
manypicom