Outreach Sequence Builder

Overview

Creates multi-touch outreach sequences for small businesses. Each sequence combines email, LinkedIn, and phone scripts with personalization, timing logic, and conditional branching. Pulls context from lead-prospector when available and stages drafts for sending.

Workflow

<Definition - Standard Cadence Template>

<Definition - C-Suite Adjustments> If prospect is C-suite or very senior at a large enterprise:

• Reduce total touches (5 max instead of 7)
• Wider spacing between touches (3-5 days instead of 2-3)
• Suggest alternative entry points: executive assistant, VP-level champion, mutual connection, warm introduction
• Set expectations: lower response rates, longer cycles
• Lead with board-level insights, not product features </Definition - C-Suite Adjustments>

<Definition - Conditional Branching>

<Definition - Delivery Modes>

<Definition - Skill-Ready Outputs> Two formatted blocks always included:

1. Active Sequence Tracking table (for follow-up-cadence): Contact, Company, Current Touch, Next Send Date, Status
2. Outreach Activity table (for deal-pipeline-manager): Prospect, Touches Sent, Last Response, Next Action, Status </Definition - Skill-Ready Outputs>

<Workflow - Build Sequence description="Create a complete multi-touch outreach sequence for one or more prospects." tools=[web_search, url_fetch, run_python, file_write, open_in_session_tab] triggers=["write outreach emails", "create a sales sequence", "draft cold emails", "build a cadence", "write LinkedIn messages", "cold outreach for"]

1. [Agent] Check for lead-prospector context in current session. If available, auto-load: prospect company, contact name + title, personalization hooks, warm/cold status. Validate: If data exists, at least company + contact + 1 hook loaded. If fails: Skip. Proceed to step 2 to gather context manually.

2. [Decide] Is context sufficient (prospect name/company, user's product/service, at least 1 differentiator)?

   • Yes (from lead-prospector or user): Confirm briefly. "Proceeding with [contact] at [company]. Top hook: [hook]. Correct?"
   • Partially: Ask only what is missing (tone preference, specific offer for this prospect).
   • No: Ask "What do you sell, who is the prospect (name + company), and what makes you different from alternatives?" Validate: Have prospect details, product/service, and at least one differentiator. If fails: Cannot write effective copy without differentiator. Re-ask.

3. [Agent] Research the prospect if personalization hooks are thin (fewer than 2). Search for recent LinkedIn posts, company news, job postings, tech stack. If hooks already loaded from lead-prospector and recent (< 90 days), skip. Validate: At least 2 specific, verifiable personalization hooks available. If fails: Ask user for any known details. Note limited personalization.

4. [Agent] Design sequence architecture. Apply <Definition - Standard Cadence Template> adjusted for: prospect seniority (apply <Definition - C-Suite Adjustments> if applicable), industry response patterns, number of touches requested. Output cadence map: Day, Channel, Purpose, Angle per touch. Validate: Timing is appropriate for seniority. Channels are diverse. Total touches match request or adjusted default. If fails: Fall back to standard 7-touch template unchanged.

5. [Agent] Write complete copy for every touch. For Touch 1: write 2 variants (A: insight-led hook, B: direct value prop). For all others: one version each. Apply copy rules: under 125 words per email, subject lines under 6 words, each touch adds new value, personalization references real details. Validate: Every email under 125 words. Every subject under 6 words. No touch says "just following up." Each touch adds distinct new value. If fails: Rewrite offending touches. If copy is too generic, ask user for more prospect context.

6. [Agent] Add conditional branching per <Definition - Conditional Branching>. Write specific response emails for: positive reply (meeting confirmation), "not now" (acknowledge + set reminder), negative (graceful exit). Validate: All 6 trigger scenarios covered with specific copy or action. If fails: Include basic branch logic (reply = exit, no reply = continue).

7. [Ask user] Present complete sequence: cadence map, A/B variants for Touch 1, full copy for all touches, conditional logic. Ask which variant to use and confirm ready to deliver. Validate: User approves sequence or requests edits. If fails: Revise per feedback.

8. [Agent] Deliver per <Definition - Delivery Modes>. If email tools are available, stage Touch 1 as ready-to-send and remaining touches as scheduled drafts. If unavailable, format full sequence in chat. Validate: Delivery completed in user's preferred mode. If fails: Display full sequence as formatted text.

9. [Agent] Produce skill-ready outputs per <Definition - Skill-Ready Outputs>. Offer to save as reusable template: "Save this as a template? (e.g., 'SEO Agency to Dentist Owner')" Validate: Both skill-ready output blocks present. If fails: Add missing outputs.

</Workflow - Build Sequence>

<Template - Sequence Output>

Outreach Sequence: [Contact] at [Company]

Cadence Map:

Touch 1 - Variant A (Insight-led): Subject: [under 6 words] [Body under 125 words]

Touch 1 - Variant B (Direct value prop): Subject: [under 6 words] [Body under 125 words]

Touch 2-N: [Full copy per touch]

Conditional Branching: [Response handling per scenario]

Active Sequence Tracking (for follow-up-cadence)

| Contact | Company | Current Touch | Next Send Date | Status |

Outreach Activity (for deal-pipeline-manager)

| Prospect | Touches Sent | Last Response | Next Action | Status | </Template - Sequence Output>