An intent signal (also called a buying signal) is an observable event that suggests a person or account may be more open to a relevant conversation right now. This catalog is the living reference for the signal types that power signal-led outbound at Aetrix. It is not a ranked “top 10” listicle, and it does not invent search volumes, difficulty scores, or reply-rate claims.

If you already read our definition of signal-led outbound, treat this page as the glossary hub that sits beside it not a redo of a “10 signals to track” roundup. Use it to decide which events deserve a queue slot, how to talk about each one in copy, and which Aetrix tracks map to your ICP.

Intent signals vs buying signals vs intent data

Buying signals are the umbrella: any observable change that creates a buying window. Intent signals are often used the same way in outbound product language. Intent data is narrower usually third-party research behavior (topic surges, review-site activity) inferred across the web.

In practice: intent data can be one input. Signal-led outbound is the system that qualifies events against ICP, researches context, drafts a why-now message, and keeps high-impact sends under human approval. A catalog of signals without that loop is just a longer list of reasons to spray.

How to read this catalog

For each signal you’ll get four things: what it is, why it can matter, a copy tip, and a common mistake. Strength is qualitative and directional only not a scored model you should copy blindly into a spreadsheet.

Aetrix markets eight core signal types. They fall into three families:

The Aetrix intent signals catalog

1. Keyword engagement

Family: Social · person-level

What it is: People publicly talking about topics tied to your product usually on LinkedIn posts, comments, or threads. The signal is engagement with language that maps to the problems you sell against, not every trending hashtag in your category.

Why it can matter: The prospect is already in the conversation. Your outreach can join that thread instead of inventing interest from a static firmographic row. Keyword engagement is often the earliest person-level hint that someone is wrestling with a problem you recognize.

Copy tip: Reference the topic they engaged with, not a generic “saw your post.” Tie it to the problem you solve in one line. Lead with shared context, then ask a sharp question or offer a useful angle not a pitch dump.

Common mistake: Treating every like as equal. Engagement on a loosely related viral post is weak; engagement on a pain-point keyword you sell against is stronger. Also: quoting the post back at them without adding insight. That reads as scraping, not listening.

2. Influencer engagement

Family: Social · person-level

What it is: Who likes and comments on the voices you already track category leaders, practitioners, or accounts your buyers follow. You define the orbit; the signal is who shows up consistently in that orbit.

Why it can matter: It surfaces people who share the same ideas as your ICP even before they visit your site or download an asset. For BDRs and growth agencies, this is a way to expand beyond known accounts without buying another cold list.

Copy tip: Lead with shared context (“saw your take on X alongside [voice]”) and pivot fast to a useful angle not flattery. The influencer is the bridge, not the product.

Common mistake: Name-dropping the influencer without a product-relevant bridge. That reads as social listening spam. Another miss: treating one casual like on a celebrity founder post as a buying window.

3. Competitor reactions

Family: Social · competitive

What it is: People engaging with rival posts and company pages liking, commenting, or otherwise showing active attention to competitors in your category.

Why it can matter: They’re already evaluating the category. You’re late to “do you have this problem?” and early to “here’s a sharper way to solve it.” For RevOps and founders comparing tooling, competitor reactions often mark active evaluation windows.

Copy tip: Stay respectful. Contrast approaches or outcomes; don’t trash the competitor in the first line. Fair competitors for context in this space include tools like Outpace, Avina, Kampaign, Swan, AiSDR, and traditional sequencers the point is category awareness, not mud.

Common mistake: Assuming engagement equals dissatisfaction. They may be a happy customer doing research or a competitor’s employee. Qualify against ICP and tone carefully before you draft.

4. Profile visitors

Family: Social · person-level

What it is: Who viewed or interacted with your LinkedIn profile (or related profile surfaces you monitor). Someone chose to look you up that is different from being on a purchased list.

Why it can matter: It’s a warm attention signal. Curiosity is not a demo request, but it is a better opening than a cold “noticed you’re in sales ops.”

Copy tip: Keep it light and specific. Offer a useful next step (resource, angle, or question) instead of “noticed you stopped by.” If you know the company fit, open a path that respects the soft nature of the signal.

Common mistake: Instant hard pitch. Profile views are curiosity, not pipeline. Another mistake: chasing every view without ICP filters that recreates list spam with a vanity pretext.

5. Recently raised funds

Family: Company event

What it is: ICP contacts at companies that just closed a round. The event is public; the useful part is which titles at that company map to your buyer.

Why it can matter: New capital often resets priorities hiring, tooling, and pipeline infrastructure move up the list. Founders and growth leaders frequently revisit outbound motion after a raise because headcount and targets change together.

Copy tip: Connect the round to a concrete motion you enable (for example, scaling outbound without scaling research headcount). Avoid “congrats on the raise” with nothing underneath. The raise is the why-now; your product still needs a reason.

Common mistake: Blasting every employee at a funded company. Stick to titles that buy or influence your category, inside your ICP. Also: treating every round size the same a seed raise and a growth round create different operational pressure.

6. Job changes

Family: Company event · person-level

What it is: New decision-makers in role especially leaders still early in the seat (commonly the first 90 days). The signal is the mandate change, not the LinkedIn announcement alone.

Why it can matter: New leaders diagnose the stack, the team, and the pipeline process. Windows open when they’re still forming the plan and before vendor lock-in hardens.

Copy tip: Speak to the first-90-days job: visibility, forecast hygiene, coverage, or ramp whichever matches your product. Show you understand the early-seat agenda, not just that you scraped the title change.

Common mistake: Congratulating the role change and stopping there. The signal is the mandate, not the announcement. Also: messaging former peers or wrong-level titles at the new company without ICP discipline.

7. Hiring momentum

Family: Company event

What it is: Companies staffing the functions you sell into AE pods, SDR teams, RevOps, growth, and related roles. Look for patterns in those functions, not a single unrelated posting.

Why it can matter: Hiring is a public proxy for budget, priority, and operational strain (ramp, tooling, process). When a company is building outbound capacity, they often feel the pain of research bottlenecks and inconsistent first lines.

Copy tip: Tie open roles to the operational gap you close. “You’re hiring three AEs” only works if the next sentence is about why that creates the problem you solve.

Common mistake: Treating one unrelated job post as momentum. Look for patterns in the functions that map to your ICP. Also: ignoring that hiring can mean chaos soft CTAs often beat aggressive demos.

8. Website visits

Family: First-party

What it is: Company-level identification when a target account hits your site. Aetrix website tracking resolves company, not personal stalking theater it is not individual IP-level personal identification for outbound theater.

Why it can matter: They’re already in your world. Pricing, features, or blog paths change how warm the first line can be. For RevOps and growth teams, this is often the highest-trust signal family because it is first-party attention on your property.

Copy tip: Open a path to the right titles at that company. Reference the moment carefully don’t invent page-level claims you can’t stand behind. Company-level ID means you know the account showed up; you still need ICP titles and judgment.

Common mistake: Waiting a week. First-party attention cools. Also: messaging a random title instead of the ICP seats that actually buy. And: overclaiming personal identity when you only have company-level identification.

How to prioritize signals without fake scores

You do not need a made-up 0–100 model to start. Invented difficulty scores and reply-rate multipliers create false confidence. Use three practical filters instead:

1. ICP fit first. Unfit signals stay out of the sequence no matter how “hot” the event looks.

2. Specificity of the why-now. Can a human write one honest sentence that names the event without inventing urgency?

3. Stacking. Two related signals on the same account (for example hiring + website visit) usually beat one isolated social like.

Then decide speed by signal family: first-party attention and active evaluation deserve faster follow-up than a broad public company event that every vendor will also see. Prioritization is judgment layered on ICP not a leaderboard of vanity events.

Turn a signal into a send (short loop)

Signal-led outbound is not “more data.” It is a repeatable path from event to approved send:

1. Detect the event

2. Qualify against ICP

3. Research just enough context

4. Draft from the trigger

5. Approve high-impact outreach (human in the loop / Copilot)

6. Execute on live channels — email and LinkedIn

That loop is the method behind what signal-led outbound is. For a narrative list of signals teams watch, see earlier buying-signal posts this catalog is the durable hub you maintain as the product and market evolve. It is explicitly not a redo of a “10 signals” listicle.

Who uses which signals

BDRs usually live in person-level social signals and job changes high volume of why-now moments they can turn into conversations. Growth agencies need clean multi-client ICP filters so keyword and competitor reactions don’t bleed across accounts. RevOps often owns website visit routing and hiring/fund event hygiene so the queue stays trustworthy. Founders frequently start with website visits plus job changes at dream accounts fewer motions, clearer judgment.

What this catalog is not

• Not a claim that every signal should auto-send

• Not a substitute for ICP definition

• Not a dump of third-party intent scores without a reason to write

• Not a redo of “congratulations on the raise” templates

• Not a place for invented search volume, position, or “X× better” claims

Bring the catalog into your outbound stack

If your team still starts from a static list and a cadence, this glossary is the missing middle: the why-now layer between ICP and first line. Aetrix is built as a signal-led AI outbound platform — find accounts, spot buying signals, ICP-qualify, research and draft, then Copilot for human approval before send on email and LinkedIn.

Want these signals scored against your ICP with drafts waiting for approval? Start free on Aetrix https://www.aetrixhq.com/ or book a demo. Email and LinkedIn are live today.