Build a multi-thread map for an existing customer
A Claude prompt that takes one known contact at an existing customer — your original buyer, your champion, the person on the renewal — and expands the relationship map into 6-8 additional verified contacts. Peers of the champion. The manager and skip-level above them. Adjacent function leaders the existing engagement should be touching. The executive sponsor at the top. The likely successor if your champion ever moves.
Single-threaded customer relationships are renewal risk in slow motion. The prompt surfaces who else inside the account should know the value story, with verified email and phone for every row.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just name your known contact and the customer, then 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 have an existing customer where I'm under-threaded — I know one contact (the original buyer or my main champion) but I should know 6-8 others across the buying group and adjacent functions.
My known contact:
- Name: [CONTACT NAME]
- Title: [TITLE]
- Company: [CUSTOMER NAME / DOMAIN]
- Function we sold into: [Sales / Engineering / Marketing / etc.]
</context>
<task>
1. Use Lusha to find 6-8 additional verified contacts at the customer account, organized into five relationship roles:
- PEER OF CHAMPION — same function, same level as my known contact (1-2 contacts)
- MANAGER / SKIP-LEVEL — the boss of my champion and the boss above (1-2 contacts)
- ADJACENT FUNCTION — leaders in functions adjacent to mine that the engagement should touch (2-3 contacts)
- EXECUTIVE SPONSOR — the C-suite owner of the function or the broader business unit (1 contact)
- SUCCESSOR CANDIDATE — someone at the Director or VP level who could step into my champion's role if they move (1 contact)
2. For each contact, return:
- Full name
- Title
- Validated email
- Direct dial / mobile
- Relationship role (one of the five above)
- Why this person matters — one sentence on the relationship angle
3. Group output by relationship role, not seniority.
4. Flag any role where the result returns zero — that's a structural gap in the relationship map worth investigating.
</task>
<constraints>
- Only include contacts with a validated email.
- Skip my known contact from the result set.
- Skip contacts who left the company.
- Cap at 2 contacts per relationship role for readability. The map is meant to be actionable, not exhaustive.
- For ADJACENT FUNCTION, pick the functions that genuinely connect to my engagement — if I sold to Sales, RevOps and Marketing make sense; HR and Legal usually don't unless the engagement touches them specifically.
</constraints>What you'll get back
Input: Known contact — Keegan R., SVP of Sales, Americas Acquisition at Snowflake. Function we sold into — Sales. Customer account — Snowflake.
Output: 7 additional verified contacts across the 5 relationship roles. Below is the real result from running the prompt against the live Lusha connector.
Peer of champion
| Contact | Title | Why this person matters |
|---|---|---|
| Mark F. | SVP of Sales | Same seniority, peer business unit — co-sponsorship potential and a second sales-side voice for the renewal conversation |
Manager / skip-level
| Contact | Title | Why this person matters |
|---|---|---|
| Jonathan B. | Chief Revenue Officer (incoming, Mar 31, 2026) | Direct manager of my champion. Inside his first 90 days — pre-empt the vendor review by being in the room with my champion |
Adjacent function
| Contact | Title | Why this person matters |
|---|---|---|
| Hillary C. | Vice President of Growth Marketing | Sales-adjacent. Sales productivity tooling that drives growth motion should also be visible to Marketing leadership |
| Patrick H. | Vice President of Revenue Operations | RevOps owns the systems my champion uses daily. Every expansion conversation runs through this seat |
| Dwarak R. | VP and Head of AI Engineering and Research | Adjacent because Snowflake is publicly rebuilding the AI data layer — any product line that touches AI workflows now has a technical evaluator here |
Executive sponsor
| Contact | Title | Why this person matters |
|---|---|---|
| Brian R. | Chief Financial Officer | C-suite owner of the revenue line my engagement supports. Annual renewal at this dollar tier crosses the CFO’s desk |
Successor candidate
| Contact | Title | Why this person matters |
|---|---|---|
| Adam G. | Director of Revenue Operations | Director-level, RevOps function, well-positioned to step into a broader scope if Keegan moves or Patrick gets promoted |
Map summary
- Known contact (your starting point): 1
- New verified contacts added: 7
- Total mapped buying group: 8
- Roles fully covered: Peer, Manager, Adjacent function (×3), Sponsor, Successor
- Gaps flagged: None
All 7 new contacts have validated emails on file. Names abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.
One credit consumed for the additional Marketing-side search. The other roles reused contact data already verified earlier in the gallery.
Why use Lusha in Claude
Single-threaded customer relationships are the single biggest renewal-risk factor in B2B. When the original champion leaves, the renewal has no internal advocate. When the executive sponsor doesn’t know who you are, the expansion conversation never reaches the budget approver. Three things shift when the multi-thread map gets built deliberately instead of by accident.
The roles matter more than the count. A multi-thread map with 8 random contacts at the customer is not better than a single-threaded relationship — it’s just noisier. The five-role framework (peer, manager, adjacent, sponsor, successor) is what turns the count into structure. Each role serves a different purpose in the relationship: the peer validates the value story sideways, the manager owns the budget that funds the renewal, the adjacent function expands the scope of the engagement, the sponsor approves at scale, and the successor is the insurance against the champion’s departure.
Adjacent functions are where expansion lives. Most expansion conversations don’t come from more seats in the original function — they come from a sister function adopting the same tool. The CSM at Snowflake whose champion is in Sales should know the RevOps VP, the Growth Marketing VP, and the AI Engineering leader by name. Those are the seats that turn a single-product renewal into a multi-product expansion. The prompt surfaces adjacent functions deliberately because most CSMs default to going up (toward the executive) instead of sideways (toward adjacent budgets).
The successor candidate is renewal insurance. Every champion eventually moves — to a new role internally or a new company entirely. A CSM who knows the likely successor by name, and ideally has met them, doesn’t lose the relationship when the champion does. The prompt flags one successor candidate per map specifically to build that resilience. It’s not paranoid; it’s structural.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How is this different from the buying group prompt in the prospecting gallery?
The buying group prompt is built for an active sales cycle on a target account — it maps economic buyer, technical evaluator, end user, and influencer in the buying process. This prompt is built for an existing customer relationship — it maps peer, manager, adjacent function, sponsor, and successor in the renewal and expansion context. Same underlying tool. Different output framing because the user moment is different.
What if my champion is a CTO or other C-suite contact already?
The map shifts. For a C-suite champion, the “manager” role becomes the CEO or COO, and the “successor candidate” becomes the SVP or VP one level below. The peer role often becomes another C-suite leader in an adjacent business unit. The prompt adjusts the roles based on the seniority of the known contact.
Should I reach out to all 7 new contacts at once?
No. The map is the plan, not the script. Most CSMs sequence the multi-thread outreach over several months — the peer of the champion first (lowest social cost), then the adjacent function with the strongest opportunity angle, then the manager when there’s a natural moment (like a business review or contract negotiation), then the sponsor at QBR time. The successor stays in the map but typically gets introduced by the champion themselves.
What if I don't have an executive sponsor in my engagement today?
The map flagging an unfilled executive sponsor role is itself useful intelligence. It means the deal got done without C-suite visibility — common in mid-market expansions and bottom-up tool adoption. The next renewal cycle is the right time to fix that, and the prompt surfaces the right C-suite contact to start that work.
Does Lusha handle very large accounts where there are 50+ adjacent function leaders?
Yes. The prompt caps output at 2 contacts per role for readability. For very large accounts (Snowflake-scale, 5,000+ employees), Lusha’s catalog has many more — the prompt’s job is to surface the right 2 per role, not all of them. Reps wanting deeper coverage in one specific function can re-run the prompt with that function as a primary filter.
How often should I update the map?
Quarterly is the right rhythm for most CSM books. The map shifts when contacts move companies, get promoted, or new leaders join — all events that the buying-signals gallery’s monitor prompt will catch. Pair this prompt with the contact-role-changes monitor for a maintained map across the book.
Ready to build this?
Get started with Lusha and set up this play in minutes.
