Outbound Engine

@di-atomic44 packages on opvs.ai
SkillBetacommunication#cold-email#outbound
v3.0.1Updated 3 Nov 20268 installs1 video1 article

The outbound EMAIL brain (guidance-only) — mode-aware. Resolves the AUDIENCE first (does the recipient know you?): that picks the infrastructure, which dictates the format. cold-volume → smartlead (warmup + mailbox round-robin) · cold-agent → AgentBoard, one card = one lead, spidermail sends while smartlead only WARMS · broadcast → opt-in audiences via the house notification layer. Cold: pick 1 of 14 copywriting frameworks + tone + CTA + personalization, write the multi-touch ladder with per-email anti-repetition, 5 scripts gate it. Broadcast: author one issue against the house invariants behind a human [TEST]→approve gate. Provisions the boards (campaign · outreach · deals). No callable API — the agent's own LLM composes following SKILL.md, anchored on 47 registry items + 13 references + 12 recipes. It never sends: it delegates to @di-atomic/smartlead, @spideriq/spidermail and @spideriq/mcp-admin. GDPR/CAN-SPAM-aware.

Most outbound tooling makes you pick a tool first and find an audience second. That is backwards, and it is how people burn a sending domain. So in 3.0 outbound-engine asks one question before it writes a word: does the recipient know you? That answer decides whether your reputation is at risk, which decides the infrastructure, which decides the format. Cold and high volume goes to smartlead, where warmup and mailbox rotation exist. Cold and high value goes to a board where the agent writes each lead its own message and sends via spidermail — with smartlead demoted to warming the mailboxes. Opt-in subscribers go to your real domain as a broadcast, where the risk is not spam filters but complaints. Each mode gets its own rules and its own QA gate, because the rules that make a cold ladder good would reject a perfectly correct newsletter. It provisions the boards, drafts everything onto cards, and stops at an approval column you own. It never sends — it hands the verified payload to smartlead, spidermail, or your broadcast layer.

Outbound EngineFree · Claude, Codex, Antigravity

Features6

01Picks the right tool

Resolves the audience first, then the infrastructure — never the other way round

02Framework fit

Picks the copywriting framework for your ICP — 1 of 14, with the reasoning

03The full ladder

Writes the whole follow-up ladder — a different angle every touch, no repeats

04Per-mode QA gates

Six verifier scripts that refuse to grade work from the wrong mode

05Your approval board

Provisions the boards with human approval gates you own before anything sends

06Drafts, then delegates

Hands the send to smartlead, spidermail or your broadcast layer — it never sends

Videos1 video

Demo

Outbound Engine · Demo video

Demo · SpiderMedia

Articles about Outbound Engine1 article

More like this

Shares a tag or category

More from @di-atomic

43 packages