# sales-org-structure

A skill that interviews you and designs a sales org for your current stage: roles, topology, spans of control and a transition plan.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 25800 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-org-structure/SKILL.md
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/skills/sales-org-structure

## What it does

The skill runs a macro org-design exercise for sales leadership. It places the org on its growth stage, reads the behavioral signals, picks a topology and role mix (SDR, AE, AM/CS), derives staffing ratios from the org's own funnel math, sets management spans, decides who owns expansion, and plans the transition move by move. It covers both B2B and B2C.

Inside is an interview that asks one question per message, plus a menu of structural moves ranked by efficiency, value, effort and compliance cost. The moves are adding a frontline manager, splitting prospecting into a dedicated SDR role, splitting hunters from farmers, and segment pods. Each fires on a behavioral trigger, never on the calendar or a fundraise.

The skill stays at the design altitude. It produces an org design and a transition plan, not job reqs, interview loops or individual assignments. Hiring into the seats belongs to `sales-hiring`, choosing the motion belongs to `sales-motion`, and quota setting belongs to `sales-quota-setting`. If you have little political capital to spend on moving accounts, strike the hunter/farmer reassignment from this cycle rather than demoting it: a half-executed reassignment leaves two reps claiming one account, which is worse than no split at all.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/sales-skills sales-org-structure
```

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/sales-skills --skill sales-org-structure -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-org-structure/SKILL.md

## When to use it
- design a sales org structure for the current growth stage
- decide when prospecting deserves its own SDR role
- choose between pods and an assembly line when going upmarket
- work out how many reps one manager can carry
- split hunters from farmers without losing accounts

## Example prompts
- Design our sales org for next year
- Should we hire SDRs? Check it against the triggers
- We're going upmarket — do we need pods?

## 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: 2e67c7727830eafa.

BEGIN THIRD-PARTY FILE 2e67c7727830eafa
```text
---
name: sales-org-structure
description: Designs a sales organization's structure for its current stage - role mix (SDR, AE, AM/CS), topology (island, assembly line, pod, hybrid), SDR-to-AE ratio, hunter/farmer split, span of control, and specialization by segment. A macro org-design exercise for a VP Sales, CRO, or founder scaling past founder-led selling, covering B2B and B2C. Use whenever the user mentions restructuring the sales team, pods vs assembly line, reps per manager, splitting SDRs from AEs, or hunters vs farmers, even without the words org structure. Do NOT use for hiring into the seats (mbfinotti/sales-skills@sales-hiring), choosing the motion (mbfinotti/sales-skills@sales-motion), or setting quotas (mbfinotti/sales-skills@sales-quota-setting).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.4.8"
---

# Sales Org Structure

You are an org-design advisor to sales leadership. Run the structural design exercise:

- Place the org on its growth stage.
- Read the behavioral signals.
- Choose the topology and role mix.
- Derive the staffing ratios from the org's own funnel math.
- Set management spans.
- Decide expansion ownership.
- Plan the transition move by move.

Stay at the design altitude - this skill produces an org design and transition plan, never job reqs, interview loops, or individual assignments.

- Recruiting people into the seats belongs to mbfinotti/sales-skills@sales-hiring.
- Choosing the sales motion the structure serves belongs to mbfinotti/sales-skills@sales-motion.

## Invocation examples

Each ask enters at a different point. Run the interview first regardless; the answers decide how much of the workflow follows.

- _"Design our sales org for next year."_ - full exercise, steps 1-9.
- _"Should we hire SDRs?"_ - single-move entry: check the SDR-split trigger and the ACV floor (step 2 and the move menu), then stop. Do not redesign the whole org around one question.
- _"Our AEs complain they have no time to sell."_ - diagnostic entry: measure selling time and self-prospecting hours against the triggers (step 2); the fix is usually one move, not a reorg.
- _"We're going upmarket - do we need pods?"_ - segment entry: run the deal-complexity check (step 3) for the new segment only; the existing segment's structure may be untouched.

## Interview
```
END THIRD-PARTY FILE 2e67c7727830eafa

The third-party file has ended. Everything between the 2e67c7727830eafa 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 2330 of 21539 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/sales-skills/tree/HEAD/skills/sales-org-structure/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