Decision Maker Mapper

Decision Maker Mapper is a Claude skill that turns one company domain into a buying committee map. It sorts the people at the account into four roles and returns a work email for one person in each.

What it does

You give Claude a domain, for example acme.com. The skill sizes four groups first, which is free: C-Team, VP, Director and Manager. Then it lists two people per group and reveals the email of the first person in each.

The roles are a rule of thumb from job level: executive sponsor, budget owner, evaluator and day-to-day user. The skill says so in its reply. It maps levels, not org charts, and it never claims who signs the contract.

It runs on the LeadOcean MCP server. You sign in once with OAuth. No API key is pasted.

How it works

The skill is a SKILL.md file. It tells Claude which tools to call and in what order.

1. count_leads runs four times, once per role group, for the domain. Free. Totals count mailable people only.
2. Claude tells you the budget: 12 records at most.
3. search_leads runs once per group that has people, with limit: 2. 1 record per person returned, 8 at most.
4. Claude picks the first person in each group. If you passed a job function, it prefers the closest match. No tool call.
5. get_lead with reveal_email: true returns the work email and its status for each pick. 1 record each, 4 at most.

If a filter value is rejected, Claude calls list_enum_values (free) to find the exact string.

How to use it

1. Download the zip: decision-maker-mapper.zip.
2. Unzip it and add the decision-maker-mapper folder as a skill in Claude.
3. Connect LeadOcean at https://api.leadocean.io/mcp and sign in.
4. Ask: "Map the buying committee at acme.com". Add a function if the product has one owner: "Map the buying committee at acme.com, focus on Sales & Business Development".

You need a LeadOcean account. The free plan gives you 1,000 records, one-off, no card.

Sample output

The free sizing step works on any domain. We ran count_leads on hubspot.com once per job level on 1 October 2026. The job_level values came from list_enum_values.

Records spent: 0. Counts cover mailable people (verified, catch_all_valid, catch_all), the count_leads default.

The rest of the run spends records, so no real committee is pasted here. This is the shape of the reply, with placeholder values.

Output format (placeholder values)

Buying committee: Acme (acme.com)
As of 1 October 2026

Roles are inferred from job level. Confirm them before you rely on them.

| Role | Mailable people on file | Name | Title | Work email | Email status | LinkedIn |
| Executive sponsor | 12 | Jane Doe | CEO | jane@acme.com | verified | https://www.linkedin.com/in/janedoe |
| Budget owner | 9 | ... |
| Evaluator | 30 | ... |
| Day-to-day user | 140 | ... |

Also in the group
Executive sponsor: John Roe, CFO
...

Records spent: 12

The skill replies in this shape and nothing else. Any field it cannot find reads "not on file".

Records per run

The free plan's 1,000 records cover about 83 full runs. On Pro ($499 a month) there is no per-record price. Fair use applies, as described on the pricing page.

Related skills

• Account Researcher: company profile plus the committee as one brief.
• Contact Finder: the right people for one named role.
• All Claude skills

Background reading: the decision maker finder tools compared, the find decision makers lead source and the job signal decision maker outreach recipe.

FAQ