A B2B intent signal is any observable behavior that raises the odds a person or company is evaluating a purchase. Signals differ a lot in strength: a comment asking for tool recommendations is worth many times a passive like. The practical skill is knowing which signals deserve a message today and which only deserve a place on a watch list.
First-party, third-party and public B2B intent signals
Intent data usually comes in three flavors, and mixing them up leads to bad expectations.
- First-party: actions on your own properties, such as pricing page visits, demo requests and replies. Highest quality, lowest volume.
- Third-party: browsing behavior inferred across other sites by data vendors. High volume, but you cannot see what the person actually read, so you cannot reference it.
- Public: things people did openly, like comments, posts, job listings and announcements. Medium volume, and you can quote them in your message.
Find people engaging with your topics and competitors on LinkedIn, scored with a reason to reach out.
Find my buyersThis guide focuses on public signals because they are the only kind a small team can find without a data contract and the only kind you can openly reference.
A strength ladder for ranking intent signals
Rank signals by how much effort the person spent and how close the action is to a buying decision. Roughly, from strongest to weakest:
| Strength | Signal | What it tells you |
|---|---|---|
| Strong | Asking for tool recommendations in a comment or post | Active evaluation, in public. |
| Strong | Complaining about a current vendor | Existing solution is failing; switching cost is being weighed. |
| Strong | Company hiring for the exact role your product supports | Budget exists and the problem is costing money. |
| Medium | Commenting on a post about the problem | Thinking about it this week, not necessarily buying. |
| Medium | Engaging with a competitor's launch or case study | Aware of the category and watching vendors. |
| Medium | New leader in a relevant function | Often reopens tool and vendor decisions in the first months. |
| Weak | Liking a post on the topic | A tap. Useful only when stacked with something else. |
| Weak | Following a thought leader in your space | Interest in the field, nothing time-bound. |
Stack weak intent signals into strong ones
One like means little. A like, plus a comment on a competitor's post, plus an open role for the job your product does, means a lot. Scoring should reward stacking: the same person or company showing up under two independent signals within a few weeks moves to the front of the queue.
A simple rule: any one strong signal gets a message. Two medium signals get a message. A single weak signal gets nothing, but stays on file in case a second one appears.
Intent signal decay matters more than you think
Signals expire. A request for recommendations is hot for days. A hiring post can stay relevant for a few weeks while the role is open. A job change keeps its value for a couple of months. Build a rough half-life into whatever you do: contact on the day for conversation signals, within the week for most others.
If you are working from a list that does not carry dates, you are working from a list that cannot tell you what to do first.
False positives to filter out of intent signals
Every signal source has a crowd that looks like intent and is not. Learn to spot them.
- Vendors and consultants selling to the same audience, who comment on everything.
- Recruiters, who engage with hiring-related posts for sourcing reasons.
- Students and job seekers, who interact with anything in a field they want to enter.
- Competitor employees, who watch each other's posts.
- Engagement pods, where groups of people like and comment on each other's posts by arrangement.
The fix is the profile filter: check role, company and seniority against your ideal customer before you spend time on a message. DMHunt does this with a 0 to 100 score and a short reason for each person, and treats 60 and above as a lead.
Turning an intent signal into an action
For each signal type, decide in advance what the response is. A table on a shared doc is enough.
| Signal | Response | Window |
|---|---|---|
| Asked for recommendations | Reply in thread with something useful, then email | Same day |
| Engaged with competitor | Email referencing the post, no pitch | Within 3 days |
| Hiring for the role | Email the decision maker, tie to the hiring plan | Within the week |
| New leader | Congratulate, ask what they are changing first | Within 2 weeks |
A weekly intent signals routine that fits in an hour
You do not need a data team to use signals. A simple weekly rhythm works for a founder or a small sales team.
- Monday: review last week's signals, drop anything older than two weeks and anyone who does not fit your profile.
- Tuesday and Wednesday: write to the strong signals first, then the stacked medium ones.
- Thursday: follow up once on anything from earlier in the week, with something new to say.
- Friday: note which signals produced replies and which produced nothing, and adjust what you watch next week.
After a month you will know which signal types turn into conversations for your product. Drop the ones that do not, however good they look on paper.
