Build an Outbound Prospect List
Define an ICP, search for matching prospects, enrich with contact data, and export a ready-to-use outbound list - end to end. Every email returned is graded A-F for deliverability risk, and you pick which grades to keep.
example prompts
-
Build an outbound list of RevOps leaders at US SaaS companies with 50-500 employees -
Define an ICP of marketing directors at fintech startups and build a prospect list with emails -
Create a targeted prospect list matching my ICP and enrich everyone with contact data
about this skill
What this skill does
Full end-to-end ICP-to-contact-list workflow. Define your ICP, search for people by company and people attributes (industry, domain, seniority, department, country), enrich the gaps with business email and mobile, and get a clean exportable list ready for outreach.
Before searching, the skill gates on input quality - if nothing scopes the search, it asks for more detail rather than burning credits on a vague search.
Chain
company + people ICP criteria
to search_people (find matching people)
to linkedin_to_business_email (per-URL parallel calls - business emails)
to linkedin_to_mobile_phone (batch array - mobile, optional)
Inputs - at least one filter
| Field | Param | Example |
|---|---|---|
| Free-text (name / role / company) | query |
"Jane Smith", "VP Sales", "Stripe" |
| Company name | company |
"Stripe", "HubSpot" |
| Exact domain | company_domain |
"stripe.com" |
| Industry | industry |
"Information Technology", "Finance and Banking" |
| Seniority | seniority |
"Director", "VP", "C Suite" |
| Department / functional area | department or functional_area |
"Sales", "Marketing", "Engineering" |
| Country | country |
"United States" |
| Target count | - | "50 contacts", "100 records" |
How it works
- Confirms at least one filter is present - prompts if under-specified
- Runs a free credit check and estimates total cost
- Probe search on 1 result to verify quality before scaling
- Paginates to target count (25 results per call)
- Deduplicates, then enriches - email as per-URL parallel calls, phone as one batch array call
- Outputs exportable table
Output
| Name | Title | Company | Country | Business Email | Risk | Mobile |
|---|
Prospects found: X
Business emails: X/N (XX%)
Mobile numbers: X/N (XX%)
Credits used: ~XXX
Email risk scores:
A: X B: X C: X D: X F: X
kept (accepted grades): X
filtered (excluded): X
Search filters
search_people filters on query, company, company_domain, country, state, city, seniority, department or functional_area, industry, linkedin_industry, naics_code, employee_range, and revenue_range.
- Filters are free precision - execution cost comes from the free-text
query, so a filters-only search runs ~40x cheaper and lands more precisely. A barequeryis never the right shape; at minimum it getscountryattached (~99% fill rate). - Size and revenue apply to the person's current employer - "VPs at 51-200 employee software companies" is one call, not a company search followed by a people search.
- Three industry vocabularies - broad
industrybuckets, LinkedIn's ~150 niche labels, or a NAICS code at any depth. Shortening the code widens the net. - Sparse filters are the usual cause of a thin result set -
seniority/industry/departmentare ~60% filled andnaics_code/linkedin_industry~50%, and every filter is exact-match, silently dropping records where the field is empty. - Probe before you pull -
search_peoplehas no count-only mode, so run it atlimit: 1first and readresults.totalbefore paginating. (count_only: trueis free, but only onsearch_linkedin_profile.)
Company-side filters
search_companies filters on query (company name only), domain, industry, linkedin_industry, naics_code, employee_range, revenue_range, country, and state.
domainbeats free text every time - exact match, and full URLs are normalised automatically, sohttps://www.acme.com/aboutneeds no cleanup first.- Filters are free precision - a filters-only search runs ~40x cheaper than one carrying free text, and most firmographic work needs no
queryat all. industryis 22 broad buckets only -"Information Technology", not"Computer Software". Niches like software or insurance live inlinkedin_industry("Software Development") ornaics_code. A thin result is often a neighbouring-label problem rather than a coverage one.- Company location is derived from where the team is based, and large multinationals resolve to a single one of their offices - pair location with another filter on enterprise or international targeting.
- Range values are exact and skewed -
"1-10"dominates employee counts,"$500k - $1M"dominates revenue.
Tips
- Industry + seniority + department is a strong role-based targeting combination; use
company_domain(notdomain) to scopesearch_peopleto one company - If filters produce fewer results than your target, the skill suggests broadening one constraint at a time
- Every returned email carries an A-F deliverability risk score; you're asked up front which grades to keep, and out-of-range grades are shown and flagged rather than silently dropped