Amplio internal · Deck 11 · Outreach engine
Internal · Outreach engine

From a cold name to a real reply.

The engine finds the humans behind a company, throws out every address that is not a real mailbox, reaches the survivors as Daragh or Jule from a warmed domain, and turns each reply into a hot lead within minutes. It used to stop at "we found a lead." Now it carries that lead all the way to a conversation.

7
Phases · A·B·C·D·E·V·Z
1
Run a day · 11:00 local
0%
Bounce · verified sends only
4
Reply sweeps per day

/ Amplio internal · 2026 · use → to advance

Internal · share with the team · do not forward
Amplio internal · Deck 11 · Outreach engine

/ 01 — The loop

Five stages. One conveyor belt.

Discovery feeds a scrub gate. The gate feeds the send. The send feeds the reply sweep. Every step writes to the dashboard so you watch the whole thing move from one screen.

/ 01

Discover — phases A to D

Crawl hiring signals and ICP fit, then find the real decision makers inside each company.

253
leads in Attio today
/ 02

Scrub gate — phase E0, the heart of it

Dedup, suppression, role filter and a real mailbox probe. Nothing risky gets through.

5
checks every send clears
/ 03

Send — phase E

A personalised first touch as Daragh or Jule, from a warmed domain, capped for safety.

8
sent · first live cohort, June 2026
/ 04

Reply sweep — every four hours

Detect replies, halt the cadence, draft the answer, ping the team in Slack.

1
reply already, first batch
/ 05

Dashboard — ops.ampliodata.io

Sent, replies, bounces and hot leads, live from the send ledger.

1
screen to watch it move
outreach-cycle · sister to deploy-cycle · daily-intelligence · weekly-reports
Amplio internal · Deck 11 · Outreach engine

/ 02 — A day in the life

Seven phases. One run. Every day.

Phases A and B crawl for new companies in parallel. C and D enrich them and find the humans. E scrubs and sends. V audits the writes and Z drafts the one summary email that lands in hello@ by 11:15.

~16 min
One run · Opus subagents
50
Top cos for contact discovery
5
Contacts max per company
11:15
Summary email in hello@
PhaseWhat runsLane
ACrawl LinkedIn + job boards — public profile snippets and hiring posts. UK · DE · NL · ES.parallel
BCrawl ATS careers — 8 applicant systems direct. UK + DACH. EN + DE. Hiring is +15.parallel
CEnrich the stubs — fill tier, persona and tech fields so no record shows a dash.backfill
DFind the humans — five persona searches per company, Clay style. Names, titles, guessed emails.top 50 cos
EScrub + send — five gate checks, then Touch 1 out as Daragh or Jule.the new lane
V·ZVerify + email — seven audit checks, refresh the dashboard, draft one summary.by 11:15
Phase registry: outreach-cycle/phases.md · add a strategy = append one row
Amplio internal · Deck 11 · Outreach engine

/ 03 — The scrub gate

Nothing leaves without clearing five checks.

An early send showed "Delivered" yet reached no one: the domain was a catch all that accepts every address and quietly drops the unknowns. So the gate now probes a random fake address first. If that is accepted too, the guess is thrown out. Verify the mailbox, never trust the receipt.

/ C1

Dedup

The send ledger is the source of truth. Nobody gets the same touch twice, ever, across runs.

/ C2

Suppression

Every client, every past contact, every unsubscribe and bounce is blocked automatically.

/ C3

Role filter

No info@ or hello@ inboxes. They kill reply rates and invite spam reports.

/ C4

Real mailbox — the key one

An SMTP probe confirms the address exists and the domain is not a catch all. Unverifiable guesses are dropped.

~1 in 10 survives
/ C5

One per company

Touch 1 goes to a single best contact, highest intent first. No five emails into one small team.

Live sample: 38 probed · 4 made it through · 0% bounce — the gate is working

scrub.py owns the gate · send.py owns the irreversible send + ledger + suppression
Amplio internal · Deck 11 · Outreach engine

/ 04 — The send

Warmed, human, and compliant by default.

A company posting a data analyst role has already decided it needs this expertise. We open problem first, never salesy: here is a faster, lower commitment path.

2
senders · one per contact, kept across every touch

As Daragh or Jule

Each contact is assigned one sender and keeps it across every touch. Replies route to Daragh, Jule and hello@ so nothing slips.

70
a day at full ramp · 2,100 a month cap

A warmed domain, capped in code

Volume climbs as the domain ages, up to 70 a day — 70% of the plan ceiling. Every send goes from send.ampliodata.io, never the main domain, so nothing we do here can touch client mail.

0·3·10·17
days · the 3·7·7 benchmark

Four soft touches

First touches go Tuesday to Thursday, 08:00 to 11:00 local, where reply rates run highest.

3%
bounce hard stop

One click opt out

Every email carries a one click unsubscribe and a real postal address. Bounces and opt outs suppress instantly.

Resend · send.ampliodata.ioHiring is the trigger+37% ROAS lift · the proof story
send-config.json owns the ramp, cadence and send window · scrub gate runs first, every time
Amplio internal · Deck 11 · Outreach engine

/ 05 — The loop closes

Every reply becomes a hot lead in minutes.

1

Attio holds the canonical record

Every qualified lead lands here, tagged with market and discovery source. Contacts live inside each company. An Outreach Step kanban tracks New, Researching, Touch 1 to 4, Replied, Meeting booked.

3 strategy lists10 kanban values
2

ops.ampliodata.io is the single screen

The Leads tab carries filter chips for strategy, market, tier and score, plus the outreach send card reading live from the ledger: sent, replies, bounces, hot leads.

Refreshed every 4h
3

The sweep detects, halts, drafts, alerts

The moment someone replies, the sequence pauses, a reply is drafted from their own audit findings, and a hot lead hits Slack with the snippet and a link to the thread.

Four sweeps a day

Three places hold the lead — Attio · the dashboard · Brain Dump for the morning tick

ops.ampliodata.io · Cloudflare Worker + KV · Cloudflare Access gated · reply detection reads hello@
Amplio internal · Deck 11 · Outreach engine

/ 06 — What the team does

Your part is five minutes a day.

Open Brain Dump, tick the borderline leads worth keeping. Open ops.ampliodata.io and read the send card. When a reply lands, the draft is already written from the prospect's own audit findings: read it, make it yours, send. The cycle does the rest.

01 · Discover A–D 02 · Scrub gate E0 03 · Send as Daragh or Jule 04 · Reply sweep ×4 a day 05 · ops.ampliodata.io
Open the leads dashboard

/ Four weeks of run stats, then the schedule tightens · next lanes: intent · directory · funding

Questions → Walter · source: outreach-cycle/SKILL.md + outreach-send/SKILL.md