How to find champions before the first call in 2027

The outcome you should expect

A pre-call champion identification pass is not a magic trick that turns cold outbound into warm inbound. It is a narrowing exercise, and the honest way to describe its payoff is that it changes *who picks up* and *what the first fifteen minutes cover*, not whether the deal closes. Teams that do this well tend to see three concrete shifts, and it is worth being precise about each because the vague version ("better meetings") is unmeasurable and therefore unimprovable.

The first shift is in first-call composition. Without pre-call work, the discovery call is a monologue: you ask about pain, the prospect describes a generic version of it, and you spend the back half guessing which of the four people on the invite actually cares. With a named likely-champion hypothesis, you can open the call with a specific, falsifiable statement — "my read is that the migration you posted about in the platform-engineering role is the thing driving this, and that your team eats the cleanup when it slips" — and let the prospect correct you. Being corrected is a win. It gives you the real map in minute four instead of minute forty.

The second shift is in the multithreading timeline. The single most common failure pattern in mid-market and enterprise cycles is discovering, in week six, that your only advocate has no budget authority and no relationship with the person who does. Pre-call champion work front-loads that discovery. If you have already mapped who reports to whom, who has been publicly complaining about the problem, and who signed off on the last comparable purchase, you can ask for the second stakeholder on the *first* call rather than the fourth. That single change compresses cycles more reliably than any sequence-optimization exercise.

The third shift is qualification honesty. A useful side effect of hunting for champions before the call is that sometimes you cannot find one. There is no one in the org whose public footprint suggests they own this problem, whose team is growing in the relevant direction, or whose past behavior indicates they buy tools like yours. That is genuinely valuable information: it means either you have the wrong account or you have the wrong entry point, and both are cheaper to learn before you burn a calendar slot.

What you should *not* expect: a reliable increase in raw meeting-set rate from champion research alone. Meeting rate is dominated by list quality, offer relevance, and channel fit. Champion research improves what happens *after* the meeting is booked. Conflating the two leads teams to over-invest in research on accounts that were never going to reply, which is a real and expensive failure mode discussed further below. The sensible posture is a tiered one: light research on volume tiers, deep research on named accounts, and a hard rule that research time never exceeds the expected value of the account.

There is also a cultural outcome worth naming. When reps consistently walk into first calls with a named person and a specific hypothesis, discovery quality rises across the team because the calls become teachable. A recorded call where the rep opened with "I think Priya owns this because of X" is a far better coaching artifact than one that opens with "so, tell me about your current process." Managers get something concrete to critique: was the hypothesis right, was the evidence sound, did the rep abandon it gracefully when contradicted?

What drives that outcome

Champion identification before a first call rests on one premise: people who care about a problem leave public traces of caring. Not all of them, and not evenly — some of the best champions are quiet operators with dormant LinkedIn profiles — but enough that a systematic sweep beats a guess. The drivers below are ordered roughly by signal strength, which matters because your time budget is finite and the temptation is to start with whatever tool you already have open.

Hiring language is the strongest single signal. A company writes job descriptions when it has decided to spend real money on a problem, and the hiring manager's fingerprints are all over the requirements section. If a posting for a revenue operations manager lists "own CPQ administration and quote-approval workflow" as a responsibility, someone senior decided that quoting is broken enough to staff against. The posting usually names or implies the reporting line — "reports to the Director of Revenue Operations" — which hands you a person to research. Postings also date the pain: a role open ninety days is a different conversation than one posted last week.

Public writing and speaking by individuals. Conference talks, podcast appearances, community posts in Slack or Discord groups, comments on industry LinkedIn threads, engineering blog posts, Stack Overflow or GitHub activity for technical buyers. A person who has publicly argued that their category of tooling is broken has pre-qualified themselves as someone who thinks about it. The key discipline is reading what they actually said rather than pattern-matching on the topic. Someone who wrote a post titled "Why we ripped out our data catalog" may be your best champion or your most entrenched skeptic, and the difference is in paragraph three.

Organizational trajectory. Headcount shape tells you where the org is investing. A support team that doubled while the company grew twenty percent implies a scaling problem someone is being held accountable for. A newly created title — "Head of Platform Enablement" where none existed — implies a mandate and a budget, and new leaders in the first ninety days are structurally more open to change than the same person will be in month eighteen. Executive changes are the cleanest version of this: a new CRO reliably re-evaluates the stack.

Prior-vendor history. If the account has publicly used a competitor or an adjacent tool — case studies, review-site profiles, integration directories, technology-detection data on their site — you learn both the buyer profile and the likely objection. The person quoted in a competitor's case study is either your champion (they bought this category once, they will buy it again) or your blocker (they own the incumbent's success internally). Either way, knowing which is worth ten minutes.

Relationship graph. Alumni of your existing customers are the highest-conversion cold path that exists, because they have used the thing and do not need to be sold on the category. Second-degree connections through investors, board members, or shared past employers matter less but are not nothing. This is where CRM hygiene pays: a well-maintained record of every person who has ever worked at a customer account is a compounding asset.

Intent and engagement data. Content downloads, pricing-page visits, webinar registration, event badge scans, docs traffic if you have a self-serve motion. This is real signal but noisy and easily over-trusted, particularly anonymized account-level intent. Treat it as a tiebreaker between accounts you already like, not as a champion identifier on its own — it rarely tells you *who*, only *whether*.

Underneath all of these sits a definitional point that teams skip and then regret. A champion is not a fan, not a friendly contact, and not the person who replies fastest. A champion is someone who (a) personally benefits from the outcome you deliver, (b) has enough internal credibility that their advocacy moves others, and (c) is willing to spend political capital on your behalf. Public signal is good at finding (a). It is mediocre at (b) — titles are a weak proxy for influence — and nearly useless at (c), which only reveals itself when you ask them to do something mildly inconvenient. That is why the pre-call phase produces a *hypothesis*, and why the first call's real job is testing it.

Benchmarks and realistic ranges

Because this work is easy to over-invest in, it deserves explicit budgets. The numbers below are operating ranges rather than industry statistics — treat them as starting points to calibrate against your own data rather than as findings.

Time per account, by tier. For high-volume SMB motions where deal size is in the low thousands, cap research at three to five minutes: check the company's careers page, scan the two or three most plausible titles on LinkedIn, note anything obvious, move. For mid-market, ten to twenty minutes is defensible. For named enterprise accounts with six-figure potential, an hour or more is fine, and for a genuine strategic target a multi-hour account plan is normal. The test is simple: research time should be a small single-digit percentage of the total selling time you expect to invest, and if you cannot articulate the expected value of the account, you should not be researching it deeply.

Candidate count. Aim to name one primary champion hypothesis and one backup before the first call. Naming five is a sign you have not actually scored anything; naming zero on a target account is a signal to re-examine account fit. In enterprise, expect the eventual buying group to be substantially larger than your pre-call map — mapping three or four people before the call and discovering seven or eight during the cycle is normal and healthy, not a research failure.

Hypothesis accuracy. A reasonable expectation for a well-run team is that the pre-call champion hypothesis survives the first call roughly half the time, and that the other half yields a *better* name supplied by the prospect. Both outcomes are wins. If your hypothesis is right ninety percent of the time, you are probably only targeting obvious title-matches and leaving quieter champions undiscovered. If it is right ten percent of the time, your signal sources are weak or your ICP is wrong.

Signal decay. Public signal has a shelf life and it is shorter than people assume. A job posting is strong signal for roughly a quarter; after that the role is either filled — which is itself new signal, since the new hire has a mandate — or quietly abandoned. A leadership change is most actionable in the first ninety days. A conference talk stays relevant for a year or so as an indicator of what someone cares about but stops being a usable conversational hook after a few months. Build a refresh cadence rather than a one-time research sprint, and re-run the sweep on any account that has been dormant more than a quarter.

The pre-call touch. A low-risk touch before the call — a short, specific note referencing the actual signal you found — is worth doing, and the discipline is brevity and specificity. Reference one thing, ask one question, offer one relevant thing. Do not send a research dossier; nothing announces "I scraped your profile" like a paragraph of biographical detail. Response is a bonus, not the goal; the note primarily serves to make your name familiar before the call and to give the prospect a chance to redirect you to the right person, which they will often do generously.

Coverage ratios. For an account-based motion, a common working target is to have identified and touched three to five people per target account before or during the first two weeks of engagement. Single-threaded deals are the dominant source of late-stage slippage, and the cheapest time to fix single-threading is before it exists.

Cost of tooling. Sales-intelligence, contact-data, and intent platforms range enormously and pricing is usually negotiated per seat and per credit volume, so any specific figure here would be misleading. The useful benchmark is directional: before buying a data tool, run the process manually for two or three weeks on a sample of accounts, measure how much of the signal you actually used, and buy against that. Teams routinely purchase intent data and then discover no one in the workflow consumes it.

Risks, edge cases, and failure modes

The confident-wrong problem. Pre-call research produces confidence, and confidence applied to a wrong hypothesis is worse than no hypothesis. A rep who has decided that the VP of Engineering is the champion will interpret ambiguous signals on the call as confirmation and steer away from the person who actually owns the budget. The countermeasure is structural: state the hypothesis out loud, early, in a form the prospect can flatly contradict, and treat contradiction as the desired outcome. "I may have this wrong, but my read is X" costs one sentence and buys a genuine correction.

Champion without power. The most seductive failure mode. Someone is enthusiastic, responsive, forwards your materials, and takes every meeting — and cannot get a purchase order signed. Public signal is nearly blind to this because org charts do not encode influence. Practical tests: ask what the last comparable purchase looked like and who signed it; ask them to bring one specific colleague to the next call; ask what happens internally if this slips a quarter. Someone with real capital answers these easily. Someone without deflects.

Over-research on low-fit accounts. Deep research is intrinsically enjoyable and feels productive, which makes it a superb procrastination vehicle. A rep spending forty minutes building an account map for a company that will never buy has converted selling time into busywork with a paper trail. Enforce tiered time boxes and audit them occasionally.

Privacy, consent, and jurisdiction. Scraping and enriching personal data sits inside a real regulatory frame — GDPR in the EU and UK, CCPA/CPRA in California, and a growing patchwork elsewhere. Rules differ for business-contact data versus consumer data, for cold email versus cold calling, and by jurisdiction. Do not improvise here: check with whoever owns compliance before standing up new enrichment or scraping workflows, honor opt-outs and suppression lists mechanically, and prefer sources people published deliberately. "It was on the internet" is not a legal standard.

The creepiness threshold. Distinct from the legal question. Referencing someone's conference talk reads as diligence; referencing their marathon time reads as surveillance. A workable heuristic: mention only things the person published in a professional context and would expect a stranger in their industry to have seen. When in doubt, reference the *company* signal rather than the *person* signal — "saw you're hiring for platform engineering" is always safe.

Stale signal. Acting on a six-month-old job posting or a departed executive damages credibility immediately and is entirely avoidable. Timestamp everything you record, and check the person is still in the role before the call. People change jobs constantly; a champion who left is not a champion.

Single-source dependency. Building the whole motion on one data provider creates fragility — coverage gaps by geography and company size are severe and unevenly distributed, and vendors change pricing, get acquired, or lose access to a source. Blend at least one paid source with direct-from-source public signal you can always reach yourself.

Blocked-by-champion. Occasionally the person with the strongest public signal is precisely the one who will oppose you, typically because they own the incumbent tool or authored the internal approach you would replace. This is not a reason to avoid them; it is a reason to know before you call. If your read is that they are the incumbent's owner, the play is usually to engage them respectfully and directly rather than route around them, since routing around a known internal owner tends to surface later as active opposition.

Automation drift. Once a scoring model works, the temptation is to automate it end-to-end and stop reading the underlying signal. Scores decay silently as the market shifts, job-title conventions change, and sources go dark. Whatever you automate, keep a human sampling the raw signal on a regular cadence — a small weekly sample is enough to catch drift before it becomes months of bad targeting.

Team-size reality check. A two-person sales team cannot run an enterprise-grade research process on every account and should not try. The scaled-down version is a single fifteen-minute weekly block where the team researches the five accounts most likely to convert that week, and nothing else. Ambition beyond capacity produces a process nobody follows, which is worse than a small process everyone does.

A practical rollout plan

Rolling this out as a repeatable habit rather than a heroic individual effort takes about a month. The sequence below assumes a small team; scale the time boxes rather than the steps.

Week one — define and instrument. Write down, in one page, what a champion looks like *for your product specifically*: which job function, what outcome they personally get, what they can approve unilaterally, what they need help approving. Then decide which two or three signals you will actually check, every time, without exception. Two signals consistently checked beat eight checked sporadically. Add fields to your CRM to record the hypothesis before the call and the result after — without this you cannot measure anything and the whole exercise stays folkloric.

Week two — pilot manually. Have each rep run the process by hand on ten upcoming first calls. No tooling purchases yet. Record the hypothesis, the evidence, the outcome. The goal is to discover which signals actually predict, because it varies enormously by category: technical products often live or die on engineering-blog and repository signal, while finance and operations products usually key on hiring and org-structure signals.

Week three — review and prune. Sit down with the twenty to thirty pilot records and ask which signal sources produced hypotheses that survived contact. Kill the ones that did not. This is the step teams skip, and skipping it is why so many organizations maintain elaborate research checklists whose middle sections nobody has read in a year.

Week four — codify and time-box. Turn the surviving signals into a short pre-call checklist attached to the calendar invite or the CRM record, with an explicit time box per account tier. Add one coaching ritual: in weekly pipeline review, every first call gets one question — "who did you think the champion was, and were you right?" That single question does more to sustain the habit than any tooling.

Ongoing — refresh and audit. Re-sweep dormant target accounts quarterly. Sample raw signal monthly to catch decay. Review hypothesis accuracy quarterly and adjust the checklist. If accuracy climbs above roughly three-quarters, deliberately widen your candidate net — you have optimized into the obvious.

A closing note on adjacent workflows, because champion research does not live alone. The same signal sweep that identifies a champion feeds account prioritization, territory planning, and content targeting — a marketing team that knows which job postings correlate with pipeline can aim campaigns at the same trigger. Downstream, the champion hypothesis should flow into the mutual action plan, the security-review sequencing, and the renewal motion, since the person who championed the purchase is usually the person whose departure puts the renewal at risk. Customer success teams that inherit the original champion map are meaningfully better at spotting churn risk when that person's title changes. Treating this as a single shared artifact rather than a rep's private notes is what turns a personal habit into an organizational capability.

Related questions

What if the account has no public signal at all?

Small, private, or low-profile companies genuinely leave little trace. Fall back to structural inference — company size and stage imply which roles exist — and use the first conversation itself as research. Ask the person who replies who else owns the problem; most will tell you.

Is a champion the same as an economic buyer?

No. The champion advocates internally and typically feels the pain daily; the economic buyer signs. They are occasionally the same person in smaller companies, but assuming so in mid-market and enterprise is the classic single-threading error. Map both, early.

How does this change for inbound leads?

Inbound tells you who raised their hand but not whether they are a champion. Run the same sweep on the person and their org before the call — you often find the requester is a junior researcher, and the actual owner is one level up.

Should this be automated?

Partially. Automate collection and enrichment; keep judgment human. Scoring models drift as titles, sources, and market conditions shift, so keep a person reading raw signal on a regular cadence rather than trusting a score you have stopped auditing.

What is the minimum viable version for a tiny team?

One weekly fifteen-minute block, two signal sources, one named hypothesis per upcoming call, recorded in the CRM. That is genuinely enough to change first-call quality. Add sophistication only after the habit holds for a full quarter.

FAQ

How do I find champions before the first call without expensive tools? The highest-value sources are free: the company's own careers page, LinkedIn people search filtered by title and company, the company blog and newsroom, public community forums for your category, and review sites where practitioners describe their stack. Paid tools mostly save time and add contact details; they rarely surface signal you could not find yourself. Run manually first, then buy against demonstrated need.

How far in advance should I do this research? Ideally the day before or the morning of the call, so signal is fresh and you actually remember it. Research done weeks ahead goes stale and gets forgotten. For strategic accounts, maintain a living account plan refreshed quarterly, but still do a five-minute freshness check immediately before the call to confirm the person is still in the role.

What do I actually say on the call to test the hypothesis? State it plainly and invite contradiction: "Before we dive in — my read from the outside is that you own the quoting workflow and that approvals are the friction point. Tell me where I've got that wrong." Then be quiet. The correction you receive is more valuable than the confirmation.

Can I find champions before the first call using intent data alone? Rarely. Most intent data operates at the account level and tells you interest exists somewhere in the building, not who has it. It is a good prioritization input and a poor identification input. Pair it with person-level public signal before you name anyone.

What if I identify the wrong person and they get annoyed? Being wrong politely costs almost nothing if you frame it as a hypothesis rather than an assertion, and most people will simply redirect you to the correct owner — a redirect that is itself a warm internal referral. The version that annoys people is the confident assertion that ignores their correction.

How do I know if my champion actually has influence? Ask them to do something small and slightly inconvenient: bring a specific colleague to the next call, share an internal document, get a thirty-minute slot with their manager. Willingness and ability to do that is the real test. Enthusiasm without action is a warning sign, not a champion.

Sources

• https://hbr.org/2012/07/the-end-of-solution-sales
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.linkedin.com/business/sales/blog
• https://gdpr.eu/what-is-gdpr/
• https://oag.ca.gov/privacy/ccpa
• https://blog.hubspot.com/sales
• https://www.salesforce.com/resources/articles/sales-prospecting/
• https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
• https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/

Related on PULSE

• How to multithread a deal before it stalls
• What separates a champion from a coach
• How to build an ICP that actually filters accounts
• How to run discovery that earns a second call
• When intent data is worth paying for
• How to keep an account plan current without busywork