本文へ移動
cccskills
無料GitHub で公開

sales-compensation-and-territory

Designs quotas, territories and commission plans that produce the behavior the business needs — sizing territories against real potential, setting quotas people can hit often enough to believe in, choosing what to pay on, handling accelerators, draws, clawbacks and disputes, and changing a plan without destroying trust. Use this to build or fix a comp plan, allocate territories, work out why reps are chasing the wrong deals, or plan a mid-year change.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.2 KB
  • references/sources.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Sales compensation and territory

A compensation plan is the clearest statement a company makes about what it actually wants. Reps will optimize it precisely, including in the ways you did not intend, and that is not a character flaw — it is the plan working.

Size territories on potential, not on the current book

A territory built from existing accounts rewards whoever inherited the good one and guarantees the argument that follows. Build from addressable potential — accounts that fit, weighted by how many of them could plausibly buy — then check that each territory can support the quota you intend to put on it.

A quota a territory mathematically cannot carry is not a stretch goal, it is a resignation on a delay. Do that arithmetic before assigning, and expect to find one or two territories that fail it.

Rebalance on a known cadence, so it is a process rather than a punishment, and account for in-flight pipeline when accounts move.

Set quotas people hit often enough to believe

If most of the team misses, the plan has stopped motivating and started demoralizing; the number is noise and everyone knows it. If nearly everyone clears easily, you are paying above market for average performance.

A distribution where a solid majority reach target, with real upside above it, keeps the plan credible. Build the aggregate from the territories rather than dividing the company number by headcount — the second is how you end up with quotas nobody accepted.

Account for ramp explicitly for new hires rather than pretending a first quarter is a normal one.

Pay on the outcome you actually want, and keep it simple

  • What you pay on should be the thing you want more of. Paying purely on new bookings gets you new bookings, including bad ones that churn.
  • Consider what protects quality: margin or discount-adjusted credit, a clawback window on early churn, or paying on collected revenue rather than signed.
  • Three components is usually the limit. A plan a rep cannot compute in their head does not change behavior, because they cannot see which action pays. Complexity in a comp plan is a design failure, not sophistication.

Accelerators above target are worth the money — that is where discretionary effort lives. Decelerators below target usually just accelerate the departure of someone already struggling.

Draws, caps and clawbacks

A recoverable draw supports ramp but creates debt; make the recovery schedule explicit or it becomes a surprise. Caps on upside are almost always a mistake — you are punishing the outcome you paid to create, and the rep will simply move the deal into the next period, which is worse for forecasting than the extra commission.

Clawbacks for early churn or non-payment are defensible when the window is short and stated in advance. Applied retroactively they cost more trust than they recover in money.

Write down how disputes get settled

Split credit, who owns an account that moved territories, what happens when a deal slips across a period boundary, how a commission on a modified contract is computed. Decide these before they occur and publish them — every one of these arguments is worse when the answer is invented under pressure by someone with an interest in the outcome.

Change plans with notice, and honor what was already earned

Mid-period changes are occasionally necessary and always expensive in trust. Give notice, explain the reason, and never restate a commission already earned under the prior plan. A team that believes the plan can be changed retroactively stops treating it as an incentive.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Commission calculation: CaptivateIQ, Spiff, Everstage, Xactly, and similar. The threshold for buying is not headcount, it is the point at which a spreadsheet error would go unnoticed — which arrives earlier than most teams expect.

Territory and quota planning: Fullcast, Salesforce Maps, Varicent, and similar; a well-built model covers a single-segment team.

Whatever calculates it, reps need a statement they can check themselves. Disputes are expensive in trust long before they are expensive in money.

Never

  • Assign a quota to a territory that cannot mathematically support it.
  • Add a component to a plan that a rep cannot compute without a spreadsheet.
  • Cap upside on the performance you designed the plan to produce.
  • Change terms retroactively for a period already worked.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する