Signal catalog
Every way the agent can find someone, in one table, with the lane each signal runs on.
A signal is an observable, public thing a person did: a post they wrote, a comment they left, a role they just started. It beats a job title alone, because it tells you what someone is working on right now instead of what their profile says they are.
The catalog
| Signal | Person or company | Needs your connected account | Best for |
|---|---|---|---|
| People search | Person | No | Building a first list from role, seniority, and location |
| Company search | Company | No | Finding accounts that fit, then pulling people from them |
| Post search | Person | No | Reaching people already talking about your problem |
| People on a post, preview | Person | No | High intent, a preview of who liked or commented |
| People on a post, saved | Person | Yes | The full like and comment list, saved to your contacts |
| Your own post engagement | Person | Yes | Warmest audience you have, they already know you |
| New in role or recent job change | Person | No | New budget, new mandate, and an open window to be early |
How to combine them
- Start broad, then narrow. Run a people or company search to get a base list, then layer a behaviour signal on top so you keep the ones who are actually active.
- Use one company signal and one person signal together. A company hiring for the role you sell to, plus a person there who posted about it, is a much stronger reason to reach out than either alone.
- Save the account lane for last. Everything public runs with nothing connected, so shape your list first and spend your connected account only where it adds something you cannot get publicly.