Org 8.0 aligns Zeta's internal operating structure with its commercial model. This model integrates platform subscription revenues and studio services.
1. The Platform-Powered Partner Model
The Platform-Powered Partner Model integrates software platforms and delivery capabilities:
- Platform Subscription: Core transactional ledgers and routing platforms (Tachyon, Photon, Electron) are standard assets. Subscription revenues scale with the client bank's transaction and processing volumes.
- Engineered Solution Delivery (Engagement Engineering): Product activation, host integration, and operational transition are executed under Engagement Engineering.
This integration supports platform activation and drives subscription volume scaling.
2. Alignment of GTM and Operations
To prevent misalignment between sales scope and operational delivery limits, GTM and Operations are bound by three rules:
- Accountability for Customization: GTM Partners own segment revenue. Client-specific customization that deviates from standard platform core parameters is penalization-mapped to the segment's delivery margins.
- Productization of Platform Layers: Technical layers, including the Analytical Data Lake, are managed and monetized as modular, independently billable and deployable assets, rather than bundled customer integrations.
- Investment Sources: Platform R&D and expansion decisions are funded through sponsorship by GTM (justified by segment pipeline) or Product Lines (justified by platform subscription ARR).
3. Strategic Context: Company A and Company B
The strategic context of the platform architecture is modeled around two domain classifications:
+-----------------------------------------------------------------------------------+
| COMMON IMPLEMENTATION SUBSTRATE |
| Engagement Engineering Model (Methodology & Delivery) |
+-----------------------------------------------------------------------------------+
|
+-------------------------+-------------------------+
| |
v v
+---------------------------------------------+ +---------------------------------+
| COMPANY A PLATFORMS | | COMPANY B PLATFORMS |
| Core-Banking Engines & Transactional | | Agentic Transformation & Work |
| Fabrics | | Orchestration |
| | | |
| - Tachyon (Accounts & Ledger Integrity) | | - Hubs (Bounded Domains) |
| - Photon (Payments Processing) | | - Neutrino (Influence Surface) |
| - Electron (Commercial Cards & Spend) | | - Quark (Domain Hub Classes) |
+---------------------------------------------+ +---------------------------------+
3.1 Company A: The Transactional Core
Company A designates core engines (Tachyon, Photon, Electron, Olympus) focused on ledger integrity, payment routing, spend management, and developer runtime infrastructure.
3.2 Company B: The Agentic Future
Company B designates programmatic influence (Neutrino), bounded domain hub classes (Quark), and the orchestrating concierge (Ibuki) designed to manage work, programmatic external search influence, and autonomous agents.
3.3 The Common Substrate: Engagement Engineering
Both platform classifications rely on the same internal operating substrate: Engagement Engineering. Engagement Engineering is the execution discipline (Initiate, Discover, Build, Transfer, Complete) operated inside the Engagement Factory.
4. Boundary Enforcement: Bank vs. Zeta Org
To prevent structural overlap, documentation separates the customer's operating model from Zeta's internal operating model:
- Bank Org Transformation (External Context): Bounded Hubs, Hub Classes, and the "Hub Way" represent the target operating model of customer banks.
- Zeta Org Transformation (Internal Operating Law): Structural engines, chapters, C3M Council gates, and partner capital decisions represent Zeta's internal functional operating model.