Organizational division maps to commercial structure by partitioning asset creation, execution assembly, and production operations.
1. Asset and Execution Partitioning
To maintain platform product margins and monetize customization services, the organization operates under three functional partitions:
1.1 Core Platform Teams (Asset Partition)
Core platform teams (Tachyon, Photon, Electron, Olympus) focus on core product-line software assets, standard variability points, and security. These teams operate under the "No-Intake Rule" and are insulated from client-specific customization.
1.2 The Engagement Factory (Execution Assembly Partition)
Custom client integrations and transition requirements are executed within the Engagement Factory. Custom customer products are built by Studio Squads utilizing sandboxed extension points and configuration parameters, preventing modification of core platform binaries.
1.3 Outcomes Centers of Excellence (Production Run Partition)
Live client instances are operated by Outcomes Centers of Excellence (SRE Operations, Processing Operations, and Customer Success). This partition is separate from core platform and delivery teams to manage servicing costs.
2. The Sequential Value Chain
The organization aligns functional units to a four-stage sequential value chain:
VALUE CHAIN: [ Pipeline ] ------> [ Platforms ] ------> [ Engagements ] ------> [ Outcomes ]
Business Unit: GTM & Product Lines Engagement Factory Outcomes CoEs
Commercial
- Pipeline (Demand Acquisition): Managed by GTM and Commercial units. This stage covers customer pipelines and segment deal opportunities upstream of delivery.
- Platforms (Product Assets): Managed by Product Line Owners. This stage covers reusable software assets, capability models, and core codebases.
- Engagements (Customer Deployment Assembly): Managed by the Engagement Factory. This stage covers configuration, localized integration, and platform transition into customer products.
- Outcomes (Production Support): Managed by Outcomes Centers of Excellence. This stage covers system operations, compliance verification, and SLA adherence in production.
3. Human-Agent Team Workforce Model
Operational work is structured around agent-augmented execution to limit coordination overhead:
- Human Agent Teams (HATs): Squads are staffed by pre-integrated, certified Human Agent Teams. Human practitioners focus on configuration, custom integration, and verification, while AI agents automate routine data-parsing and administrative tasks.
- Codified Work Catalog: Chapter Stewards maintain a Work Catalog containing standardized blueprints, integration instructions, and agent configurations. This repository preserves operational context during staff rotations.