B2B Outbound Engine — ICP to Ready-to-Send Sequences (AI) avatar

B2B Outbound Engine — ICP to Ready-to-Send Sequences (AI)

Pricing

$600.00 / 1,000 account packageds

Go to Apify Store
B2B Outbound Engine — ICP to Ready-to-Send Sequences (AI)

B2B Outbound Engine — ICP to Ready-to-Send Sequences (AI)

The whole outbound motion in one run: describe your ideal customer, get a prioritized list of in-market companies — each with an intent score, a pre-call brief and a ready-to-send multi-touch email sequence. Orchestrates the full fuze B2B suite.

Pricing

$600.00 / 1,000 account packageds

Rating

0.0

(0)

Developer

Fredrik Hansson

Fredrik Hansson

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 hours ago

Last modified

Share

The whole outbound motion in one run. Describe your ideal customer (and/or paste a company list), say what you sell, and this Actor hands back a prioritized set of account packages — each company with a buying-intent score, a one-page pre-call brief and a ready-to-send multi-touch email sequence. It is the capstone of the fuze B2B suite: one call orchestrates discovery, intent scoring, account research and sequence writing, then assembles everything into an account package sorted highest-intent first.

You bring your ICP. It hands back a pipeline you can work today. It never sends — you review the sequences and send from your own tool, so you stay in control of consent, volume and deliverability.


The flow

ICP / domains / dataset
│
▼
┌───────────────┐ discover ┌──────────────┐ score ┌───────────────┐
│ RESOLVE │ ───────────▶ │ INTENT │ ─────────▶ │ filter by │
│ companies │ │ RADAR │ │ minIntent │
└───────────────┘ └──────────────┘ └───────┬───────┘
│
┌──────────────────────────────────────────────┤
▼ ▼
┌──────────────┐ ┌───────────────┐
│ PRE-CALL │ │ EMAIL │
│ BRIEF │ │ SEQUENCE │
└──────┬───────┘ └───────┬───────┘
└───────────────────┬──────────────────────────┘
▼
PRIORITIZED ACCOUNT PACKAGES
(intent score · brief · talking points · sequence)
  1. Resolve companies. Start from an icp (the engine discovers matching companies for you), a domains list, a chained datasetId, or any mix of the three.
  2. Score buying intent for every company and keep only those at/above your minIntentScore.
  3. Write a pre-call brief and a ready-to-send email sequence for the companies that pass.
  4. Assemble one account package per company, sorted by intent — your prioritized call sheet.

What you get per company

For every packaged company you get a complete account package:

  1. intentScore (0–100), stage (cold / aware / warming / in-market) and a recommendation (prioritize / nurture / skip) — so you work the hottest accounts first.
  2. keySignals — the concrete buying signals the engine observed, plus icpFitScore and topTechnologies.
  3. outreachAngle and personalizedHook — the sharpest way in, grounded in real company data.
  4. briefMarkdown — a clean one-page pre-call brief, plus talkingPoints and discoveryQuestions for the call.
  5. sequence — a ready-to-send multi-touch cold email cadence (touches[] with step, day offset, subject, body and purpose) and sequencePlain, the whole cadence as copy-paste plain text.
  6. executiveSummary — a two-sentence top-of-package summary tying intent + brief + why-now (OpenAI gpt-4o-mini).
  7. sourcesUsed — exactly which organs fired for this company, so you can trust the data.

Three ways people use it

  • Founders running outbound solo — go from an ICP description to pipeline in one run: ICP to pipeline, AI outbound automation, no stitching five tools together. Describe who you want, get in-market companies with buying intent, briefs and sales sequences ready to send.
  • SDR / sales teams — feed a target account list and get a prioritized call sheet: intent scores, pre-call research and end-to-end prospecting in one place, so reps spend time selling instead of researching and writing.
  • Agencies running outbound for clients — point it at a client's ICP, get a full outbound motion per account (intent → brief → sales sequences) you can hand over or run on their behalf. One repeatable, billable workflow across every client.

How the orchestration works

This is a super-actor: it runs each organ once across all companies and degrades gracefully if any organ returns nothing.

StageOrganWhat it contributes
Discoveryfuze/b2b-lead-list-builderTurns your ICP into a ranked list of matching company domains.
Intentfuze/b2b-intent-radarScores buying intent, surfaces signals, outreach angle and personalized hook (enriches internally).
Brieffuze/b2b-account-briefOne-page pre-call brief, talking points, discovery questions, cold opener.
Sequencefuze/b2b-cold-outreach-sequencerReady-to-send multi-touch cold email cadence.

Each organ toggle (discover, scoreIntent, writeBrief, writeSequence) defaults to on. Turn any of them off to run a lighter, cheaper motion.


Input

FieldTypeNotes
icpstringIdeal customer description. With discover on, triggers company discovery.
domainsarrayKnown company domains / URLs / emails to start from (used with or instead of the ICP).
offeringstringRequired. What you sell — drives discovery, intent, brief and sequence.
senderNamestringRequired. Signs the email sequences.
senderCompanystringRequired. The company you reach out on behalf of.
datasetIdstringOptional. Read company domains from a prior run's dataset (no-code chaining).
datasetFieldstringWhich dataset field holds the domain/URL (auto-detects domain, website, companyDomain, url).
maxCompaniesintegerMax companies to package. Default 15, max 100. Keep modest — this is a heavy run.
minIntentScoreintegerOnly package companies at/above this intent score (0–100). Default 0.
numberOfTouchesintegerEmails per cadence (last is a breakup). Default 4.
discover / scoreIntent / writeBrief / writeSequencebooleanOrgan toggles, all default true.
modelstringModel for the executive summary. Default gpt-4o-mini.

Provide at least one of icp (with discovery on), domains, or datasetId.

Minimal input — from an ICP

{
"icp": "Mid-sized Shopify skincare brands in the US",
"offering": "We sell a SOC2 compliance automation platform for SaaS companies.",
"senderName": "Fredrik Hansson",
"senderCompany": "Fuze",
"maxCompanies": 10
}

Minimal input — from a company list

{
"domains": ["stripe.com", "notion.so"],
"offering": "We sell a SOC2 compliance automation platform for SaaS companies.",
"senderName": "Fredrik Hansson",
"senderCompany": "Fuze",
"maxCompanies": 2
}

Output example

One record per packaged company (sorted highest intent first):

{
"domain": "notion.so",
"companyName": "Notion",
"executiveSummary": "Notion is a fast-scaling productivity SaaS whose recent enterprise push and new security hires signal active SOC2 and compliance pressure. Lead with how your platform automates SOC2 evidence collection so their lean security team ships audits without slowing product.",
"intentScore": 78,
"stage": "in-market",
"recommendation": "prioritize",
"icpFitScore": 85,
"keySignals": [
"Hiring for a security/compliance role",
"Expanding into enterprise plans with security requirements"
],
"outreachAngle": "Position SOC2 automation as the way their lean security team keeps up with enterprise demand.",
"personalizedHook": "Saw Notion is leaning harder into enterprise — SOC2 evidence collection is usually the bottleneck there.",
"topTechnologies": ["AWS", "Segment", "Cloudflare"],
"talkingPoints": [
"Enterprise expansion raises the bar on security proof",
"Automating evidence collection frees the security team"
],
"discoveryQuestions": [
"How are you handling SOC2 evidence collection today?",
"Who owns compliance as you move upmarket?"
],
"oneLineOpener": "Saw Notion is leaning harder into enterprise — SOC2 evidence collection is usually the bottleneck there.",
"briefMarkdown": "# Account Brief — Notion\n**Domain:** notion.so · **Industry:** Productivity software ...",
"sequence": [
{ "step": 1, "dayOffset": 0, "channel": "email", "subject": "SOC2 without the fire drill", "body": "Hi — saw Notion ...", "purpose": "intro + value" }
],
"sequencePlain": "— Email 1 (Day 0) —\nSubject: SOC2 without the fire drill\n\nHi — saw Notion is moving upmarket...\n\n— Email 2 (Day 3) —\n...",
"sourcesUsed": ["b2b-intent-radar", "b2b-account-brief", "b2b-cold-outreach-sequencer"]
}

Pay-per-event pricing

EventPriceCharged when
account-packaged$0.60Once per company turned into a complete outbound package (intent + brief + sequence).

One account-packaged charge bundles four orchestrated sub-actor runs (discovery, intent, brief, sequence), so it is cheaper than buying each separately. The run logs its OpenAI token usage and estimated cost at the end, so the event price always stays safely above model cost.


Compliance

This Actor generates drafts only — it never sends anything. You review each sequence and send it from your own email tool, so consent, volume and deliverability stay entirely in your hands. The sequences and briefs are grounded only in data the organs actually gathered; the AI is instructed never to invent facts, customers or news.


Setup

The engine orchestrates fuze-owned sub-actors (no extra credentials needed) and makes one short OpenAI call per company for the executive summary. Set the environment variable / secret OPENAI_API_KEY on the Actor. Without it, every organ still runs and every package still ships — only executiveSummary is left empty.


Use it from an AI agent (Apify MCP server)

This Actor is available through the Apify MCP server, so AI agents (Claude, ChatGPT, or anything that speaks MCP) can call it as a tool — hand it an icp or domains plus your offering, senderName and senderCompany, and read back ready-to-run account packages — with no custom integration code.


Run it locally

npm install
# put your input in storage/key_value_stores/default/INPUT.json
export OPENAI_API_KEY=sk-... # optional, enables the executive summary
apify run -p

Chain it

This is the capstone that runs the whole suite — one call fans out to discovery, intent, brief and sequence organs and assembles the result. You can also run any organ on its own, or chain them manually via each Actor's datasetId field. Point the engine at a prior run's dataset (datasetId) to start from companies another Actor found.