Neeraj Sujan
← Writing

Signals, Intent, and Triggers: The Vocabulary That Separates GTM Engineers from Spray-and-Pray

Signals are company-level events. Intent is person-level engagement. Triggers are automated workflows. Most outbound teams treat all three as the same thing — which is why their reply rates are 0.3%.

·12 min read

Most outbound is timeless.

Not in a good way.

It is sent regardless of where an account is in a buying cycle. Regardless of whether anyone at the company has shown a single indication of interest. Regardless of whether the timing makes any sense at all. The sequence fires because someone hit "launch campaign" — not because the account was ready to hear from you.

This is why reply rates get measured in decimal points.

The teams getting 3–8% reply rates are not writing better subject lines. They are reaching out to accounts that are already moving — and they are reaching out at the exact moment those accounts are moving. That requires a vocabulary most outbound teams do not have.

Signals. Intent. Triggers.

Three different things. Three different infrastructures. Three completely different outreach strategies. And almost everyone treats them as synonyms.


Why the Vocabulary Matters (It Is Not Pedantry)

Here is the operational reason these distinctions matter.

Signals tell you which accounts to prioritize. A company that just raised a Series B, is hiring three SDRs, and changed their CRM last quarter is a different account than a company that has been sitting still for eighteen months. Same ICP. Completely different urgency.

Intent tells you which people at those accounts are actively in a buying cycle right now. The VP of Sales at a signal-positive account is one thing. The VP of Sales who visited your pricing page twice this week and downloaded your case study is something else entirely. That person is already evaluating solutions. You are not starting a conversation — you are responding to one.

Triggers are what you do when you detect a signal or an intent event. They are the automated workflows — the sequence that fires, the personalized email that generates, the Slack notification that lands in your rep's channel.

Most teams conflate all three. They build one sequence and send it to everyone on the list. Accounts with zero signals and accounts with five signals get the same email. People who have never heard of your product and people who were on your pricing page Tuesday get the same subject line.

That is spray-and-pray with a Clay logo on it.


Signals: Company-Level Events That Predict Buying Behavior

Signals are public data points at the company level. They do not tell you that a specific person is ready to buy. They tell you that something has changed at this account — and that change makes them more likely to be receptive right now than they were six months ago.

The most predictive signals, ranked roughly by urgency:

Leadership changes. A new VP of Sales, VP of Marketing, or CRO typically re-evaluates the entire tech stack within their first 90 days. This is one of the highest-signal events you can track. The new leader wants to put their stamp on the function. They are actively looking for tools to support their plan. If your ICP hires into revenue leadership roles, this signal alone can drive a meaningful percentage of pipeline.

Funding rounds. A Series A or B announcement means the company just received capital and a mandate to grow. They are in buying mode. Headcount is expanding. New tools are being evaluated. The window is short — the first sixty days post-announcement is when most buying decisions get made.

Hiring spikes. Not just headcount growth generally — specific role hiring as a signal. A company hiring three SDRs is evaluating outbound tools. A company hiring data engineers is investing in data infrastructure. A company posting for a RevOps manager is formalizing their GTM motion. The job posting is a strategic signal disguised as an HR document.

Tech stack changes. A company that switched from HubSpot to Salesforce last quarter is re-evaluating the entire adjacent ecosystem. New CRM means new SEP, new enrichment vendor, new intent tools. Track tech stack changes with BuiltWith or Bombora. The window after a major platform migration is a predictable buying moment.

Social media statements. A founder posting about a specific pain point is essentially a warm lead announcement. Competitor mentions in leadership posts. Category research language. Engagement with your content. These are lower-signal but useful for prioritization.

How to find signals without expensive tools. LinkedIn is free. Job boards are free. Crunchbase has a generous free tier. For most of these signals, you do not need a $50K/year intent platform — you need a Clay table with a Trigify integration and a hiring spike column.

For company-level keyword research patterns — which companies are actively searching for solutions in your category — Bombora and 6sense are the gold standard. But they are expensive. Use them when the deal size justifies it.


Intent: Person-Level Engagement That Tells You Who Is in the Market Now

Intent data operates one layer below signals. Where signals are company-level, intent is person-level. And that distinction matters enormously.

A company with three strong signals has potential. A person at that company who visited your pricing page twice this week has interest. Those are not the same thing. The former tells you to prioritize the account. The latter tells you who to reach out to and what to say.

Website intent — RB2B. RB2B deanonymizes website visitors and returns person-level data — name, company, title, LinkedIn profile — for people who visit your site. This is the highest-intent signal available because the person came to you. They were not discovered. They self-selected.

RB2B operates US-only due to privacy compliance constraints — GDPR and CCPA make person-level deanonymization in the EU and California legally complex. If your ICP is US-based, this is one of the first tools you should wire up.

The intent hierarchy from RB2B:

  • Pricing page visit = very high intent (evaluating)
  • Case study or ROI calculator = high intent (justifying internally)
  • Multiple blog posts in a session = medium intent (researching the space)
  • Single blog post = low intent (might be a competitor, might be curious)

Bombora for keyword research intent. Bombora tracks which companies are actively researching specific topics across hundreds of thousands of B2B websites. If your category keyword shows up in a company's research pattern, that company has intent at the organizational level. It is not person-level — Bombora cannot tell you who at the company is searching — but it confirms that the buying conversation is happening internally.

6sense for predictive intent. 6sense layers AI over intent signals to predict which accounts are in an active buying cycle before they show overt intent. It uses pattern matching across historical buying journeys. High signal for enterprise sales with long buying cycles where you want to get in early.

Koala for product-led intent. If you have a freemium or trial product, Koala surfaces which users are engaging with which features — and flags when usage patterns match conversion-to-paid behavior. This is intent data from inside your product, not from external sources. The signal quality is extremely high.


Triggers: The Automation Layer That Closes the Timing Gap

Detecting a signal or intent event means nothing if you act on it three weeks later. The value of intent data is almost entirely time-dependent.

The account is warm right now. It will not be warm forever.

A trigger is the automated workflow that fires immediately when a signal or intent condition is met. Not when someone checks the dashboard. Not when the weekly review happens. Automatically, within hours.

RB2B webhooks. When RB2B identifies a visitor, it can fire a webhook to your CRM, to Slack, to Clay, or directly to your sequencing tool. A person visits your pricing page → RB2B identifies them → webhook fires → Clay enriches the contact → personalized email generates and queues in Smartlead within the hour. That entire chain can be fully automated.

Trigify for LinkedIn triggers. Trigify monitors LinkedIn activity and fires workflows when specific events occur — a prospect comments on a relevant post, shares content about a pain point your product solves, or engages with a competitor's content. LinkedIn activity is a behavioral signal that is difficult to capture otherwise.

The timing imperative. A signal-triggered email sent within two hours of a pricing page visit gets 5–8x higher reply rates than the same email sent two days later. The window is real. Waiting is not neutral — it actively degrades the conversion probability.

The operational target: any high-intent signal should trigger outreach within one business hour. Anything slower requires a human bottleneck to be removed from the workflow.


The Signal × Intent Scoring Matrix

Not all signals are equal. Not all intent events are equal. A scoring matrix lets you prioritize outreach rationally rather than by gut feel.

The basic structure:

Signal/Intent EventWeightRationale
Pricing page visit (RB2B)10Highest-intent self-identified action
Demo request10Already converted to pipeline
VP of Sales hired (new)8Stack re-evaluation window
Series A/B announced7Active buying mode
3+ SDR job postings7Outbound tool evaluation in progress
Bombora keyword surge5Category research active
Tech stack change detected5Adjacent buying likely
LinkedIn pain point post3Awareness-level signal
Blog post read (single)1Low, may be noise

Layer this on top of your ICP fit score. A company that is a 9/10 ICP fit with a signal score of 15 goes to the top of the queue. A company that is a 6/10 ICP fit with a signal score of 3 stays in the nurture pool.

Fit × intent = outreach priority. Simple framework. Dramatic improvement in how you allocate rep time.


The Personalization Unlock

Here is where the vocabulary pays off in the actual copy.

Most personalization is cosmetic. It uses the contact's name, their company name, and a LinkedIn post they wrote six months ago. This is "personalization" in the same sense that a birthday card from a bank is "personal."

Signal and intent data enables contextual personalization — opening lines that reference something specific, recent, and relevant to what that person is actively experiencing right now.

Three examples. Same ICP. Same product. Three completely different emails:

Signal: hired new VP of Sales last month. "Noticed you brought on [Name] as VP of Sales last month — congrats. New revenue leadership usually means a full GTM stack review in the first 90 days. If enrichment and outbound are on the list, I have something worth 15 minutes."

Signal: hiring three SDRs right now. "Saw you're scaling the outbound team — three SDR postings this quarter. The enrichment and sequencing infrastructure that gets built now determines whether those hires succeed or churn out in six months. Worth a quick look at what we've built for similar teams."

Intent: pricing page visit Tuesday. "You were on our pricing page Tuesday — figured I'd reach out directly rather than waiting for the form. Happy to walk through the specifics or answer questions about how the enrichment waterfall works for your use case."

One of these converts. You know which one.

The person who was already on your pricing page does not need a discovery call. They need a faster path to the information they were already looking for. Treating them like a cold prospect is a waste of the signal they just gave you.


The Manual Layer You Cannot Automate Away

Everything above can be automated. But high-value accounts — enterprise deals, strategic partnerships, high-ACV targets — require a manual layer on top.

Automation is accurate at scale. It is imprecise for individuals.

For Tier 1 accounts — the twenty or thirty accounts that would each meaningfully change your quarter — do not rely on RB2B and Trigify alone. Human-led research catches signals that no tool surfaces:

  • A founder posted something on LinkedIn that reveals a strategic shift
  • A company was mentioned in a podcast episode about a specific problem you solve
  • A prospect's industry just had a regulatory change that directly affects their buying timeline
  • A mutual connection mentioned that the company is actively evaluating vendors

These signals are real. They convert. They are also invisible to automated tools.

The protocol for Tier 1: automated signals surface the account and confirm urgency. Manual research uncovers the specific angle. The combination produces outreach that reads like it came from someone who did their homework — because it did.


Build Your Signal Stack This Week

Here is the practical exercise from the GTME training curriculum:

Build a one-page document with:

  • 10 signals relevant to your specific ICP (not generic — signals that actually predict buying behavior for your product)
  • 5 intent events you can track today (at least one from website, one from LinkedIn, one from job postings)
  • 3 triggers you can automate within the next week (RB2B webhook, Trigify rule, hiring spike alert)

For each signal: define what tool surfaces it, what score you assign it, and what the outreach sequence looks like when it fires.

This is not a theoretical exercise. It is the infrastructure that replaces a list of cold contacts with a prioritized queue of accounts that are already moving.

Most teams skip this. They go straight to writing copy.

Do not skip this. The sequence is only as good as the intelligence that decides when to send it.

The difference between 0.3% reply rates and 4% reply rates is not the subject line. It is whether you reached out to the right person, at the right company, at the right moment — with a message that references why right now is the right time to talk.

That is what signal-driven outbound does.

Build the stack first. Write the copy second.

#gtm-engineering#signals#intent#outbound#rb2b#clay