Use case · Sales

Compose a specialist agent for every phase of outbound.

One agent picks accounts, another researches signals, another writes email campaigns, another handles follow-ups, another triages replies — every agent ICP-loaded, every send gated, every reply tracked. You define the pack you actually need.

Best fit for · Outbound teams running specialist agents across prospecting, research, email campaigns, and follow-ups
Request beta accessSee an example pack
vs Lindy →
packwolf.app · Outbound pipeline
Live
Week 17 · Outbound142 ACTIVE PROSPECTS · 6 STAGES · ICP-LOADEDDAYWEEKPIPELINESDMANAGERSDR LeadAPPickerSELECTING 50RSResearcherRESEARCHING 24SWSequencerDRAFTING 18RTReply TriageTRIAGING 6TO AE3 hot repliesSELECTED50 · BY PICKERRESEARCHED24 · BY RESEARCHERSEQUENCED18 · BY SEQUENCERSENT22 · BY SEQUENCE ENGINEREPLIED14 · BY REPLY TRIAGEBOOKED → AE6 · BY ACCOUNT EXECAcme RoboticsSERIES B · Q1APOWNSACTIVEGlobex Logistics+VP ENGAPOWNSACTIVESoylent FoodsHIRING SDRSAPOWNSACTIVEInitechNEW PRODUCTAPOWNSACTIVEPied PiperFUNDED MARRSOWNSACTIVEHooliENG LEADERSHIPRSOWNSACTIVEStark IndustriesOPEN DATA ROLERSOWNSACTIVEWayne EnterprisesPRODUCT LAUNCHRSOWNSACTIVECyberdyneDRAFTED TUESWOWNSACTIVEApertureDRAFTED WEDSWOWNSACTIVEBlack MesaDRAFTED WEDSWOWNSACTIVETyrell CorpT1 SENT · D2SEOWNSWARMWeyland-YutaniT1 SENT · D4SEOWNSCOLDMassive DynamicT2 SENT · D6SEOWNSWARMOceanicT1 SENT · D1SEOWNSACTIVESkynet AIHOT · MEETING?RTOWNSHOTUmbrella CorpSOFT PASS · Q3RTOWNSWARMVandelayHARD PASSRTOWNSCOLDPendant PubTHU 2PM W/ AEAEOWNSBOOKEDKramericaFRI 11AM W/ AEAEOWNSBOOKEDSTAGE OWNERAPPICKERRSRESEARCHERSWSEQUENCERSESEQUENCE ENGINERTREPLY TRIAGEAEACCOUNT EXECSTATEACTIVEWARMHOT REPLYCOLD / PASSBOOKED
An example outbound pipeline run by an AI sales pack. SDR Lead gates the first batch; specialist agents own each phase; ICP rubric loads into every agent. Yours can look different — you define the agents and the cadence.
What the pack does

Five concrete tasks.

  1. 01

    Specialist agents for every phase of outbound.

    Compose the pack you need: a Picker for weekly account selection, a Researcher for per-account signals, a Sequencer for email campaigns, a Reply Triage for follow-ups and qualification. Add or drop specialists as your motion changes.

  2. 02

    ICP loads into every agent.

    An ICP custodian (or your ICP memory) holds the rubric: firmographics, anti-signals, scoring weights. Every other agent — Picker, Researcher, Sequencer, Reply Triage — loads it before acting. Bad-fit accounts drop out before any outreach goes out.

  3. 03

    Personalize email campaigns with real context.

    Sequencer writes the first-touch using what Researcher found — recent funding, hiring posts, product launches. Per-prospect memory keeps later messages aware of earlier ones, so 'just following up' never reads as canned.

  4. 04

    Follow-ups timed by signals, not the calendar.

    A follow-up specialist (or your sequence engine) paces touches against the lead's last engagement signal — open, click, reply — not 'second touch in 24 hours' regardless of context. Re-engagement only fires on a new signal.

  5. 05

    Hot replies route to humans, the rest stays auto.

    Reply Triage classifies every inbound reply: hot ones route to your AE with a brief, soft passes update memory for next quarter, hard passes kill the sequence. The pack optimizes for meetings booked, not emails sent.

How a team uses this

Setup once, then watch it run.

Concrete operator setup, the phases the pack moves through, and where you stay in the loop.

Compose your pack: pick the agents your team needs (lead, picker, researcher, sequencer, reply-triage, analyst, etc).
Author your ICP rubric — firmographics, anti-signals, scoring weights, do-not-contact list — as durable memory every agent reads.
Connect your CRM (read + write on accounts, contacts, opportunities, notes) and your email send domain with proper SPF/DKIM.
Set the SDR Lead (or AE) as the first-batch send-approver. Loosen the gate as confidence in the pack builds.
Phase 1

Account selection

Picker scans target accounts against the ICP rubric, dedupes against open opps in the CRM, and assembles this week's batch. Anti-signals knock disqualified accounts out before any work happens.

Phase 2

Per-account research

Researcher pulls one real signal per account — funding round, product launch, leadership change, hiring posts. Hooks live in per-prospect memory for later follow-ups.

Phase 3

Email campaign + send

Sequencer drafts a personalized first-touch using the signal. SDR Lead gates the first batch's send. Sequence engine paces follow-ups so nothing fires on a federal holiday or in the wrong time zone.

Phase 4

Reply triage + follow-up

Replies stream back. Reply Triage classifies — hot routes to AE, soft pass updates memory for next quarter, hard pass kills the sequence. CRM stays in sync; every state change lands in audit.

Phase 5

Pipeline report

Analyst pulls reply rate, meeting-book rate, pipeline movement against the ICP. Calls out which signals worked. Proposes next week's ICP refinements back to the rubric.

PHASE 01Account selectionPHASE 02Per-account researchPHASE 03Email campaign + sendPHASE 04Reply triage + follow-upPHASE 05Pipeline reportSubmitApprovedHotRefineSDR teamSETS WEEKLY TARGETICP rubricPROCEDURAL MEMORYPickerSELECTS BATCHCRMDEDUPE + STATEAccount batchTHIS WEEKResearcherONE REAL SIGNALMarket signalsFUNDING · HIRING · LAUN…Signal notesPER ACCOUNTSequencerDRAFTS CAMPAIGNSDR LeadFIRST-BATCH APPROVERSend approvalTHREE-TIERSequence enginePACED FOLLOW-UPEmail sendYOUR DOMAINOn replyINBOUNDReply TriageCLASSIFIES + ROUTESAccount ExecOWNS HOT REPLIESCRM SyncSTATE + NOTESPipeline AnalystWEEKLY RECAPWeekly reportWINS + ICP TWEAKS
An example pack + workflow

Your pack, your workflow.

Workflows are markdown that reference the roles in your pack. Below is one example shape - yours can have different agents, different steps, different cadence.

  1. Step 01Monday

    Account selection

    ReceivesWeekly target + ICP rubric
    APPickerICICPCRCRM Sync

    Picker scans target accounts against the ICP, dedupes against open opps, assembles this week's batch. Anti-signals knock accounts out cleanly.

    Hands offThis week's account batch
  2. Step 02Mon-Tue

    Per-account research

    ReceivesAccount batch
    RSResearcherMSSignals

    Researcher pulls one real signal per account - funding round, product launch, leadership change. Hooks live in per-prospect memory for follow-ups.

    Hands offSignal notes per account
  3. Step 03Tue-Thu

    Sequence + send

    ReceivesSignal notes
    SWSequencerICICPSDSDR Lead

    Sequencer drafts a personalized first-touch referencing the signal. Sequence engine paces follow-ups; SDR Lead gates the first batch's send.

    Hands offSent sequences (with cadence)
  4. Step 04Ongoing

    Reply triage

    ReceivesInbound replies
    RTReply TriageCRCRM Sync

    Reply Triage classifies: hot replies route to AE, soft pass updates memory for next quarter, hard pass kills the sequence. CRM stays in sync.

    Hands offQualified opportunities + CRM state
  5. Step 05Friday

    Pipeline report

    ReceivesWeek's pipeline data
    PAAnalyst

    Analyst pulls reply rate, meeting-book rate, pipeline movement. Calls out which signals worked. Proposes next week's ICP refinements.

    Hands offWeekly report → feeds next week's ICP + selection
Example workflow · 5 steps · weekly handoff chain
Workflow · markdownExample outbound cycle
# Example weekly outbound cycle
# Workflows are markdown — yours can swap agents,
# add phases, change the cadence, or define a
# different qualification rubric.

Match: tasks labelled "outbound"
Required tools: web_search, http_request, email_send, crm
Required skills: prospect-research, icp-qualification, sequence-craft

## ICP context — always-on
Every agent in this pack loads from your ICP memory before acting:
firmographics, anti-signals, scoring weights, last-quarter wins,
do-not-contact list. No agent runs without ICP context.

## Step 1 — Account selection (Monday)
Picker pulls target accounts against the ICP, dedupes against open
opps in the CRM, and assembles this week's batch. Anti-signals
knock disqualified accounts out cleanly.

## Step 2 — Per-account research (Mon-Tue)
Researcher pulls one real signal per account — funding round,
product launch, leadership change, hiring posts in target roles.
Hooks live in per-prospect memory for later follow-ups.

## Step 3 — Email campaign + send (Tue-Thu)
Sequencer drafts a personalized first-touch referencing the signal.
SDR Lead approves the first batch's send; later batches loosen as
confidence builds. Sequence engine paces follow-ups so nothing
fires on a federal holiday or in the wrong time zone.

## Step 4 — Reply triage + follow-ups (ongoing)
Reply Triage classifies replies: hot ones route to the AE with a
pre-call brief, soft pass updates memory for next quarter, hard
pass kills the sequence. CRM stays in sync; every state change
lands in the audit log.

## Step 5 — Pipeline report (Friday)
Analyst pulls reply rate, meeting-book rate, pipeline movement.
Calls out which signals worked and which didn't. Proposes next
week's ICP refinements back to the rubric.

Approvals: SDR Lead signs off on the first batch monthly. Hot
replies require a human AE to take the meeting.
Built on
CapabilityMemoryCapabilityWorkflowsCapabilityHeartbeatsCapabilityTools
The ROI

A specialist agent for every phase of outbound — composable, ICP-loaded, gated where it matters, with no missed follow-ups at five o'clock on a Friday.

Common questions

Things teams actually ask.

No. The shape of an outbound team is different at every company — some only need a picker + sequencer, others want a dedicated reply-triage agent, a separate AE-handoff agent, a competitor-signals agent, an LinkedIn-specialist agent. PACKWOLF lets you compose the specialists you actually need. The example here is one shape, not the shape.

Related use cases
Use caseMarketing automationHands off the qualified content audienceUse caseCustomer serviceInbound triage with the same pack patternUse caseRecruitingSame pack shape, different ICP

Run this pack on your team's work.

Closed-beta cohorts are small. Tell us about your work and we'll configure the pack for what you actually do.

Request beta access