How to Research Decision Makers Before Contacting Them

To research decision makers before outreach, use a quick process that answers two things: who can approve the decision and what they are trying to change right now. Start by defining the “yes” you need (budget approval, technical approval, or a partnership green light). Then find the person who owns that outcome—usually the leader accountable for the team’s results—plus the people who will evaluate risk like IT/security, finance, procurement, or legal.

In 10–15 minutes, you can usually narrow it down by checking the company’s leadership page and org signals on LinkedIn, then validating priorities in recent news, press releases, job postings, and the decision maker’s public posts or talks. Pull out 2–3 safe hooks you can mention (a new initiative, hiring push, product launch, stated goal), avoid personal details, and write one clear message that connects their priority to a specific outcome you can help with. Always include a routing question in case you picked the wrong owner (e.g., “Are you the right owner for this, or should I speak with whoever leads X?”).

TL;DR (10-minute plan)

1. Define what “yes” means (budget, technical, or operational approval)

2. List likely stakeholder titles (economic buyer + champion + evaluator)

3. Confirm names + scope (LinkedIn + company site)

4. Find “why now” triggers (news, job posts, product updates)

5. Extract 2–3 business-relevant hooks

6. Write a value hypothesis + add a routing question

7. Multi-thread with 1–2 adjacent stakeholders (not everyone)

What “decision maker” actually means (so you don’t email the wrong person)

In B2B, “the decision maker” is rarely one person. It’s usually a small buying group, and each stakeholder has different power:

• Economic buyer (budget owner): can approve spend and sign off.

• Champion: wants the change to happen and helps you navigate internally.

• Technical buyer / evaluator: cares about feasibility, integration, security, and implementation.

• Procurement / finance: cares about terms, vendor risk, and price.

• Legal / security (often in larger orgs): cares about compliance, data handling, and contracts.

• End users: influence the decision because they’ll live with the tool/process.

Your goal before outreach isn’t to find a mythical “perfect contact.” It’s to identify the best first contact and understand who else will likely be involved.

How to research decision makers before outreach: a 10–15 minute workflow

1) Define what approval looks like for your offer

Before you open LinkedIn, write one sentence:

“For this to be a ‘yes,’ we need approval from the person who owns [function/outcome] and controls [budget/priority].”

Examples:

• “Approval from the person accountable for pipeline generation (VP Sales / Head of Growth).”

• “Approval from the person responsible for IT systems and security (CIO/CTO + security).”

• “Approval from the person responsible for finance operations (CFO / VP Finance).”

This prevents “title chasing” (emailing impressive titles that don’t map to your use case).

2) Confirm company context (size, structure, and complexity)

Company size changes how decisions get made:

• 1–50 employees: founders and functional heads decide quickly; titles are flexible.

• 50–500: VPs/Heads run structured teams; buying committees start to appear.

• Enterprise: expect formal processes: security review, procurement, legal, multi-threading.

Spend 2 minutes confirming:

• What they sell (and to whom)

• Geography (regional vs global decision-making)

• Whether they’re regulated (healthcare, finance, public sector)

3) Identify likely stakeholder titles (before you search for names)

Search for a short list of roles, not one person.

4) Find names and scope (LinkedIn + company website)

Use two sources because either one can be wrong:

• Company website: leadership page, “About,” press releases.

• LinkedIn: current role, tenure, scope, adjacent stakeholders.

What to look for on LinkedIn:

• Scope words: “Global,” “North America,” “Enterprise,” “SMB,” “Platform,” “Revenue.”

• Seniority signals: VP/Head/GM often owns budgets; Managers/Directors are frequently champions.

• Tenure: a new leader often has an agenda and is more open to change.

5) Validate decision authority (triangulate)

Don’t rely on one clue. Validate with at least two signals:

• Leadership page shows they run the function

• Press releases quote them about the initiative

• Job posts show their team hiring for the problem

• Their posts/talks mention the priority

If data conflicts, trust the newest info and keep a backup contact.

6) Find “why now” triggers (intent signals)

Best outreach is “I see this is happening,” not “Can I show you a demo?”

Look for triggers like:

• New leadership / reorgs

• Hiring spikes in the target function

• Funding / acquisitions / expansion

• Product launches or new segments

• Compliance deadlines (SOC 2, HIPAA, GDPR)

• Tool changes hinted in job posts (“migrate,” “implement,” “consolidate”)

7) Pull 2–3 “safe hooks” for personalization

Good personalization is business-relevant and verifiable.

Safe hooks:

• “Saw you’re hiring for RevOps / Sales Ops…”

• “Noticed your team launched X…”

• “Read your post about reducing cycle time…”

Avoid:

• Personal/family details

• Hyper-specific tracking references

• Anything that feels like surveillance

8) Turn research into a value hypothesis (one sentence)

This is the bridge from research to a strong first message:

“Because you’re focused on [priority], you might be running into [problem]. We help teams like yours get [outcome] without [common cost/objection].”

9) Multi-thread thoughtfully (don’t spam)

Multi-threading = contacting more than one relevant stakeholder with role-specific relevance.

A simple approach:

• Start with the best-fit owner (likely decision maker)

• Add 1–2 adjacent stakeholders (potential champion + evaluator)

• Adjust the angle by role (ROI for budget owner; workflow pain for champion; risk/integration for technical)

If you’re doing this at scale, tools like kwAI can help reduce manual prospect research by surfacing likely buyers and context (fit signals, priorities, relevant angles) so you’re not stitching together the story from dozens of tabs.

Where to research decision makers (and what each source is good for)

LinkedIn (roles, scope, org signals)

Use it to:

• Confirm current title and tenure

• Infer scope (regional vs global)

• Identify adjacent stakeholders (People tab, similar titles)

• Find mutual connections (warm intro opportunities)

Company website (official truth + initiatives)

Use it to:

• Validate leadership and org language

• Understand how they describe their priorities

• Find case studies (what they measure and value)

• See partner ecosystem (incumbents and constraints)

Press releases and news (timing and momentum)

Use it to:

• Spot initiatives, partnerships, expansion

• Identify “why now” moments

• Pull safe public details to reference

Job postings (what they’re building and what’s broken)

Job posts often reveal:

• Tools and systems (stack signals)

• Skills gaps

• Projects underway (“implement,” “migrate,” “scale,” “automation”)

Investor materials / annual reports (public companies)

Use these to understand:

• Strategic priorities and KPIs

• Risk/compliance language

• Budget focus areas

Tech stack tools (only if relevant)

If integrations or tooling matter, tools like BuiltWith/Wappalyzer can help you hypothesize what they use.

Treat tech stack as a signal, not a certainty.

How to infer reporting lines when org charts aren’t obvious

When LinkedIn doesn’t make reporting lines clear, use proxies:

• Scope keywords: “Global/Corporate/Platform” often outranks “Regional/Segment.”

• Team clues: “Leads X,” “owns Y systems,” “responsible for Z budget.”

• Tenure sequencing: a new VP followed by new director hires can imply structure.

• Job postings: many include “reporting to the Head of ___.”

If you’re still unsure, start with the closest owner of the outcome and use a routing question.

Champion vs. economic buyer: how to tell who you’re looking at

Champion signals:

• Talks about execution, workflow, “how we do this”

• Engages with tools/process topics

• Often Manager/Director/Ops roles

Economic buyer signals:

• Owns budget and top-level outcomes (revenue, margin, risk)

• Talks about strategy, trade-offs, priorities

• Often VP/C-level/GM roles

If you start with a champion, confirm the path early:

“If this looks useful, who else needs to weigh in—finance, IT/security, or procurement?”

Gatekeepers and executive assistants: how research changes when access is filtered

In larger orgs, the “decision maker” might be reachable only through an EA or gatekeeper.

What works:

• Identify the EA (LinkedIn: “Executive Assistant” + leader name/company)

• Prepare a one-sentence reason that’s easy to forward internally

• Offer a 3-bullet summary rather than a big ask

EA-friendly routing script:

“I’m trying to reach the owner of [outcome]—is that [Exec], or someone else? If it is [Exec], I can send a 3-bullet note they can review in under a minute.”

A simple decision-maker research template (copy/paste)

Use this as a note in your CRM.

Account

• Company:

• ICP fit (why them):

• Potential triggers (why now):

Stakeholders

• Economic buyer (name/title/link):

• Champion (name/title/link):

• Technical evaluator (name/title/link):

• Procurement/finance/legal (if enterprise):

Hooks (2–3)

• Hook #1:

• Hook #2:

• Hook #3:

Value hypothesis (one sentence)

Routing question (if wrong person)

• “Are you the right owner for ___, or should I speak with ___?”

Two quick walkthroughs (end-to-end examples)

Walkthrough A: Mid-market SaaS (200 employees), selling into RevOps/Sales

1. Approval definition: “Yes = RevOps owner + Sales leader alignment.”

2. Context: 200 employees → likely VP/Head-led teams, lighter procurement.

3. Titles list: Head/Director RevOps, Sales Ops Manager, VP Sales/CRO.

4. Find names: LinkedIn People search + company leadership page.

5. Validate owner: look for “owns GTM systems,” team size, seniority.

6. Why now: job posts referencing “forecasting,” “territory planning,” “Salesforce admin.”

7. Hooks: hiring + initiative language in postings.

8. Outreach plan: start with Head of RevOps; add Sales Ops Manager (champion) + VP Sales (economic alignment).

Walkthrough B: Enterprise (regulated), selling a security/compliance-adjacent solution

1. Approval definition: “Yes = security owner + IT owner + procurement/legal.”

2. Context: regulated → expect formal security review.

3. Titles list: CISO/VP InfoSec, CIO/VP IT, Vendor Risk, Procurement.

4. Validate: press release quotes + job posts mentioning compliance initiatives.

5. Hooks: compliance deadline + hiring for security roles.

6. Outreach plan: multi-thread earlier so the deal doesn’t stall later.

Outreach examples based on your research

Example 1: You found a hiring trigger

Subject: Quick question about your RevOps hiring

Hi [Name] — saw you’re hiring for [role] on the [team]. When teams ramp that function, they often hit a bottleneck on account research and finding the right decision makers to start conversations with.

Would it be worth a quick 15 minutes to share how teams reduce research time and increase outbound relevance? If you’re not the right owner for this, who leads [function]?

Example 2: You found a new leader

Subject: Congrats on the new role

Hi [Name] — congrats on stepping into [role]. When leaders take over [function], one of the fastest wins is tightening the target account list and messaging so reps spend time on the right companies.

Open to a quick chat to compare notes on what’s working for outbound at [Company] this quarter?

Example 3: You’re unsure who the decision maker is

Subject: Who owns [initiative]?

Hi [Name] — I’m trying to reach the right owner for [initiative/problem]. Is that you, or is there someone on your team (or a peer) who leads it?

Reason I’m asking: we’ve helped similar teams improve [outcome] by reducing time spent researching prospects and focusing outreach on higher-fit accounts.

Disqualifying signals (when research says “don’t outreach yet”)

Sometimes the best outcome is saving time.

Common disqualifiers:

• They’re mid-merger / reorg and the function is frozen (hiring paused, leadership churn)

• They publicly committed to a direct competitor (partner page, case study)

• The org is too small to have the problem (no function, no related hires, no signals)

• The likely owner is brand new (<30 days) and your ask is too heavy (switch to a lighter ask)

What to do instead:

• Put them on a monitor list for 30–90 days and watch for triggers (hiring, tooling changes, leadership priorities).

Common mistakes (and how to avoid them)

• Assuming the highest title is the buyer: map the function owner and the buying committee.

• Over-researching: timebox to 10–15 minutes for first pass; go deeper after engagement.

• Using “fun facts” personalization: use initiative-based hooks tied to business outcomes.

• Ignoring procurement/security/legal: especially in enterprise, plan for these stakeholders early.

• Not capturing findings: use a simple template so research compounds over time.

Research ethics and compliance (keep it professional)

• Use public, work-relevant information (role, initiatives, job posts, public content).

• Avoid sensitive personal data and anything that implies tracking behavior.

• Follow your organization’s data handling policy (and applicable privacy requirements) when storing notes.

FAQ

How do I research decision makers before outreach?

Start by answering two things: who can approve the decision, and what they are trying to change right now. Check the person’s title and scope, confirm who they report to, and look for current priorities in recent posts, interviews, press releases, or job listings. Then pull 2–3 specific details you can mention safely in outreach.

What sources are best for validating who the decision maker is?

Use multiple sources because titles can be misleading. Good options include the company website leadership page, LinkedIn, recent press releases, SEC filings or annual reports for larger firms, podcasts or conference agendas, and job postings that show which team owns the problem. If sources conflict, trust the newest information and look for reporting lines or budget ownership.

How can I tell whether someone has budget and approval power?

Look for clues like team size, ownership of a function, and language that suggests accountability. Titles like Head of, Director, VP, or GM often indicate authority, but it varies by company size. Confirm by checking if they lead the relevant department, have direct reports, or are connected to initiatives that involve spend. When unsure, include a routing question in your message, such as “Are you the right person for this, or should I speak with someone on your team?”

What should I research about a decision maker’s priorities before I contact them?

Focus on what is active and measurable: initiatives, hiring, tech stack changes, growth signals, cost-cutting, compliance needs, and customer experience changes. Priorities often show up in LinkedIn activity, product announcements, press releases, and the language used in job postings.

How do I personalize outreach without being creepy?

Use information they shared publicly and keep it high level. Mention a company initiative, a public quote, a job post, or a product update—not personal details. Avoid referencing exact timestamps of their activity or anything that suggests you tracked them. If the detail would feel uncomfortable to hear from a stranger, don’t use it.

What are common mistakes when researching decision makers before outreach?

Common errors include assuming the highest title is always the buyer, relying on a single data source, and confusing influencers with approvers. Another mistake is overpersonalizing with irrelevant details instead of tying research to a clear reason for reaching out. Finally, many people skip stakeholder mapping, so they miss the champion, procurement, or security reviewer who can slow the process later.

How many people should I contact per account?

Start with 1 primary owner and 1–2 adjacent stakeholders (champion/evaluator). More than that can look like spam unless your message is highly role-specific and clearly relevant.

What if LinkedIn is wrong or outdated?

Triangulate using recency-based sources: press releases, leadership pages, job posts (sometimes mention reporting lines), and the person’s own recent posts. If it’s still unclear, use a routing question and position your outreach as “finding the right owner,” not pitching blindly.

Should I reach out to the champion or the economic buyer first?

If your “why now” is strong and outcome-driven, start with the owner/economic buyer. If implementation is complex or risk-heavy, start with a champion/evaluator to confirm fit and map stakeholders—then loop in the budget owner with a clearer story.

How is decision-maker research different for enterprise accounts?

Assume security + procurement + legal will be involved. Research the buying process earlier, multi-thread earlier, and tailor by stakeholder: ROI and strategic impact for executives, risk and compliance for security/legal, and implementation details for technical evaluators.