Design a sales org's structure by stage: topology, ratios, spans, transitions
Org-design exercise for sales leadership — stage the org, read behavioral signals, pick topology (island, assembly line, pod, hybrid), derive the SDR:AE ratio from your own funnel math, set spans, plan the transition
- What
- Org-design exercise for sales leadership — stage the org, read behavioral signals, pick topology (island, assembly line, pod, hybrid), derive the SDR:AE ratio from your own funnel math, set spans, plan the transition
- Cost
- Free
- Needs
- a sales organization (or founder-led sales) to design for — the skill is an org-design methodology, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Maya-Beth Finotti's sales org-design skill: a structural design exercise for a VP Sales, CRO or founder scaling past founder-led selling, for B2B and B2C. The method: run the interview first (what triggered this, motion, deal size, current shape, behavioral signals, segments, expansion ownership, attrition/ramp, hiring plan, deadline, mandate, effort ceiling), then pick from a structural-move menu ranked by efficiency — frontline manager, SDR split, hunter/farmer split, segment pods — where every move fires only on its behavioral trigger (a hard rule: no move without a fired trigger is designed). Topologies are stage-gated, not substitutes: island (1-5 reps), assembly line (B2B SaaS, roughly $10M-$200M ARR), pod (~20+ reps, complex enterprise), hybrid where mature orgs actually land. The SDR:AE ratio is DERIVED from the org's own funnel math — never copied from a published number, with honest handling of contested figures. Spans set by role (median 7 AEs per manager), expansion ownership with the credited-tail rule, a written transition plan, next-stage triggers, and a measurement gate that must pass 100% before the design is done. Includes the B2B vs B2C deltas (published benchmarks are B2B SaaS data; commission-agent verticals and retail/call-center structures differ fundamentally) and failure modes (specializing too early/late, copying published ratios, pods as default upgrade, restructuring on the calendar). Honest caveats: pure methodology for leadership planning — no tooling, no job reqs; the published rep-level benchmarks are B2B SaaS data, calibrate B2C designs against your own historicals; the 2025-2026 AI-headcount evidence is presented as genuinely contested. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a sales organization (or founder-led sales) to design for — the skill is an org-design methodology, not software to install Install "Design a sales org's structure by stage: topology, ratios, spans, transitions" for me. It teaches my agent Maya-Beth Finotti's org-design exercise: run the 12-question interview first, stage the org on the growth ladder, pick structural moves from an efficiency-ranked menu fired only on behavioral triggers, choose the stage-appropriate topology (island, assembly line, pod, hybrid), derive the SDR:AE ratio from the org's own funnel math, set management spans, decide expansion ownership, stress-test against attrition and ramp reality, and assemble the written org design with next-stage triggers. MIT-licensed. Repository: https://github.com/mbfinotti/sales-skills/blob/main/skills/sales-org-structure/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "sales-org-structure". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. answer the agent's interview questions about my sales org; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.