mcpField
T
territory-optimization

territory-optimization

github.com/gtmagentsMarketing & growth42864 installsUpdated 30w ago
Repository

About territory-optimization

territory-optimization is a skill for designing and evaluating sales territory plans, intended for RevOps, Enablement, and teams responsible for territory planning. It combines coverage constraints, fairness measures, and operational checks in a structured process for comparing options and preparing leadership readouts.

Key features

  1. 01Prepare account TAM, ARR, and travel constraints
  2. 02Model and score territory scenarios
  3. 03Calculate Gini, whitespace, and attainment probability
  4. 04Validate CRM ownership, routing, and ROE
  5. 05Summarize recommendations, rationale, and risks
  6. 06Provide scoring matrix and change checklist

Use cases

  1. 01Design new coverage models or rebalance routes
  2. 02Assess fairness during territory carve-up reviews
  3. 03Prepare leadership readouts on territory effectiveness

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill territory-optimization

After installing, type/territory-optimizationin Claude Code to confirm it loaded.

Details

From the project README

Territory Optimization Skill

When to Use

  • Designing new coverage models or rebalancing routes.
  • Evaluating fairness metrics during carve-up reviews.
  • Preparing leadership readouts on territory effectiveness.

Framework

  1. Input Prep – normalize account TAM, ARR, propensity, and travel constraints.
  2. Scenario Modeling – generate multiple carve-ups (geo, industry, hybrid) with scoring weights.
  3. Fairness Scoring – calculate Gini, whitespace %, and attainment probability per rep.
  4. Operational Check – validate CRM ownership, routing rules, and ROE impact.
  5. Recommendation – surface top options with rationale and risks.

Templates

  • Territory scoring matrix (scenario vs KPIs).
  • Leadership readout deck outline.
  • Change management checklist for RevOps + Enablement.

Tips

  • Keep scoring weights transparent to avoid stakeholder confusion.
  • Include travel/coverage constraints early to prevent downstream rework.
  • Pair with roe-governance to confirm routing + escalation rules.

Comments

Markdown supported