Map new buying centers inside an existing customer
A Claude prompt that fires when an existing customer creates a new structural buying opportunity — opens an EMEA office, hires a head of a new business unit, acquires another company, splits a function into its own org. The prompt surfaces who’s running each new buying center with verified contacts and the structural event that created the opportunity.
The original contract covers one buying center. The customer is now running three. Built for CSMs whose customer expanded faster than the original scope.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just name the customer and the trigger event, 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>
My existing customer just created one or more new buying centers since my original deal closed. The original contract covers the original buying center, but the customer is now running more of them.
My customer and known scope:
- Customer name / domain: [CUSTOMER]
- My function we sold into: [Sales / Engineering / Marketing / etc.]
- Original buying center we serve: [region, BU, or function — e.g., "US Sales", "North America Engineering"]
- Trigger event (if known): [new region, new business unit, M&A as acquirer, function split — leave blank to auto-detect]
</context>
<task>
1. If the user named a specific trigger event, focus the search there. If not, use Lusha's signals layer to surface recent triggers that would create new buying centers:
- Geographic expansion (new VP of EMEA, Head of APAC, new country office)
- Business unit launch (new VP or GM of a product line we don't currently serve)
- M&A as acquirer (newly acquired entity now part of the customer's footprint)
- Function split (RevOps separating from Sales Ops, AI Engineering becoming its own org)
2. For each new buying center surfaced, find the verified leadership running it:
- The owner of the buying center (VP, Head of, Senior Director)
- One adjacent function leader at the same regional or BU level (channel, marketing, partnerships)
- One technical evaluator if the buying center is product-led (Solutions Engineering, Customer Success leader for that region)
3. For each contact, return:
- Full name and current title
- Validated email
- Direct dial or mobile (with DNC where applicable)
- Buying center role (owner / adjacent / technical evaluator)
- Structural trigger — one sentence on what event created this buying center
- Engagement angle — one sentence on how the original engagement extends
4. Order output by buying center, then by role inside each.
5. Flag any buying center where Lusha returns zero matched leadership — that may mean the buying center is being run by the original team (no expansion opportunity) or it's too new to be indexed.
</task>
<constraints>
- A new buying center is a structural change, not just a hire. A new VP joining the existing US team is a relationship signal, not a new buying center. A new VP of EMEA opening the first European office is a new buying center.
- Do not invent triggers. Surface only what Lusha returns.
- For very large customers (5,000+ employees), cap at 3 buying centers per run to keep the output actionable.
- The engagement angle should be specific: extending a US security platform contract to cover EMEA is concrete; "deepen the relationship" is not.
</constraints>What you'll get back
Input: Customer — Verkada. Function we serve — Security platform deployment. Original buying center — US Security team. Trigger event — recent funding round plus EMEA and Middle East expansion in the last 6 months.
Output: 4 new buying centers surfaced with 5 verified contacts running them. Below is the real result from running the prompt against the live Lusha connector.
New Buying Center 1: EMEA Region
| Contact | Title | Role | Structural trigger |
|---|---|---|---|
| Lewis P. | Regional Vice President of Enterprise | Owner | Verkada’s EMEA expansion accelerated after the Dec 2025 CapitalG-led $5.8B funding round |
| Ben W. | Director of EMEA Channel | Adjacent | Channel-led GTM motion in Europe; controls partner-driven security deployments |
Engagement angle: The original US security platform contract scope doesn’t extend to EMEA deployments. Lewis is the regional owner and Ben is the channel-side gatekeeper. Both need to know the value story before EMEA rollout decisions get made without the existing vendor in the conversation.
New Buying Center 2: Middle East Region
| Contact | Title | Role | Structural trigger |
|---|---|---|---|
| Fred C. | Senior Director and Head of Middle East | Owner | Dubai office opened Jan 2026 — brand-new buying center, less than 4 months old |
Engagement angle: The Middle East region didn’t exist 6 months ago. The buying center is new enough that vendor selection is still being scoped. Direct introduction from the existing US contact is the right path, ideally before the regional security platform decision gets locked.
New Buying Center 3: Mid-Market Sales (separate from Enterprise)
| Contact | Title | Role | Structural trigger |
|---|---|---|---|
| Peter R. | Regional Vice President of Mid-Market Sales | Owner | Mid-Market emerging as a distinct GTM segment post-funding — distinct from the Enterprise org our contract serves |
Engagement angle: The original contract is Enterprise-scoped. Mid-Market is a structurally separate buying center with different deployment scale, different pricing tier, and different deal cycle. Same product, different commercial conversation.
New Buying Center 4: Solutions Engineering (Global Technical)
| Contact | Title | Role | Structural trigger |
|---|---|---|---|
| Adrian T. | Director of Solutions Engineering | Technical evaluator | Engineering function expanding in parallel with Sales — the +25% Engineering hiring surge over the last quarter signals a build-out of the technical evaluation function |
Engagement angle: Solutions Engineering becomes the technical evaluator across all new regions. Securing this contact early means the existing platform doesn’t get re-evaluated against alternatives during regional rollouts.
Summary
- Buying centers mapped: 4
- Verified contacts surfaced: 5
- Structural triggers identified: 3 (CapitalG funding + geographic expansion, Middle East office opening, Engineering hiring surge)
- Original contract coverage: US Enterprise security platform
- New scope opportunities: EMEA Enterprise, Middle East, Mid-Market US, Global Solutions Engineering
One credit consumed for the regional leadership search. The signal data reused from earlier gallery runs.
Why use Lusha in Claude
The original contract scope rarely tracks the customer’s structural growth. Three patterns repeat across every fast-growing customer.
Geographic expansion creates new buying centers, not just new locations. A US Enterprise security contract doesn’t automatically extend to a new Dubai office. The Middle East region has its own head, often its own pricing structure, often its own approved vendor list. The CSM who treats geographic expansion as “more of the same customer” misses the structural reality — it’s a new buying center with new decision-makers and a clean vendor slate. The prompt surfaces the regional owners deliberately so the CSM can be in the room before the regional vendor decision gets made.
Business unit launches and function splits are quieter triggers, but they matter more for expansion ARR. When a customer’s RevOps function spins out as a separate org reporting to the CRO instead of Sales Ops, that’s a new buying center even though no new building opened. When a customer launches a new product line with its own VP, that VP gets a new vendor stack to build. The trigger is structural change, not physical change.
M&A as the acquirer is the most under-mined expansion trigger in B2B. When the customer acquires another company, the CSM inherits a new buying center that runs on different vendors. The acquired entity’s contracts come up for review in the first 12-18 months post-close, and the existing customer’s vendors are usually the first incumbents the new team evaluates. The prompt catches M&A-as-acquirer events in the trigger scan and maps the leadership at the acquired entity as a new buying center inside the customer.
The engagement angle has to be concrete. “Deepen the relationship” is a sentence that fits any context, which means it fits no context. “Extend the US Enterprise security platform contract to cover EMEA deployments, starting with a regional pilot in Q3” is concrete enough that the CSM knows what to propose, who to propose it to, and when. The prompt forces specificity by asking what structural event created the buying center.
Data drawn from 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What counts as a "new buying center" vs just a "new hire"?
A new hire into an existing team is a relationship signal — handled by the multi-thread map prompt and the new-champion prompt. A new buying center is structural — a new region, a new business unit, an acquired entity, or a function that newly reports outside the original buying group. The test: does the new hire have their own budget authority, or are they spending against the original budget owner’s line? Independent budget authority means new buying center.
How does the prompt decide which triggers create new buying centers?
Four trigger types qualify: geographic expansion (new region head with regional budget authority), business unit launch (new VP or GM of a product line with separate P&L), M&A as the acquirer (acquired entity now has buying authority inside the customer), and function split (function moves out of original buying group reporting structure). The prompt watches for these specifically in the signal scan.
Should I run this against my whole book or per account?
Per account, when a specific trigger event has fired. The prompt is event-driven, not scan-driven. When the buying-signals gallery’s customer-expansion prompt flags a customer with geographic expansion or M&A activity, that’s the signal to run this prompt on that specific account. Running it against an entire book without trigger context surfaces too many candidate buying centers and dilutes the action.
What if the new buying center is too new to be in Lusha's catalog?
Brand new offices (less than 30 days old) often don’t have indexed leadership yet. The prompt will flag the buying center as detected (via the trigger) but with no matched leadership. Re-run in 30-45 days to catch the new hires when they’re indexed. In the meantime, ask the existing contact for an introduction — that’s the right path for fresh expansion territory.
Does the prompt work for very large customers like Snowflake or MongoDB?
Yes. Large customers actually have more new buying centers per quarter than mid-market customers — they create new regions, BUs, and functions continuously. The constraint block caps at 3 buying centers per run for very large customers to keep the output actionable. For comprehensive coverage of all buying centers, run multiple times scoped by trigger type (regions one run, BUs another).
Can I combine this with the multi-thread map?
Yes. The combined workflow is: (1) Multi-thread map prompt builds the relationship map at the original buying center. (2) This prompt surfaces new buying centers as they form. (3) Each new buying center gets its own multi-thread map. Some CSMs run all three in one session for a major account expansion plan.
Ready to build this?
Get started with Lusha and set up this play in minutes.
