Get a single-account signal brief before the call

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

A Claude prompt that pulls a structured pre-call brief on one target account — every recent signal in the last six months, organized by category. Leadership changes, M&A, strategic investments, product launches, hiring surges by function, geographic expansion, headcount growth, and web traffic shifts.

The kind of brief that takes a rep three hours to assemble manually. Built into one prompt.

Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just name the account and 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

Open in Claude Open in ChatGPT 
<context>
Discovery call or strategic review on [ACCOUNT NAME / DOMAIN] in the next [TIMEFRAME, e.g. 24 hours].
Pre-call brief: every recent signal in the last 6 months, organized to scan in 60 seconds.
</context>

<task>
1. For the target account, pull every signal type from the last 6 months via Lusha's signals layer.
   Organize into five categories:
   - Leadership: executive hires, executive promotions, executive departures
   - Strategic moves: M&A, IPO, funding rounds, strategic investments
   - Product activity: launches, integrations, new features
   - Hiring intensity: surges by department and by location, headcount growth (1m / 3m / 6m / 12m)
   - Market signals: web traffic shifts, partnerships, new customers, recognition events
2. For each signal, return:
   Event type | Event date or signal date | Headline (one-line summary) | Source article URL where available.
3. At the top of the brief, surface a 3-line "headline" summary:
   - Most important leadership move
   - Biggest strategic shift
   - Strongest active hiring signal
4. After the categorized brief, suggest 3-5 talk tracks for the call, each tied to a specific surfaced signal.
</task>

<constraints>
- Pull every available signal type, not just funding and hiring. Pre-call briefs need leadership, product, and market context too.
- Surface the source article URL on every signal that has one. Useful for outreach and discovery prep.
- Do not invent any event, date, or name. Surface only what Lusha returns.
- If no signals fired in the window, surface that honestly. A quiet account is intelligence too.
</constraints>

What you'll get back

Input: Single target account — [a cloud data platform]. Window — last 6 months. All signal types enabled.

Output: A complete pre-call brief covering leadership churn at the top, three M&A deals, two strategic investments, six product launches, multi-function hiring surges, geographic expansion, headcount growth, and web traffic shifts. Below is the real result from running the prompt against the live Lusha connector.

Headline summary

  • Leadership: New Chief Revenue Officer (Jonathan B., internal hire, March 31, 2026) and new Chief Security & Trust Officer (Mayank U., April 1, 2026)
  • Strategic shift: Three acquisitions in six months — an agentic AI data engineering startup (Feb 2026), a data catalog startup (Nov 2025), an AI observability startup (Jan 2026)
  • Hiring intensity: Sales +29% surge against baseline of 116, Operations +60%, Marketing +57%, Engineering surge in select pockets — overall headcount up roughly 9% year-over-year

Leadership (last 6 months)

EventDateDetail
Executive HireApr 1, 2026Mayank U. appointed Chief Security & Trust Officer
Executive HireMar 31, 2026Jonathan B. (internal veteran) appointed Chief Revenue Officer
Executive DepartureMar 31, 2026Mike G. (prior CRO) left for personal reasons
Executive HireFeb 2, 2026Dayne T. appointed SVP for EMEA
Executive DepartureMar 25, 2026Caroline V. moved to a security vendor
Executive DepartureMar 31, 2026Bryan A. moved to a competing data platform as CRO

Strategic moves (last 6 months)

EventDateDetail
M&AFeb 4, 2026Acquired an agentic AI data engineering startup
M&AJan 30, 2026Closed acquisition of an AI observability startup
M&ANov 24, 2025Announced acquisition of a data catalog startup for AI
Strategic InvestmentDec 11, 2025Venture arm invested in a decision intelligence startup
Strategic InvestmentDec 9, 2025Venture arm invested in an agentic data trust startup

Product activity (last 6 months)

  • Apache Iceberg v3 launched (Apr 22, 2026) — open data strategy advancement
  • Cortex Code Agent SDK launched (Apr 21, 2026) — Python and TypeScript for enterprise app integration
  • Snowflake Intelligence + Cortex Code updates (Apr 21, 2026) — agentic enterprise control plane
  • Agent GPA framework launched (Apr 5, 2026) — open-sourced in TruLens library
  • Trust Center detection findings (Mar 4, 2026) — security signals for customer accounts
  • Cortex Code CLI extensions to dbt and Airflow (Feb 24, 2026)

Hiring intensity (last 6 months)

FunctionSignal dateJobs / 4 weeksBaselineSurge
OperationsApr 27, 2026127.5+60%
MarketingMar 23, 20261811.5+57%
EngineeringApr 27, 202610(low absolute)
SalesMar 30, 2026151116.8+29%

Headcount up roughly 9% year-over-year (10,281 → 11,103 employees).

Geographic hiring spikes flagged in: South Carolina (+233%), Virginia (+100%), New York (+99%), Norway (+78%), Georgia (+56%).

Market signals (last 6 months)

  • Web traffic +279% spike on Feb 12, 2026 (8,420 → 31,924 monthly visits)
  • Web traffic +33% spike on Apr 11, 2026

Suggested talk tracks

  1. Open with the new CRO mandate. Jonathan B. is six weeks into a global revenue role at an 11,000-person public company. Internal hire, so he knows the stack. Ask what the first quarter of his mandate is changing.
  2. The agentic AI investments tell the story. The agentic AI startup acquisition plus the code agent SDK plus the agent evaluation framework — all in the same window. The company is publicly committing to agentic infrastructure. Lead with how your product supports that direction.
  3. Security and trust is a new C-suite priority. The CSTO role is brand new for this account. Anyone selling into security, governance, or observability has a fresh executive sponsor to find.
  4. Operations team is surging hard. +60% surge with a baseline of only 7.5. Small absolute number, but the team is doubling. Worth asking what the operational mandate is.
  5. EMEA expansion is on the agenda. Dayne T. joined as SVP EMEA in early February. Combined with a +7% hiring surge in Germany, the region is being scaled. Useful angle for any rep working European territories.

77 credits consumed for the full multi-signal brief on one account. The brief above is dense, but every row is the kind of intel that historically takes a rep three hours of LinkedIn scrolling and news search to assemble.

Why use Lusha

A discovery call without a signal brief is asking the prospect to tell the rep what changed. A discovery call with a signal brief is asking the prospect what they’re going to do about what changed. Three things shift when the brief lands inside Claude in one prompt.

The categorization mirrors how a rep actually reads the account. Leadership churn changes who decides. Strategic moves change what they’re building toward. Product activity changes what they’re competing with. Hiring intensity shows where the spend is going. Market signals confirm whether the public narrative matches the internal one. The five-category structure isn’t decorative — it’s the order an experienced rep already evaluates an account.

Every signal carries a date. Time-stamped intelligence is what separates a fresh brief from a stale one. A CRO appointment six weeks ago opens different conversations than a CRO appointment six quarters ago. The prompt surfaces dates so the rep reads recency in context and pairs the signal with the right tenure framing.

Source article URLs accompany the news events. The rep can verify the context before the call, quote the actual headline in outreach, and reference the specific article the prospect’s leadership will have seen. The signal isn’t third-hand summary — it’s the article the company itself published or that covered the company directly.

Data drawn from Lusha’s signals layer, built on 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How is this different from the target-account-list signal scan?

    The list scan answers “which of my accounts are heating up this week?” It surfaces one or two top-line signals per account so the rep can prioritize. This prompt goes deep on one account. The output is structured for the 60 seconds before a discovery call or strategic review, not for portfolio prioritization.

  • How many signals does Lusha return per account?

    The signals layer pulls from a broad set of event types — executive moves, M&A, IPO, funding, product launches, hiring surges by department and by location, headcount changes at multiple intervals, web traffic shifts, partnerships, and several news categories. The default window is the last 6 months. For very active accounts (large public companies), expect 50-100+ discrete signal events in that window.

  • Why are there hiring surges flagged at very low absolute numbers?

    A surge is measured against the company’s own historical baseline. A function that historically hires zero people in a quarter and now hires one is technically a +100% surge. The prompt surfaces both the absolute number and the baseline so the rep reads the signal in context. Low-absolute surges in small teams sometimes matter (new function spinning up), sometimes don’t.

  • Does the prompt include public-company filings or SEC disclosures?

    The prompt surfaces news events that Lusha’s signals layer indexes, which includes coverage of public-company events when reported in business press. For deep SEC filings (10-K, 10-Q, proxy statements), reps should still reference EDGAR directly. The brief covers the news of the event, not the underlying filing.

  • How many credits does the brief consume?

    A complete multi-signal brief on a large active account can consume 50-100 Lusha credits depending on signal volume. Smaller accounts in quieter windows consume fewer. The prompt confirms before running when the credit cost is meaningful. For weekly account scanning at scale, the list-scan prompt is more credit-efficient.

  • Can I narrow the signal types to save credits?

    Yes. The prompt accepts an explicit signal list. Reps preparing for a security-focused discovery may want only leadership and product activity. Reps preparing for an ABM campaign may want only hiring surges and headcount. Specify the categories in the request and the prompt narrows the call accordingly.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Get free access Read the Docs