Marketing-native AI agent
01Agent — Outbound Automation

Book qualified meetings from the right signals.

AI SDRs ship volume. The Outbound Automation agent ships qualified conversations — signal, fit, timing, hypothesis, draft, approval, learn.

SurfaceEmail · LinkedIn · sequencer · CRM
OutputBriefs · drafts · play attribution
ReviewOperator approves before send
SEO Optimizer

Find 6 high-fit accounts based on today's signals and draft personalized openers.

I'll break this into agent steps and execute with your guardrails.

Browsing
Signal Aggregator
ICP Scorer
Personalization Drafter
Signal AggregatorSonnet 4.6
Working…
ICP ScorerSonnet 4.6

Queued…

Personalization DrafterSonnet 4.6

Queued…

02The harness gap

Claude Code can write the email. It cannot run the play.

Generic agents do not score signals. They do not check ICP fit. They do not remember which plays converted. They do not respect a do-not-contact list. They draft. The harness is the rest.

Personalization without a hypothesis is trivia.
Generic agents
claude.ai · new chat
fresh context
You

Write a cold email for Acme. Make it sound personalized.

acme-research-notes.md· 312 linespasted
Context window 88% full
Claude

Subject: Quick question about Acme's growth plans

  • I noticed Acme is doing great work in your space and wanted to reach out.
  • We have helped similar companies scale their pipeline.
  • Would you be open to a 15-min chat next week?
No rubric. No source policy. No refresh hook. No memory write.
vs.
Metaflow
outbound-automation.run
signals fresh · 6 accounts queued
Play memory loaded — winners persist, retired plays excluded
Signal stack · Acme
hiring growth roleseries fundingtech-change
ICP fit
0.91
Timing
0.88
Hypothesis
0.79
Approval queue · 3 drafts · DNC verified
03Old way vs. agentic way

Static lists and a sequencer vs. one signal-to-play layer.

The list is six months old. The sequencer fires on schedule. Personalization tokens replace relevance. Replies get triaged manually. Plays never retire.

List + sequencer + hope
Apollo · saved list

ICP B · cold · 4,212 contacts

Last refreshed 38 days ago

Outreach · sequence

Step 1 · email

Step 2 · email

Step 3 · LinkedIn

accounts.xlsx

acme · ?

globex · ?

initech · ?

Claude · draft email

"Write a cold email for Acme"

No signal data · no CRM

vs.
One operating layer
outbound-automation.run
signals fresh · 6 accounts queued
Play memory loaded — winners persist, retired plays excluded
Signal stack · Acme
hiring growth roleseries fundingtech-change
ICP fit
0.91
Timing
0.88
Hypothesis
0.79
Approval queue · 3 drafts · DNC verified
Dimension
List + sequencer + hope
One operating layer
Sourcing
Static list. Quarterly refresh.
Real-time signal-led plays, scored before outreach.
Personalization
First-name token, podcast you listened to.
Why this account, this person, now, this offer.
Review
AI writer ships. Operator skims.
Outbound QA scores every draft. Approval before send.
Attribution
Reply rate, open rate.
Play-level: signals + audience + message → qualified conversations.
04The encoded playbook

What replaces volume motion.

Four operating principles. Each one carries a method anchor and a piece of product evidence.

Signals are play inputs, not magic triggers.

A signal only matters when it is fresh, relevant, tied to ICP fit, and strong enough to support a reason to reach out. Treat signal selection as a first-class design step.

Method anchor — Clay-style signal selection

Signal library · top 4
  • hiring growth role14d
  • tech stack change21d
  • series funding30d
  • pricing visit3d
05The operating loop

From signal detected to play memory.

The agent watches signals, scores fit and timing, enriches the account, builds a relevance hypothesis, drafts outreach, runs QA, routes for approval, classifies replies, and writes outcomes to memory.

outbound-automation.run
Continuous loop
InputSignals · ICP · accounts · CRM
OutputQualified conversations · play memory

Each run writes outcomes to memory. The next run starts with the prior decision graph and review boundary already loaded.

Outbound Automation — reliability stack

Production-grade agents need more than a clever prompt. Each layer below is required for governed autonomy.

01
Instructions
A skill.md file scopes mission, inputs, principles, and output contract.
02
Tools
Domain APIs, search, scrapers, CRMs, and platform connectors.
03
Memory
Workflow memory carries context, brand voice, and prior decisions.
04
Evaluations
Quality gates score every output against domain-specific rubrics.
05
Execution trace
Every tool call, decision, and rubric pass is inspectable.
06
Human review
Approval thresholds route risky outputs to operators for sign-off.
07
Feedback loop
Outcomes write back to memory so the next run starts smarter.
06The skill file

What the agent reads before every play.

A versioned, editable operating procedure. The way a senior outbound lead would document their own playbook.
What is a skill file?

Every Metaflow agent is grounded in a domain-specific skill file — a structured operating procedure that defines inputs, workflows, evaluation criteria, anti-patterns, and output contracts.

The skill file is editable, versioned, and inspectable. It is not a hidden prompt.

outbound-automation.skill.md
v1.4.0 · last edited 4d ago
# Mission

Create qualified conversations from real buying signals — not from
list volume.

Signal selection. Fit and timing. Enrichment. Relevance hypothesis.
Governed drafting. Human approval. CRM coordination. Reply
classification. Play memory.

## Optimizes for
- qualified conversation rate per play
- time-to-meeting from signal detection
- play attribution accuracy

## Does not promise
- guaranteed meetings
- "AI SDR" replacing the operator
- set-and-forget outbound at scale
UTF-8 · markdown · 6 sectionsgoverned by run.evals.json
07The quality gate

Drafts are scored before they ever land in an inbox.

The agent does not send. It scores every draft and routes anything below threshold to an operator with the failing element flagged.

outbound_rubric — outbound-automation
run.evals.json

Refusal conditions

Where the agent stops or hands back instead of guessing.

  • Account is on do-not-contact in any source.
  • Signal stale beyond freshness window.
  • Relevance hypothesis incomplete.
  • Audience saturation flagged on the play.
Autonomous
  • Watch signals
  • Score ICP fit and timing
  • Run enrichment waterfall
  • Compose relevance hypothesis
Recommend
  • New play candidates
  • New signal sources
  • Audience expansion within ICP
  • Sequencer cadence changes
Approve
  • New play launch
  • Drafts before send
  • Cross-channel push
  • CRM field overwrite
08What it produces

System evidence, not feature cards.

Five artifacts the agent produces, scores, or maintains. Hover to pause.

Signal library

Signals scored before any outreach.

Audience fit, baseline conversion, freshness window, execution difficulty. Saturated or stale signals retire automatically.

SignalHalf-lifeFitStatus
hiring_growth_role14d0.84Active
tech_stack_change21d0.81Active
series_funding30d0.78Active
pricing_page_visit3d0.72Active
general_award7d0.31Retired
Methodology anchors

Clay-style signal selection

Common signals become noisy. Advantage comes from unique signal selection, strong enrichment, and fast execution.

Signal library scored on freshness, fit, baseline conversion, saturation risk before plays are designed.

UnifyGTM signal-based outbound

Replace static lists with real-time signal-led plays. Start with one strong signal before scaling.

Plays designed first — signal, ICP filter, enrichment, message angle, routing, measurement.

Common Room signal scoring

Signals scored by fit, frequency, baseline conversion, pipeline potential, execution difficulty.

Signal scoring runs before any outreach is composed. Generic activity is filtered out.

ColdIQ relevance discipline

Personalization is a relevance hypothesis: why this account, this person, now, this offer.

The four-question test ships with every draft. Trivia personalization does not pass.

Production-grade agent governance

Serious agents need explicit instructions, evals, traces, human oversight, and stopping conditions.

External actions require human approval. Confidence drives routing. Plays retire on rule, not vibe.

Reforge-style growth loops

Execution should produce learning that improves the next cycle.

Play-level attribution and objection memory persist. Future drafts pre-empt patterns the team already saw.

09Against the field

Not another AI SDR. A governed signal-to-play layer.

Four contenders. One operating layer that compounds. Hover the Metaflow column for product evidence.

Dimension
Claude Code, Cursor

Generic agents in chat windows.

AI SDR products

Volume-led outbound automation.

Outbound agency

Outsourced humans with sequencer access.

Metaflow agent

Agentic operating layer.

SourcingWhatever you paste in.Static lists, bulk enrichment.Whatever the agency supports.
Real-time signal-led plays, scored before outreach.
PersonalizationGeneric prompts, surface tokens.Token-based with light AI rewriting.Variable across SDRs.
Four why-questions answered explicitly per draft.
MemoryResets every chat.Limited, often per-sequencer.Lives in slack and the SDR.
Workflow memory persists plays, retired plays, objections.
AttributionNone.Reply rate, open rate.Meeting volume.
Play-level: signals + audience + message → qualified conversations.
ComplianceUnbounded.Variable.Process-dependent.
DNC enforced. Refusal conditions explicit. Saturation flagged.
10Where it runs

Repeatable plays the agent runs end-to-end.

Each play has the same shape: signal, fit, timing, enrichment, hypothesis, draft, QA, approval, push, classify, learn.

01

Hiring signal play

A target persona is hiring into a function the buyer would build with your category.

Outcome

Drafts grounded in speed-to-hire pressure, scoped to a 90-day mandate.

Hiring signal · Acme

Hired 3 growth roles · 14 days · post-funding

Speed-to-hire pressure · 90-day mandate
01 / 06
11The first session

Design your first signal-led play in one focused session.

A 30-minute working session with a Metaflow operator. We pick the strongest signal you have access to, define the play, score the audience, propose a hypothesis, and outline the approval boundary.

  • 01Scored signal library of the top 5 signals available to you.
  • 02A defined first play: signal, ICP filter, enrichment, message angle.
  • 03Relevance hypothesis template against your top-fit account.
  • 04A written 1-page memo with the next 3 plays we would design.
What you leave with
Signal library · top 4
  • hiring growth role14d
  • tech stack change21d
  • series funding30d
  • pricing visit3d
Hiring signal · Acme

Hired 3 growth roles · 14 days · post-funding

Speed-to-hire pressure · 90-day mandate

A focused diagnostic. No slides. Walk away with a designed play whether or not we work together.