Pull a verified org chart for a target account
A Claude prompt that returns a structured org chart for a target account — by department, by seniority level, every contact verified and callable. Useful before a strategic account review, an account plan, or a territory handover.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the prompt and run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I want a verified org chart for [COMPANY NAME] before a strategic account review.
</context>
<task>
1. Use Lusha to pull verified contacts at [COMPANY NAME] across these departments:
- [DEPARTMENT 1, e.g. Sales]
- [DEPARTMENT 2, e.g. Marketing]
- [DEPARTMENT 3, e.g. Engineering and Technical]
2. For each department, structure the output by seniority:
- C-suite and VP level
- Director level
- Manager level (optional, if needed)
3. For each contact, return:
- Full name
- Title
- Validated email
- Direct dial / mobile
4. Group output by department, then by level inside each department.
5. Cap output at 30 contacts total for readability. Surface the total available headcount per department so I can dig deeper if needed.
</task>
<constraints>
- Only include contacts with a validated email.
- Skip contacts who left the company.
- If a department returns no contacts at a given level, note it.
</constraints>What you'll get back
Input: Target account — Snowflake. Departments — Sales, Marketing, Engineering and Technical. Levels — C-suite/VP and Director.
Output: 282 verified contacts identified across the three departments at the two seniority levels (15 Sales VPs, 213 Sales Directors, 14 Marketing VPs, 40 Engineering VPs). Below is a real slice of the live result — eight named leaders across the three departments, all with validated work emails and phones.
| Contact | Title | Department | Level | Phone | |
|---|---|---|---|---|---|
| Denise P. | Chief Marketing Officer | Marketing | C-suite | ✓ | ✓ |
| Tanuj B. | SVP of Marketing and Global Revenue Enablement | Marketing | C-suite | ✓ | ✓ |
| Keegan R. | SVP of Sales, Americas Acquisition | Sales | VP | ✓ | ✓ |
| Mark F. | SVP of Sales | Sales | VP | ✓ | ✓ |
| Brian D. | VP of North American Sales | Sales | VP | ✓ | ✓ |
| Dwarak R. | VP and Head of AI Engineering and Research | Engineering | VP | ✓ | ✓ |
| Alex D. | SVP of Solutions Engineering | Engineering | VP | ✓ | ✓ |
| Julian H. | Director of Global Accounts | Sales | Director | ✓ | ✓ |
Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
Why it works
Org charts hand-built from LinkedIn are stale within weeks. A verified org chart pulled inside Claude is current at the moment you ask for it. Three things matter for the output to be useful.
The structure mirrors how you’ll work the account. Department first, then seniority — which is how an AE actually thinks about coverage. The VP layer carries the buying mandate. The Director layer carries the day-to-day execution. Both matter, and the prompt keeps them grouped.
The data is callable today. Every row carries a validated email plus a verified phone, drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe. No mass-downloading a static org map and watching the contacts go stale before the meeting.
The total headcount per department signals where the buying gravity sits. A company with 213 Sales Directors and only 14 Marketing VPs is structured very differently from a company with the inverse split. That ratio is intelligence — useful before the strategic call, useful for territory planning, useful for forecasting.
FAQ
How is this different from the buying group prompt?
The buying group prompt slices an account by role in the buying process — economic buyer, technical evaluator, end user, influencer. The org chart prompt slices by department and seniority. Use the buying group prompt for active deals. Use the org chart prompt for strategic account planning, territory handovers, or coverage analysis.
Can the prompt show real reporting lines?
The Lusha tools return department, seniority, and title — not direct reporting relationships. The prompt groups by level within each department, which is how org charts are practically read anyway. For named reporting lines, run a follow-up query naming the manager and asking who reports to them.
Can I add or remove departments?
Yes. Pass any combination of Lusha’s department names in the prompt — Business Development, Customer Service, Engineering and Technical, Finance, General Management, Human Resources, Information Technology, Legal, Marketing, Operations, Product, Research and Analytics, or Sales.
Does the prompt handle very large accounts?
Yes, but cap the output. A company at Snowflake’s scale returns hundreds of director-level contacts in a single department. The prompt is built to cap at 30 total and surface the available count per department so you know where to dig deeper.
Can I use this for global subsidiaries?
Lusha returns contacts across the parent company’s verified org. For multi-entity accounts, run the prompt per entity by passing different domains.
Ready to build this?
Get started with Lusha and set up this play in minutes.
