Grow workflow
Signal-Based Outbound: From Buying Signal to First Line
Signal-based outbound means you contact someone because something observable just happened: they were promoted into a buying role, their company posted new sales roles, or they engaged with a post on your topic. The trouble is that no single tool turns that signal into a sent email. A signal tool tells you someone was promoted, but you still cannot reach them without a verified work email. A sending tool is a perfect sender with an empty list. This workflow connects the three jobs, signal detection, enrichment and verification, and sending, then logs every reply in your CRM so the next signal does not hit someone already in a deal.
Typical timeline
3-5 weeks to the first live sequence, mostly set by sending domain warm-up
Stack
Trigify for job-change, hiring and LinkedIn engagement signals · Clay for enrichment, email finding and verification · Instantly for sending, warm-up and reply tracking · Your CRM (Attio, HubSpot or Salesforce) as the system of record · n8n for routing, suppression checks and the CRM sync
What we need to start
- · Your ideal customer profile, specific enough to filter on: roles, company size, markets
- · The two or three signals you believe precede a purchase in your market
- · CRM access, so open deals, customers and opt-outs can be checked before anyone is contacted
- · Sending domains you are willing to warm up, separate from your main domain
How it works
- 01
Pick the signals that matter
There are dozens of observable buying signals across job moves, company growth, tech stack, site visits, engagement, research, public complaints and spending. Most teams wire up one and wonder why nothing improves. We pick two or three that fit how your best customers actually bought, and write down what each one means for the message.
- 02
Detect the signal
The signal tool watches for the events you chose: a promotion into the budget-holding role, a backfill for a role that buys, three new account executive roles posted in a week, a like or comment on a competitor's post. Each event arrives with the person, the company and what happened.
Tools: Trigify
- 03
Make the person reachable
The event feeds a Clay table that finds the work email, verifies it will not bounce, and checks the account against your ICP filters. A name, a title and a company are not an address a sending tool can use. A verified email is.
Tools: Clay
- 04
Check the CRM before anything is sent
n8n checks the contact against the CRM: existing customers, open deals, past opt-outs and anyone a rep is already talking to are suppressed. This check runs again at send time, not only when the list is built, because the CRM changes in between.
Tools: n8n, Attio, HubSpot, Salesforce
- 05
Send with the signal as the first line
The verified email and the trigger event become both the send list and the opening line. The message says why you are writing now, in one sentence, before anything about your product. It goes out from a warmed sending domain inside daily limits, and you approve the templates before volume goes up.
Tools: Instantly
- 06
Log the reply and close the loop
A reply pauses the sequence for that contact and lands in the CRM against the right person and company, so the rep picks it up with the context. Each week we compare which signals produced replies and cut the ones that did not.
Tools: Instantly, n8n
- ✓ Live signal to enrichment to send pipeline
- ✓ Suppression checks against your CRM at list build and at send time
- ✓ Approved sequence templates that open with the signal
- ✓ Reply logging in your CRM and a weekly signal report
- · You cannot name who buys from you beyond a job title; the signals will match everyone and mean nothing
- · Your offer is unproven; a better reason to write does not fix a product nobody wants yet
- · You want to send from your main company domain; we will not risk it, and you should not either
Open resources
Frequently asked
What is signal-based outbound?
Outbound where the reason to contact someone is an event that already happened, such as a promotion, new hiring or engagement with a relevant post, rather than a static list of people who match a persona. The event decides who gets contacted and becomes the first line of the message.
Why do I need three tools instead of one?
Because they are three different jobs. The signal tool finds who changed, the enrichment tool makes them reachable with a verified email, and the sending tool handles deliverability, limits and replies. Each one alone leaves you stuck: a signal with no email, or a sender with no list.
Can this use LinkedIn as well as email?
Yes. The same signal can feed a HeyReach LinkedIn sequence. We coordinate the two so one person is not contacted on both channels the same day, and the CRM check covers both.
Do I have to use Attio as the CRM?
No. We run Attio ourselves, but the pipeline logs to HubSpot or Salesforce just as well. What matters is that the CRM is the single place the suppression check reads from.
Want this running in your business?
We build and run this workflow for clients.
Related services: GTM engineering agency · Clay enrichment and GTM tables · Cold email system on Instantly · Hire a GTM engineer
Free weekly brief
Steal this workflow
Get new teardowns like this one by email: the steps, the tools, and the honest failure modes. No spam, unsubscribe anytime.