How Do You Map a Buying Committee for One Target Account?

How do you map the buying committee for one target account?

Start with the problem your product solves, then list every role that feels that problem, signs off on the budget, or can block the deal. Find a real person for each role, note what each one cares about, and record it in your CRM. One account, one map, updated as you learn.

This tutorial is for one specific situation: a founder or a small sales team going after a single high-value account. Maybe it is your dream logo. Maybe it is a deal that has stalled because you only know one person there. Either way, you need to see the whole group of people who will decide.

Account mapping sounds like an enterprise sales ritual. It is not. It is a simple habit that keeps you from betting a deal on one contact who may not have the power to buy.

What is a buying committee in B2B sales?

A buying committee is the group of people inside a company who influence, approve, or block a purchase. It usually includes the person with the problem, their manager, someone who controls budget, and people from functions like IT, security, legal, or procurement who must sign off before a contract goes through.

Not everyone on the committee has equal weight. A champion pushes for the purchase. An economic buyer controls the money. Technical evaluators check whether the product works with their systems. Blockers can stop a deal even if they never say yes to anything.

Your job in mapping is not to label everyone perfectly. It is to make sure you know who these people are before they surprise you late in the deal.

Step one: what problem are you mapping around?

Write one sentence describing the problem your product solves for this account. The committee forms around that problem, so the sentence tells you which departments to look at. A lead routing tool touches sales and RevOps. A security tool touches IT and compliance. Start there.

This step keeps the map focused. Without it, people tend to list every senior name at the company. That produces a long list of people who will never be involved.

If you need help sharpening the problem statement, the work is similar to writing a clear ICP. I walked through that in how to write an ICP one-pager for a new SDR. The same clarity that defines who you sell to defines who inside an account cares.

Step two: which roles belong on the map?

List roles before names. For most B2B deals, include the user with the problem, their direct manager, the budget owner, a technical evaluator, and any approval function such as security, legal, or procurement. Add an executive sponsor if the deal size needs one. Then mark which roles you already have a contact for.

I do this in a simple table in a Google Sheet or directly as notes in the CRM. One row per role. Columns for name, title, what they care about, their likely stance, and the last time you spoke.

The gaps jump out right away. If you have three contacts in the user's team and nobody in finance, you know where the deal is exposed. That gap is more useful than any of the names you already have.

Step three: how do you find the real people for each role?

Use the company's website, LinkedIn, and your enrichment tools to find people in each role, then confirm with your existing contact. Ask your champion directly who else will be involved. A direct question is often faster and more accurate than any database.

Tools like LinkedIn Sales Navigator, Apollo, and Clay can help you find names and titles at the account. Titles vary widely between companies, so read the role descriptions rather than trusting the title alone. A "Head of Operations" at one company might own the budget you need. At another, they might never see your category.

Then ask. Something like, "Who else usually weighs in on a decision like this?" Most champions are happy to answer, because they also want the deal to go smoothly. Their answer often reveals a blocker you would never have found on your own.

Step four: what does each person care about?

For each person, write one line about what they need to see to support the deal. The user wants the problem solved. The manager wants their team's results to improve. Finance wants a clear return. IT wants it to fit their systems safely. Your message to each person should match that line.

This is where mapping turns into a plan. If you know the security lead cares about data handling, you can send them your security documentation before they ask. If finance cares about payback, you can help your champion build that case.

Keep it short. One honest line per person is enough. Long profiles tend to get written once and never read again.

Step five: how do you record the map in your CRM?

Add every person as a contact associated with the account, record their role on the committee in a dedicated property, and keep the "what they care about" note on the contact record. That way anyone on the team can open the company record and see the whole committee at a glance.

In HubSpot or Salesforce, a single custom property for "buying role" with a short list of values works well. Champion, economic buyer, evaluator, approver, blocker, unknown. Keep the list short so people actually use it. Check your CRM's documentation for how to create custom properties on your plan.

A map that lives only in a rep's head is lost when that rep leaves or goes on holiday. A map in the CRM survives. It also lets you spot accounts that are single-threaded. I covered that risk in how to flag single-threaded deals in HubSpot.

Step six: how often should you update the map?

Update it after every meaningful conversation and review it before each stage change in the deal. People change jobs, new stakeholders appear, and priorities shift. A map that was right at the first call may be wrong by the proposal. A quick review before each stage keeps it honest.

I find a simple rule helps. Before moving a deal to the next stage, ask whether each role on the map has a named person and a known stance. If the economic buyer is still "unknown" at the proposal stage, the deal is not as far along as the pipeline says.

Job changes deserve special attention. If your champion leaves, your map needs a new champion fast, and the person who left may become a champion at their new company.

What mistakes make account maps useless?

The common mistakes are listing names without roles, mapping too many people, never asking the champion who else is involved, and letting the map go stale. Each one creates a map that looks complete but does not help you sell. A short, accurate map beats a long, outdated one.

Another mistake is treating the map as a sales task only. Marketing can help by sending role-specific content to each person, such as a security overview for IT or a payback example for finance. That only works if marketing can see the map.

Finally, do not confuse activity with coverage. Ten emails to the same champion are not multi-threading. Coverage means real conversations with different roles.

What should you do next?

Pick your single most important open deal. Write the problem sentence, list the roles, and mark who you know and who you do not. Then ask your champion who else will be involved, add the answers to your CRM with a buying role property, and review it before the next stage.

Do that for one account this week. Once it feels natural, make it standard for every deal above a certain size.

If you want help setting up account mapping in your CRM or building the outbound and enrichment systems that feed it, reach out. Designing these GTM systems is the core of my work. Let's chat.