Outbound Prospecting
Boundary
Own sequence architecture, personalization, response handling, and diagnosis. Do not evade channel or jurisdiction rules, fabricate personalization or proof, or optimize opens as the primary outcome. If contact eligibility cannot be verified, do not produce an executable sequence.
Required Inputs
- Target account and buyer criteria
- Verified problem, offer, proof, and permitted claims
- Channels, list source, target jurisdictions, and lawful contact basis
- Applicable consent, suppression, do-not-call, identification, and platform requirements
- Current sequence, volume, reply, positive-reply, meeting, show, and conversion data
Workflow
- Verify list provenance and channel eligibility for each target jurisdiction, including suppression, do-not-call, sender identification, and platform status. Stop and escalate legal uncertainty to qualified counsel before writing executable outreach.
- Choose a single goal and one primary response action.
- Map a short sequence where each touch adds a distinct reason to respond.
- Set personalization depth by account value and available verified evidence.
- Write channel-appropriate touches without pretending a template variable is known.
- Define positive, objection, not-now, unsubscribe, and no-response branches.
- Diagnose from reply, positive-reply, meeting, and downstream quality. Treat opens as directional only.
- Run one-variable tests with a decision date and guardrail metric.
Output
- Target and sequence hypothesis
- Touch-by-touch sequence with response branches
- Evidence and personalization fields
- Measurement and test plan
Quality Gate
- Every claim is supported or qualified.
- Eligibility and list provenance are verified before execution.
- The sequence stops on reply, opt-out, do-not-call status, or suppression.
- No fixed cadence or benchmark is presented as universally optimal.
- Open-rate distortion from mail privacy is acknowledged.
Reference
Read benchmark-safety.md before using external performance ranges.
1---2name: outbound-prospecting3description: Design and diagnose evidence-safe cold outreach sequences across email, phone, and professional social channels. Use when building a prospecting sequence, fixing low reply or meeting rates, choosing personalization depth, or testing channel and message changes.4---56# Outbound Prospecting78## Boundary910Own sequence architecture, personalization, response handling, and diagnosis. Do not evade channel or jurisdiction rules, fabricate personalization or proof, or optimize opens as the primary outcome. If contact eligibility cannot be verified, do not produce an executable sequence.1112## Required Inputs1314- Target account and buyer criteria15- Verified problem, offer, proof, and permitted claims16- Channels, list source, target jurisdictions, and lawful contact basis17- Applicable consent, suppression, do-not-call, identification, and platform requirements18- Current sequence, volume, reply, positive-reply, meeting, show, and conversion data1920## Workflow21221. Verify list provenance and channel eligibility for each target jurisdiction, including suppression, do-not-call, sender identification, and platform status. Stop and escalate legal uncertainty to qualified counsel before writing executable outreach.232. Choose a single goal and one primary response action.243. Map a short sequence where each touch adds a distinct reason to respond.254. Set personalization depth by account value and available verified evidence.265. Write channel-appropriate touches without pretending a template variable is known.276. Define positive, objection, not-now, unsubscribe, and no-response branches.287. Diagnose from reply, positive-reply, meeting, and downstream quality. Treat opens as directional only.298. Run one-variable tests with a decision date and guardrail metric.3031## Output32331. **Target and sequence hypothesis**342. **Touch-by-touch sequence with response branches**353. **Evidence and personalization fields**364. **Measurement and test plan**3738## Quality Gate3940- Every claim is supported or qualified.41- Eligibility and list provenance are verified before execution.42- The sequence stops on reply, opt-out, do-not-call status, or suppression.43- No fixed cadence or benchmark is presented as universally optimal.44- Open-rate distortion from mail privacy is acknowledged.4546## Reference4748Read [benchmark-safety.md](references/benchmark-safety.md) before using external performance ranges.
majesticlabs-dev