.svg)
Cargo
Cargo is where GTM teams build revenue infrastructure—modeling data, orchestrating Plays, deploying AI agents that act on real-time signals. It's purpose-built for the complexity of modern B2B motions: PLG signals feeding outbound, scoring models triggering handoffs, agents running qualification in parallel.
But Cargo orchestrates execution. The strategic context that execution depends on—ICP definitions, qualification logic, persona relevance, competitive positioning—ends up embedded inside Plays and agent prompts. That context fragments across your workspace. When positioning shifts, you're hunting through Plays to update prompts. When a new product launches, you're rebuilding workflows instead of configuring them. The orchestration layer becomes a context graveyard.
Octave is the GTM repo that Cargo consumes. It maintains a structured, versioned model of your ICPs, personas, use cases, and positioning—exposed to Cargo at runtime via API. Cargo handles orchestration. Octave supplies the strategic intelligence. The boundary is clean: Plays define when and how; Octave defines what and why.
Top Use Cases
PLG-to-Sales Handoff
Cargo triggers expansion and handoff workflows based on product usage signals. Octave provides the context to act intelligently:
- Which behaviors actually indicate buying intent for your ICP
- Which personas and use cases are relevant to their activity
- Which messaging, proof points, and next-best-actions apply
PQL motions stay automated without hard-coding assumptions into every Play. As your product evolves, campaigns adapt—configuration changes, not rebuilds.
Transparent Account Scoring
Instead of black-box models, Cargo workflows query Octave to evaluate accounts against a living GTM model:
- Fit scoring based on ICP definitions using natural language qualifiers
- Use-case and product alignment across your portfolio
- Strategic priority within your TAM
See exactly why a lead scored the way it did. RevOps can adjust qualifiers with a toggle—no formula rewrites, no waiting on engineering. Scores stay consistent across every system that consumes them.
Multi-Channel Outbound with Shared Positioning
Cargo Plays and Agents pull messaging context directly from Octave's Library:
- Persona-specific pain points and objection handling
- Value propositions mapped to their use case
- Proof points and competitive framing
Email sequences, LinkedIn touches, and agent responses all reflect the same positioning. When PMMs update messaging in Octave, every channel updates automatically. No sync issues, no version drift.
Cargo provides the orchestration layer for revenue automation. Octave provides the GTM repo that orchestration depends on.
For GTM teams: Plays become leaner because context lives upstream. Workflows become resilient because strategy changes don't require rebuilds. And every campaign you ship makes the system smarter—Octave captures what works and feeds it back into the Library. Context compounds instead of decaying.
Build your generative GTM motion today
