The 10 best Claude prompts for account management in 2026

Account Management is the hybrid role most B2B companies build inconsistently. AMs aren’t pure CSMs — they own new revenue, not just retention. They aren’t pure AEs — they own existing relationships, not just acquisition. The job is the strategic deep-account work that sits between: protecting the renewal, expanding the scope, managing the executive sponsor, multi-threading across the buying group, finding the next budget window before the customer’s procurement team does.

The 10 prompts below are the ones a working AM actually runs in 2026 — designed for fewer accounts and bigger contracts, executive-level relationships, multi-product expansion, and the structural awareness that catches a renewal risk three months before it becomes a churn conversation.

Organized by workflow so you can find what you need fast — strategic account intelligence, expansion plays, renewal protection. Copy the green/black block, paste it into Claude, replace the bracketed values with your specifics, and run.

Connect Lusha to Claude in two minutes →

Strategic account intelligence (Prompts 1–4)

The deep-account work. Pre-meeting briefs, stacked-signal prioritization, multi-thread relationship mapping, structural buying-center detection. The intelligence that makes a strategic-account portfolio actually strategic instead of just a list of named logos.

Prompt 1 — Get a single-account signal brief before any executive meeting

Pre-meeting prep in 60 seconds. Every signal event in the last six months at one strategic account, organized into five categories, with talk tracks tied to each signal.

<context>
I have an executive meeting or strategic review on [ACCOUNT NAME] in [TIMEFRAME — e.g., 24 hours]. I need a complete pre-meeting brief.
</context>
 
<task>
Use Lusha's signals layer to pull every signal at the account from the last 6 months, organized into five categories:
 
1. LEADERSHIP — executive hires, promotions, departures
2. STRATEGIC MOVES — M&A, IPO, funding, strategic investments
3. PRODUCT ACTIVITY — launches, integrations, new features
4. HIRING INTENSITY — surges by department, headcount growth, geographic spikes
5. MARKET SIGNALS — web traffic shifts, partnerships, recognition events
 
For each signal:
- Event type and date
- One-line summary
- Source article URL where available
 
At the top, surface a 3-line headline summary:
- Most important leadership move
- Biggest strategic shift
- Strongest active hiring signal
 
After the categorized brief, suggest 3-5 talk tracks for the meeting, each tied to a specific surfaced signal and the relationship dynamic it creates.
</task>
 
<constraints>
- Pull every signal type, not just funding and hiring
- Surface source URLs on every news event that has one
- If the account is quiet, surface that honestly — also a useful read on the meeting context
</constraints>

See the full workflow with a live demo →

Prompt 2 — Find which strategic accounts have stacked signals this quarter

For AM book-portfolio prioritization. Stacked signals — multiple types firing on the same account in the same window — separate accounts moving in real buying motions from accounts where nothing structural has shifted.

<context>
I want to identify the accounts in my strategic book with the highest concentration of buying signals — multiple signal types firing in the same window. Stacked signals separate accounts in real buying motion from accounts with isolated news events.
 
My strategic accounts:
[PASTE — one company per line]
 
Window: last [WINDOW — e.g., 90 days]
</context>
 
<task>
For each account, retrieve activity in the window across multiple signal types:
- Financial events (funding, IPO, M&A, strategic investments)
- Leadership events (hires, promotions, departures)
- Hiring surges by department
- Product launches and partnerships
- Headcount growth
- Web traffic shifts
 
Count distinct signal types per account. A stacked-signal account has 3+ different types firing.
 
Output a ranked table:
Account | Signal types fired (count) | Specific signals | Stack tier | Recommended action
 
Tier definitions:
- TIER 1 — 4+ distinct signal types (drop-everything strategic action this week)
- TIER 2 — 3 distinct signal types (call this week)
- TIER 3 — 2 distinct signal types (monitor, reach out next week)
- SINGLE — 1 signal type (worth tracking, not stacking)
- QUIET — no signals in window
</task>
 
<constraints>
- Stack density (breadth of signal types) is the metric, not absolute signal count
- A QUIET account is intelligence — surface the count so I know the scan covered the full book
- For TIER 1 accounts, the recommended action should reference WHICH signal type creates the urgency
</constraints>

See the full workflow with a live demo →

Prompt 3 — Build a multi-thread map for a strategic account

Strategic accounts that run on a single relationship are renewal risk in slow motion. Map the 6-8 verified contacts you should have at every active strategic account.

<context>
I have a strategic account where I'm under-threaded — I know one main contact but should know 6-8 across the buying group.
 
My known contact:
- Name: [NAME]
- Title: [TITLE]
- Strategic account: [ACCOUNT NAME]
- Function we sold into: [FUNCTION]
</context>
 
<task>
Use Lusha to find 6-8 additional verified contacts at the account, organized into five relationship roles:
 
- PEER OF CHAMPION — same function, same level (1-2)
- MANAGER / SKIP-LEVEL — the boss above, and the boss above that (1-2)
- ADJACENT FUNCTION — leaders in adjacent functions the engagement should touch (2-3)
- EXECUTIVE SPONSOR — C-suite owner of the broader business unit (1)
- SUCCESSOR CANDIDATE — Director/VP-level who could step into my champion's role if they move (1)
 
For each:
Name | Title | Validated email | Direct dial | Relationship role | Why this person matters (one sentence on the strategic angle, not generic relationship benefit)
 
Group output by relationship role, not seniority. Flag any role where Lusha returns zero — that's a structural gap in the strategic relationship map.
</task>
 
<constraints>
- Only include contacts with validated email
- Cap at 2 contacts per relationship role
- For ADJACENT FUNCTION at strategic accounts, pick functions tied to the account's stated strategic direction — not generic adjacencies
- The successor candidate is renewal insurance; the executive sponsor is expansion insurance
</constraints>

See the full workflow with a live demo →

Prompt 4 — Map new buying centers inside a strategic account

When a strategic account opens a new region, acquires another company, launches a business unit, or splits a function — they’ve just created a new buying center. The original contract doesn’t cover it. The AM’s job is to find the leadership before procurement does.

<context>
My strategic account just created one or more new buying centers — opened a region, acquired a company, launched a business unit. The original contract covers the original buying center; the account is now running more of them.
 
My account and current scope:
- Account: [ACCOUNT NAME / DOMAIN]
- Function we serve: [FUNCTION]
- Original buying center: [REGION, BU, OR FUNCTION — e.g., "US Sales", "Engineering North America"]
- Trigger event (if known): [new region, new business unit, M&A, function split — leave blank to auto-detect]
</context>
 
<task>
1. Use Lusha's signals layer to surface recent triggers that create new buying centers:
   - Geographic expansion (new regional VP, country office launch)
   - Business unit launch (new VP or GM of a product line)
   - M&A as acquirer (newly acquired entity inside the account footprint)
   - Function split (new C-suite role, function spun out from existing org)
 
2. For each new buying center, find the verified leadership:
   - The owner (VP, Head of, Senior Director)
   - 1 adjacent function leader at the same regional/BU level
   - 1 technical evaluator if the buying center is product-led
 
For each contact:
Name | Title | Validated email | Direct dial | Buying center role | Structural trigger | Engagement angle (how the original engagement extends)
 
Order by buying center, then by role within each.
</task>
 
<constraints>
- A new buying center is structural (new region, new BU, acquired entity) — not just a new hire in the existing team
- Cap at 3 buying centers per run for very large accounts (5,000+ employees)
- The engagement angle must be specific (e.g., "extend US Enterprise contract to EMEA following the new VP appointment"), not generic
- The job is to be on the calendar before the new buying center's procurement team formalizes vendor selection
</constraints>

See the full workflow with a live demo →

Expansion plays (Prompts 5–7)

For accounts that are READY for more. Cross-sell to adjacent functions, time the proposal to the budget window, scan for the expansion-positive signals that say “now.”

Prompt 5 — Identify cross-sell opportunities by adjacent function

For multi-product companies. Cross-sell converts an installed account into a strategic account — different function at the same customer, different product, warm-intro path from the existing champion.

<context>
I have a strategic account using Product A. I want to identify the right buyer at the same account for Product B, which lives in an adjacent function.
 
The existing engagement:
- Account: [ACCOUNT NAME / DOMAIN]
- Product A (deployed): [PRODUCT NAME]
- Function we sold Product A into: [FUNCTION]
- My champion: [NAME, TITLE]
 
The cross-sell:
- Product B: [PRODUCT NAME]
- Function that owns Product B: [FUNCTION]
- Buyer profile for Product B: [SENIORITY + ROLE FAMILY]
</context>
 
<task>
1. Use Lusha to find the verified leadership in the cross-sell function at the account:
   - C-suite owner of the function (CMO, CTO, CFO — the right one for Product B)
   - 1-2 VP-level leaders running operational areas matching the product's use case
   - 1 Director-level operator likely to be the day-to-day evaluator
 
2. For each contact:
Name | Title | Validated email | Direct dial | Buyer role for the cross-sell (economic, operational, technical evaluator) | Warm-intro path from my existing champion
 
3. Surface the cross-sell rationale per buyer — one sentence on why this specific person, in this specific function, is the right buyer for Product B given the account's current state and recent signals.
 
4. If recent buying signals (funding, hiring surge in the new function, product launches) make the cross-sell timing especially strong, flag those signals.
</task>
 
<constraints>
- The cross-sell is to an adjacent function. If Product B sells to the same buyer as Product A, that's upsell — use the multi-thread prompt instead
- The warm-intro path matters — a cross-sell intro routed through the existing champion converts at multiples of cold outreach
- Cap at 4 target buyers per cross-sell for a single discovery brief
- The rationale should reference what the account is publicly doing, not generic product-fit language
</constraints>

See the full workflow with a live demo →

Prompt 6 — Surface the post-event budget window

The “when to propose” prompt. Find the structural moments when the account’s budget reopens — fiscal year crossings, new leader mandate windows, post-funding allocation periods, M&A vendor rationalization cycles.

<context>
I want to know when my account's budget reopens for new vendor commitments — the structural moments inside the next 6-12 months when an expansion proposal would land inside an active budget window.
 
My account:
- Account: [ACCOUNT NAME / DOMAIN]
- Current contract scope and renewal date: [SCOPE + DATE]
- Expansion I want to propose: [ADDITIONAL SEATS / NEW REGION / CROSS-SELL PRODUCT]
</context>
 
<task>
1. Use Lusha's signals layer to scan the account's last 12 months for structural budget events:
   - Funding rounds (budget allocation lands 60-90 days post-close)
   - IPO events (6-12 months of investor-mandated growth spending)
   - M&A as the acquirer (acquired entities vendor-rationalized within 12 months)
   - Executive hires in the buying group (CRO, CFO, CMO, CTO — 60-90 day mandate windows)
   - Executive departures (HOLD window — avoid expansion during transition)
 
2. For each event, calculate:
- Open date (when budget conversation becomes possible)
- Peak window (when allocation decisions are being made)
- Close date (when window narrows back to normal procurement)
 
3. Cross-reference with the account's likely fiscal year structure.
 
4. Output a budget calendar:
Event | Window opens | Peak window | Window closes | Status (OPEN NOW / OPENING SOON / CLOSED / HOLD) | Recommended action
 
5. At the bottom, list the 2-3 highest-value windows to act on this quarter.
</task>
 
<constraints>
- A budget window is structural — created by a specific event, not a calendar quarter
- New CRO/CFO/CMO mandate windows are 60-90 days; funding allocation is 90-180 days; IPO is 6-12 months
- Do not propose expansion inside a HOLD window
- Surface only events Lusha actually returns; don't invent triggers
</constraints>

See the full workflow with a live demo →

Prompt 7 — Identify expansion signals on existing accounts

The monthly expansion-readiness scan. Surfaces which accounts in your strategic book are showing the events that precede an expansion conversation — funding, hiring surges, new leadership, product launches, geographic expansion.

<context>
I want to scan my strategic accounts and find which are showing expansion signals — events that mean the account's buying context just shifted in a direction that creates upsell, cross-sell, or scope-expansion opportunity.
 
My strategic accounts:
[PASTE — one row per account, with current spend area and function we sold into]
</context>
 
<task>
For each account, use Lusha's signals layer to scan the last 90 days for expansion triggers:
- Hiring surge in the function we sold into (more seats, more usage)
- New leadership in the buying group (mandate window, vendor scope under review)
- Funding round, IPO, M&A as acquirer (budget unlocked)
- Strategic investment in adjacent tech (direction of next spend)
- Major product launch (new platform area we could deepen scope into)
- Geographic expansion (new region rollout opportunity)
 
For each account, return:
Account | Current scope | Expansion trigger fired | Trigger date | Expansion angle (what conversation this opens) | Recommended next step
 
Rank by expansion-readiness: READY (strong trigger, last 60 days) / WARM (signal fired but requires more discovery) / STABLE (no signal, continue normal cadence).
</task>
 
<constraints>
- The trigger must map to a real expansion conversation — generic news doesn't count
- New leadership in the buying group function is the strongest single trigger
- A STABLE account isn't failure — surface for next monthly scan
</constraints>

See the full workflow with a live demo →

Renewal protection (Prompts 8–10)

For protecting the strategic book. Coverage audits on active renewals, replacement-champion discovery when key contacts move, pre-signature validation on renewal contracts before they go out.

Prompt 8 — Audit multi-thread coverage on a renewal in motion

A renewal is a deal. AMs working strategic accounts should audit renewal coverage the same way an AE audits a new-business deal in Negotiation. Stage-aware, gap-prescriptive, forecast-protective.

<context>
I have an active renewal at a strategic account. I want to audit my multi-thread coverage against the verified buying group — surface the gaps at the current renewal stage and prescribe the next 2-3 touches.
 
My renewal:
- Account: [ACCOUNT NAME]
- Renewal stage: [Discovery / Proposal / Negotiation / Closing — apply the same framework to a renewal as to a new-business deal]
- Renewal scope (current contract + any expansion proposed): [SCOPE]
- Contacts touched (name, role, days since last touch): [LIST]
</context>
 
<task>
Use Lusha to pull the full verified buying group at the account. Apply the stage-aware coverage framework:
 
- Discovery → Proposal: must have technical evaluator + end user
- Proposal → Negotiation: must have economic buyer
- Negotiation → Closing: must have economic buyer + procurement gate
- Closing → Won: must have economic buyer signed + executive sponsor briefed
 
Output:
- Touched contacts (role + last-touch recency)
- Critical gaps (musts missing for current stage)
- Stale threads (touched but silent 14+ days at active stage)
- Prescribed next touches with verified contact details and a one-line angle
 
For each gap, specify which role family is missing and which contact at the account fills it. Renewals at strategic accounts often need the executive sponsor briefed even at Negotiation — flag if missing.
</task>
 
<constraints>
- Coverage requirements at strategic renewals are typically stricter than new-business deals — the executive sponsor matters more, procurement coordination starts earlier
- Each prescribed touch needs a specific angle, not generic outreach
- Flag any contact in the buying group who has been touched but gone silent 14+ days
</constraints>

See the full workflow with a live demo →

Prompt 9 — Find the new champion when yours moves on

Strategic accounts with a single champion are renewal risk by structural design. When the champion leaves, find the verified replacement before the renewal cycle reaches them first.

<context>
My champion at a strategic account just left. I need to find the verified replacement and re-engage before the renewal cycle reaches them first.
 
My departed champion:
- Name: [NAME]
- Former title at the account: [TITLE]
- Account: [ACCOUNT]
- Function they owned: [FUNCTION]
</context>
 
<task>
1. Use Lusha to find current contacts at the account matching the departed champion's function and seniority (4-6 candidates including one level up).
 
2. CROSS-VALIDATE each candidate against their individual record:
- Confirm current employer is still the account
- Confirm current title and job start date
- Flag anyone who ALSO moved to a different company (company-side data may still list them at the account)
 
3. For each verified candidate:
Name | Current title | Validated email | Direct dial | Tenure in role | Previous job | Inheritance likelihood (HIGH / MEDIUM / LOW based on scope, seniority, tenure)
 
4. If no clean candidate emerges in the function, surface the C-suite owner one level up as the re-engagement starting point.
 
5. At strategic accounts, also surface the executive sponsor's reaction window — a new champion arriving usually means the executive sponsor's vendor view is being re-shaped in real time. The first 30-60 days post-arrival is the highest-leverage moment.
</task>
 
<constraints>
- Cross-validation is the critical step — company search may return contacts whose individual records show they moved on
- Inheritance likelihood is a judgment based on scope, tenure, seniority — surface the reasoning
- For strategic accounts, the replacement champion may not exist at the same title — sometimes the role gets restructured and the buying decision migrates one level up
</constraints>

See the full workflow with a live demo →

Prompt 10 — Decision-maker validation pre-renewal-signature

The pre-signature check for renewal contracts. Has the signer departed? Did a new C-suite role get created? Did the acquirer freeze contracts? Catch the structural change before the renewal contract goes out.

<context>
I'm about to send a renewal contract for signature. Validate decision makers and structural state at the account before send.
 
The renewal at contract stage:
- Account: [ACCOUNT NAME]
- Planned signer: [NAME, TITLE]
- Contract value (annual): [DOLLAR AMOUNT]
- Contract term: [LENGTH]
- Buying group worked with: [LIST]
- Last meaningful touch with the signer: [DATE]
</context>
 
<task>
Validate three things:
 
1. SIGNER VALIDATION
- Still at the account?
- Current title matches contract?
- Job start date — recent enough that authority for this contract size may not yet apply?
- Seniority appropriate for the contract value?
 
2. BUYING GROUP VALIDATION
- Each contact's current title still matches my notes?
- Anyone departed or changed roles since last touch?
 
3. STRUCTURAL CHANGES at the account (last 30-90 days)
- Executive departures in the contract approval chain
- Leadership hires creating new approval routing
- M&A (especially as acquired party — triggers contract freezes)
- Security incidents (may trigger new procurement scrutiny)
 
Return one of:
- SEND — validated, no structural changes; contract goes out today
- HOLD, verify one thing first — minor issue, specific verification needed
- HOLD, structural change — significant change affects contract path; surface what changed and the next move
 
At strategic accounts, renewal contracts going through a fresh procurement gate (new CSTO, new CFO) often need a 5-7 day pre-coordination touch. Flag that timing if applicable.
</task>
 
<constraints>
- Validation is binary on each check — don't soften with "probably still there"
- If the signer has departed, surface the replacement candidate
- For strategic renewals, the cost of post-signature slip (e.g., new CSTO requesting review after signature) is materially higher than for new-business deals — the validation discipline matters more
</constraints>

See the full workflow with a live demo →

The pattern across all 10 prompts

The 10 prompts above cover three different AM workflows — strategic account intelligence, expansion plays, renewal protection — but share one structural pattern: the verified data layer is what makes them usable at the strategic-account scale. Generic AI prompts produce plausible content about a customer. These prompts return verified buying groups, time-stamped signal events tied to source URLs, and cross-validated identity that catches the contact moves the company-side data hasn’t refreshed yet.

For AMs specifically, the difference shows up in four measurable ways:

• Strategic account expansion ARR rises when proposals land inside actual budget windows, not at random
• Cross-sell attach rate improves when the right adjacent buyer is identified via warm-intro paths, not cold outreach
• Renewal save rate rises when champion departures and risk events surface 60-90 days before the renewal conversation
• Multi-thread relationship depth becomes structural insurance, not ad-hoc effort

Verified data isn’t a nicety for Account Management. It’s the difference between a strategic book that compounds and a strategic book that erodes.

Running it all in one chat

The 10 prompts above each solve one workflow well. For AMs who want to run the full strategic-account workflow as one chat — health scan → expansion classification → renewal-risk classification → role-specific Gmail drafts for every action item — the Customer Health to Action Skill packages it into a single Claude Project install.
(See the Skill →)

See the full Claude prompts gallery →

More in this series:

The 12 best Claude prompts for sales in 2026

The 10 best Claude prompts for B2B marketing in 2026

The 12 best Claude prompts for RevOps in 2026