Crew Expansion Map

Confirmed Status

Approval Record

The final compiled response YAML approved Stage 3 with no unresolved required questions, no explicit edit notes, and no negative section feedback.

alignment_page: "alignment/expansion-map-crew.html"
response_status: complete
approval_status: ready-for-agent-review
required_gate_status: complete
unanswered_required_questions:
  []
gate_answers:
  - section: "Evidence Matrix"
    gate_type: "research completeness"
    status: "answered"
    answer: |-
      Evidence is sufficient for Stage 3 canonicalization after applying any explicit edits in this response.
  - section: "User Format Preferences"
    gate_type: "user format preferences"
    status: "answered"
    answer: |-
      Approve the Stage 2 review format as written.
  - section: "Final Artifact Approval"
    gate_type: "final artifact approval"
    status: "answered"
    answer: |-
      Approve Stage 3: archive/remove the working packet, write canonical Crew expansion-map and interview artifacts, and confirm the alignment page.
    target_path: "research/crew/expansion-map.md"

Canonical Expansion Map

Summary

Crew's primary expansion model is shared-account scope expansion, not a Solo-to-Platform tier ladder. A retained Crew account should grow when the same CalcLLM account needs to answer a neighboring cost question: Crew users need production LLM cost attribution through Trace, or Trace users need engineering AI-tool spend governance through Crew.

Crew-only expansion begins when visibility becomes governance. A monthly dashboard habit is retention; expansion starts when Crew adds team leads, Finance/FP&A, budget thresholds, cost-center allocation, executive reporting, chargeback, enterprise controls, a sibling product module, or advocacy proof.

Role expansion matters as much as seat expansion. Crew should track which new stakeholder consumes a workflow artifact and which role gains budget authority: Platform Eng Lead champion, platform/admin owner, team leads, Finance/FP&A, VP Eng or CTO, Security/Compliance, and Procurement.

Native vendor controls validate the problem and raise the bar. GitHub Copilot, Claude Code, Cursor, Devin/Windsurf, and adjacent vendors expose budget, usage, admin, or enterprise controls. Crew should therefore lead with cross-tool normalization, team attribution, outcome linkage, and shared Crew-plus-Trace account intelligence rather than generic budget alerts.

Expansion Triggers

Upgrade And Seat Growth Paths

Team Or Account Rollout

Referral And Advocacy Paths

Risks And Constraints

Product Gaps

Product Path Implications

Crew should stay scoped to AI dev-tool cost intelligence while treating Trace as the first sibling expansion path. The shared CalcLLM account should carry common identity, teams, cost centers, billing, Slack reporting, and account navigation so cross-sell can be presented as adding an answer inside the same operating model.

Do not create a Trace expansion artifact from this Crew map. Trace should receive its own expansion-map pass later if the product path remains active and the Trace-to-Crew trigger needs canonical treatment.

Next Steps

1. Run $lifecycle-metrics research/crew to define expansion triggers, account-health thresholds, cross-sell events, and advocacy readiness signals.
2. Run monetization or packaging research before finalizing tier names, prices, or plan limits.
3. Validate integration feasibility for per-user and per-team attribution before promising chargeback workflows.
4. Gather customer discovery around Crew-to-Trace and Trace-to-Crew trigger questions before implementing in-product cross-sell prompts.

Visual Account-Flow Diagrams

Interview And Evidence Artifact

Evidence Matrix

Source Coverage

Assumptions And Confidence Register

Interview Prompts To Validate

1. When does a monthly Crew budget review become an account expansion opportunity?
   • Expected answer to validate: when it adds team leads, Finance/FP&A, budget thresholds, cost-center allocation, or chargeback.
   • Evidence needed: lifecycle metrics or customer discovery.
2. What should trigger Crew-to-Trace cross-sell?
   • Expected answer to validate: a production-cost attribution question that Crew cannot answer, such as "why is our production LLM bill 3x expected?" or "which feature/customer drove the production spend?"
   • Evidence needed: onboarding flow, dashboard event, or discovery interview.
3. What should trigger Trace-to-Crew cross-sell?
   • Expected answer to validate: a Trace account's CTO scales engineering headcount and begins asking what engineers spend across AI coding tools.
   • Evidence needed: Trace onboarding and expansion map.
4. Which roles must be mapped before chargeback is credible?
   • Expected answer to validate: platform admin, team lead, Finance/FP&A, economic buyer, and a dispute owner.
   • Evidence needed: chargeback workflow spec.
5. What makes an advocacy ask appropriate?
   • Expected answer to validate: budget surprise prevented, ROI proof, cost-per-PR narrative, or tool-consolidation win.
   • Evidence needed: customer feedback and public-story permission.

Current-Market Validation Interview

1. Do GitHub AI Credits and budget controls reduce Crew demand or create urgency? Current synthesis: both. They validate volatility and governance needs, but weaken single-vendor budget-alert differentiation.
2. Does Claude Code's own cost tooling make Crew redundant? Current synthesis: not by itself. It helps within Claude, but Crew's value depends on cross-tool and cross-team normalization.
3. Does Cursor or Devin/Windsurf already solve team cost intelligence? Current synthesis: they expose admin/usage surfaces and enterprise controls, but public pages do not show cross-vendor, per-outcome cost intelligence.
4. Does Cohrint directly compete? Current synthesis: yes, as cost optimization/routing and dashboards for AI coding spend. Crew should differentiate on read-only governance, attribution, account rollout, and Trace cross-sell.

Follow-Up Research Questions

1. Which account-health event best predicts Crew-to-Trace interest: dashboard repeat use, unanswered production-cost question, executive export, or provider-integration milestone?
2. Which expansion package should own budget thresholds, forecasting, and chargeback: baseline Crew, a governance add-on, or an enterprise tier?
3. What data quality threshold is required before Team Lead and Finance views become trustworthy?
4. Which advocacy artifact is easiest to produce without exposing sensitive spend data?
5. Which vendor APIs expose enough user/team-level data for reliable cost-center allocation?

Archive Record

Downstream Implications

The next research dependency is lifecycle instrumentation for Crew expansion signals. The confirmed map recommends $lifecycle-metrics research/crew as the next concrete skill command, with monetization/packaging and integration feasibility work following before final pricing or chargeback commitments.