Identify expansion signals on existing customers

<context>
I'm a CSM or Account Manager. I want to scan my customer book and find which accounts are showing expansion signals — events that mean the customer's buying context just changed in a direction that creates upsell, cross-sell, or scope-expansion opportunity.

For each customer, I'll provide:
- Account name or domain
- Current spend with us (or product line)
- Function we sold into (Sales, Engineering, Marketing, etc.)
</context>

<task>
1. Take this customer list (one row per customer, with current spend area and function sold into):
   [PASTE CUSTOMER LIST]

2. For each customer, use Lusha's signals layer to scan the last 90 days for expansion triggers:
   - Hiring surge in the function we sold into (means more seats / more usage)
   - Hiring surge in adjacent function (means cross-sell opportunity)
   - New leadership in the buying group (new mandate, vendor scope under review)
   - Funding round, IPO, M&A (budget unlocked or stack consolidating)
   - Strategic investment in adjacent tech (direction of next spend)
   - Major product launch (new platform area where we could deepen scope)
   - Geographic expansion (new region rollout opportunity)

3. For each customer, return:
   - Customer name and current function/spend
   - Expansion trigger fired (or "stable — no signal")
   - Trigger date
   - Expansion angle — what conversation this opens
   - Recommended next step (QBR talking point, expansion proposal, multi-thread to new leader)

4. Rank customers by expansion-readiness:
   - READY — strong trigger fired in the last 60 days that maps cleanly to an expansion conversation
   - WARM — signal fired but the expansion angle requires more discovery
   - STABLE — no expansion-relevant signal in window (continue normal cadence)
</task>

<constraints>
- The expansion trigger has to map to an actual conversation you can have. A hiring surge in a function we don't sell into is interesting but doesn't drive expansion unless it opens cross-sell.
- New leadership is the strongest single expansion trigger when the new leader sits over the function we serve.
- Do not invent triggers. Surface only what Lusha returns.
- A customer with no triggers is not a failure — surface them as STABLE for the next monthly scan.
</constraints>

Input: 5-account customer book. Each customer scoped with current spend area and function sold into. Window — last 90 days.

Output: 3 READY, 1 WARM, 1 STABLE. Below is the real result from running the prompt against the live Lusha connector.

Ready for expansion (strong signal in last 60 days)

MongoDB — TRIGGER: NEW CRO arriving April 27, 2026

• Current spend area: Sales productivity tooling for the corporate sales vertical
• Trigger: Ryan Mac Ban appointed Chief Revenue Officer, effective April 27, 2026 — hired to “support next phase of growth”
• Expansion angle: A new CRO inside their first 90 days will review every vendor in the GTM stack. The CSM’s job is to be on the calendar before the review starts, not after. Position the existing engagement as the foundation; tee up usage data and ROI metrics for the new CRO’s onboarding.
• Recommended next step: Pre-empt the vendor review. Schedule a “new-leader briefing” with the original buyer and offer to co-present the impact summary to the incoming CRO in week 4-6 of their tenure.

Snowflake — TRIGGER: NEW CSTO + 3 ACQUISITIONS in AI data layer

• Current spend area: Data platform tooling
• Trigger: Brand-new Chief Security & Trust Officer (April 1, 2026), 3 acquisitions in 6 months (TensorStax, Select Star, Observe) — all AI-adjacent. Strategic investments in RelationalAI and Ataccama.
• Expansion angle: Snowflake is publicly building an agentic AI data layer. Any product line that supports AI data quality, observability, or governance now has a direct connection to a stated strategic priority. The expansion conversation is no longer “more of what you bought” — it’s “how do we extend our scope into the AI data trust stack you’re publicly building.”
• Recommended next step: Multi-thread to the new CSTO. Re-position the existing engagement as the entry point into a broader AI data trust scope.

Verkada — TRIGGER: $5.8B FUNDING + EMEA expansion

• Current spend area: Security platform deployment
• Trigger: $5.8B valuation funding round (CapitalG-led, Dec 2025), new VP of EMEA (Feb 2026), new Head of Middle East with Dubai office opening (Jan 2026)
• Expansion angle: Two expansion vectors firing simultaneously. The funding round unlocks budget for the next deployment phase. The EMEA and ME hires create geographic expansion opportunity if the current contract is US-only.
• Recommended next step: Schedule a “post-round scope review” with the original buyer. If the current contract is US-only, request an introduction to the EMEA and ME leaders for regional rollout discussion.

Warm (signal fired, angle requires more discovery)

Notion — TRIGGER: SALES HIRING SURGE +204%

• Current spend area: Engineering productivity tooling
• Trigger: Sales hiring +204% against a 16.7-job baseline (April 20, 2026)
• Expansion angle: The trigger is real and intense, but the function surging (Sales) is not the function our engineering-tooling sale serves. Cross-sell opportunity exists if our product line extends into RevOps or sales enablement; if not, the signal is interesting but not directly actionable.
• Recommended next step: If we have a relevant Sales-adjacent product, introduce. If not, monitor for an Engineering-side hiring surge as the expansion trigger we actually need.

Stable

Together AI — no expansion-relevant trigger in the 90-day window

• Current spend area: AI infrastructure deployment
• Status: No trigger fired in the last 90 days. Funding negotiation in progress (covered in the prospecting gallery) but no closed event yet. Continue normal cadence.

Real signal data drawn across all 5 customers. Zero new credits consumed — reuses the signal scans already run earlier in the gallery.