Outreach
Menu
PricingDocsLog in
Theme
Language
Request access
In closed beta

Run an entire outbound campaign for you

Outreach is a mission console: you give the task, the agent keeps moving, and it pauses where your judgment matters. Not another dashboard full of forms.

01 · Hero

Conversation with the agent

The primary entry point. Agent messages bleed into the page; user messages get a soft surface. Tool activity sits inside the agent's turn — calm, not noisy.

outreach.app/new
⌘K
YO
You · 12:38
Help me reach the CTOs of AI-agent SaaS companies. I want personalised outreach — no template feel. Series A or B, US or EU.
Agent · 12:38

Got it. Before I start the loop, three things I want to align on:

  • Voice: I'll mirror your last 8 LinkedIn posts — direct, slightly dry, no hype words. Override?
  • Volume: ~ 60 prospects / week, sent in batches of 12. Adjustable.
  • HITL: I'll pause for review on anything with sensitive context (layoffs, lawsuits, recent press misses).

I'll discover candidates first, then come back with a sample of 5 for you to react to before I scale.

Agent thinking
Compiling candidate list — checking Crunchbase, LinkedIn, public funding signals, GitHub org activity
prospects.discover(role:cto, stage:A-B, tag:ai-agents)
Reply, or type / for commands…
01 · Hero

HITL — agent waiting on you

The handoff moment must be unmistakable but never blocking. A warm amber halo on the action area, the rest of the page browsable. The agent tells you what it sees and why it stopped.

outreach.app/m/cto-ai-agent-saas
⌘K
M-014Waiting on you
Auto-resume in 4h 22m
Agent · paused

I've drafted the first 12 messages. Two of them touch on a public layoff at the prospect's company — I want you to read those before I send. The other 10 look clean.

JR
Jules Reyes · CTO, Loomwaveflagged · sensitive context
Review needed
Subject

The eval question your last post left open

Hi Jules — caught your post on agent eval drift. The half you didn't write yet — "how do you know your eval is the right eval" — is exactly what we obsess over at Outreach.

I noticed the recent headcount adjustment at Loomwave. Not bringing it up to be glib — just to say the case for "one founder + a tireless agent doing the outreach loop" probably resonates harder this quarter than last.

Worth 15 minutes Thursday or Friday?

1 of 2 flagged·10 unflagged ready to send
How it runs

Three moves

You describe the mission

Say who you want to reach and why in one sentence. Outreach turns it into an agent objective, not a form.

Agent runs the workflow

Discovery, research, personalised drafts, sending, and follow-up all run in one loop, with the timeline visible to you.

You approve key moments

Sensitive context, batch sends, tone changes — the agent stops for your call. HITL is rhythm, not a toggle.

Why a console

Why a console

agent is running

Dashboards show charts. Forms make you fill fields. Drip campaigns make you schedule time. Outreach lets you assign a mission and lets the agent take the rest.

You do not fill prospect data cell by cell, and you do not write blanks into email templates. A one-sentence mission plus a few interruption rules is the interface.

The timeline is the core view. What the agent is doing, where it is blocked, and what decision it needs should feel like watching a teammate's progress, not a BI report.

Console is not decoration. It means you are directing a system that can keep running, not submitting yet another form.

Pricing

Simple. Predictable.

Priced by mission, not by seat. One outbound campaign is one fixed number, no matter how many people on your team review it.