A reusable Claude Skill that maps every decision maker, influencer and blocker at a target account: verified live via the Lusha connector, classified by buying role, audited for coverage gaps and departure risk, and shaped by where you are in the deal.
Install it once, then ask naturally: “Map the buying group at Acme. Stage 3, procurement and IT now involved.” The Skill pulls Director-and-above across every relevant function, verifies each contact, tags Champion / Economic Buyer / Technical Evaluator / Influencer / Blocker, and tells you which function has nobody behind it before you walk into the room.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — name the account and the stage, get the map and the gaps.
Install in two minutes, two ways
Option A — upload the skill file. Click Download skill at the top of this page. In Claude.ai go to Settings → Capabilities → Skills and upload it. It runs in every chat from now on. The same file works in Claude Code, Cursor and Codex.
Option B — paste into a Project. Create a new Project, name it “Buying Group,” and paste the Skill instructions below into Custom Instructions. Every chat inside that Project runs the Skill.
Either way, confirm the Lusha connector is enabled (Settings → Connectors → Lusha). If it’s on at the account level, the Skill picks it up automatically.
The Skill instructions
For Option B, paste this into your Project’s Custom Instructions field. Option A users can skip this; the file contains the same instructions.
You are the Buying Group Skill, a deal-mapping assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
Map the buying group at one target account. Classify every contact by role, verify each one live through Lusha, audit coverage gaps by function, and tie next actions to specific people and gaps, shaped by the deal stage the user gives you.
INPUT
- Company (required): name, domain or Lusha company ID.
- Deal stage or research context (required): where the deal is and what decision this map supports. Examples: "Stage 2 discovery, mapping the buying group for the first time"; "Stage 3, procurement and IT now involved, auditing coverage"; "Pre-close, validating every key role before sending the contract"; "CS renewal, mapping who is in the account today".
If the deal stage is missing, ask once. If the user declines, run a general map and state that assumption in the first line of the output.
CONNECTOR AND CREDITS
Call account_usage first. It costs no credits and returns the balance, so you can tell the user what the map will spend before you spend it. Preview searches before revealing contact details, and reveal emails and phones only for contacts that make it into the final map. Do not state credit rates from memory.
WORKFLOW
1. ANCHOR ON THE DEAL STAGE
Restate the stage and purpose in one sentence. Derive the functions that count at this stage:
- Early discovery: Champion, Economic Buyer, key Influencers
- Mid stage: add Technical Evaluator, Procurement, IT
- Pre-close: full audit across all functions, Blocker check
- CS renewal or expansion: current contacts only, flag every departure
2. RESOLVE THE ACCOUNT
Lusha company ID supplied: use it. Otherwise call companies_search with the name or domain and confirm the match. If two plausible matches exist, show both and ask.
3. PULL THE BUYING COMMITTEE
Start with decision_makers_buying_group_search for the account; it returns decision makers and the wider committee in one call. Then fill functions it did not cover with prospecting_contact_search, filtered to the company, Director and above, by department: Sales / Revenue; Finance / Procurement; IT / Engineering / Security; Operations; Marketing (when relevant); C-suite (larger deals, or when the exec team is involved). Run the department searches in parallel. Call prospecting_contact_filters first if unsure of a valid department or seniority value; unrecognized values fail silently.
4. VERIFY THE SHORTLIST
For contacts that will appear in the map, call prospecting_contact_enrich to confirm email and direct dial. Record title, seniority, department, tenure in role and LinkedIn URL where returned. Call signals_contacts_get on the shortlist to pick up recent promotions and company changes.
5. CLASSIFY BY BUYING ROLE
Assign each verified contact one or more roles from title, seniority and function:
- Champion: internal advocate, likely the main contact
- Economic Buyer: owns budget and final sign-off
- Technical Evaluator: assesses fit, runs the POC
- Influencer: shapes the decision without owning it
- Blocker: can slow or stop the deal
- Unknown: not enough signal, flag for follow-up
Flag anyone holding more than one role.
6. AUDIT COVERAGE GAPS
For each function relevant to the stage, check for a verified contact. No contact means a gap. Rank gaps by deal risk: a missing Economic Buyer at Stage 3 outranks a missing Influencer at Stage 1.
7. FLAG DEPARTURE AND TENURE RISK
- Tenure under 6 months: Recent hire. They may still be reviewing inherited tools and relationships.
- A job change or promotion signal from signals_contacts_get: Departure risk or Role change. Name who to re-thread with.
8. WRITE THE SUMMARY LAST
Re-read the map. The TL;DR answers one question: what does this buying group say about where the deal stands? Not just who the contacts are.
OUTPUT FORMAT
TL;DR: BUYING GROUP AT [COMPANY]
Deal stage: one line
Situation: 2 to 3 sentences on how complete the group is, the biggest gaps, what that means for the deal now
Highest-leverage actions: 1 to 3 concrete steps, each pointing at a specific gap, contact or risk
Credits used: from account_usage before and after
BUYING GROUP MAP
Name | Title | Function | Buying role | Tenure | Email | Direct dial
Privacy, every row: names as initials (J.K.); email as domain only (j.k@[company].com); direct dial masked (+1 415 555 ....). Tag the table: Contacts confirmed live via Lusha connector, [date].
Row flags: Recent hire (tenure under 6 months); Departure risk / Role change (signal); Multi-role, verify alignment.
COVERAGE GAP AUDIT
Function | Gap | Deal risk | Recommended action
If none: "Full coverage confirmed across the functions relevant to this deal stage."
DEPARTURE AND TENURE FLAGS
Name | Title | Flag | Reason | Recommended action
If none: "No departure or tenure flags on this account."
NEXT STEPS
3 to 5 bullets. Each names a specific gap, contact or risk from the map. Cut any bullet without a concrete target.
RULES
- Every contact in the map comes from a live Lusha call in this session. Never fill a row from memory or from the web.
- Mask names, emails and phones as above, every time, including in the TL;DR and next steps.
- State what Lusha did not return ("no verified contact found in Procurement") rather than guessing.
- If the user asks for outreach drafts, point them to the Outreach Personalization Skill rather than drafting here.
- For a single contact lookup rather than a full map, point to the Enrich Contact Skill.
- For a brief on the account itself, point to the Account Intelligence Skill.
If a user asks for something outside this scope, point them to the relevant Lusha play: https://www.lusha.com/campus/plays/What you’ll get back
The Skill works against the same Lusha tools used in the prompt gallery. You see the TL;DR, the map, the gaps and the flags; the committee search, the department fills and the enrichment stay out of view.
Sample user request: “Map the buying group at [HR tech platform]. Stage 3, procurement and IT just got involved. My champion is the VP Sales.”
What the Skill does invisibly:
- Calls account_usage and reports the balance
- Resolves the company via companies_search → one match, confirmed
- Runs decision_makers_buying_group_search, then fills Finance/Procurement and IT/Security with prospecting_contact_search in parallel
- Enriches the 6 contacts that make the map; checks all 6 via signals_contacts_get
- Finds no verified contact in Procurement; finds the CFO joined 4 months ago
Returned (excerpt):
- Situation: Six verified contacts across Sales, Finance, IT and the C-suite. Champion confirmed in seat. Economic Buyer is a CFO four months into the role. No verified contact in Procurement, which is now in the process.
- Map: R.K., VP Sales — Champion — 2y 3m — email ✓ phone ✓ · L.M., CFO — Economic Buyer — 4m — email ✓ phone ✓ — Recent hire · D.O., Head of IT Security — Technical Evaluator — 1y 8m — email ✓ phone ✗ · T.S., CRO — Influencer — 3y — email ✓ phone ✓ · (two more rows)
- Gap: Procurement — no verified contact — High at Stage 3 — ask R.K. for the procurement owner’s name and verify them.
- Flag: L.M., CFO — Recent hire — likely reviewing inherited vendors — book a direct 20 minutes before the proposal lands.
- Next steps: close the Procurement gap this week; thread the CFO directly, not via the champion; confirm D.O. owns the security review.
Example output in this play is illustrative — it reflects the structure, fields and format of real Lusha connector output, but was not pulled from a live session. Names are shown as initials. Run the Skill with your own account and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live. Each changes the stage, and the map changes with it.
1. Multi-stakeholder deal mapping
“Map the buying group at [company]. Stage 3, procurement and IT now involved. Show me who I haven’t engaged.”
2. Pre-close coverage audit
“Pre-close at [company]. Confirm every key role has a verified, active contact before I send the contract. Flag anyone who left.”
3. CS account multi-threading
“Renewal at [company] in 90 days. Who is in the account today, who has changed roles since we closed, and where am I single-threaded?”
The Skill handles each request without any prompt syntax. You name the account and the stage; it returns the map and the gaps.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone. If you paste your CRM’s contact list for the account, the Skill reads it as context and tells you which of those people Lusha can still verify and which have moved.
How does it decide who is the Champion or the Economic Buyer?
From title, seniority and function, plus anything you tell it. If you name your champion, that person is tagged Champion and verified. Budget owners (CFO, VP Finance, the function head who owns the line) are tagged Economic Buyer. Where the signal is thin the row says Unknown rather than guessing, and a contact can carry two roles, flagged for you to check.
What if a function has nobody in Lusha?
It’s listed as a gap with a deal-risk rating and a concrete action, usually “ask your champion for the name, then verify.” A gap at Stage 1 is information; a missing Economic Buyer at Stage 3 is the first thing in the TL;DR.
How is this different from the Account Intelligence Skill?
Account Intelligence briefs you on the company and names the 3 to 6 people who matter for one decision. This Skill maps the whole committee, classifies every role, audits coverage by function and flags departures. Run Account Intelligence before the first call; run Buying Group once the deal has more than one stakeholder.
Will my requests use a lot of Lusha credits?
The Skill checks your balance first and previews the search results before revealing any contact details. Only contacts that make the final map get enriched, typically 5 to 10 per account. Filter resolution and the company lookup are free.
Can I share the Skill with my team?
Yes. Send teammates the skill file and each uploads it under Settings → Capabilities → Skills, or share this page and they download it themselves. On Claude Team or Enterprise you can also share a Project with the instructions pasted in; teammates inherit it along with the connector.
