smithery.ai

account-tiering

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

First seen Mar 31, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,298 B
  • docs SUMMARY.md 86 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.