Target Account Pipeline
Signal-based outbound: hiring, funding, new leaders and stack changes
Outreach timed to buying signals, like a new VP, a funding round or a job posting, instead of a bought list: the Clay setup, the scoring and the messages.
6 min · Ayhan K. Isaacs · November 2026
- Signal cohorts
- CapturedObserved
- Difficulty
- Operator
- Time to run
- About 2 weeks to the first signal-based send
- Tools
- Clay, Smartlead, Instantly, LinkedIn Sales Navigator, HubSpot, Salesforce, n8n, BuiltWith, Claude
A funding round is a reason to offer something, not a reason to pitch. Every vendor in your category gets the same alert on the same morning, so a newly funded founder gets many emails that open with "congrats on the raise."
Signal-based outbound works when the signal changes what you offer, and when you stack it with a signal only you can see, such as a visit to your pricing page or a reply.
Who this is for
This playbook is for SaaS teams that sell into a defined market, already run outbound, and want fewer sends with better timing.
You need Clay, a sequencer on warmed domains, and a named account list or the criteria to build one.
Who this is not for
This is not for teams whose deliverability is not in order. Fix domains and warmup first.
It is also not for teams that want signals to raise volume. If the signal does not change the message, it is a bought list with a date on it.
The signal it engineers or captures
The triggers in signal-based outbound are observed signals: job postings for relevant roles, a hiring surge in a function, a new executive hire (VP Sales, CMO, CRO, CISO), a funding round, and a tech install or removal. Anyone can see them, so on their own they decide timing and nothing else.
The playbook stacks them with captured signals that only you have: a pricing page visit, an identified website visit, an email reply and LinkedIn post engagement. An account with one observed and one captured signal gets a person. An account with only the observed signal gets an offer by email.
The workflow
01 Pick three signals that change what you would say
List the events that make your product more urgent and keep the three where you can say why. Examples: a job posting for the role your product supports, a new CRO or CMO in their first 90 days, a funding round in the last 30 days, or a competitor added to or removed from the stack.
Write one sentence per signal on what the buyer is probably dealing with. If you cannot write that sentence, drop the signal.
02 Set the monitors in Clay
On your named account table, turn on Clay signals: job postings filtered by title keywords, new hires filtered by title and seniority, news and fundraising, and job changes for your contacts. Add a stack check with BuiltWith or a Claygent prompt, rerun it monthly, and compare it with last month to catch installs and removals.
Run the monitors weekly. Write each fired signal to a column with its date and source URL.
03 Qualify before you write
A signal on an account that does not fit is noise. Score fit first (size, industry, country and stack), then add points for signals.
Example weights to tune: fit out of 50; a relevant job posting 15; a new executive in the buying role within 90 days 20; funding in the last 30 days 10; a competitor added or removed 15; a captured signal in the last 14 days (pricing visit, reply or post engagement) 25. Cap the total at 100 and send nothing under 50.
04 Find the right person for each signal
Each signal points to a different person. A job posting points to the hiring manager, not the person being hired. A new executive is the person to write to, after their first few weeks. A funding round points to the founder or the leader of the function you sell to.
Find them in Clay or Sales Navigator and verify every email.
05 Write the offer from the signal
The first line names the event. The second offers something useful for it, with no meeting ask.
Job posting: "You are hiring a RevOps manager. Here is the onboarding checklist we give new RevOps hires, free to copy." New executive: "You joined [company] as CRO in [month]. If a stack review is on your list this quarter, we have a one-page template for it. Want a copy?" Funding: "After a raise the board usually asks for a pipeline plan. Here is the one-page model we use. Want it?"
Draft variants with Claude inside Clay, and have a person read every first line before it goes out.
06 Send in small, dated batches
Send each signal's sequence in small batches from Smartlead or Instantly: two or three emails over about ten days, plus a LinkedIn connection request from the same sender.
Stop sending on a signal once it is past its useful window: about a month for funding, the first 60 days for a new executive, and while the posting is open for a job ad. Our glossary gives each signal a useful life; use those as starting points.
07 Route captured signals to a person
When an account that got a signal-based email visits pricing, replies or engages with a post, Clay or n8n creates a task and an alert for the owner. That account leaves the sequence and gets a personal touch the same day.
08 Review signals by outcome every month
Tag every meeting with the signal that started it. After two or three months, cut the signal that produces replies and no meetings, and test the next one on your list.
Keep the signal library in one shared document: the rule, the persona, the message and the result.
What it costs and how long it takes
Tools: Clay with signals, a sequencer (Smartlead or Instantly) on warmed secondary domains, Sales Navigator for finding people, and the CRM.
Time: a week to choose the signals, write the offers and build the monitors, with the first batches in week two. Upkeep is a weekly review of fired signals and a monthly decision on which to keep.
The numbers
Perfect Venue is our closest record. We used Ahrefs, Brizo and Clay to find restaurants running competing tools, sent them a stronger switching offer, and asked for interest in a one-pager instead of a call. The program produced 66 positive responses handed to the SDR team and about USD 175,000 in ARR pipeline.
For your own run, measure by signal: sends, replies, positive replies, meetings held, and pipeline after 90 days.
- Perfect Venue 66 positive responses Restaurants running competing tools, found with Ahrefs, Brizo and Clay, got a switching offer and a one-pager; about USD 175,000 in ARR pipeline.
Where it breaks
Saturation is the first thing that breaks. The most popular signals, funding and a new VP, reach every vendor at once. Use them for timing and pair them with something only you can see.
Stale signals are the second. A funding round from four months ago is old news. Respect the window and drop old signals from the sequence.
The third is a message that only states the signal. "Saw you raised" gives nobody a reason to reply. If the offer does not change with the signal, cut the signal.
The fourth is deliverability. Signal programs send less, but every send still needs warmed domains, verified emails and sensible daily caps.
Hand-off to sales
A positive reply reaches the owner within the hour with the signal, the email thread and the Clay account summary. The rep answers the question in the reply first, sends the promised asset, and asks for a call after that.
For a captured signal without a reply, the rep sends a short personal note and a LinkedIn message about the asset, never about the visit.
FAQ
Related
- Simplified ABM with Clay: qualify 5,000 accounts and score them
A simplified ABM playbook: take 5,000 accounts through Clay for tech stack, news, hiring and org chart checks, score them, and work the top tier by hand.
- Champion tracking: follow past buyers to their new company
How to track job changes among past buyers and users with Clay, score the new company, and reach out in the first 90 days with a reason to talk.
- Outbound reply handling: classify, route and answer every reply
How to sort every outbound reply by intent, route interested ones to an SDR within the hour, answer the questions, and catch the referrals.