
Clay
Categories
When you join an engineering team, you clone the repo. When you join a GTM team, you inherit an 18-column Clay table and schedule fifteen coffee chats to understand what the last person tried.
Clay is the execution engine for GTM teams—unmatched at aggregating data, chaining enrichments, and triggering downstream actions. But execution needs context, and that context ends up embedded directly in Clay: scoring logic in formulas, ICP definitions in conditionals, messaging assumptions spread across prompt chains. Every time your ICP shifts, a new product launches, or positioning changes, you're rewriting prompts and debugging fragile workflows. 60% of your time goes to maintenance instead of building.
Octave is the GTM repo that Clay has been missing. It provides a structured, versioned, API-accessible model of your GTM knowledge—ICP definitions, personas, use cases, value props, proof points, competitive context—that Clay consumes at runtime. Clay handles execution and flow control. Octave provides the strategic context. One source of truth, consumable everywhere. Workflows that are declarative instead of procedural, resilient instead of fragile.
Top Use Cases
Automated Outbound with Shared Context
Clay workflows pull messaging context directly from Octave's Library:
- Persona-specific pain points and value propositions
- Relevant use cases and product angles
- Proof points and competitive framing
Generate emails, sequences, or agent inputs grounded in your actual positioning—not a prompt someone wrote six months ago. When messaging evolves, every Clay workflow reflects it automatically. No find-and-replace across tables.
Lead Qualification & TAM Scoring
Instead of black-box scoring rules, Clay references Octave's living ICP model to:
- Classify leads and accounts with natural language qualifiers
- Score accounts against your true TAM definition
- Expose exactly why a lead scored the way it did
As your ICP evolves, qualification logic updates upstream. Toggle qualifiers on or off—no formula debugging, no model retraining. PMMs can refine targeting criteria in plain language; Clay workflows stay aligned without GTM Engineer intervention.
Automated Research & Call Prep
Clay uses Octave’s context to generate structured rep-ready research, including:
- Account summaries tailored to your ICP
- Persona-relevant talking points
- Recommended positioning and proof points
This makes call prep faster, more consistent, and easier to scale — especially for teams supporting high-volume outbound or AI-assisted sales motions.
Clay is a powerful execution engine. Octave is a shared GTM brain. Used together, they form a clean separation between what the business believes and how automation runs.
For GTM teams, this means fewer brittle workflows, less duplication, and systems that evolve as fast as your strategy does

