Sales Org Structure
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).
- Skill ID
- mbfinotti/sales-skills/sales-org-structure
- Publisher
- mbfinotti
- Repository
- sales-skills
- Installs
- 1,060
- Files
- 4
- License
- MIT
- Synced
- Oct 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
mbfinotti/sales-skills/sales-org-structureInstalls these files- SKILL.md
- evals/evals.json
- references/ratio-span-benchmarks.md
- references/topology-transition-cases.md
What this skill tells the agent
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
Ask before designing. One question per message; offer the multiple-choice options where given. Skip anything already answered by prior context.
- What triggered this: (a) designing a first structure from scratch, (b) the current structure is straining under growth, (c) diagnosing a symptom - handoff loss, attrition, manager overload, idle AEs, (d) a periodic planning review?
- Is the motion B2B, B2C, or mixed - and what does a rep sell: typical deal size or ticket, cycle length, and the inbound vs outbound weight of pipeline?
- Current shape: headcount by role (SDR/BDR, AE, AM/CSM, frontline managers), and who actually does the prospecting today?
- Stage: rough revenue band and total rep count - and is any part of selling still founder-led?
- Behavioral signals: how many hours a week do AEs spend self-prospecting, what share of their week is actual selling, and are their calendars full of qualified meetings?
- Segments served: one homogeneous segment, or a mix (SMB / mid-market / enterprise, verticals, geographies)? Where do deals concentrate?
- Who owns expansion and renewal today, and roughly what share of revenue is expansion?
- Last 12 months: attrition and ramp time per role, if known?
- Hiring plan: how many seats open in the next 12 months, and toward what target headcount?
- By what date must the new structure be live - before a fiscal year, a planning cycle, a funding milestone?
- Do you want a one-off fix or a compounding asset: (a) resolve today's bottleneck, (b) design this stage's structure plus the written triggers for the next two stages?
- What is your effort ceiling: hiring budget and open headcount, management bandwidth, and the political capital you can spend moving accounts and reworking comp? A reorg's real cost is its low reversibility.
Re-rank the move menu below against answers 10-12 before proposing anything, and say which answer moved what:
- A hard date inside a quarter demotes pods and any full rebuild - a reorg mid-quarter breaks live pipeline. A single split or a manager hire is what fits the window.
- A compounding mandate (11b) promotes writing next-stage triggers into the plan; a bottleneck mandate (11a) keeps the plan to the one move whose trigger has fired.
- Low political capital deletes the hunter/farmer account reassignment this cycle rather than demoting it - a half-executed reassignment leaves two reps claiming one account, worse than no split. Say what you struck and why.
The structural-move menu
At any decision point the real choice is which move to make next, not which textbook topology to admire. Default rung: no move - each move fires only on its behavioral trigger, never on the calendar or a fundraise. When several triggers fire at once, take the moves in efficiency order:
- efficiency:
frontline manager > SDR split > hunter/farmer split > segment pods - value:
segment pods > SDR split > hunter/farmer split > frontline manager - effort:
segment pods (a full reorg with duplicated management) > hunter/farmer split (account reassignment plus comp rework) > SDR split (a hiring quarter plus handoff design) > frontline manager (one hire) - compliance cost:
hunter/farmer split > segment pods > SDR split > frontline manager (none)- rewritten commission agreements need HR and legal sign-off, and earned-credit disputes over reassigned accounts are the hardest thing on this menu to unwind; reporting-line changes need consultation before announcement wherever employee representation applies; an SDR split only writes a new role definition and a plan from scratch, with nothing to renegotiate.
- Add a frontline manager.
- Trigger: 2 reps consistently hitting quota (typically around $1M-$2M ARR) for the first manager. After that, roughly one manager per 6-8 reps per stage.
- Buys: coaching and ramp speed for one hire's worth of effort, the best ratio on the menu.
- Caveat: favor a hungry player-coach Director over a premature VP for the first seat, but never leave leadership a permanent player-coach. Player-coaches spend as little as 14-16% of their time coaching, versus a ~28% best practice and 40-60% for dedicated managers.
- Split prospecting into a dedicated SDR role.
- Trigger: AE self-prospecting exceeds ~4 hours/week, AE selling time drops below ~30% of the week, or the org commits to outbound as a deliberate strategy.
- Blockers that delete this move: ACV below roughly $4K (Aaron Ross's own caveat - not enough deal value to fund a prospecting role), or AE calendars already full from inbound (add SDRs only once AEs show empty-calendar syndrome).
- Buys: recovered selling hours plus stage-level conversion data the org cannot see any other way.
- Split expansion ownership (hunter/farmer).
- Trigger: roughly 25 AEs and expansion revenue material enough to deserve a dedicated owner. Jason Lemkin and Brett Queener both warn against splitting earlier, because quota-credit rules below that size distort behavior (reps slow-roll expansion to stay inside their credited window).
- Signal: the split is a maturity signal. At maturity only ~26-27% of companies still leave expansion with the AE.
- Mechanics: cap the hunter's credited tail (commonly 12 months) and pay the farmer base-heavy on retention/expansion - the comp mechanics belong to mbfinotti/sales-skills@sales-comp-design.
- Stand up segment pods.
- Trigger: ~20+ reps and multi-segment complexity where a single stage manager can no longer hold conversion accountability, typically an enterprise segment whose 11-20+ stakeholder buying committees need dedicated cross-functional attention.
- Buys: the highest value on the menu, at the highest disruption cost.
The efficiency order starves segment pods - highest value, highest effort, they lose every ratio round. Promote them anyway once the trigger above fires: past that point, no cheaper move restores conversion accountability. This ordering is a default, not a law - re-rank it against what you know about the user: an org that already runs cross-functional squads elsewhere gets pods cheaper; an org with no spare management bandwidth gets the manager hire promoted regardless.
Topology by stage
Ranking Island against Assembly Line against Pod in the abstract would be false precision - they are stage-gated, not substitutes at a given size. The efficient topology is the smallest one the signals support; the menu above is how you move between them.
More from mbfinotti
Use this skill in a project
Open any RiverX project, search the Skills panel for mbfinotti/sales-skills/sales-org-structure, and install it in one click.
