revops-org-chart

What problem does it solve?

This Skill helps B2B teams avoid RevOps org design mistakes by translating revenue complexity and ARR stage into a practical team structure, role sequencing, and reporting lines that create real mandate and steerability.

Core Features & Use Cases

• Team sizing by ARR stage: Recommends when to add a generalist, manager, analyst, Business Partners, and (later) an Architect based on growth inflection points.
• Role archetypes and responsibilities: Clarifies what a Generalist Manager, Business Partner, Systems Architect, and Analyst should own, including the critical Admin vs Architect distinction.
• Structural model selection: Guides choices between departmental, centralized (center of excellence), hub-and-spoke, and embedded models, including multi-BU/multi-instance designs.
• Hiring sequencing and engagement modes: Provides when to use advisory vs fractional vs FTE Architect engagement and how to transition teams from CRM automation toward RevOps governance.

Quick Start

Ask the Skill: "We’re at €60M ARR with one CRM instance and we want to evolve from a small CRM admin team into a RevOps hub-and-spoke model—what org chart should we use, who should RevOps report to, and what should we hire next?"