Legionis Agent Hierarchy & Team Scope Analysis

Date: 2026-02-14 Context: Strategic decisions before building Extension Teams Status: Discussion document — needs decisions


1. Pricing Model: Team-Based Expansion

Proposed Model

TierPriceIncludes
Individual$10/mo1 team of your choice
Team (3+ seats)$7/seat/mo1 team of your choice
Additional team+$5/mo (individual) / +$5/seat/mo (team)Per team unlock

How It Works

A user signs up and picks their primary team (most will pick Product). To access Finance agents, they add the Finance team for $5/mo more.

Individual examples:

Team examples (5 seats):

Strategic Implications

Pros:

Cons: Recommendation: Add a "Full Organization" tier that bundles all teams at a discount:

TierIndividualTeam (per seat)
Single Team$10/mo$7/mo
Each Additional+$5/mo+$5/seat/mo
Full Organization (all teams)$25/mo$20/seat/mo

The "Full Organization" price should be attractive enough that users with 4+ teams would choose it over à la carte. At 4 teams à la carte = $25 (individual) or $22/seat (team), so $25/$20 creates a natural breakpoint.

What Counts as a "Team"?

This depends on how we define the team roster. If we align to a corporate hierarchy:

TeamCore Functions
ProductProduct Management, Product Marketing, UX
FinanceFP&A, Revenue, IR, Controller, Treasury
LegalContracts, Privacy, IP, Compliance, Employment
DesignUI, Visual, Interaction, User Research, Motion
ArchitectureAPI, Data, Security, Cloud, AI
MarketingContent, SEO, CRO, Paid, Email, Social, Growth, PR
OperationsPMO, Procurement, Process, Risk, Quality
Corporate DevelopmentM&A, Strategic Partnerships, Corporate Venture

Plus coaches are embedded per-team (not a separate purchasable team).

The Executive layer (CEO, CFO, CTO, CMO, etc.) could be:


2. Hierarchy Alignment Across Teams

Current State: Inconsistent

The Product OS has a 4-tier hierarchy that no other team matches:

Product OS (4 tiers):
👑 CPO (C-level)
└── 📈 VP Product (VP)
    ├── 📋 Dir PM (Director)
    ├── 📣 Dir PMM (Director)
    └── ICs: PM, PMM, BizOps, BizDev, CI, ProdOps, UX, VR, Mentor

Extension Teams (2 tiers): 🎨 Dir Design → 5 specialists 🏗️ Chief Architect → 5 specialists 📢 Dir Marketing → 13 specialists

My Finance/Legal Plan (2 tiers): 💼 Dir Finance → 6 specialists + coach ⚖️ General Counsel → 6 specialists + coach

The Hierarchy Question

In an AI agent team, hierarchy serves three purposes:

  • Routing: Higher = more strategic/ambiguous requests
  • Judgment quality: Higher = opus model, better synthesis
  • Scope: Higher = broader scope, cross-functional awareness
  • Three Options

    Option A: Standardize on 3 Tiers (Recommended)

    Every team follows: C-Level → Director → Specialists

    C-Level (opus)     — Strategic, portfolio-level, cross-functional
    Director (opus)    — Operational leadership, team routing, synthesis
    Specialists (sonnet) — Domain-specific task execution
    

    Product Team:

    👑 CPO → 📈 VP Product → Dir PM, Dir PMM → ICs
    
    (Keep as-is — Product is the flagship team with deepest hierarchy)

    Finance Team:

    💰 CFO → 💼 Dir Finance → FP&A, Revenue, IR, Controller, Treasury
    

    Legal Team:

    ⚖️ General Counsel → 📜 Dir Legal → Contracts, Privacy, IP, Compliance, Employment
    
    (GC is effectively C-level already. Dir Legal is new — manages operational legal)

    Design Team:

    🎨 Chief Design Officer → 🖼️ Dir Design → UI, Visual, Interaction, Research, Motion
    
    (Promote current Dir Design to CDO, add Dir Design as operational lead)

    Architecture Team:

    🏗️ CTO → 🔧 Dir Engineering → API, Data, Security, Cloud, AI
    
    (Rename Chief Architect to CTO, add Dir Engineering)

    Marketing Team:

    📢 CMO → 📣 Dir Marketing → 13 specialists
    
    (Promote current Dir Marketing to CMO, add Dir Marketing or keep as-is since Marketing already has 14 agents)

    Pros: Clean, consistent, scalable. Each team has strategic + operational + execution layers. Cons: Adds ~6 new agents (one C-level or Director per team). More agents to build.

    Option B: Keep 2-Tier for Extension Teams, Match Existing

    Only Product gets the full hierarchy (CPO/VP/Dir/IC) because it's the flagship. All other teams keep: Lead → Specialists

    The "Lead" adapts per domain (GC for Legal, Chief Architect for Architecture, etc.)

    Pros: Fewer agents, simpler, faster to build. Cons: Inconsistent. Users might expect a CFO agent if they see a CPO. No strategic layer for non-Product functions.

    Option C: Executive Team as Separate Gateway

    Create a cross-functional Executive Team that includes all C-level agents, plus CEO:

    Executive Team (@executive):
    🏢 CEO → Company strategy, cross-functional alignment, board prep
    ├── 👑 CPO (already exists in Product OS)
    ├── 💰 CFO → Financial strategy, budget governance
    ├── ⚖️ CLO/GC → Legal strategy, risk governance
    ├── 🏗️ CTO → Technology strategy
    ├── 📢 CMO → Marketing strategy
    └── 🎨 CDO → Design strategy
    

    Each C-level agent interfaces with their team's Director:

    Pros: Clean separation of strategic vs operational. C-suite is a premium offering. CEO adds unique value. Most realistic to how companies actually work. Cons: Creates a new team layer. C-level agents might feel redundant for small-team users.

    The CEO Question

    Should we have a CEO agent?

    A CEO agent would handle:

    Argument FOR: CEO is the natural apex. In a "Full Organization" deployment, someone needs to be the ultimate synthesizer. The PLT gateway currently serves this purpose but doesn't have a single accountable perspective — it's a committee. A CEO agent provides that single-point strategic view.

    Argument AGAINST: Most Legionis users won't be actual CEOs. A CPO or VP Product is a more natural primary user. CEO might feel presumptuous.

    My recommendation: Yes, include CEO — but position as the "Strategic Advisor" that synthesizes across all functions. Available in "Full Organization" tier only.

    Recommended Hierarchy (Option A + C Hybrid)

    EXECUTIVE TEAM (@executive) — Available in Full Organization tier
    🏢 CEO
    ├── 👑 CPO (exists — Product OS)
    ├── 💰 CFO (new)
    ├── ⚖️ General Counsel / CLO (new — currently GC in Legal team)
    ├── 🏗️ CTO (new — rename from Chief Architect)
    ├── 📢 CMO (new)
    └── 🎨 CDO (new)

    PRODUCT TEAM (@product) — Flagship, deepest hierarchy 👑 CPO (shared with Executive) └── 📈 VP Product ├── 📋 Dir PM ├── 📣 Dir PMM └── ICs: PM, PMM, BizOps, BizDev, CI, ProdOps, UX, VR

    FINANCE TEAM (@finance) 💰 CFO (shared with Executive) └── 💼 Dir Finance └── FP&A, Revenue, IR, Controller, Treasury

    LEGAL TEAM (@legal) ⚖️ General Counsel (shared with Executive) └── Dir Legal Affairs └── Contracts, Privacy, IP, Compliance, Employment

    DESIGN TEAM (@design) 🎨 CDO (shared with Executive) └── Dir Design (existing, retitled) └── UI, Visual, Interaction, Research, Motion

    ARCHITECTURE TEAM (@architecture) 🏗️ CTO (shared with Executive) └── Chief Architect (existing, now operational lead) └── API, Data, Security, Cloud, AI

    MARKETING TEAM (@marketing) 📢 CMO (shared with Executive) └── Dir Marketing (existing) └── 13 specialists

    COACHING LAYER — Embedded per team (not separate) Each team gets a Coach agent (opus)

    Key design decisions:


    3. Missing Corporate Functions

    Currently Covered

    FunctionWhereAgents
    Product ManagementProduct OS13 agents
    DesignExtension Team6 agents
    Architecture / Engineering PlanningExtension Team6 agents
    MarketingExtension Team14 agents
    Finance (planned)Extension Team7 agents
    Legal (planned)Extension Team7 agents

    Not Yet Covered (Planning Functions Only)

    A. Operations Team (COO Domain)

    The operational backbone of any company. Planning-only scope:

    AgentKeyDomainPlanning Focus
    Dir Operations@ops-dirOperational leadership, process governanceProcess strategy, operational excellence
    Program Manager@program-managerProgram management, cross-functional coordinationProgram planning, dependency mapping, milestone tracking
    Project Manager@project-managerProject planning, resource allocationWBS, Gantt planning, risk registers, status frameworks
    Procurement Specialist@procurementVendor evaluation, purchasing strategyVendor selection frameworks, RFP creation, contract evaluation
    Process Engineer@process-engineerBusiness process optimizationProcess mapping (BPMN), bottleneck analysis, automation strategy
    Risk Manager@risk-managerEnterprise risk managementRisk registers, mitigation planning, business continuity

    Knowledge Packs: Project Management (PMBoK, Agile Portfolio), Process Optimization (Lean, Six Sigma, BPMN), Procurement (RFP/RFQ, vendor evaluation), Enterprise Risk (COSO ERM, ISO 31000)

    Overlap with existing:

    B. Corporate Development Team

    Strategic growth beyond organic product development:

    AgentKeyDomainPlanning Focus
    Head of Corp Dev@corpdev-dirStrategic development leadershipM&A strategy, partnership strategy, investment thesis
    M&A Analyst@ma-analystM&A analysis, due diligenceTarget identification, valuation, synergy analysis, integration planning
    Strategic Partnerships@strategic-partnershipsPartnership strategy, ecosystemPartnership frameworks, deal structures, JV planning
    Corporate Venture@corp-ventureVenture investments, innovation scoutingInvestment thesis, startup evaluation, portfolio management

    Knowledge Packs: M&A Frameworks (valuation, due diligence, integration), Partnership Models (JVs, strategic alliances, licensing), Venture/Innovation (CVC, startup evaluation, portfolio theory)

    Overlap with existing:

    C. IT / Technology Governance Team

    Planning and governance of enterprise technology (distinct from Architecture which focuses on product architecture):

    AgentKeyDomainPlanning Focus
    CIO / IT Dir@it-dirIT strategy, technology governanceIT roadmap, digital transformation, technology standards
    IT Security Policy@it-securityIT security policies, cyber governanceSecurity policies, awareness programs, incident response planning
    Enterprise Systems@enterprise-systemsEnterprise tooling, SaaS managementTool evaluation, integration strategy, vendor management
    Data Governance@data-governanceData strategy, governance, qualityData classification, retention policies, data quality frameworks

    Knowledge Packs: IT Governance (COBIT, ITIL), Cybersecurity Frameworks (NIST CSF, CIS Controls), Data Governance (DAMA-DMBOK, data mesh), Digital Transformation

    Overlap with existing:

    Priority Assessment

    TeamBusiness ImpactMVP PriorityRationale
    FinanceHighP0 — Build nowEvery company needs financial planning
    LegalHighP0 — Build nowEvery company needs legal guidance
    OperationsMedium-HighP1 — Next waveProject/program management is universal
    Corporate DevelopmentMediumP2 — LaterOnly relevant for growth-stage companies
    IT GovernanceMediumP2 — LaterOverlaps heavily with Architecture + Legal
    ExecutiveHighP1 — Next waveCEO + C-suite for "Full Organization"

    Complete Team Roster (Full Vision)

    #TeamGatewayLeadAgentsPriority
    1Product@productCPO13✅ Done
    2Design@designCDO/Dir Design6-7✅ Done
    3Architecture@architectureCTO/Chief Architect6-7✅ Done
    4Marketing@marketingCMO/Dir Marketing14-15✅ Done
    5Finance@financeCFO7-8🔨 P0
    6Legal@legalGC/CLO7-8🔨 P0
    7Operations@operationsCOO/Ops Dir6-7📋 P1
    8Executive@executiveCEO6-7📋 P1
    9Corp Dev@corpdevHead of Corp Dev4-5📌 P2
    10IT@itCIO4-5📌 P2

    Full vision totals:

    Marketing Angle

    At full build-out, Legionis offers:

    "Your complete AI-powered organization: 80+ specialized agents across 10 teams covering every planning function — from strategy to finance to legal to operations. Start with one team, grow to a full organization."


    Decisions Needed

    Decision 1: Pricing Model

    Decision 2: Hierarchy Standard

    Decision 3: Team Scope

    Decision 4: Coaches


    Created: 2026-02-14