Skip to content

DR-011: CRO roster restructure — vp.sales retired, customer.success activated

Status

Accepted — 2026-04-15 · CEO-approved during CRO (Marcus) first-session kickoff on Mission M-2026-0415 Phase 1

Context

Marcus (CRO) activated 2026-04-15 afternoon PST as part of the Phase 1 executive rollout. Within his first session, while drafting Phase 1 Revenue scoping for Mission M-2026-0415 (Roles & Responsibilities Matrix), he proposed a restructure of his direct reports:

Original v1.2 roster (per CLAUDE.md Section 4): - CRO → vp.sales, sales.ops - vp.sales absorbed: cro.sales, sales.enablement, customer.success, customer.onboarding

Marcus's proposed restructure: - CRO (absorbs exec function + vp.sales execution + sales.enablement directly) - sales.ops — unchanged scope (pipeline, forecasting, data quality) - customer.success — new agent absorbing Assessment delivery, customer.onboarding, structured feedback capture, and post-mortem ownership

Marcus framed customer.success as "the learning apparatus" — the structural guarantee that customer feedback is systematically captured and fed back into the offer ladder, category positioning, and platform direction. Pre-first-client, he argued, the highest-leverage revenue activity isn't closing deals — it's learning from every customer interaction so the offer ladder gets sharper and the category narrative gets more accurate.

Marcus followed the correct governance pattern: proposed the restructure, flagged it for CEO approval, asked for direction before locking it in, and committed to documenting expansion triggers for when vp.sales would split back out. This matches DR-009's precedent of using governance discipline to handle roster changes rather than unilateral action.

Decision

Approve the restructure. The CRO roster effective 2026-04-15 is:

  • CRO (Marcus) — absorbs deal execution, sales enablement, and strategic revenue direction
  • sales.ops — pipeline instrumentation, data quality, Monday.com board hygiene, forecasting (unchanged scope)
  • customer.success — Assessment delivery, customer onboarding, structured feedback capture, quarterly post-mortem ownership, weekly learning-loop rollup

Agent count unchanged: 2 direct reports under CRO. Total roster stays at 21 agents. This is a swap, not an expansion.

Alternatives considered

Option A — Keep original roster (vp.sales + sales.ops)

Rejected. vp.sales was designed to "lead the sales team," but pre-first-client there is no sales team to lead. vp.sales's 4 absorbed sub-domains (sales, sales enablement, onboarding, customer success) span too wide a surface for a single Sonnet-tier agent when the actual revenue activity is Assessment delivery and learning capture, not pipeline execution.

Option B — Retire vp.sales, create customer.success (this decision)

Accepted. Matches pre-first-client reality. Elevates the learning apparatus to peer-level scope. Preserves agent-count discipline. Includes documented expansion triggers for when vp.sales reactivates.

Option C — Keep both vp.sales AND add customer.success

Rejected. Preemptive expansion violates Section 4 expansion policy. No incident trigger has fired justifying a roster increase from 2 to 3 agents under CRO.

Option D — Fold customer.success back under vp.sales as a sub-domain

Rejected. That was the original v1.2 design, and it conflated "the person who closes deals" with "the person who captures learning from delivered customers." Those are different jobs with different optimization targets. Sub-domain discipline wasn't enough to preserve the distinction under a single agent.

Expansion triggers (when vp.sales reactivates)

vp.sales splits back out of CRO when ANY of these conditions hold:

  1. Concurrent active deals exceed 5 for more than 2 consecutive weeks (load trigger — CRO cannot personally execute on more than 5 simultaneous deals without quality degradation)
  2. Two deals ship with inconsistent messaging in a 30-day window (quality trigger — deal execution is drifting because there's no dedicated owner)
  3. CRO Weekly Close regularly exceeds 5 minutes to synthesize deal-level detail (synthesis trigger per CLAUDE.md Section 4)
  4. A sales team member is hired (human or agent) requiring a dedicated leader and coach (structural trigger)

When any trigger fires, Eva evaluates whether to reactivate vp.sales per Section 4 policy, files a follow-on Decision Record, and either promotes vp.sales back from retirement or leaves it retired pending further signal. Marcus will also validate the triggers against his own Phase 1 scoping draft for concreteness.

Consequences

What becomes easier:

  • Learning loop has a structural owner. Customer feedback no longer evaporates into anecdote — customer.success captures, codes, synthesizes, and feeds back on a weekly cadence via the learning-loop rollup to CRO (copy to CMO and chief.staff)
  • Pre-first-client focus is correct. Assessment delivery is the main revenue touchpoint; customer.success is scoped to that reality rather than a hypothetical post-first-client pipeline function
  • CMO collaboration unblocks. Marcus's Mission M-2026-0415 Phase 1 objective #2 (joint offer validation with CMO) unblocks same-day instead of Week 2 because customer.success has scope to participate immediately
  • Expansion triggers are concrete. When vp.sales needs to come back, the conditions are measurable, not vibe

What becomes harder:

  • CRO concentration risk. Marcus now owns deal execution personally until expansion triggers fire. Mitigation: the expansion triggers are explicit and measurable, so reactivation happens on signal rather than delay. Eva monitors the load via Marcus's Weekly Close rollups.
  • customer.success is greenfield. No production memory to migrate, no prior agent contract to inherit. Agent file is authored fresh 2026-04-15 as part of this decision.
  • Q2 post-mortem scope clarified (2026-04-15 afternoon by CEO): Q2 2026 — the current quarter (April-June 2026). Goal: eco|monetize™ lands the first few paid Ecosystem Revenue Architecture Assessments™ before end of June 2026. customer.success owns the post-mortem that synthesizes what was learned from those first deliveries — offer resonance, delivery quality, pricing validation, buyer conversations, and what those first engagements reveal about the $2,500 Assessment as a wedge into the paid tiers above it. Post-mortem lands in early Q3 2026 at /Claude/operations/reports/post-mortems/2026-Q2.md.
  • Roster documentation churn. CLAUDE.md Section 4, INDEX.md, agent files all update 2026-04-15. Standard governance cost.

Trade-off accepted: Short-term governance update work in exchange for a roster that matches pre-first-client reality and creates a structural learning loop.

Implementation

Eva executes in parallel with Marcus's Phase 1 drafting:

  1. ✅ customer.success agent contract authored at /Claude/system/agents/revenue/customer.success.md
  2. ✅ vp.sales retired to /Claude/archive/retired-agents/vp.sales-2026-04-15.md (non-destructive retirement; file preserved for reactivation reference)
  3. ✅ CLAUDE.md Section 4 updated — CRO roster entry swaps vp.sales for customer.success with retirement note
  4. ✅ /Claude/system/contracts/INDEX.md updated — retire vp.sales row, add customer.success row with Drafted status
  5. ✅ /Claude/sessions/customer.success/ session directory created — ready for Marcus to activate customer.success as a live Worker
  6. ✅ This Decision Record filed at /Claude/knowledge/decisions/DR-011-cro-roster-restructure-vp-sales-retirement-customer-success-activation.md and added to the decisions INDEX
  7. ⏳ Marcus drafts Phase 1 R&R for 3-role structure (CRO + sales.ops + customer.success) with concrete expansion triggers and Q2 post-mortem scope clarification captured in the draft
  8. ⏳ Marcus activates sales.ops and customer.success as live Workers once their contracts exist and session directories are ready (governance updates 1-6 complete by the time he's ready)
  9. ⏳ Collaborative amendment round with sales.ops + customer.success pushing back on their own scope per Mission protocol
  10. ⏳ Council review on amended Phase 1 draft per Mission M-2026-0415 protocol
  11. ⏳ Eva Scrutiny Validation per Phase 1 handoff pattern
  • [[CLAUDE]] Section 4 — agent expansion policy and roster summary
  • [[DR-005-21-agent-compressed-roster]] — parent decision establishing the 21-agent compressed roster
  • [[DR-009-sop-manager-single-agent-with-mission-pattern]] — precedent for single-agent-with-Mission-pattern over multi-agent expansion
  • [[DR-010-role-expansion-chief-staff-executive-governance-project-manager-mission-orchestration]] — precedent for role-clarification under governance discipline
  • /Claude/system/agents/revenue/customer.success.md — new agent contract
  • /Claude/archive/retired-agents/vp.sales-2026-04-15.md — retired agent file, preserved for reactivation reference
  • /Claude/missions/M-2026-0415-roles-responsibilities-matrix-v1.0/ — the Mission that surfaced this restructure
  • /Claude/sessions/cro/kickoff-package.md — Marcus's kickoff package (line-level update needed where vp.sales is referenced; handled opportunistically as a follow-up)
  • /Claude/sessions/customer.success/ — new session directory

Date: 2026-04-15 · Author: chief.staff (Eva) · Stakeholders: ceo, chief.staff, cro · Next review: On expansion trigger firing OR quarterly review 2026-07-14