---
name: outbound-prospecting
description: Decides whether a market segment is worth attacking, sources and qualifies prospects against written criteria, deduplicates against the existing pipeline, and prepares a sequenced campaign for approval. Use when the user asks to find prospects, evaluate a market, build a target list, or prepare outbound.
metadata:
  version: "1.1.1"
---

# outbound-prospecting

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Outbound Prospecting |
| Live category | CRM & Sales |
| Catalog entry | 8 |
| Internal capability ID | `CAP-CRM-05` |
| Provider | Sourcing, enrichment and sequencing services |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `limited_pilot_package` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

Outbound starts from a qualified list and a defensible market decision, not from a scraped export.

## Operating modes

Read · Analyze · Draft · Send with approval

## Prerequisites — what must be true before this runs

- Workspace Context (ICP, positioning, geography)
- Approved sourcing and sequencing grants
- A suppression list and pipeline export

## Required inputs

| Input | Source |
|---|---|
| Segment definition and the offer | Required |
| Qualification criteria | Required — written, testable, and applied to every record |
| Geography policy | Workspace Context |
| Suppression and existing-pipeline data | Required |
| Named approver before any send | Configuration |

## Decide the market before building the list

Run the segment decision first: estimated reachable market, whether the qualification criteria can actually be
evaluated from available data, and the best discovery entry point. A clear *not enough market* is a successful
outcome — it prevents a quarter spent on a list that was never going to convert.

## One channel per prospect at a time

A prospect reached by email and connected to on a social platform in the same week reads as a swarm. Arbitrate the
channel per prospect and record which one was chosen.

## Suppression is checked before, not after

Screen against the suppression list, existing pipeline and prior contact history before a record enters the list —
not after the campaign is built. Contacting an existing client as a cold prospect is the most expensive error this
workflow can make.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Public company and contact sources, directory and map data, existing pipeline records, suppression lists |
| Analyze | Market-size estimate, qualification scoring, deduplication and channel arbitration, deliverability screening |
| Draft | A market verdict, a qualified list with the reason each record passed, and sequence copy |
| Send with approval | Uploads to the sequencing tool as a **draft campaign** and stops. Activation is a separate approval |
| Destructive | None |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A market verdict with the reasoning, a qualified prospect list with per-record justification, prepared sequence copy, and a draft campaign awaiting activation.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `SEGMENT_PLACEHOLDER` | Target segment |
| `GEO_PLACEHOLDER` | Geography policy |
| `APPROVER_PLACEHOLDER` | Named approver |