Signal-Based Outbound: Timing Beats Copy — If a Human Still Writes the Email
Signal-based outbound is a timing window, not a buying signal. Stack events, skip unsupervised AI SDRs, and let a human write the email.
Signal-based outbound is outreach triggered by an observable event — a hire, a raise, a stack change — not a static list. The event is a window, not a purchase. It should feed a human-written email, not fire an unsupervised AI SDR. Intent data is one noisy input; stacked, verifiable events are the rest.
That is the whole argument. The 2026 SERP will sell you the opposite: detect a signal, let software author the message, send before a competitor does. Timing matters. Authorship still decides whether anyone replies.
If you already have a sharp ICP and a reason to write, signals tell you when. They do not tell you what to say, and they do not make a stranger a buyer.
What is signal-based outbound?
Signal-based outbound is a timing layer on top of a list, not a replacement for one.
You still start with companies that fit. Then you wait for something observable to happen — a new VP in a buying seat, a funding round, a relevant job post, a tool appearing or disappearing in the stack, a pricing-page visit on your own site — and you write because of that event. The email has a reason to exist this week that it did not have last month.
That is different from “we bought intent and now we spray the accounts Bombora flagged.” It is also different from an AI SDR that treats every job change as a send trigger. A window is not a mandate.
The useful test: if you stripped the event out of the first sentence, would the email still make sense as a generic pitch? If yes, you did not run signal-based outbound. You ran a list with a coincidence in the opener.
How is a signal different from intent data?
Teams mash these together because vendors do.
Intent data infers that an account is researching a topic. Providers such as Bombora, G2 Buyer Intent, and 6sense watch content consumption across co-op networks or review sites and score a surge. The question it answers is “what is this company reading?” It does not tell you who inside the company cares, whether they have budget, or whether an intern was writing a blog post.
A signal is a verifiable event. Someone took the VP of Sales job on a Tuesday. The company closed a round. A careers page posted three SDR roles. BuiltWith flipped a pixel. Your own site saw a return visit to pricing. The question it answers is “what changed?”
Intent is a subset of the broader pile, and it is the noisiest subset. Every competitor on the same co-op sees the same spike. A funding announcement is public too — but at least you can name the round, the date, and the implication in a sentence a human would actually write.
Use intent to narrow a universe you already believe in. Use events to time the email and to choose the angle. Do not treat a topic surge as proof someone is buying.
| Signal | What it actually means | How to use it | How it gets abused |
|---|---|---|---|
| Job change into a buying seat | New leader, first 90 days, no incumbent loyalty — and a calendar full of congrats mail. | Write to the job they were hired to do, only if the company was already ICP. | “Congrats on the new role!” to every title change, including people who left your category. |
| Funding round | New capital and pressure to deploy it. Not a signed budget for your tool. | Tie the raise to an operating problem (hiring that will outrun pipeline). | Same paragraph as every other vendor the morning the announcement lands. |
| Hiring spike for a role you support | They are trying to buy the outcome with headcount. | Reference the posting and the work, only if you replace or amplify that role. | Trigger on any job in the department, including internships. |
| Tech stack change | They added or ripped out a tool in your neighborhood. | Say what changed and why that creates a gap. Recheck ICP. | “I noticed you use Salesforce” — that is a firmographic, not a signal. |
| First-party site intent | Someone from the account came to you. Warmest signal you will get. | Fast, specific, human follow-up. Hours actually matter here. | Auto-send the whole buying committee off one anonymous IP match. |
| Third-party intent surge | The account (maybe) researched a topic. Every other customer of the vendor sees it too. | Score an already-qualified list. Never the only reason to write. | “Saw you were researching CRMs” to an account you cannot name a contact at. |
One event is context. Two events in a few weeks is a window. A topic score with no event is a maybe.
Which signals are actually worth automating?
Automate detection. Do not automate authorship.
Wire detection for events that are public, cheap, and time-bounded: new leaders in buying seats, funding or M&A, job posts that describe the work you do, stack changes in your category, first-party visits you can resolve to an account.
Do not treat as send triggers: a LinkedIn like, an anonymous pageview, a co-op intent spike with no named contact, headcount growth with no function attached, or a social post about productivity.
If the event does not change the offer or the consequence you lead with, it was filler. AI email personalization that name-drops a raise and then pitches last quarter’s paragraph is still a template.
Detection can run every day. LinkedIn Sales Navigator, Crunchbase alerts, BuiltWith, and your own visitor ID tools are enough to start. Paid intent (Bombora, G2) is optional once the motion works without it.
Do not automate the sentence. That is the ~10% of outbound that actually gets read — the split in AI SDR vs human SDR. Signals belong in the 90% machines should watch. The email still needs a person.
Does signal-based outbound replace a cold list?
No. It filters one.
A signal on a company that was never ICP is a distraction. A new VP of Sales at a consumer app you do not sell to is not a lead. You still need the firmographic and title work from how to build a cold-email lead list. Signals sit on layer three: when, after which company and which person.
The list gets smaller. That is the point. Teams that “go signal-based” and keep sending the same 10,000-row CSV, now with a merge field for the event, have decorated the motion, not changed it.
You also still need a verified email. A perfect trigger pointed at a catch-all is a reputation bet. A Ken lead is a contact that is both qualified and has a valid email — finished output, not a credit. If you want that without standing up the watch list, Ken Daily sends 10 verified ICP-matched leads each morning, free, no card.
Can AI send the message when the signal fires?
It can. It should not.
This is the pitch Unify, Valley, and the rest of the 2026 “signal-to-conversation” category are selling: detect, draft, sequence, optionally skip the human. Speed is the claimed advantage — hours, not days — because a public event decays as every other vendor hits the same press release.
Speed on a bad sentence is just faster spam. The new VP got sixty “congrats on the new role” notes in week one. The ones that survive map the hire to the job they were hired to do, in a voice that does not read like a model. Unsupervised AI is unusually good at the congrats version.
Ken’s rule is the same on signal campaigns as on everything else: a human writes the framework, AI fine-tunes and personalizes from real context (not {{FirstName}}), and a human approves before anything sends. We do not position Ken as “our AI writes your emails for you.” That is the AI-SDR pitch. Signals change which account you work this week. They do not fire the send.
If you want software to watch the event and queue a draft, fine. If you want software to hit send because a pixel flipped, you are buying domain risk and a meeting calendar full of people who were never going to buy.
How fast do you actually need to act on a signal?
Faster than a monthly list refresh. Slower than a bot.
A public funding round is stale in a couple of weeks, not because the company stopped needing help, but because the inbox filled up with the same paragraph. First-party pricing visits go cold in days. A new VP is still evaluating vendors at day 60; they are just harder to reach with a “saw the announcement” line.
Practical operating rules:
- Detect daily. Do not wait for the next campaign build to notice the event.
- Write within a few days for first-party intent. Someone came to you. That is the only signal where hours matter more than the sentence.
- Write within 1–2 weeks for public events (raise, hire, job post), and only if you have an angle that is not the press release. If you cannot say something the other forty vendors will not say, wait — or do not write.
- Do not send in week six off a week-one event with the event still in the opener. By then it is trivia.
- Never skip ICP because the event was exciting. A bad-fit window is still a bad fit.
Vendors will quote 15–25% reply rates and 3–4× lifts for “triggered” mail versus cold. Treat those as marketing until you have your own cuts. Offer and copy still move the number more than the trigger. Ken’s public benchmarks — not SLAs — sit around ~3% reply versus a ~1% industry norm, ~30% of replies positive, and ~7 meetings per 10,000 contacts. We do not publish a separate “signal versus cold” conversion table, because we will not invent one.
What this looks like when Ken runs it
On Ken’s pricing, Core and VIP are both done-for-you outbound with the same software limits: 5,000 qualified leads, 1,000 emails/day, 5 LinkedIn seats. Core is $597/mo (or $1,497/quarter). VIP is $4,597/mo (or $13,497/quarter) and adds the higher-touch layer: founder onboarding, unlimited campaigns and revisions, Slack or WhatsApp, weekly iteration — and signal-based campaigns.
That last line is the product version of this article. VIP is where we run the watch list as part of the motion, not a DIY Clay board you babysit. The customer can also run the same motion in the app. We still do not let the model send unsupervised.
Most teams searching this query do not need another autonomy layer. They need the event in a brief, and a human to use it. The AI lead generation guide is the hub this spoke sits under: signals are one stage in a pipeline that still has to enrich, qualify, write, send, and handle replies.
For the 90/10 split, read AI SDR vs human SDR. For how a signal should change the sentence, read AI email personalization. For the finished lead, not the theory, start with Ken Daily. For the motion run — including signal-based campaigns on VIP — that is Why Ken.
FAQ
What is signal-based outbound in one sentence?
Outreach you send because something observable just happened at an account you already wanted, not because a static list came due.
Is intent data the same thing as a buying signal?
No. Intent data infers research (content consumption, topic surges). A buying signal is a verifiable event (hire, raise, stack change, first-party visit). Intent is one input. It is usually the weakest one to put in the first line of an email.
Does signal-based outbound replace cold email?
It replaces untimed volume, not the channel. You still need ICP, a verified email, infrastructure that lands in the inbox, and a sentence a person wants to read. The list is smaller and the reason is dated.
Should AI send automatically when a signal fires?
No. Let AI watch the event, enrich the account, and draft inside a human framework. A person approves. Autopilot on a public trigger is how forty vendors hit the same new VP on the same morning.
Does Ken run signal-based campaigns?
Yes — on VIP. Public plans are Core ($597/mo) and VIP ($4,597/mo), both done-for-you, same software limits. Signal-based campaigns are part of the VIP layer. A human still authors and approves.