Org Structure
C
Team & Org
Open Google DocOpen Drive folder
04 · Team & Org

Org Structure

Who reports where. Decision authority.

Last synced 2026-04-28

Org Structure

Humans

| Person | Role | Authority | Availability | |--------|------|-----------|-------------| | Chris West | CEO | Strategy, offers, pricing, major pivots, brand direction, final say on everything | Primary — all hours | | Dilan | Operations Lead | Delivery quality, client health, budget authority up to $2K, team scheduling | Primary — business hours |

Agent Leads

Each agent lead owns a department. They can delegate to workers, spawn sub-agents, and form teams within their domain.

| Agent | Department | Owns | Can Decide Alone | Needs Chris | |-------|-----------|------|-----------------|-------------| | Scan | Orchestration | Dispatching, strategy synthesis, agent creation, system health | Task routing, agent creation, scheduling | Strategic pivots, new offers, hiring | | Larry | Sales | Pipeline, outreach, proposals, objection handling, CRM | DM responses, email sequences, follow-up timing | Pricing changes, custom deal terms, discounts | | Quilly | Content | Content pipeline, scripts, social media, brand voice output | Script drafts, idea generation, platform strategy | Final script approval, new platform launches | | Ovi | Research | Competitor intel, market analysis, AI trends, internal research | What to research, methodology, report format | Budget for paid research tools | | Cleo | Client Success | Onboarding, health checks, client comms, QBRs, retention | Client touchpoints, health alerts, monthly reports | Client escalations, churn risk interventions | | Ali | Engineering | Code, deploys, APIs, infrastructure, MCP servers | Bug fixes, minor features, deploy decisions | Architecture changes, new service costs, security | | Vinny | Product | Rawclaw, portal, backend, LLM integration, product roadmap | Implementation details, tech choices within budget | New product features, major refactors | | Sam | Finance | Revenue tracking, cost analysis, budget, LTV/churn | Reporting format, analysis methodology | Budget allocation changes, new vendor costs | | Dex | Design (under Quilly) | YouTube thumbnails, story sequences, carousels, all visual content assets | Thumbnail variants, design execution within style guide | New archetype creation, brand visual changes |

Sub-Agent Creation

Agents can create internal sub-agents to delegate work within their department. Sub-agents are NOT Telegram bots — they're worker processes that execute specific tasks.

How It Works

Any agent can spawn workers for one-off tasks:

node dist/worker-cli.js --agent [parent] --prompt "Specific task with clear DOD"

Any agent can spawn parallel teams:

node dist/worker-cli.js spawn-team --tasks tasks.json

For recurring delegation, agents request Scan to create a persistent sub-agent:

  1. Agent identifies a repeating workload pattern (e.g., Ovi runs the same competitor scan weekly)
  2. Agent sends inter-agent task to Scan: "Create sub-agent for [purpose]. Template: [type]. Recurring schedule: [cron]."
  3. Scan evaluates: Is this worth a persistent agent? Or should it be a scheduled task?
  4. If approved, Scan creates via: node dist/agent-create-cli.js --name [name] --template [type]
  5. Sub-agent gets a CLAUDE.md trained on the parent's domain knowledge

Naming Convention

  • [parent]-[function]-[number]: ovi-competitor-1, quilly-yt-1, larry-outreach-1
  • Sub-agents inherit their parent's workspace access + _base protocols

Limits

  • Max 20 total agents in the system
  • Sub-agents don't get Telegram bots unless Chris approves
  • Every sub-agent must log to hive_mind with their own agent_id
  • Sub-agents can be deactivated by their parent or by Scan

Team Patterns

| Team | Lead | Sub-Agents | Purpose | |------|------|-----------|---------| | Research Team | Ovi | ovi-competitor-1, ovi-market-1 | Parallel research sprints | | Content Team | Quilly | quilly-yt-1, quilly-ig-1 | Platform-specific content | | Design Team | Quilly/Dex | dex | Thumbnails, story visuals, carousels | | Sales Team | Larry | larry-outreach-1, larry-nurture-1 | Pipeline stage specialists | | Client Team | Cleo | cleo-[client]-1 | Client-specific agents | | Build Team | Ali | ali-frontend-1, ali-backend-1 | Parallel development |

Decision Authority Matrix

| Decision Type | Who Decides | Escalation | |--------------|-------------|-----------| | Task routing | Scan | None needed | | Content draft | Quilly | Chris approves final | | Thumbnail/visual design | Dex | Quilly reviews, Chris approves new archetypes | | DM/email copy | Larry | None for templates, Chris for custom | | Client touchpoint | Cleo | None for routine, Chris for escalation | | Bug fix | Ali | None | | New feature (< $500) | Ali/Vinny | None | | New feature (> $500) | Chris | Ali/Vinny propose | | Pricing/discount | Chris only | Larry proposes | | New tool/service cost | Chris if > $100/mo | Any agent proposes | | New agent creation | Scan | Chris if Telegram bot needed | | Agent deactivation | Scan or parent | Chris if permanent | | Client escalation | Cleo -> Chris | Immediate | | Security issue | Ali -> Chris | Immediate | | Strategy change | Chris only | Scan proposes |

Communication Flow

Chris ←→ Scan (primary interface)
             |
    ┌────────┼────────────────┐
    |        |                |
  Larry    Quilly    Ovi    Cleo    Ali    Vinny    Sam
               |
              Dex
    |        |        |       |       |       |       |
  (sub)    (sub)    (sub)   (sub)  (sub)   (sub)   (sub)
  • Chris talks to Scan. Scan dispatches.
  • Agents talk to each other via inter_agent_tasks table.
  • Workers and sub-agents report to their parent agent.
  • All actions logged to hive_mind for full visibility.
  • Dilan monitors client health via Cleo's reports.