Outbound Prospecting

---
name: outbound-prospecting
description: Build source-backed prospect lists and write the relevant, lawful cold outreach that follows: account and contact discovery, demand signals, qualification, permitted data sources, CSV-ready handoff, then B2B cold-email sequences with truthful personalization, follow-up limits, reply routing, and deliverability boundaries. Use for target-account lists, lead research, and SDR sequences; use lifecycle-messaging for permissioned messaging and sales-kit for collateral.
license: MIT
metadata:
  version: "2.0.0"
  author: MTEnt
---

# Outbound Prospecting

A list is only as good as the evidence behind each row, and relevance begins with qualification. A scraped fact or compliment that does not change the offer's fit is not personalization.

If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [prospecting-system.md](references/prospecting-system.md) for branches, sources, demand signals, qualification, contact data, and output. Read [outbound-system.md](references/outbound-system.md) for legitimacy, frameworks, subjects, follow-ups, reply routing, and measurement.

## Operating contract

1. Define market, geography, jurisdiction and lawful basis, qualifying situation, ICP, disqualifiers, demand signals, buyer roles, intended use, list size, freshness, sender identity, volume, and suppression.
2. Separate account fit, timing signal, contact access, value, and risk; use permitted current sources with URL, checked date, exact observation, and confidence.
3. Verify contact routes; never present a generated address as verified. Deduplicate, suppress prohibited records, and report exclusions and coverage limits.
4. Write a concise sequence with a truthful reason for contact, a relevant hypothesis, credible mechanism or proof, a low-friction next step, new value in each follow-up, a hard attempt limit, and stop conditions.
5. Require authorization before enrichment, purchase, CRM import, account setup, or sending.

Do not guess addresses and label them verified, impersonate familiarity, hide commercial intent, switch identities to bypass silence, infer private intent, or continue after opt-out.

## Return

Qualified list with method, coverage, exclusions, and compliance notes; the complete sequence with personalization fields and fallbacks, reply routing, suppression, QA, measurement, and the send-approval boundary.