Signal-based outbound

Reach accounts in the week they show a buying signal

The machine watches your ICP accounts for signals. When one fires, it researches the account, writes a reason to reach out and queues a sequence for approval.

Send a scoping brief

Lfrom $8,000 · £6,400

Indicative price. You get a fixed quote after the brief.

Trigger

A tracked account raises a round, posts a sales or RevOps job, hires a new exec, or visits your pricing page.

How the signal-based outbound workflow runs

01
List
Account list
Your ICP accounts sit in the database, refreshed each week.
02
Signals
Signal check
Daily jobs check funding, job posts, exec changes and site visits for each account.
03
Enrich
Find the buyer
The waterfall finds the right person and a verified email for the signal.
04
AI research
Research and score
An LLM reads the signal and the account. It writes one line on why now, and a score.
05
Route
Approve
High scores go to Slack for a named person to approve or edit.
06
Send
Send
Approved contacts enter an email or LinkedIn sequence.
07
Report
Report
Replies and meetings write back to the CRM with the signal that started them.

Tools

Crustdata or Apollo for signals and people
LeadMagic or Apollo for verified emails
Claude API for research
Instantly, Smartlead or HeyReach for sends
HubSpot, Salesforce or Attio as the CRM
Slack for approvals

Data in

Your ICP rules
A list of target accounts, or rules to build one
Your offer and 2 or 3 example emails that worked

Data out

A dated signal per account with its source link
A score and a one-line reason per account
Approved contacts in a sequence
Replies and meetings in the CRM

You own

The signal jobs and their schedule
The scoring prompt and its tests
The approval rules
The cost log for each run

Code or Clay?

We build this in code by default, because daily signal checks across many accounts run as direct API calls, with no per-action platform fee. The diagnostic compares both costs at your volume. We can build it in Clay if your team already lives there.

See the GTM tech stack by layer and Clay vs Claude Code.