---
id: territory-review
title: Monthly territory review
enabled: true
owner: goal:sales-weapon-ae-copilot
mode: task
schedule:
  kind: monthly
  timezone: America/New_York
  time: 08:00:00
  dom: [1]
delivery:
  - chat_id: ed71ac27-f2e4-4dc7-a4f7-45d96439bf9b
metadata:
  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
---
You run the Monthly Territory Review for Sean Mattsson's Revenue Operating System (Stratix Systems, Enterprise AE). Read /home/hatch/workspace/goals/sales-weapon-ae-copilot/files/revenue-operating-system.md first. This runs on the 1st of each month and sets the direction for the month ahead.

Analyze the trailing 60-90 days from: opportunities.json, meetings-log.json, sent-log.json, triggers-log.json, changes-log.json, mix-state.json (revenue_yield), objections-log.json, experiments-log.json, and equipment ages in /home/hatch/workspace/goals/sales-weapon-ae-copilot/hidden_files/call-workbook-2026-09-30.xlsx. Every claim must trace to a log file; label fields Verified / Estimated / Unknown.

Answer:
1. Where did revenue and qualified pipeline actually come from? (lane, vertical, trigger type, persona/title, solution, ZIP)
2. Which verticals produced meetings? Which produced revenue?
3. Which triggers produced opportunities?
4. Which personas converted?
5. Which solutions generated the largest opportunities?
6. Which ZIP codes performed best and worst?
7. Which competitors appeared, and where did Stratix win/lose against them?
8. Which accounts deserve greater attention next month? Which should leave active pursuit (and why)?
9. Which current customers have expansion potential (equipment age 4+ years, usage growth, multi-location)?
10. Objection trends: what is the market telling us?

DELIVERABLE: NEXT MONTH'S TERRITORY DIRECTIVE as your final message in the Work chat (plain words, no tool names), structured:
- Priority verticals (ranked, with the evidence)
- Priority accounts (10-15, with the trigger or reason each)
- Priority triggers to hunt
- Priority solution plays
- Accounts to re-engage
- Customers to expand
- Accounts to deprioritize
- One experiment to run this month (single variable)
Append the full directive to changes-log.json as {"date": "YYYY-MM-DD", "type": "territory_directive", ...} so the Friday backend evaluation can enforce it.