← Search

Design a sales org's structure by stage: topology, ratios, spans, transitions
Sales 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 1ef6888
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a sales organization (or founder-led sales) to…

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

At a glance
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.

Version:

Quick answer

Sales org structure is a free listing for VP Sales, CRO or founder design, scaling past founder-led sales. The method runs the interview first, then picks from a move menu ranked by efficiency: frontline manager, SDR split, hunter-farmer split and segment pods. Every move fires only on its behavioral trigger, a hard rule: no move without a trigger.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1ef6888

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/mbfinotti/sales-skills/1ef68881b2ed853fb1f02272b57dc71dd375677f/skills/sales-org-structure/SKILL.md Pinned version: install the code at commit 1ef68881b2ed853fb1f02272b57dc71dd375677f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 1ef6888 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
1ef6888 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.