How to Identify Key B2B Decision-Makers: Problem Owners, Economic Buyers and Buying Committees

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.

Advanced field manual: how to quality-control decision-maker identification

Long-form research is only useful when it improves a decision. The final pass should therefore test whether each role is reproducible, current, material and connected to problem-owner mapping. The standard is not “did we find a lot of information?” but “could another researcher follow the source trail, understand the reasoning and reach a similar proceed/hold/reject decision?”

A recurring failure mode in this area is that the CEO or highest-ranking title is always the right first contact. Avoid that by forcing every important conclusion through a verification question and a counter-hypothesis. If the alternative explanation is equally plausible, lower confidence and turn the uncertainty into a discovery question instead of hiding it.

12 audit questions before the record is sales-ready

1. Audit 1: confirm that the business problem is defined before searching names. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
2. Audit 2: confirm that the function that owns the problem is identified. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
3. Audit 3: confirm that problem ownership is separated from budget authority. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
4. Audit 4: confirm that company size changes the likely level of ownership. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
5. Audit 5: confirm that role scope is verified from current sources. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
6. Audit 6: confirm that the researcher maps likely influencers and blockers for complex deals. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
7. Audit 7: confirm that job-title synonyms are considered across industries. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
8. Audit 8: confirm that regional versus global responsibility is checked. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
9. Audit 9: confirm that recent reorganization or leadership change is considered. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
10. Audit 10: confirm that the proposed contact can actually act on the problem. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
11. Audit 11: confirm that alternative owners are recorded when evidence is ambiguous. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
12. Audit 12: confirm that the first outreach question is appropriate to the person’s remit. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.

Counter-hypothesis discipline

For every strong role, write one credible alternative explanation. This is not academic caution; it prevents outreach from sounding accusatory or naive. The researcher should be able to answer three questions: what is directly observed, what does it possibly mean, and what evidence would show that the interpretation is wrong? When the counter-hypothesis wins, downgrade or remove the item. A clean rejection is better than a personalized message built on a false premise.

Use calibrated language in the final brief. “Observed” describes a source-backed fact. “Inferred” describes the commercial interpretation. “Verified” should be reserved for a field that has actually been confirmed by a reliable source or human check. “Unknown” is allowed. This vocabulary makes the research usable by sales without pretending uncertainty has disappeared.

Ten edge cases that should change the decision

Edge case 1: small business where founder owns several functions

Treat this as a scope question, not automatic positive evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 2: enterprise account with a dedicated RevOps or digital team

Ask whether the condition is intentional or temporary before making a recommendation. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 3: professional partnership without conventional executives

Lower confidence until the current state can be confirmed from a stronger or more recent source. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 4: franchise where local owner lacks technology authority

Check whether the apparent opportunity belongs to another team, vendor or buying authority. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 5: portfolio company with parent-level procurement

Do not let a compelling narrative override contradictory evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 6: government or education organization with formal procurement roles

Treat this as a scope question, not automatic positive evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 7: newly hired executive still building the team

Ask whether the condition is intentional or temporary before making a recommendation. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 8: interim or fractional executive

Lower confidence until the current state can be confirmed from a stronger or more recent source. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 9: business unit with its own P&L inside a larger group

Check whether the apparent opportunity belongs to another team, vendor or buying authority. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Edge case 10: cross-functional problem such as website conversion or automation

Do not let a compelling narrative override contradictory evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.

Research handoff standard

Before a salesperson sees the record, compress the research into a small brief: company and source-verified identity; why the account fits; the strongest current evidence; the interpretation and alternative explanation; likely problem owner; what is still unknown; the recommended first question; contact-route status; and the next review date. Keep the raw sources attached but do not force the salesperson to read a 5,000-word article or a 40-field crawl output to understand why the account matters.

For high-value accounts, add a second-source check and a buying-group view. For lower-value accounts, reduce research depth but keep the same evidence rules. This makes the method economical: rigor stays constant while the amount of work scales with expected value.

How to learn from outcomes

After enough outreach, compare research fields with actual conversation outcomes. Which evidence classes most often led to useful discovery? Which were frequently corrected by prospects? Which roles were mapped accurately? Which findings became stale before use? Update the research template from those results. A methodology that never learns from false positives becomes a content exercise rather than a sales system.

Do not optimize only for replies. A sensational claim can produce replies while damaging trust. Better outcome measures include accepted meetings, confirmed problem ownership, opportunity creation, stage progression, data correction rate and the percentage of researched accounts sales considers genuinely relevant. Those metrics keep decision-maker identification tied to commercial quality rather than volume.

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.

Decision-maker research in 2026 is increasingly buying-committee research

The phrase decision-maker is convenient, but it can hide how purchases actually happen. LinkedIn Sales Navigator's current guidance explicitly frames complex B2B deals around buying committees and multi-threading: sellers are encouraged to identify decision-makers, influencers, executive sponsors, potential blockers and budget ownership rather than relying on one champion. Its Relationship Map feature is built around visualizing those stakeholders inside an account. That does not mean every small purchase has a committee. It means the research method should be able to expand from one likely owner to several roles when the company, risk or purchase complexity requires it.

A practical rule is to treat company size, purchase risk and cross-functional impact as escalation triggers. A $1,000 website refresh for an owner-operated business may genuinely be decided by one founder. A CRM migration affecting sales, marketing, service, finance and IT may require a problem owner, technical evaluator, economic buyer and procurement or security review. The research record should grow only as the decision structure grows.

A five-pass method for identifying the likely owner

Pass 1: define the business outcome

Write the outcome in business language before opening LinkedIn. “Sell AI automation” is not an outcome. “Reduce manual lead routing between web forms, email and the CRM” is. “Sell SEO” is not an outcome. “Improve discoverability for a newly expanded service footprint” is. The more concrete the outcome, the easier it is to map ownership.

Pass 2: identify the operating function

Ask which team would be accountable if the problem became materially worse. If missed enquiries increased, would operations, marketing, sales or a practice manager be asked to fix it? If a quoting workflow failed, would finance, sales operations or the owner intervene? This counterfactual question is often more useful than searching titles because it points to accountability.

Pass 3: infer the likely role level from company context

At a ten-person firm, the owner may control marketing, operations and budget. At a 150-person firm, a functional head may own the process while finance or an executive approves spend. At an enterprise, a director-level operator can sponsor a change while security, legal and procurement determine whether it can proceed. Use employee count, locations, organizational complexity and the scope of the proposed change as contextual clues, not as rigid rules.

Pass 4: verify current people with multiple sources

Prefer current first-party sources when available: leadership pages, team pages, press releases, investor relations pages and official filings. LinkedIn is valuable for current employment, tenure and role changes. For U.S. public companies, SEC EDGAR provides free access to filings that can clarify executive leadership and governance. For UK companies, Companies House provides current and resigned officers and filing history. The purpose is not to collect more data than necessary; it is to prevent a stale title or directory entry from becoming a false routing decision.

Pass 5: label authority as a hypothesis until confirmed

Public information can strongly support a role mapping, but it rarely reveals internal signing limits, informal influence or the exact approval chain. Store labels such as confirmed responsibility, strongly supported owner, likely owner and unknown. The first conversation can then validate the map rather than pretending the map is perfect.

Seven stakeholder roles worth distinguishing in larger accounts

Not every deal has all seven. The table is a diagnostic. Add a role only when the purchase creates a reason for that stakeholder to care.

Expanded role mappings for common agency and consulting offers

Treat people data as perishable

Role research decays faster than many company facts. A business can retain the same products and locations while the person responsible for a function changes twice in a year. LinkedIn's current Sales Navigator materials emphasize job changes, recent senior hires and account alerts for exactly this reason. A research workflow should therefore record verification date separately from source date.

For a high-value account, recheck the primary stakeholder immediately before outreach. If the person left, do not simply substitute the next most senior title. Re-run the ownership logic because a reorganization can change reporting lines and responsibilities.

Multi-threading is not mass-contacting an account

LinkedIn describes multi-threading as engaging multiple relevant stakeholders so a deal does not depend on a single advocate. That should not be translated into sending the same cold message to six people at once. A disciplined multi-threaded approach assigns a different reason to each person: the operator receives the workflow context, the technical evaluator receives integration context, and the economic buyer receives the strategic or economic framing when appropriate.

If you cannot explain why a specific stakeholder should care, do not contact them merely because they appear in an organizational chart. Better stakeholder mapping should reduce irrelevant outreach, not multiply it.

A simple role-confidence score

When researchers work in teams, use a small scoring model so the salesperson can see how strong the role mapping is. Score each factor from 0 to 2:

• Functional fit: does the role clearly align with the problem?
• Current-role evidence: is employment current and supported?
• Responsibility evidence: is there first-party or strong contextual evidence of ownership?
• Company-size fit: is the seniority plausible for this organization?
• Decision-context fit: does the role make sense for the likely purchase risk and scope?

A score of 8–10 can be treated as strongly supported, 5–7 as likely but requiring validation, and below 5 as insufficient. This is not a statistical probability. It is a workflow device that forces the researcher to show their reasoning.

What to store in a decision-maker research record

• Person name and current title
• Company and location where relevant
• Likely stakeholder role
• Problem/function mapping
• Why this person is relevant in one sentence
• Primary source URL
• Secondary verification source
• Source date where visible
• Date last verified
• Confidence level
• Adjacent stakeholders
• Unknowns to validate in conversation

The last field matters. Good research does not eliminate uncertainty; it makes uncertainty explicit enough that the salesperson knows what to ask.

Current source note: what first-party platforms are signaling

LinkedIn's current Sales Navigator guidance on buying committees says complex enterprise deals benefit from mapping decision-makers, influencers, executive sponsors, blockers and budget ownership. Its learning center also describes Relationship Map as a way to organize and track a buyer committee. These are product-specific materials, but they reinforce a broader research principle: complex purchases are safer to model as a network of roles than as a single magic title.

For public-company verification, the SEC continues to provide free access to millions of filings through EDGAR. Companies House likewise provides free UK company information including current and resigned officers and filing documents. Use those sources for what they actually establish; neither registry proves who owns a particular purchasing decision.

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: Build and Navigate Buying Committees
• U.S. SEC: Search Filings / EDGAR