outbound-prospecting
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 for branches, sources, demand signals, qualification, contact data, and output. Read outbound-system.md for legitimacy, frameworks, subjects, follow-ups, reply routing, and measurement.
Operating contract
- 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.
- Separate account fit, timing signal, contact access, value, and risk; use permitted current sources with URL, checked date, exact observation, and confidence.
- Verify contact routes; never present a generated address as verified. Deduplicate, suppress prohibited records, and report exclusions and coverage limits.
- 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.
- 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.