Who to contact first: mapping the buying committee

The first person to contact in a B2B account is usually whoever owns the change your buying signal points to, such as the manager hiring a new team or a new leader with a fresh mandate. That person is one member of the buying committee: the group of people inside a company who influence whether a purchase happens. In B2B sales, one person rarely decides alone. Someone feels the problem, someone controls the budget, someone checks the technical details, and someone may push back. Mapping the committee means figuring out who those people are before you start reaching out.

For a BDR, the most practical question is not “who is everyone?” It is “who should I contact first, and why?” This guide gives you a simple way to answer that.

The five roles

Titles vary from company to company, so think in roles rather than job titles. One person can hold more than one role.

1. Economic buyer. The person who controls the budget and gives final approval. Often a VP or department head.
2. Champion. Someone inside the company who wants the change and will argue for it. A champion has influence and a personal reason to see the problem solved.
3. User. The people who will use the product day to day. They know the current pain best and will notice quickly if a solution does not work.
4. Technical evaluator. The person who checks whether the product fits the company’s systems, security and processes. Often in operations, IT or a “RevOps” (revenue operations) role.
5. Blocker. Someone who may resist the change. They might own the current tool, worry about workload, or have a competing priority. Blockers are not enemies. Their concerns are often real and worth hearing early.

You will not find all five at every account, especially at smaller companies. That is fine. The map is a guide, not a checklist.

Choose the first contact from the signal

The best first contact is usually the person who owns the change the signal points to. A signal is evidence that something shifted at the account. Ask: whose job does this change most affect, and who is accountable for making it work?

Some common patterns:

• A new sales leader joins. Start with that leader. New leaders often arrive with a mandate and want to make early progress. See leadership change as a buying signal.
• A cluster of BDR job postings. Start with the person hiring them, often the sales development manager. They will own ramping those new reps.
• A new region or product launch. Start with the leader responsible for that launch, not a general executive.
• A tool change mentioned in job posts. Start with the operations owner who will manage the transition.

This keeps your first message grounded. You are not contacting someone because their title matches a list. You are contacting them because a specific change lands on their desk. The hiring signals guide shows how to read job posts for these clues.

Single-threading vs multi-threading

Single-threading means all your contact with an account runs through one person. Multi-threading means you build relationships with several people in the committee.

Single-threading is risky. If your one contact goes quiet, changes jobs or lacks influence, the opportunity stalls. Multi-threading spreads that risk and gives you a fuller picture of what the company actually needs.

But multi-threading does not mean contacting everyone at once. Start with one person, learn what you can, and add others with a reason.

Build a simple map

Before you send anything, sketch a short map in your notes or CRM. Five rows is usually enough.

Role	Name and title	Why they care	When to contact
Economic buyer
Champion
User
Technical evaluator

Fill in what you know and leave blanks where you are guessing. Blanks are useful. They tell you what to learn in your first conversations.

A worked example

Imagine a fictional 600-person cybersecurity software company. You notice two signals: a new VP of Sales started five weeks ago, and the company has posted six BDR roles across two regions.

Your map might look like this:

• Economic buyer: the new VP of Sales. Owns the plan and the budget.
• Champion (likely): the sales development manager hiring the six BDRs. Will feel the ramp pressure directly.
• Users: the current BDR team.
• Technical evaluator: the RevOps manager, who owns the CRM and tooling.
• Blocker (possible): whoever chose the tool currently in place.

Who first? The hiring is the most concrete change, and the manager running it will live with the results. Start there.

Hi Sam, I saw the team is hiring six BDRs across two regions. When a team grows that fast, new reps often spend their first weeks unsure which accounts to work first. How are you planning to get the new hires productive?

If Sam replies, ask who else is involved in planning the ramp. If not, a few days later contact the VP with a different angle tied to their first quarter in the role, not a copy of Sam’s message.

Avoid spamming five people the same day

It is tempting to email every name on the map on the same morning. Resist it.

• It looks automated. People at the same company talk. If five colleagues get near-identical messages, they will notice.
• It removes your learning. The first conversation should shape the next one. You cannot use what you learn if you have already sent everything.
• It can feel like pressure. Respectful outreach gives people room to respond.

A better rhythm:

1. Contact the first person, the one who owns the change.
2. Wait a few business days, or until you get a response.
3. Add the next person with a message written for their role and concerns.
4. If you mention a colleague, be honest and specific: “I also reached out to Sam about the BDR ramp.”
5. Keep a note of who you contacted, when, and with what angle.

This takes longer than a blast, but each message is more relevant.

The rule to remember

Let the signal tell you who owns the change, and start there. Map the rest of the committee as you learn, and add each person one at a time with a reason that fits their role.

When you are ready to reach out, see signal-based outbound examples or how Syntri approaches signal-based outbound.