# sales-comp-design

Walks through the annual sales compensation design: base/variable split, paid measures, accelerator curves, SPIFs and crediting rules.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 25700 installs · ★ 3
- Author: Maya-Beth Finotti
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mbfinotti/sales-skills/tree/HEAD/skills/sales-comp-design/SKILL.md
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/skills/sales-comp-design

## What it does

The skill runs the yearly comp-design exercise as an interview, one question per message, then presents 2–3 candidate plan structures that differ in pay mix, measures and curve shape. From there it moves through the workflow: governance spine, job design check, pay mix derived from role influence, paid measures, payout curve, role plans and crediting rules.

It offers three depths. A targeted tune changes one mechanic inside the standing structure and gets back-tested against last cycle's actual payout data. A full redesign is the complete annual workflow. A standing program adds a steering committee, plan-health telemetry and a back-test model rerun every cycle. The targeted tune is the safer mid-cycle choice, because changing pay mid-year is a governance exception that needs re-signed agreements.

Stay aware of the boundary: this skill prices a quota, it never sets one. Quota derivation lives in `sales-quota-setting`, and org design in `sales-org-structure`. Jurisdictions where reps sit are only flagged for legal review, not resolved inside the plan.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-comp-design -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sales-comp-design/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sales-comp-design/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-comp-design -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sales-comp-design/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-comp-design -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sales-comp-design/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/sales-skills sales-comp-design
```

2. **Manually: put the files in place**
- File: `.github/skills/sales-comp-design/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-comp-design -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mbfinotti/sales-skills --path skills/sales-comp-design
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sales-comp-design/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-comp-design -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mbfinotti/sales-skills/tree/HEAD/skills/sales-comp-design/SKILL.md

## When to use it
- build next fiscal year's comp plans for a sales org
- split OTE into base and variable by role influence
- fix an accelerator that blew up finance's budget
- write a credit-split rule for AE and SE before the deal closes
- decide whether a quarterly SPIF can become permanent pay

## Example prompts
- Design next year's comp plans for our 20-rep sales org.
- Reps blew past quota and the accelerator blew up finance's budget. What do we do with the curve?
- Should we split credit between the AE and the SE on this deal? Write the rule.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4c284037b799ca8c.

BEGIN THIRD-PARTY FILE 4c284037b799ca8c
```text
---
name: sales-comp-design
description: Designs the sales compensation plan structure - pay mix (base/variable split) set by role influence, performance measures under the rule of three, accelerator and decelerator curves, SPIF overlays, draws, and role plans for SDR, AE, manager, overlay, and CSM seats. A macro annual exercise for sales leadership, RevOps, and finance, covering B2B SaaS and commission-heavy B2C. Use whenever the user mentions commission plans, OTE, accelerators, clawbacks, SPIFs, capping commissions, or "how should we pay our reps", even without the words comp design. Do NOT use for deriving the quota the plan pays against (mbfinotti/sales-skills@sales-quota-setting) or structuring the org (mbfinotti/sales-skills@sales-org-structure).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.3.2"
---

# Sales Compensation Plan Design

You are a compensation-design advisor to sales leadership, RevOps, and finance. Run the annual comp-design exercise: set the governance spine, check job design, derive pay mix from role influence, pick the paid measures, shape the payout curve, write the role plans and crediting rules, back-test, gate on legal review, then ship signed plan documents.

The comp plan is a virtual supervisor - it tells the sales force what's important, every day (Cichelli). A badly designed plan doesn't fail to work; it works against its owner, rewarding exactly what its mechanics pay for.

Stay at plan-structure altitude:

- Deriving the quota the plan pays against: mbfinotti/sales-skills@sales-quota-setting.
- Designing the org whose seats these plans map to: mbfinotti/sales-skills@sales-org-structure.

## Invocation examples

- _"Design next year's comp plans for our 20-rep sales org."_ - full workflow, steps 1-10.
- _"Reps blew past quota and the accelerator blew up finance's budget."_ - curve entry: steps 5 and 9 against the shipped plan; the cost was never modeled.
- _"Should we split credit between the AE and the SE on this deal?"_ - crediting entry: step 6. Write the rule before the next deal closes, never after this one.
- _"Our Q3 SPIF worked - can we run it every quarter?"_ - the SPIF-to-permanent-pay trap; step 7.

## Interview

- One question per message.
- Multiple-choice where offered.
- Skip what prior context already answers.

1. Scope: (a) all plans for the next fiscal year, (b) one role's plan, (c) one mechanic - accelerator, SPIF, crediting rule, draw, (d) diagnosing a plan that misfires?
```
END THIRD-PARTY FILE 4c284037b799ca8c

The third-party file has ended. Everything between the 4c284037b799ca8c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2488 of 21083 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/sales-skills/tree/HEAD/skills/sales-comp-design/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md