Find expansion opportunities in your accounts before the QBR

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own account list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Expansion revenue is the most efficient revenue a CS or AM team generates — no new logo acquisition cost, existing relationship, proven value. The problem is most teams find expansion opportunities too late. A customer mentions a new team at the QBR. A new office opens and nobody noticed. A hiring surge in an adjacent function happens six weeks before budget freezes. This Claude prompt scans your existing customer accounts through Lusha, surfaces every signal that correlates with expansion readiness, maps new buying centers that haven’t been touched, and returns a ranked list of accounts worth a proactive conversation this week — before the QBR forces the agenda.

The prompt

Open in Claude Open in ChatGPT 
<context>
I want to find expansion opportunities in my existing customer
accounts before my next QBR cycle — accounts that are showing
signals of growth, new buying centers, or adjacent use cases
I haven't tapped yet.

My accounts:
[Paste company names or domains — or say "use my full
book of business" if your CRM is connected]

What I sell: [one sentence — product and the function
or use case it serves]

Adjacent functions or use cases I could expand into:
[e.g. "currently sell to Sales — could expand to
Marketing, RevOps, or Customer Success"]
</context>

<task>
1. EXPANSION SIGNALS — For each account, use Lusha to
   check for signals that indicate growth or expansion
   readiness:
   - Hiring surge in the function I currently sell into
     (scaling means more seats or more usage)
   - Hiring surge in an adjacent function I could
     expand into
   - New office or geographic expansion
   - Funding event in the last 90 days
   - New executive hire in an untouched buying center
   - Headcount growth 15%+ in the last 90 days

2. NEW BUYING CENTERS — For each account, identify
   functions or teams I'm not currently selling into
   that could benefit from my product:
   - Verify at least one VP+ contact in each new
     buying center via Lusha
   - Confirm they are not already in my CRM or active
     deal (check Gmail if connected)
   - Flag buying centers where Lusha has strong contact
     coverage vs thin coverage

3. CURRENT CONTACT HEALTH — Verify that my existing
   contacts are still in seat:
   - Flag any champion departures
   - Flag any promotions — expanded scope may mean
     expanded budget authority
   - Flag recent hires in key roles — new stakeholders
     who don't know your product yet

4. EXPANSION SCORING — Score each account by expansion
   readiness:
   - High: 2+ expansion signals, new buying center
     identified with verified contact
   - Medium: 1 expansion signal or new buying center
     with thin contact coverage
   - Low: no signals, contacts confirmed, no obvious
     expansion trigger right now

5. RANKED OUTPUT — Return accounts ranked by expansion
   readiness. For each account:
   - Expansion score: High / Medium / Low
   - Specific signals driving the score
   - New buying center identified with verified contact
   - Current contact status
   - Recommended expansion angle tied to the signal
   - Urgency: this week / this month / next QBR
</task>

What you'll get back

Your full book of business ranked by expansion readiness. High-signal accounts at the top with a specific buying center, a verified contact, and an expansion angle ready to use before your next QBR.

Accounts scanned: 18  ·  High expansion readiness: 4  ·  Medium: 7  ·  Low: 7  ·  New buying centers identified: 6  ·  Contacts flagged: 3

High expansion readiness — act this week

AccountScorePrimary signalNew buying centerUrgency
[Company A]HighSeries B closed — $28M raisedMarketing — VP verifiedThis week
[Company B]HighHeadcount up 24% — sales and RevOpsRevOps — Head of RevOps verifiedThis week
[Company C]HighNew office opened — EMEA expansionEMEA Sales — VP verifiedThis week
[Company D]HighChampion promoted to CROCS function — not yet coveredThis week

[Company A] — full detail

Expansion signals

SignalTypeDate
Series B closed — $28M raisedFunding event[date]
14 new sales roles postedHiring surge[date]
3 marketing roles posted — demand gen focusAdjacent function hiring[date]

New buying center — Marketing

FieldValue
ContactK.L.
TitleVP of Marketing
Tenure14 months
Emailk.l@[company].com
Direct dial+1 415 555 ••••
In CRMNo — net new contact

Contact confirmed live via Lusha connector, [date]

Expansion angle: Series B just closed and they’re scaling both sales and marketing simultaneously. Your current champion owns the sales motion — introduce the product to the VP of Marketing before someone else does. The demand gen hiring surge is the hook: they’re building outbound capacity and need the same verified data foundation their sales team already runs on.

Medium expansion readiness — act this month

AccountScoreSignalGapUrgency
[Company E]MediumHeadcount up 11% in salesNo new buying center identifiedThis month
[Company F]MediumNew VP of CS hired 8 weeks agoCS buying center — thin coverageThis month
[Company G]MediumNew office — APACAPAC contacts — not in LushaThis month
[Company H]MediumChampion promoted to VPNew scope — budget authority unclearThis month
[Company I]MediumRevOps team hiring surgeRevOps contact not verifiedThis month
[Company J]MediumFunding — bridge roundBudget pressure — timing sensitiveThis month
[Company K]MediumNo signals — stable accountNo obvious expansion triggerNext QBR

Low expansion readiness — monitor

7 accounts checked. No expansion signals found. Key contacts confirmed in seat. No action required this month — revisit before next QBR cycle.

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own account list and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Gmail, Lusha
Type: Prompt

Why use Lusha in Claude

Expansion revenue is won or lost in the weeks before a QBR, not during it. By the time a customer brings up a new team or a new use case at a quarterly review, they’ve already been thinking about it for a while — and if a competitor has been in the account in the meantime, you’re not leading the conversation anymore.

The signals that predict expansion show up in Lusha’s data before they show up in a customer conversation. A Series B that closed last month means budget just expanded. A 24% headcount surge in sales and RevOps means seats are being added and workflows are being built. A new EMEA office means a new regional team that hasn’t been onboarded yet. A champion promoted to CRO means expanded scope, expanded budget authority, and a relationship that just became more valuable — if you get in front of it before the new role absorbs their attention entirely.

Lusha tracks all of these as named, verified, time-stamped signals across 1.2B+ data points processed daily. The expansion scoring in this play layers those signals against what you already sell and the adjacent functions you could grow into — so the output isn’t a list of accounts that are generally healthy. It’s a list of accounts where something specific happened in the last 30 to 90 days that creates a concrete reason to have a different conversation than the one you had at the last QBR.

The new buying center step is where the revenue opportunity becomes specific. A funding event at a customer where you only sell to Sales is interesting. A funding event at a customer where you only sell to Sales and Lusha finds a verified VP of Marketing who’s hiring three demand gen roles this month is an expansion call. The contact is verified live during the session — current title, direct dial, business email — so the conversation can start this week, not after a separate enrichment run.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How is this different from the Expansion Signal Account Scan play?

    The Expansion Signal Account Scan play sweeps your book of business for expansion signals and returns a broad signal digest — useful for a weekly review of what moved across all accounts. This play goes further: it identifies specific new buying centers, verifies a contact in each one, scores accounts by expansion readiness, and returns a ranked list with a concrete expansion angle tied to the specific signal. It’s built for action, not awareness. Use the account scan for weekly monitoring. Use this play when you want to walk into QBR prep with a specific expansion conversation already prepared.

  • What if I sell into one function and don't know which adjacent functions to expand into?

    Describe what you sell in the context field and leave the adjacent functions field blank. The play will identify the functions most commonly associated with your product category and check for contacts and signals in those functions automatically. If you sell a prospecting data tool to Sales, it will check for RevOps, Marketing, and CS buying centers without you having to specify them. You can review the suggestions and remove any that don’t fit your motion before acting on them.

  • How does the play handle accounts where the champion was promoted?

    A promotion is flagged as both an opportunity and a risk. The opportunity: your champion now has more budget authority and a broader mandate — if the product is working, a promotion is the right moment to expand the conversation. The risk: a promoted champion has a new job and new priorities, and if you don’t re-engage quickly, the relationship can go cold while they’re adjusting to the new role. The play surfaces both signals and recommends acting within two weeks of the promotion date — the window where the relationship is still warm and the new scope is still being defined.

  • Should I run this before every QBR or on a different cadence?

    Six weeks before your QBR cycle is the sweet spot — enough time to have the expansion conversation, get internal buy-in from a new stakeholder, and build the business case before the formal review. Running it monthly keeps the signal feed fresh and means you’re never starting a QBR from a cold position. If you have a large book of business, prioritize accounts due for renewal in the next 90 days first, then run it across the full book.

  • What if an account is showing expansion signals but also has churn risk signals?

    The play will flag both and surface them together in the account detail. A company that just raised a Series B but also had a champion depart five weeks ago needs a different conversation than a straightforward expansion call. The recommended action in that case is to re-establish the relationship and confirm the new owner of your product before leading with an expansion pitch. Running this play alongside the Find the accounts most likely to churn before they tell you play gives you the full picture — which accounts to protect and which to grow — before the QBR calendar forces both conversations at once.

Related Prompts

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs