Skip to content
Back to skills

Account Tiering

ASecurity

Use when defining ABM tiers, scoring logic, and coverage rules.

  • 396 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
businessgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add gtmagents/gtm-agents --skill account-tiering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Account Tiering?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Account Tiering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gtmagents-account-tiering/badge)](https://www.skillsdirectory.com/skills/gtmagents-account-tiering)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: account-tiering
description: Use when defining ABM tiers, scoring logic, and coverage rules.
---

# 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.

---

Files in this skill

  • SKILL.md1.3 KB
  • assets/tiering_matrix.md1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…