enterprise-account-planning

enterprise-account-planning is a skill for Claude Code from beingsmit/technical-product-gtm. It costs 54 tokens per session (3,566 once invoked), scanned A, a copy of gtm-enterprise-account-planning, MIT.

A planning guide for complex enterprise sales deals, where several people and departments may influence the purchase. It includes MEDDICC, a sales-qualification framework, and mutual action plans, shared lists of steps and dates for buyer and seller.

In plain words
What is it for?
Use it to plan strategic accounts, qualify enterprise opportunities, manage complex buying processes, build mutual action plans, and spot deals that are losing momentum.
Why use it?
It helps reveal whether a long sales process is genuinely moving instead of relying on encouraging conversations or pipeline labels. It also provides a way to track stakeholders, actions, dates, and deal health.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the technical-product-gtm plugin — 11 skills shipped together

Good fit Use it to plan strategic accounts, qualify enterprise opportunities, manage complex buying processes, build mutual action plans, and spot deals that are losing momentum.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/beingsmit/technical-product-gtm/enterprise-account-planning
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add beingsmit/technical-product-gtm --skill enterprise-account-planning
Clone the repo
git clone --depth 1 https://github.com/beingsmit/technical-product-gtm

Made for: Claude Code.

Or install technical-product-gtm, the plugin that ships this one along with the rest of its 11 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for enterprise-account-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/enterprise-account-planning/github.svg)](https://agentmods.dev/skills/beingsmit/technical-product-gtm/enterprise-account-planning)
Your own site
<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/enterprise-account-planning"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/enterprise-account-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for enterprise-account-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/enterprise-account-planning"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/enterprise-account-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.03566
Opus 5 $0.00027 $0.01783
Sonnet 5 $0.00011 $0.00713
Haiku 4.5 $0.00005 $0.00357

Measured 12d ago against content hash 3bf1275234c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

enterprise-account-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to gtm-enterprise-account-planning — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/enterprise-account-planning/SKILL.md · 431 lines

How it starts

The opening of the file, as written. The whole thing — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Enterprise Account Planning

Strategic account planning and execution for enterprise deals. Turn complex sales cycles into systematic wins — or at least know when they're dying before you waste months.

When to Use

Triggers:

  • "How do I plan this enterprise deal?"
  • "This deal has been in motion 3 months, why isn't it closing?"
  • "Should I create a full account plan or simplified version?"
  • "How do I know if this deal is actually moving?"
  • "MEDDICC qualification"
  • "Building a mutual action plan"

Context:

  • Strategic deals above your average ACV
  • Multiple stakeholders involved
  • Sales cycle exceeds 60 days
  • Complex buying process (legal, procurement, security)
  • Enterprise or mid-market accounts

Core Frameworks

1. If Your MAP Hasn't Been Updated in 3 Weeks, That Deal Is Dead

The Pattern I've Seen:

The Mutual Action Plan (MAP) is the single best indicator of deal health. Not pipeline stage. Not verbal commitments. Not "they love the product."

The MAP tells you everything:

Healthy deal:

  • MAP updated weekly
  • Customer adding their own action items
  • Both sides completing tasks on schedule
  • New stakeholders appearing in MAP
  • Dates moving up (not pushed out)

Dying deal:

  • MAP last updated 3+ weeks ago
  • Only your side has action items
  • Customer tasks marked "pending" for weeks
  • No new stakeholders engaged
  • All dates in the past

Why This Happens:

When a deal is real, the customer wants it to happen. They're doing work. They're involving stakeholders. They're moving through their process.

When a deal is dying, you're doing all the work. They're "too busy." They'll "get back to you next week." The economic buyer is "traveling."

The 3-Week Rule:

If your MAP hasn't been updated in 3 weeks, the deal is dead — you just don't know it yet. I've never seen a deal close with a stale MAP. Not once in 11 years.

What to Do:

Week 1 of silence: Send MAP update: "Here's what we've completed. What's your status on [specific customer action]?"

Read the full file on GitHub · 431 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 431 lines · 54 tokens per session scan A 3bf1275234c9

Subscribe to this mod's changes

enterprise-account-planning is a skill published in the GitHub repository beingsmit/technical-product-gtm (42 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 3,566 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gtm-enterprise-account-planning, differing in 5 lines, and is treated as a copy.

Related

Other skills, from other repositories

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens