Weekly Signal Digest
Outcome: a single weekly digest covering product launches, new executives, job changes and promotions across your tracked accounts and contacts, for roughly 350 credits a week.
- Surface
- MCP server
- Level
- Advanced
- Uses
- company_product_launch · newly_hired_executives · check_job_change · check_promotions
- Credits
- ~350 per week
- Prerequisite
- A target account list and a tracked contact list
Four checks, two lists
| Check | Runs against | What it finds |
|---|---|---|
| company_product_launch | Target accounts | Launches — attention and budget moving |
| newly_hired_executives | Target accounts | New leaders with a mandate |
| check_job_change | Tracked contacts | Champions who moved |
| check_promotions | Tracked contacts | New authority at known accounts |
Two of them run against accounts, two against people. Keeping the lists separate is what keeps the cost predictable — you know exactly how many rows each check bills for.
The prompt
Using the SyncGTM MCP server, produce this week's signal digest.
Accounts (attached list of 150 domains):
1. company_product_launch — last 30 days.
2. newly_hired_executives — started in the last 90 days, in sales,
revenue operations or data functions only.
Contacts (attached list of 200 profile URLs):
3. check_job_change
4. check_promotions
Then produce a digest in this format:
LAUNCHES (n)
company — what launched — date
NEW EXECUTIVES (n)
company — name, title — started
CHAMPIONS WHO MOVED (n)
name — from company → to company — new title
PROMOTIONS (n)
name — company — old title → new title
Exclude:
- title normalizations that do not change authority
- company renames and acquisitions reported as job changes
- anything older than the windows above
Do not call any other tools.The exclusion block is what makes the digest trustworthy. Without it, a company rename shows up as four people changing jobs, and after the second week of false entries nobody reads it.
Route each signal type differently
| Signal | Goes to | Why |
|---|---|---|
| Champion moved to a new company | Whoever owns new business in that territory | Warm outbound, in-window |
| Champion moved to an existing customer | That account’s owner | An internal introduction, not outbound |
| Promotion at a known account | The account owner | Relationship exists |
| New executive at a target account | The account owner or new business, per your model | Cold but mandated |
| Product launch | Marketing and the account owner | Context, and sometimes a trigger |
Routing matters more than the digest. A signal delivered to a group channel where nobody owns it produces exactly nothing.
Make it readable
Five sections, counts in the headers, and nothing that requires opening another tool.
Signal digest — week of <date>
LAUNCHES (3)
acme.com — launched an analytics module — 4 days ago
...
NEW EXECUTIVES (2)
globex.com — Sam Rivera, VP Revenue Operations — started 3 weeks ago
...
CHAMPIONS WHO MOVED (4)
Priya Nair — Initech → Umbrella, now Head of RevOps
...
PROMOTIONS (2)
...
Nothing this week in: <empty sections listed, not omitted>List the empty sections explicitly. A digest that silently omits a section looks the same whether nothing happened or the check failed.
Cost and control
| Check | Rows | Cost each | Total |
|---|---|---|---|
| Product launch | 150 | ~0.5 | 75 |
| New executives | 150 | ~0.5 | 75 |
| Job change | 200 | ~1 | 200 |
| Promotions | 200 | shared with above | — |
| ~350 |
The contact checks dominate, and the only real lever is the size of the tracked list. Prune people who have left your buying centre entirely — see Job Changes lesson 07.
Do this now
Assemble the two lists
Target account domains, tracked contact profile URLs.
Run the four checks
Apply the exclusions
Renames, normalizations, out-of-window.
Format the digest
Five sections with counts, empty ones listed.
Route each signal type
To a named owner, not a channel.
Schedule it
Early in the week, before planning happens.
Add a zero alert
No changes at all across 200 people means something broke.
Check your work
- Account checks and contact checks run against separate lists
- Exclusions remove renames and title normalizations
- Empty sections are listed rather than omitted
- Every signal type routes to a named owner
- A zero-result alert exists
Where this breaks
A digest nobody owns gets read for two weeks and then ignored. Signals delivered to a general channel are everyone’s information and nobody’s job. Route each item to a named person with the action implied — “Priya moved to Umbrella, you own that territory” — and the digest becomes a work queue rather than a newsletter.
Further automation
Write the moves back to the CRM as well as into the digest. A champion_moved flag on the contact record means an account owner sees the context months later without anyone remembering the digest — and it supports the internal-introduction play when a champion lands at an existing customer.
Next lesson
07 — Audit and iterate, attributing the spend and adjusting the guardrails from evidence.
Reference for this lesson: company_product_launch, newly_hired_executives, check_job_change, Signals & ABM.