Who is the decision-maker when several people take the decision?
A decision-maker is a role in a specific purchase, not a universal job title. For an accounting-system rollout, finance may initiate the conversation, IT may define the requirements, and the owner or general director may approve the budget. Writing only to one of them with a vague partnership proposal can stall the conversation even when the address is correct.
| What you sell | Who defines the need | Who approves the decision |
|---|---|---|
| Industrial equipment | Technical or production leader | General director or owner |
| A sales-related service | Commercial director or head of sales | Commercial director, sometimes the owner |
| Process automation | Functional leader and IT | Business leader or budget owner |
Your research brief therefore needs a role map, not an instruction to “find the director”: initiator, user, expert and budget owner. It should follow your ideal customer profile. When accepting a list, check that every company includes a reason for selecting that role, rather than a senior title copied from a directory.
A record that says “general director” but has no function, verification date or alternative contact is not ready for outreach. It is a hypothesis.
How do you separate a current leader from an outdated record?
Company names and job titles can outlive the real structure for years. A department may have changed leadership, a function may have moved to another division, and a former employee may still appear in a public profile. The cost is not only a missed email: addressing someone who has left signals that you have not understood their business.
- Match the legal and trading company name, website and business activity.
- Match the job title to the relevant task: procurement, sales, production, IT or finance.
- Look for evidence that the person is currently connected to the company, rather than having worked there before.
- Record the verification date and a backup role in case the person has moved on.
A good record makes the route clear without another round of research: company, business line, role, name, reason for selection, channel and verification date. A poor one says only “Ivan, director, email found.” In the first case, your sales team has context; in the second, it must investigate again or write blind.
- A specific function is stated, not only a management status.
- There is evidence of the person’s current connection to the company.
- The company matches your target industry, size and geography.
- The primary contact route and an acceptable backup route are recorded.
- The verification date makes the record’s freshness clear.
Why is finding a director’s email not enough for the first touch?
A corporate address answers “where can the email be delivered?”, not “who will read it?”. A shared inbox may route enquiries, a personal inbox may belong to someone who no longer owns the task, and a leader’s valid address may still be the wrong place to introduce the topic. Contact verification is separate from role relevance.
For example, a warehouse-equipment supplier may write to a head of sales about warehouse optimisation. The contact may be active, but the recipient may not own the subject. It is usually more precise to start with the operations or warehouse leader, while keeping sales as a secondary participant if fulfilment affects orders.
What a contact-research report should show
Contact quality affects deliverability and sender reputation, but it does not replace the work of writing a relevant message. After research, use list verification and a scenario that connects the role to the business topic. See How to Write a B2B Cold Email for the first-message framework.
What errors break decision-maker research before outreach begins?
The first error is collecting every manager without a priority order. In a company of one hundred people, that creates five contacts instead of one route and can produce overlapping, uncoordinated touches. The second is treating a job title as proof of authority. The third is mixing up branches, management companies and legal entities, so the message reaches an organisation with a similar name but without the relevant budget.
Another common error is treating an address as consent to have a conversation. Even precise decision-maker research does not justify promising a meeting or counting a record as a lead before a substantive reply. We define an explicit yes as a request for details, a proposal or a meeting; see what counts as a result.
When accepting a list, ask to see several records end to end: why the company was selected, why the role was selected, what confirms the contact, and what happens if the record is wrong. If a provider shows only an address export, you cannot assess the central part of the work: the selection logic.
When will decision-maker research not deliver the result you need?
This method is not a fit if your offer is unclear and you cannot explain which business problem it solves. You may find a director’s email accurately, but still have no relevant reason to write. It is also not the right starting point for markets where the buyer is a broad consumer audience rather than a defined B2B buying group.
It also cannot solve weak reply handling. If “please send more details” receives a catalogue with no qualifying question, the value of the research disappears in the first exchange. A separate process for reply handling and lead qualification is needed to pass context into sales.
We build a role map, verify the company-task-contact connection, and hand over a list built for work rather than an archive of addresses. This work can be part of B2B lead list building or a full Russia and CIS outreach programme.