Build a weekly GTM digest for the whole team
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, Calendar, and Slack connector output, but were not pulled from a live session. Run the prompt with your own accounts and pipeline to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A weekly GTM digest that combines signals, pipeline movement, data quality alerts, and meeting prep in a single Monday-morning Slack post means the whole team starts the week informed rather than asking four separate questions to four separate tools. This Claude prompt scans Lusha for new account signals, Gmail for thread movement and open commitments, Google Calendar for meetings that need prep, and posts the full digest to Slack with one specific action item before anyone opens their inbox.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
Every Monday morning I want one brief — not three separate reports — that gives the full GTM picture: what signals fired this week, where pipeline moved, what data quality issues need fixing, and which meetings need prep. One read, everything I need to start the week.
My GTM digest setup:
- My accounts and pipeline: [PASTE COMPANY NAMES, DEAL STAGE, ACV — or "use all active accounts and pipeline"]
- Function I sell into: [e.g. "Sales, RevOps"]
- Slack channel to post to: [CHANNEL NAME]
- Timeframe: last 7 days
</context>
<task>
1. SIGNALS — Use Lusha to scan all accounts for new buying signals in the last 7 days:
- New exec hire in the target function
- Funding event
- Headcount surge 15%+
- M&A activity
- List only accounts with a NEW signal this week — skip accounts with no change
2. PIPELINE MOVEMENT — Search Gmail for thread activity across active deals:
- Any inbound replies received this week?
- Any open commitments from reps that are now overdue?
- Any deal threads that have gone silent for 7+ days?
- Any new contacts added to deal threads?
3. DATA QUALITY — Use Lusha to run a contact freshness check:
- Any primary deal contacts who have departed?
- Any contacts promoted or with a title change?
- Limit to contacts on active deals only
4. MEETINGS THIS WEEK — Check Google Calendar for upcoming external meetings:
- Any external meetings in the next 5 days?
- For each: company, attendees, last discussed (Gmail), one prep note
5. Build and post the weekly GTM digest to the specified Slack channel:
## GTM digest — week of [Date]
### Signals this week
[Account · signal · date · recommended action]
— or "No new signals this week"
### Pipeline pulse
[Deal · what happened · action needed]
— or "No notable thread movement"
### Data quality flags
[Contact · company · what changed · CRM action]
— or "All contacts current"
### Meetings this week
[Date · Company · attendees · prep note]
### One thing to act on today
The single most time-sensitive item from the full digest
6. Tag the relevant rep or manager per alert where possible.
</task>
<constraints>
- Each section scannable in under 60 seconds.
- "One thing to act on today" must be specific: a named deal, contact, or account.
- Signal section: only NEW signals this week — don't repeat prior weeks.
- If a section has nothing to report: state it clearly.
- Post to Slack only — don't return a long report to the chat.
</constraints>What you'll get back
The situation: A sales manager sets up the weekly digest for a team of 3 reps. Runs automatically every Monday at 8am. Here’s the digest for the week of June 2.
Slack post — #gtm-weekly
GTM digest — week of June 2, 2026
Signals this week
Dunmore Analytics · Series B closed May 30 · @sarah.ae Signal fired 3 days ago. Post-funding window is open — reach out this week before it closes. → Sarah: reply to T.K.’s pricing thread today
Crestline Software · New CRO joined June 1 · @james.ae New CRO is 2 days in. First 30 days = stack evaluation window. → James: reach out this week before the new CRO gets inbound from competitors
Pipeline pulse
Ashford Platforms · Negotiation · $95K · @sarah.ae ⚠ ZoomInfo comparison section promised May 14 — still not sent (overdue 19 days) → Send today. D.R. has asked for it twice.
Vantage Enablement · Proposal · $58K · @marcus.ae ⚠ No inbound in 14 days · Primary contact departed per Lusha (see data quality below) → Marcus: deal is stalled — find replacement contact before next touch
Briarway SaaS · Discovery · $50K · @sarah.ae ✓ P.O. replied June 1 — first inbound in this thread → Sarah: reply today while the thread is warm
Data quality flags
⚠ B.N., Sr Director RevOps, Vantage Enablement — departed per Lusha Active deal: Vantage Enablement, $58K, Negotiation Replacement found: J.A., VP Revenue Operations · j.a@[vantage].com ✓ → @marcus.ae: update CRM, reassign J.A. as primary contact
ℹ P.M., Meridian Analytics — promoted VP Sales → SVP Sales → Update CRM title field before next campaign send ({{title}} token)
Meetings this week
Thursday June 5, 2pm · Ashford Platforms · D.R. + M.L. Last discussed: Proposal review — HubSpot integration and pricing tiers Prep note: ZoomInfo section must be in updated proposal before this call. D.R. expects it.
Friday June 6, 10am · Dunmore Analytics · T.K. Last discussed: Pricing inquiry — March thread, went cold Prep note: Series B just closed. Open with the funding angle, not the product.
One thing to act on today
🔴 Send Sarah’s overdue ZoomInfo comparison to D.R. at Ashford — promised May 14, asked for twice, proposal review call is Thursday. Every day this stays unsent risks the deal.
@sarah.ae @james.ae @marcus.ae
Illustrative example — fictional company names used. Run with your own accounts and pipeline to see live results.
Why use Lusha in Claude
Four connectors, one Slack post, read in under 3 minutes. The alternative is four separate plays run separately: signal digest, pipeline review, CRM change log, meeting brief. The weekly GTM digest combines all four and posts in one place — which means the team actually reads it instead of opening four different reports. The “one thing to act on today” section is the most important: it forces a single priority out of 15 data points. Everything else in the digest can be addressed later this week. The ZoomInfo section at Ashford cannot — the proposal review is Thursday and the commitment is 19 days overdue.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How is this different from the weekly pipeline review or the weekly signal digest?
The weekly pipeline review focuses on pipeline risk in detail. The weekly signal digest surfaces only signal activity. This play aggregates both — plus data quality and meetings — into a single Slack post for the whole team. Use the individual plays when a specific area needs depth; use this digest when the goal is one Monday-morning read.
Can this be automated to run every Monday automatically?
Run the prompt manually each Monday for best results — the account and pipeline context changes week to week and benefits from a fresh paste. For fully automated weekly runs, the Lusha + Zapier or n8n automation plays on the Campus handle scheduled execution.
What if the digest is too long to scan in 3 minutes?
Each section is capped at the most time-sensitive items only — not a comprehensive log. If a section produces more than 3–4 items, the prompt prioritizes by urgency: departed contacts on active deals first, overdue rep commitments second, signals third. Everything else is excluded unless the rep or manager needs the full detail play.
Who should run this — managers or reps?
Managers running it for a team of 3–5 reps get the full GTM picture before the weekly team call. Reps running it for personal accounts get a personal Monday brief. Both use cases are valid — the inputs adjust the scope.
Ready to build this?
Get started with Lusha and set up this play in minutes.
