mcpField
A
account-tiering

account-tiering

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

About account-tiering

account-tiering is a marketing skill for defining and reviewing account tiers in ABM programs. It combines firmographic fit, propensity signals, strategic value, team capacity, and tier-specific service expectations.

Key features

  1. 01Assess firmographic fit
  2. 02Use intent and engagement signals
  3. 03Evaluate strategic value
  4. 04Match tiers to team capacity
  5. 05Define tier-specific SLAs

Use cases

  1. 01Set T1/T2/T3 tiers for an ABM program
  2. 02Review tiers against revenue priorities
  3. 03Align sales, marketing, and partner coverage

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill account-tiering

After installing, type/account-tieringin Claude Code to confirm it loaded.

Bundled filesassets/tiering_matrix.md

Details

From the project README

Account Tiering Systems Skill

When to Use

  • Establishing T1/T2/T3 definitions for new ABM programs.
  • Auditing existing tiers to ensure they reflect current revenue priorities.
  • Aligning sales, marketing, and partner teams on coverage and SLA expectations.

Framework

  1. Firmographic Fit – revenue, employee count, industry, region.
  2. Propensity Signals – intent, product usage, previous engagement, open opportunities.
  3. Strategic Value – partnership potential, brand influence, expansion runway.
  4. Capacity Planning – match tiers to owner bandwidth (SDR, AE, marketing pods).
  5. SLA Definitions – touch frequency, personalization level, reporting cadence by tier.

Templates

  • Tiering Matrix: See assets/tiering_matrix.md for criteria and scoring logic.
  • Coverage planner (tier → owner type → touch expectations).
  • Governance checklist (review cadence, data sources, exception handling).

Tips

  • Recalculate tiers quarterly or when GTM strategy shifts.
  • Keep a single truth source (sheet or CDP) to avoid conflicting tiers.
  • Document exceptions (e.g., strategic design partners) so automation logic stays clean.

Comments

Markdown supported