Signals usually arrive attached to the wrong person. A junior analyst posts a complaint, a recruiter posts the job description, a database says "this account is researching your category" and names nobody at all. Knowing that an account is in-market is half a lead; the other half is knowing whose inbox to appear in.
Short answer: map three roles at every account — the champion who feels the pain, the economic buyer who signs, and the blocker who can veto — and enter through the champion while making sure your material can survive being forwarded upward.
Key Takeaways
| Role | How to spot them | Contact when |
|---|---|---|
| Champion | Feels the pain daily, posts about it, owns the workflow | First, almost always |
| Economic buyer | Owns the budget line, usually VP or C-level | After the champion, or directly for large deals |
| Technical evaluator | Security, IT, data — assesses feasibility | When the deal is real |
| Blocker | Owns the incumbent tool or the competing plan | Never cold — neutralize via champion |
Start With the Signal, Not the Org Chart
The person attached to the signal tells you where the pain is, which is more useful than a title. If a support lead complains about response times, the pain lives in support even if the budget lives with the COO.
Three shapes come up constantly:
The signal names an individual. A post, a comment, a review, a complaint. This person is usually the champion, not the buyer. Contact them, but expect the deal to need someone above them.
The signal names a company only. Intent data, website visits, funding news. You are choosing a person from scratch — start from the function most affected, per intent data tools.
The signal names the wrong individual. A recruiter posts the job ad; the hiring manager owns the problem. A junior analyst complains; their director owns the fix. Read past the poster to the owner.
Finding the Right People on LinkedIn
Once you know the function, finding names is mechanical.
Company page → People tab. Free, and filterable by keyword. Search the function term ("revenue operations", "security", "data") and read titles.
Search with company plus title filters. Free search handles this adequately; Sales Navigator adds seniority and function filters plus saved-list alerts, which matters when you are tracking accounts over time.
Read who posts. The person from a company who posts publicly about your problem space is a champion who has already self-identified. Catching them is keyword monitoring applied to a named account list.
Read job postings. The hiring manager named in a JD for the relevant function is usually the tool owner, per hiring signals.
Check for recent arrivals. Someone who started in the last 90 days in the relevant function is disproportionately likely to be reviewing tooling — see job-change signals.
Champion First, Almost Always
The instinct to "go to the top" is mostly wrong for mid-market software. A cold message to a VP about a problem they experience second-hand gets deleted; the same problem described by their own team member gets a meeting.
Reasons to enter through the champion:
- They can describe the pain in the company's own language, which you cannot
- They will be asked to evaluate the tool anyway
- An internal recommendation outperforms any external pitch
- They tell you who actually signs, which saves you guessing
Go directly to the economic buyer in three cases: the company is small enough that the buyer is the champion, the deal size demands executive sponsorship from day one, or the signal itself came from the executive.
Sizing the Deal Before You Pick
Contract size determines how many people you need.
Under roughly $10k a year, one person can usually buy without a committee — sell to the champion and stop. Between $10k and $50k, expect the champion plus a budget owner plus a light security review. Above that, expect a formal evaluation with procurement, security, legal and a competing internal priority, and plan to be introduced to several people over months.
Matching effort to deal size is what separates useful multithreading from spraying an org chart. Six people at a $6k account is wasted work; one person at a $200k account is a deal that dies when they change jobs.
Writing for the Forward
The most useful thing you can do for a champion is make it easy for them to sell you internally. Assume every message you send them will be pasted into a Slack thread with their boss.
To the champion:
Hi [Name] — saw your post about [specific problem]. That is the exact thing we handle. Attaching a one-pager written for whoever owns the budget on your side, since I assume that is not you: it covers cost, security posture, and the rollout timeline. Happy to answer anything before you pass it on.
To the economic buyer, after the champion:
Hi [Name] — [champion] and I have been talking about [specific problem] in [function]. Rather than repeat the demo, here is the business case in one page: [link]. The number that matters is [specific outcome]. Fifteen minutes if it is worth it, and nothing if not.
Executives want cost, risk and outcome. Champions want the workflow. Sending the champion's material to the executive is the most common reason multithreaded deals stall. More patterns in signal-based outreach templates.
Making It Continuous
Signal to person is the step that quietly eats the time. Every signal requires opening the company, reading the org, guessing the owner, verifying the title, and finding a contact route — five to ten minutes each, which caps you at a few accounts an hour.
Updately closes that gap: when a signal fires, it enriches the person and the company, checks ICP fit, and identifies the right contact rather than handing you a company name. Category context in best sales intelligence platforms 2026.
Frequently Asked Questions
Basics
Should I contact the person who posted, or their manager? The person who posted, in almost all cases. They own the pain and can bring you in. Their manager owns the budget and will hear about you from them.
How many people should I contact at one account? Match it to deal size: one for small self-serve deals, two or three for mid-market, more only for large enterprise cycles.
Execution
How do I find who owns the budget? Ask the champion directly — "who else would need to be involved?" is a normal question and the answer is usually accurate. Guessing from the org chart is less reliable.
What if the champion goes quiet? That is precisely the risk single-threading creates. Once a deal is real, get a second contact, ideally introduced by the champion rather than found cold.
Risk
Is going over someone's head a mistake? Usually yes, if you do it after engaging them. Going around a champion you have already spoken to is the fastest way to lose them and the deal.