How to Find the Right Decision-Maker at a Company

The wrong question is “who is the most senior person I can find?”

Seniority matters, but authority is contextual. A CEO can approve a purchase and still be the wrong first conversation. A Marketing Director may own website conversion. An Operations Manager may own scheduling. A Head of IT may own infrastructure but not information-security governance. At a small company, the founder may own all of those decisions personally.

HubSpot's current decision-maker guidance recommends defining the value of your offer, building a decision-maker persona, researching the company and using LinkedIn and connections. LinkedIn's own guidance similarly uses title and seniority filters to find decision-makers, while its buyer-targeting material warns that larger organizations can involve multiple stakeholders.

The practical rule is: map the problem before you map the person.

Four roles that are often confused

In a five-person agency, one founder may occupy all four roles. In a 5,000-person company, each can be a different person and procurement, legal or security may join later.

Map the problem to a function before searching names

Create a simple problem-to-function map for your own offer.

This table is illustrative, not universal. Companies organize differently. The purpose is to start with ownership logic rather than title scraping.

Company size changes the likely decision structure

Owner-operated / very small businesses

The owner or founder often controls both problem and budget. Still check whether a manager handles the function day-to-day. A practice owner may approve an automation project while a practice manager knows the actual workflow.

Small and mid-sized businesses

Functional leaders become more important. The right first conversation is often the person who owns the outcome, with a founder, managing director or finance leader approving later.

Larger organizations

A single “decision-maker” model becomes risky. LinkedIn's current guidance on buyer groups notes that sellers can miss hidden influencers and outdated titles if they rely on one contact. For larger accounts, map several roles: operational champion, technical evaluator, budget owner and procurement/security stakeholders where relevant.

Where to verify the person and role

1. Company team / leadership page. Strong first-party evidence when current.
2. Company newsroom. Useful for leadership appointments and role changes.
3. LinkedIn. Useful for current role, tenure, job changes, professional history, posts and relationship context.
4. Official filings. For public companies, filings and proxy materials can identify executive roles and governance positions.
5. Industry associations / conference pages. Can confirm titles, but check dates.
6. Reliable news coverage. Useful for recent appointments or organizational changes.

Do not use a stale directory title as the sole basis for outreach. People change jobs. Responsibilities change even when titles do not.

Using LinkedIn for decision-maker research without reducing it to title search

LinkedIn's current Sales Navigator documentation recommends using title and seniority filters, Lead Pages, Account Pages, job-change alerts, company headcount trends and decision-maker changes. That is useful because decision-maker research needs both who and context.

A disciplined workflow is:

1. Search the function.

   Start with operations, marketing, finance, IT, sales or the function relevant to the problem.

2. Review titles in the context of company size.

   “Manager” at a 30-person company can hold more practical authority than “Director” at a global enterprise.

3. Check tenure and recent change.

   A recent role change can affect priorities, but do not assume a new leader is automatically buying.

4. Review public activity only when it is relevant.

   A post about the exact operational issue can add context. Personal trivia does not improve B2B relevance.

5. Map adjacent stakeholders.

   If the account is complex, note who else likely influences the decision.

When there is no single decision-maker

In larger B2B purchases, “decision-maker” can be shorthand for a buying group. Even a simple software purchase can require an operational owner, budget approver, IT/security reviewer and procurement contact.

Instead of asking “Who is the decision-maker?”, ask:

• Who owns the business outcome?
• Who uses or manages the process?
• Who evaluates technical fit?
• Who approves spend?
• Who can block implementation?
• Who will be judged if the problem is not solved?

LinkedIn's buyer-targeting guidance explicitly recommends uncovering relevant stakeholders and avoiding reliance on a single contact in larger accounts. The practical implication for research is to identify a best first role rather than pretending to know the entire internal decision process from public information.

Worked decision-maker mappings

Example 1: AI automation for a multi-location clinic

Observed issue: appointment requests flow through phone and general web forms across multiple sites; several recent reviews mention delayed callbacks.

Likely function: Operations / Practice Management.

Likely first role: Operations Manager or Practice Manager. The owner may be economic approver in a smaller practice.

Why not immediately target the dentist-owner? The manager may know the workflow better and can validate whether the problem is real. If the practice is very small, owner outreach may still be appropriate.

Example 2: website conversion for a 70-person B2B services company

Observed issue: new service line launched; paid campaigns point to a generic contact form; a marketing team exists.

Likely function: Marketing / Growth.

Likely first role: Marketing Director or Head of Growth, not the CEO. The CEO may become relevant if spend or strategic repositioning is material.

Example 3: security consulting for a 500-person software company

Observed context: public cloud migration and security hiring.

Likely function: Security / IT.

Likely first roles: Security Director/CISO or relevant IT leader. Technical, risk, procurement and finance stakeholders may join depending on scope.

Decision-maker verification checklist

• The company itself is a good fit
• The business problem is mapped to a function
• The person's role appears current
• The person's responsibility plausibly overlaps the problem
• Role relevance is explained in one sentence
• At least one current source supports the role
• For larger accounts, adjacent stakeholders are considered
• Uncertainty is labeled (“likely owner”, not “confirmed buyer”)
• Contact route is appropriate and compliant

How decision-maker research should change the first message

The message should reflect the person's responsibility, not simply insert their name.

Weak: “Hi Alex, I saw you're the Operations Director at ExampleCo. We help companies automate processes.”

Better: “Alex, I noticed ExampleCo has expanded to four locations and still routes new-service enquiries through a central phone line. We help multi-location service teams improve lead-response handoffs. Is enquiry routing something operations owns on your side?”

The second version does three things: uses company evidence, maps the issue to the role, and asks a question that can correct the research.

Common decision-maker research mistakes

Always choosing the CEO

High seniority can reduce relevance. The operational owner often has the best first conversation.

Always choosing the lowest operational contact

The reverse mistake also happens. A contact can understand the issue but have no influence. Map adjacent authority.

Trusting title alone

“Head of Operations” can mean very different things across companies. Use company size, reporting context, public responsibilities and function.

Ignoring role freshness

People move. Check current employment and recent announcements where material.

Assuming one person controls a complex purchase

Larger deals involve buying groups. Map roles, not just names.

Stating inferred authority as fact

Public sources rarely prove internal signing authority. Use language such as “likely problem owner” until confirmed.

Frequently asked questions

Who is the decision-maker in a small business?

Often the owner or founder, but a functional manager may own the day-to-day problem and be a better first contact. Research the operating structure instead of assuming.

Should I contact the CEO?

Contact the CEO when the issue and company size make the CEO a plausible owner or approver. Do not use CEO outreach as a shortcut for role research.

What if I cannot identify the exact person?

Identify the likely function first. A company contact page, receptionist, general business inbox or professional network route may help route you appropriately, subject to applicable rules.

How do I know whether someone has budget authority?

Public research often cannot confirm this reliably. Treat budget authority as an unknown to validate rather than inventing certainty from seniority.

Can AI find decision-makers?

AI can help classify roles and summarize public information, but current employment, source evidence and role relevance should be verified before acting.

Build your own offer-to-role map

A reusable role map speeds research because you are not starting from zero on every account. For each service you sell, document the functions most likely to own the problem, the common first-contact roles by company size, and the roles that often join later.

This is a starting model. The company's actual structure overrides the template.

Gatekeepers and coordinators are part of the map

Receptionists, executive assistants, office managers and coordinators are sometimes treated as obstacles. That is a poor research mindset. They can be the people who understand routing and ownership best. If your evidence says operations likely owns the issue but you cannot identify a current name, an appropriate company contact route can help you ask who manages that area.

Be clear about why you are calling. Do not misrepresent who you are or invent an existing relationship to bypass a gatekeeper.

What to do when you can identify the function but not the name

Do not downgrade a strong account merely because a public directory lacks a personal email. Options include:

• use the company's contact page and ask for the relevant function;
• call the main business line and ask who owns the area;
• use LinkedIn to search the function and company;
• check current team, leadership, newsroom and event pages;
• for larger public companies, review filings or governance material where appropriate.

The goal is an appropriate professional route, not extracting every possible personal detail.

When to multi-thread rather than pick one person

Multi-threading means building relationships with more than one relevant stakeholder. It can be useful when:

• the purchase affects multiple functions;
• the operational owner cannot approve budget;
• technical or security review is material;
• one contact has gone quiet;
• the organization is large enough that responsibility is distributed.

It does not mean sending the same cold message to six executives simultaneously. Research should explain each person's likely role and why contact is appropriate.

Seniority is a clue, not authority proof

A title tells you something about scope, but internal authority depends on budget, reporting lines, company size and the type of purchase. In a 15-person company, a “Marketing Manager” may own the entire budget. In a global enterprise, a “Director” may influence a decision that requires VP and procurement approval.

Use title, seniority and company size together, then validate through conversation. HubSpot's guidance is useful here because it pairs contact research with qualifying questions rather than assuming the public title settles authority.

Role freshness checklist

• Current company shown
• Current title shown
• Tenure plausible
• Company team/newsroom does not contradict the role
• No recent job-change signal suggests the person left
• Research date recorded

If a role is central to a high-value account, verify it immediately before outreach. People data decays faster than many company facts.

Sometimes the best first question is a routing question

If the function is clear but authority is not, outreach can ask for routing rather than pretending certainty. For example: “Who owns lead-response operations across your locations?” or “Is website conversion managed by marketing or growth?” This can be more professional than messaging several executives with the same pitch.

A routing question is especially useful in smaller businesses where titles are inconsistent and in larger organizations where public org charts are incomplete.

Separate “right person” from “available contact detail”

A common workflow starts with an available email and then invents a reason that person must be relevant. Reverse that order. Determine the function and likely role first, then find an appropriate business route. If no route exists, hold the account rather than downgrading to an irrelevant contact merely because their address is easy to find.

A practical company-size map

These ranges are heuristics, not rules. Organizational design varies by industry and ownership model. Use them to generate a search strategy, then let company-specific evidence override the template.

Questions that validate decision ownership in conversation

Research should prepare questions that clarify the internal process without turning the first interaction into an interrogation:

• “Who normally owns this workflow?”
• “Is this managed centrally or by each location?”
• “Who else would need to be involved if you changed the process?”
• “Does marketing own this, or does it sit with operations?”
• “Who evaluates the technical side?”

The answers improve your future role map. They are also safer than assuming budget and authority from a public title.

Write the role evidence, not only the name

Instead of storing “Sarah, VP Operations,” store a short reason: “Current VP Operations; company team page says she leads customer operations; issue concerns multi-location inquiry handling.” This makes the contact selection auditable and helps the salesperson understand why the person matters.

If the role evidence is weak, mark it as a hypothesis. A strong account with an uncertain owner can be held for one more research step rather than pushed into generic outreach.

For high-value accounts, record the date each role was verified and recheck shortly before outreach. A correct title from six months ago can become a wrong routing decision today, especially during leadership transitions or restructuring.

Use role-certainty levels instead of pretending every owner is confirmed

These labels help the seller know whether to approach with a direct business hypothesis or a routing question. They also prevent a research database from quietly converting guesses into “decision-maker” facts.

Sources and further reading

These sources were reviewed on 26 Aug 2026. They support the external facts and platform-specific guidance referenced in this article. Noustiq's frameworks, examples and decision rules are editorial synthesis, not claims made by these sources.

• HubSpot: How to Find the Decision Maker
• HubSpot: A 3-Step Guide to Performing Prospect Research
• LinkedIn Sales Navigator: How to Use Sales Navigator
• LinkedIn Sales Navigator: How to Find and Target the Right Buyers Within Accounts
• U.S. SEC: Search Filings / EDGAR