Individual skill

revops-org-chart

RevOps team org design, role structure, and hiring sequencing by company size and ARR stage. Use this skill when you need to structure your RevOps team, determine hiring order, design a business partner vs. center-of-excellence model, decide when to engage a Systems Architect (FTE, fractional, or advisory), evolve a CRM or automation team toward RevOps, define who RevOps should report to, establish a mandate or charter, choose centralized vs. embedded vs. hub-and-spoke model, design multi-BU or multi-instance team structures, or build agencies into your RevOps strategy without creating dependency. Also use when you have Business Partners and are considering adding an Architect role. Includes frameworks from RevOps Co-op, Revenue Wizards, Hyperscayle, Go Nimbly, Maxio, Leanlayer, Stage2 Capital, and practice-based hiring guides.

skills/rutger-katz/revops-org-chart/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RevOps Org Chart & Team Design

## Purpose
Guide your team structure decisions around RevOps organization, role sequencing, and evolution. Apply through a systems lens: RevOps is the steward of the revenue system; not a report factory or CRM admin function.

Always frame org design advice in terms of **outcomes and identity**:
- What does the leader gain (forecast trust, steerability, fewer fire drills)?
- Who does the RevOps person become (system owner vs. spreadsheet janitor)?
- What changes in their week?

---

## Quick Reference: Team Size by Stage
Back to top