How to Find the Right Decision-Makers at a Company
Finding the most senior person at a company is easy to explain and often wrong in practice. The person who controls budget may not own the daily problem. The person who wants the change may not approve security or implementation. If we search only for a CEO, we can miss the people who understand the pain, evaluate the workflow and move the decision internally.
Our method begins with the work the customer wants to change. We map the required buying roles, translate those roles into searchable title sets, find the matching contacts and measure coverage at the account level. The completed output is not a giant list of executives. It is a small, explainable contact plan for each target account.
Decision-maker is a role, not a universal title
“Decision-maker” can refer to several responsibilities:
- Economic buyer: influences or controls the commercial approval.
- Internal champion: owns the problem and helps the change progress.
- Primary user: works with the product or output in daily operations.
- Technical or operational evaluator: reviews security, integration, data or process fit.
Not every purchase needs four different people. In a founder-led company, one person may act as buyer, champion and user. In a larger organization, those responsibilities may be distributed.
We use the four-role model as a coverage checklist, not a universal statement about every B2B purchase. Before searching, we decide which roles this specific offer and account type require.
Start with the customer job
We write:
The target team is trying to:
[change an operational outcome]
without:
[primary cost/risk]
For Getlead's approved ICP example:
Account: US B2B SaaS company
Target function: Sales
Job: Build and operate qualified prospect lists
Without: fragmented research, duplicate records and unclear verification status
This points to sales leadership and revenue/sales operations. It does not automatically point to the CEO.
Questions:
- Which team owns the current process?
- Who experiences the problem?
- Who approves the budget or tool?
- Who evaluates data, integration or security?
- Who can stop the project?
- Does company size change the likely role distribution?
Answers are hypotheses until confirmed with current evidence.
Build a buying-role map
Use one row per required role:
| Buying role | Responsibility | Primary title hypotheses | Alternative titles | Evidence needed | |---|---|---|---|---| | Economic buyer | Commercial priority/budget | CRO, VP Sales | Head of Sales, Chief Sales Officer | Current leadership role | | Champion | Owns workflow improvement | RevOps Director | Sales Ops Director, Revenue Operations Lead | Operations responsibility | | User | Runs daily process | SDR Manager | Business Development Manager | Team/process ownership | | Evaluator | Reviews systems/data | IT, Security, RevOps | Systems Manager | Applicable technical role |
We do not populate every account with every title. We select the roles required by:
- offer complexity;
- implementation needs;
- likely budget level;
- data/security impact;
- company operating structure.
Translate roles into title families
A single exact title produces fragile coverage. Companies use different naming conventions for similar responsibilities. We create:
- primary titles;
- accepted variants;
- excluded lookalikes.
Sales-technology example
Primary:
CRO
VP Sales
Head of Sales
Sales Operations Director
Revenue Operations Director
Accepted variants:
Chief Revenue Officer
Chief Sales Officer
VP Revenue
Director of Sales Operations
Head of Revenue Operations
Exclude unless separately justified:
Sales Assistant
Sales Intern
Retail Sales Associate
Unrelated regional roles
Customer Support leadership
The exclusion list is as important as the included titles. Broad keyword matching can return Sales Assistant when our buying-role hypothesis requires a sales leader.
Use a solution-to-role matrix
| Solution category | Economic buyer | Champion | User | Evaluator | |---|---|---|---|---| | Sales intelligence | CRO, VP Sales | RevOps/Sales Ops | SDR/AE leader | RevOps, IT, Security | | Marketing technology | CMO, VP Marketing | Demand Gen/Growth | Campaign team | Marketing Ops, IT | | HR technology | CHRO, VP People | People Ops | Recruiter/HRBP | IT, Security, Legal | | Data/IT platform | CIO, CTO | IT/Data Director | Analyst/Engineer | Security, Procurement |
This matrix is an editorial aid, not a claim that every company uses these titles.
Adjust the hypothesis using company size
Employee Count is available in the confirmed Getlead export and can support post-export qualification. It is not presented as an active search filter in the current B2B Search interface.
Operating hypotheses:
- 1–20 employees: founder or function leader may combine several roles.
- 21–200 employees: function leader and operations owner may be separate.
- 201+ employees: economic buyer, user and evaluator may be more distributed.
These bands help us ask better questions. They do not determine org structure with certainty.
For a 12-person company, selecting the founder and Head of Sales may create enough coverage. For a 600-person company, adding RevOps and a relevant evaluator may be more appropriate.
Search in Getlead
The confirmed B2B Search criteria include:
- Job title;
- Industry;
- Country;
- Seniority;
- Function/department;
- Verified Emails Only;
- requested result count.
For the approved example:
Industry: Software
Country: United States
Function: Sales
Seniority: C-Level, VP, Head, Director
Title set: CRO, VP Sales, Head of Sales, RevOps Director, Sales Ops Director
Verified Emails Only: On
We start with a calibration sample. We inspect whether titles map to the planned roles before expanding the result count.
Review results at the account level
The confirmed export columns are:
First Name
Last Name
Job Title
Email
Company
Website
LinkedIn URL
Industry
Employee Count
Verification Status
For each row, we confirm:
- Company and Website refer to the target account.
- Industry is compatible with the ICP.
- Employee Count does not contradict the account hypothesis.
- Job Title maps to one required buying role.
- LinkedIn URL supports identity and current-role review.
- Verification Status meets policy.
In Getlead, Verified Emails Only keeps contacts that passed the real-time SMTP check at verification time and excludes catch-all and risky results. It reduces hard-bounce risk; future delivery remains subject to later mailbox and server conditions.
Calculate buying-role coverage
Buying-role coverage =
Required roles found / Required roles defined × 100
Example:
Required: Economic buyer, champion, user
Found: Economic buyer, champion
Coverage = 2 / 3 × 100 = 66.7%
The percentage does not predict purchase. It tells us whether our planned account research is complete.
Coverage states
| Coverage | Operational interpretation | |---|---| | 100% | All roles in our hypothesis are represented | | Partial | Continue title search or accept documented gap | | 0% | Revisit role/title assumptions or account fit |
We can choose to proceed with partial coverage when the missing role is not required for the next action. The reason is documented.
Limit contacts per account
More contacts do not automatically create better coverage. Five people with nearly identical titles may represent one role.
Working policy:
- select distinct roles before title duplicates;
- keep 2–4 relevant people for a multi-role account when justified;
- use fewer for small/simple accounts;
- add more only when buying complexity requires it.
The 2–4 range is an operating guideline, not a product limit or industry benchmark.
We avoid overlapping outreach. If several people are selected, the campaign plan determines sequencing, ownership and suppression so the account does not receive uncoordinated messages.
Choose the first contact
We choose based on the goal:
| Goal | Likely first role | |---|---| | Validate the operational pain | Champion/user leader | | Discuss commercial priority | Economic buyer | | Resolve technical feasibility | Evaluator | | Navigate the organization | Champion with cross-functional visibility |
Starting with the champion can create better context than starting at the top. In a small founder-led account, the economic buyer may still be correct.
Create the account contact plan
Add workflow fields after export:
Account ID
Buying Role
Role Priority
Coverage Status
Account Owner
Contact Sequence
Evidence Date
Next Action
These are not native Getlead export fields.
Example:
| Account | Contact | Buying role | Priority | Next action | |---|---|---|---:|---| | Northstar Cloud | VP Sales | Economic buyer | 2 | Hold until champion context | | Northstar Cloud | RevOps Director | Champion | 1 | Research workflow evidence | | Northstar Cloud | SDR Manager | User | 3 | Add if user proof needed |
All companies and people in examples are synthetic.
Handle missing or ambiguous roles
No exact title
Search alternative title families and function/seniority combinations. Review manually; do not assume a broad match is correct.
Several similar executives
Use current responsibility, geography and scope. A regional VP may not own a company-wide tool decision.
Founder-led company
Combine roles only when evidence supports it. Record Economic buyer + champion, rather than duplicating the person.
No verified contact
Do not relax verification language. Try another relevant role, place the account in research or use an approved alternative workflow.
Uncertain company match
Use Website and LinkedIn URL. If identity remains ambiguous, hold the row.
Connect role coverage to prioritization
JTBD-08's prospect prioritization model scores fit, timing, reachability and evidence. Buying-role coverage is a separate account-level quality measure.
An excellent account with only an irrelevant contact should not enter Tier 1 outreach. A fully mapped account with weak ICP fit should not receive priority merely because research is complete.
We combine:
Account fit
Buying-role coverage
Contact reachability
Evidence confidence
Capacity and ownership
without hiding them in one unexplained label.
Move the search state into onboarding
The CTA carries supported criteria:
/register?industry=software&role=sales&seniority=cxo,vp,head,director&country=united-states&verified=true&utm_source=seo&utm_medium=guide&utm_campaign=jtbd02_decision_makers
The Lead SEO Engineer maps public parameter names to the current onboarding contract.
Event:
{
"event": "seo_get_started_click",
"content_id": "jtbd-02",
"content_cluster": "prospecting",
"cta_name": "find_my_decision_makers",
"cta_position": "inline",
"destination": "register",
"state_transfer": true,
"tool_completed": false
}
QA the decision-maker list
Review:
- every included title family;
- every alternative-title rule;
- all records near the seniority boundary;
- all company/domain mismatches;
- all duplicate roles at one account;
- all accounts with partial coverage;
- all uncertain verification states;
- all active-campaign overlaps.
Reviewer questions:
- Which customer job justified this role?
- Does the current title support that role?
- Are we selecting distinct responsibilities or title duplicates?
- Is the account identity confirmed?
- Is the verification language accurate?
- Who owns the first contact and later account coordination?
If we cannot answer, the row stays in review.
Run title-search iterations without losing the hypothesis
We do not solve low coverage by opening the title filter indefinitely. We change one layer at a time:
Iteration 1: primary titles
Use the strongest direct titles for the required role. Review precision: what share of sampled records genuinely performs the expected responsibility?
Iteration 2: accepted title variants
Add documented variants such as Director of Revenue Operations for RevOps Director. Keep the original role mapping visible.
Iteration 3: function + seniority discovery
If title conventions vary, use supported function and seniority criteria to discover additional titles. Sample them manually and decide which belong in the accepted or excluded set.
Iteration 4: role substitution
If the planned champion does not exist at smaller accounts, decide whether the founder or sales leader genuinely combines that responsibility. This is a change to the buying-role hypothesis, not merely a search expansion.
For each iteration, record:
Search version
Criteria changed
Reason
Sample size
Relevant results
New title variants accepted
New exclusions
Coverage change
Reviewer
This prevents a broad search from silently redefining the ICP.
A full synthetic account example
Assume Northstar Cloud is a 140-person US B2B SaaS company. Our solution changes how the sales team builds and verifies outbound lists.
Required roles
Economic buyer: Sales leader
Champion: Revenue or Sales Operations
User: SDR team leader
Evaluator: Not required for the first discovery step
Search results
VP Sales → maps to Economic buyer
Revenue Operations Director → maps to Champion
SDR Manager → maps to User
Regional Sales Director → review; scope may not cover the process
Account Executive → exclude from this buying-role plan
We find three required roles, so research coverage is 100%. That does not mean we contact all three immediately. We choose the RevOps Director as the likely first contact because the workflow problem belongs to operations. The VP Sales remains the economic-buyer path. The SDR Manager provides user evidence if the conversation progresses.
We then verify:
- all three profiles still list Northstar Cloud;
- Website and Company match;
- titles are current;
- verification statuses meet the approved policy;
- none is suppressed or in an overlapping campaign.
Our contact plan might be:
1. RevOps Director — research and first outreach
2. VP Sales — use only through coordinated account sequence
3. SDR Manager — hold for user validation
If the RevOps Director's email is unavailable under the approved verified condition, we do not pretend coverage is complete for outreach. Research coverage remains complete, but reachable coverage is 2/3. Keeping these metrics separate preserves the truth.
Distinguish research coverage from reachable coverage
We track:
Research coverage =
Required roles with a confirmed person / Required roles × 100
Reachable coverage =
Required roles with an eligible verified contact / Required roles × 100
Active outreach coverage =
Required roles assigned to a coordinated campaign step / Required roles × 100
One metric cannot replace the others. A profile can be identified but not reachable. A contact can be reachable but deliberately held from the first sequence. This distinction helps RevOps diagnose whether the gap belongs to research, data or campaign coordination.
Build a reusable title library
After each reviewed search, we update a controlled library:
| Field | Purpose | |---|---| | Solution category | Which customer job the titles relate to | | Buying role | Economic buyer, champion, user or evaluator | | Canonical title | Primary label | | Accepted variants | Reviewed alternatives | | Excluded lookalikes | Similar but irrelevant titles | | Company-size note | Where the title usually needs review | | Last reviewed | Recency | | Reviewer | Accountability |
We do not assume a title library remains correct forever. Companies create new titles, combine functions and change scope. The library accelerates calibration; current evidence still decides the row.
This library also improves internal linking and content coherence. JTBD-01 can link to the title-selection method, JTBD-03 can use the same role contract for a company CSV, and JTBD-08 can score contact fit without inventing another title definition.
Coordinate multiple contacts ethically and operationally
Account-based outreach should not become simultaneous pressure on several employees. We define:
- one account owner;
- one active campaign hypothesis;
- a first-contact role;
- a waiting period or response rule;
- cross-contact suppression;
- a reason for adding another role.
We stop later steps when someone replies or opts out as required by policy. We do not use a colleague's response to manufacture a relationship with another person. Notes remain factual, professional and limited to the business context.
If an evaluator is needed only after discovery, we do not include that person in initial outbound merely to raise account coverage. Coverage is a research measure; outreach follows the appropriate stage.
Report the workflow to leadership
A useful weekly view shows:
- target accounts researched;
- median required roles per account;
- research coverage;
- reachable coverage;
- accounts with only title duplicates;
- accounts held because of identity or verification ambiguity;
- first-contact roles selected;
- active multi-contact accounts;
- qualified outcomes by role.
We avoid celebrating raw contacts found. The better question is whether the team has the smallest sufficient, verified and coordinated account contact plan.
Common mistakes
Selecting only CEOs
The CEO may not own the workflow or evaluation.
Treating a title as universal
Companies distribute responsibilities differently.
Ignoring buying roles
A list of five sales executives can still have zero user or evaluator coverage.
Using company size as certainty
Employee Count informs a hypothesis; it does not reveal the org chart.
Counting duplicates as coverage
Several people in one role do not fill another required role.
Treating Verified as permanent delivery
It is a time-bound SMTP result under the approved policy.
Contacting several people without coordination
Account ownership and cross-campaign suppression must prevent contradictory outreach.
Decision-maker workflow checklist
- [ ] Customer job is explicit.
- [ ] Required buying roles are selected.
- [ ] Primary, alternative and excluded titles exist.
- [ ] Company-size assumptions are labeled hypotheses.
- [ ] Only supported Getlead search criteria are used.
- [ ] Calibration sample is reviewed.
- [ ] Native export columns are preserved.
- [ ] Website and LinkedIn support identity review.
- [ ] Verification status meets policy.
- [ ] Coverage is calculated by distinct role.
- [ ] Contact count per account is justified.
- [ ] First-contact logic is documented.
- [ ] Account owner and suppression are assigned.
- [ ] CTA carries supported search state.
Continue through the Prospecting hub
If the ICP is unclear, use the Ideal Customer Profile Builder. If accounts are not ready, start with JTBD-01 prospect list creation. If a company CSV exists, continue with JTBD-03 company list to contacts. Clean the result through JTBD-04 and allocate limited capacity with JTBD-08 prioritization.
Frequently asked questions
Is the CEO always the decision-maker?
No. The correct role depends on the customer job, operating structure, budget and evaluation needs.
How many contacts should we find per company?
Use the smallest set that covers the required roles. Our working range is often 2–4 for a multi-role account, not a universal benchmark.
What if one person has several buying roles?
Record combined roles for that person when evidence supports it. Do not add duplicate rows.
What is a buying-role coverage score?
It is required roles found divided by required roles defined. It measures research completeness, not purchase probability.
Can Employee Count identify the decision-maker?
No. It can guide a post-export hypothesis about operating structure, but current evidence is still required.
What if no verified decision-maker is available?
Search another relevant role or hold the account. Do not call catch-all/risky results “verified” or promise future delivery.
Should several contacts at one account enter the same campaign?
Only through a coordinated account plan with ownership and suppression. Avoid overlapping, contradictory outreach.