Build a weekly signal digest on your saved territory

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

A Claude prompt that takes a saved account territory and returns a weekly digest of fresh buying signals — funding rounds, leadership moves, product launches, hiring surges. One run on Monday morning surfaces which accounts moved during the week, which ones were quiet, and where the rep’s attention should go next.

The digest is short by design. Five lines per active account, none for quiet accounts. Built to be scanned with a coffee.

Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just save your territory once and run the prompt every Monday.

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>
Weekly signal digest on my saved territory.

My territory (save once, reuse weekly):
[PASTE ACCOUNT LIST: domains or company names]

Run this prompt every Monday morning to surface the week's signal activity.
</context>

<task>
1. For every account in my territory, retrieve activity in the last 7 days via Lusha's signals layer (or 30 days for a monthly digest):
   - Funding events (rounds, IPO, M&A, strategic investments)
   - Leadership events (executive hires, promotions, departures)
   - Hiring surges by department (Sales, Engineering, Marketing, Operations)
   - Product launches and partnerships
2. Sort accounts into three buckets:
   - ACTIVE: one or more signals fired in the window
   - QUIET: no signals in the window (carry to next week)
   - NO MATCH: Lusha could not resolve the domain or name (re-check the entry)
3. For each ACTIVE account, return a short block:
   - Account name
   - Signal type and date
   - One-line summary
   - Source article URL where available
   - Recommended action for the week (call, email, monitor, hold)
4. At the top, surface a one-line "this week's headline": the single highest-intensity signal across the full territory.
5. At the bottom, list the QUIET accounts as a single line for next-week carryover.
</task>

<constraints>
- Keep each active-account block to 4-5 lines max. The digest is meant to be scannable.
- QUIET is not failure. Surface the count so the rep knows the digest covered the full territory.
- Do not invent dates or events. Surface only what Lusha returns.
- A NO MATCH usually means a domain typo or a company that doesn't resolve to Lusha's catalog. Worth re-checking once before retiring the row.
</constraints>

What you'll get back

Input: Saved 5-account territory across enterprise SaaS: cloud data, observability, productivity, AI infrastructure, and cloud security. Window — last 30 days.

Output: 4 ACTIVE, 1 QUIET. Below is the real digest from running the prompt against the live Lusha connector.

This week’s headline

The productivity SaaS sales hiring surged +204% against a 16.7-job baseline — 51 new sales jobs posted in 4 weeks. Highest-intensity signal across the territory.

Active accounts

[Cloud data platform] — ACTIVE

  • Executive Hire (Apr 1, 2026): Mayank U. appointed Chief Security & Trust Officer — article
  • Product Launch (Apr 22, 2026): Apache Iceberg v3 — open data strategy advancement
  • Product Launch (Apr 21, 2026): Cortex Code Agent SDK for Python and TypeScript
  • Hiring Surge (Apr 27, 2026): Operations +60% (12 jobs vs 7.5 baseline)
  • Recommended action: Call this week. Brand new CSTO role + active product expansion in agentic AI = fresh executive sponsor and a public direction the rep can anchor outreach against.

[Productivity SaaS] — ACTIVE

  • Hiring Surge (Apr 20, 2026): Sales +204% (51 jobs vs 16.7 baseline) — the strongest single signal in the territory
  • Recommended action: Call this week. Tripling sales hiring rate at a company this size is a budget-unlocked, scope-being-defined moment. Reach RevOps and Sales leadership while the mandate is fresh.

[Cloud security SaaS] — ACTIVE

  • Product Launch (Apr 17, 2026): Cloud-based platform integrating video security, access control, and sensor systems — presented at Asia’s premier integrated security event
  • Recommended action: Email this week. The cloud security SaaS is expanding the platform story beyond pure video — useful angle for any rep selling adjacent infrastructure or analytics.

[Cloud observability] — ACTIVE

  • Product Launch (Apr 22, 2026): GPU Monitoring — now globally available — article
  • Recommended action: Monitor. One product signal in the window, no other activity — interesting but not urgent for outreach.

Quiet accounts

  • [AI infrastructure SaaS] — no signals fired in the 30-day window. Carry to next week.

10 credits consumed for the full territory scan. The digest above is intentionally short — the rep reads it in 60 seconds and has a clear plan for the week before the first meeting.

Why use Lusha

A monthly account review is too slow to catch fresh mandates. A daily scan is too noisy to act on. The weekly rhythm is where signal intelligence becomes usable. Three things shift when the digest runs on the same day every week against the same saved territory.

The territory is saved once. The Claude Project where the digest lives carries the account list in the conversation context. Monday after Monday, the rep runs the same prompt against the same accounts. No re-typing, no maintaining a separate target list. The territory is the input; the digest is the output.

Signal intensity is comparable week-over-week. When the rep runs the same prompt every Monday, the surge percentages, executive hire dates, and product launch counts become comparable across runs. Three weeks of quiet on one account is intelligence. A previously quiet account that suddenly fires three signals in one week is a sharp escalation signal. The weekly rhythm produces the time-series the rep needs.

QUIET accounts are useful intelligence. An account that stays quiet for 4-6 weeks is either a stable target with no urgent buying window or a dead lead worth retiring. The digest surfaces quiet accounts by name so the rep can decide. Quiet is not failure. It’s a signal in itself.

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 account list signal scan?

    The list scan is an on-demand prompt for a one-time review of any account list. The digest is the same scanning behavior wrapped in a weekly habit pattern — saved territory, consistent window, rhythm of comparison week over week. Use the list scan for ad-hoc reviews and ABM list-building. Use the digest for the Monday morning territory rhythm.

  • How do I save my territory so it persists?

    Set up a Claude Project, name it after your territory, paste your account list into the Project’s Custom Instructions or first message. Run the digest prompt as a new chat inside the Project every Monday. The Project keeps the account list in context across sessions.

  • What's the right cadence — weekly or monthly?

    Weekly catches mandates inside their first-30-day window — usually the period of highest buying intent. Monthly is fine for stable mid-market territories where new signals fire slowly. The prompt supports both windows. Reps with 50+ accounts typically run weekly. CSMs running expansion plays sometimes run monthly with deeper signal types enabled.

  • How many credits does the digest consume?

    Signal credits scale with the events returned, not the accounts scanned. A 5-account weekly digest in a calm market may consume under 10 credits. A 50-account weekly digest covering active enterprise accounts may consume 100+. The digest format is more credit-efficient than the deep single-account brief because the per-account result is capped at 4-5 lines.

  • What if an account is consistently quiet?

    After 4-6 weeks of QUIET, the rep has a decision to make. Either the account is in a stable pre-buying window (worth keeping in the territory for visibility), or it’s a dead row that should be replaced. Quiet for a quarter is usually a signal to swap the account out.

  • Can the digest combine with email drafting?

    Yes. With both Lusha and Gmail connected, the digest can flow into the Prospect-to-Outreach skill — the rep reviews the digest, picks the active accounts worth contacting, and the skill drafts a personalized message per account using the surfaced signal as the opener.

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