---
id: sales-weapon-trigger-watch
title: Trigger watch (weekly)
enabled: true
owner: goal:sales-weapon-ae-copilot
mode: task
schedule:
  kind: weekly
  timezone: America/New_York
  time: 07:18:00
  dow: [Wed]
delivery:
  - chat_id: ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b
metadata:
  tags: [cron:flexible-time]
  originating_chat_context_json: '{"chat_id":"ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b","origin_provider":"main","chat_kind":"direct","event_kind":"message","require_mention":false,"device_id":"11d6f508-35e2-48ec-9e92-39b4972d1a29"}'
  presentation_locale: en-US
---
Weekly trigger watch for Sean's named accounts (delivered in the Work side chat).

The strategic account list lives at ~/workspace/goals/sales-weapon-ae-copilot/hidden_files/strategic-accounts.txt — 200 accounts, format "Account | Vertical | Relationship | Priority | City/ZIP". The full workbook (with contacts, talk tracks, call cards) is at ~/workspace/goals/sales-weapon-ae-copilot/hidden_files/call-workbook-2026-09-30.xlsx.

Rotation: 200 accounts is too many for one run. Cover them on a 4-week rotation (~50/week). Track rotation state in ~/workspace/goals/sales-weapon-ae-copilot/hidden_files/trigger-watch-state.txt: the index of the next account to cover and a log of triggers already reported (company + trigger + date) so nothing repeats. Each week: prioritize accounts not yet covered in the current rotation, but always include any High-priority or Previous-customer accounts with fresh news even if already covered. Advance the rotation index each run; when it passes the end, reset to 0.

For each account in this week's batch, search the web (browser.search, news vertical where useful) for genuinely new, material developments from the last ~30 days:
- Funding rounds, M&A, ownership changes
- Leadership changes (new CEO/COO/CFO/CIO, facilities or operations heads)
- Data breaches, ransomware, or other cybersecurity incidents
- Expansions, new locations, major hires, new construction

Report ONLY real triggers with a verifiable source. For each trigger post, in plain words:
- Company + what happened + when (with the source)
- Why it matters for Stratix: the managed IT, cybersecurity, or print-fleet angle
- A 2–3 sentence talk track / opening line Sean can use on a call or in an email

If no material triggers surface for the batch, stay silent (post nothing). Never invent news. Never name search queries, tools, or file paths in the report.

After the run, update the state file (rotation index + reported triggers) and append a one-line outcome note to ~/memory/YYYY-MM-DD.md (date in ET): accounts covered, triggers found.