Skip to main content

​
How the Library works

The Library is Octave’s central knowledge graph. It stores everything your GTM team knows — your ICP definitions, buyer personas, competitive positioning, messaging, proof points, objections, motions, and reference customers — as structured entities that AI agents and workflows can query at runtime. Every library entity is workspace-scoped (each customer has their own), searchable via full-text and semantic search, versionable to track changes over time, and interconnected through typed relationships. When you run an Octave agent, it pulls context from the Library to generate relevant, accurate output grounded in your actual strategy — not generic templates. This is what separates Octave from tools that rely on prompt engineering alone. The agent reads your strategy, selects the relevant entities, and generates output that reflects your positioning, your proof points, and your competitive differentiation for each specific prospect.

​
Entity types in the Library

The Library contains the following entity types. Each serves a distinct role in your go-to-market strategy:
EntityWhat it representsExample
OfferingsWhat you sell — Products, Services, and Solutions”Octave Platform”, “Implementation Service”, “Enterprise GTM Solution”
PersonasBuyer and user profiles”VP of Sales”, “GTM Engineer”
Use CasesProblems your offering solves”Automate outbound sequencing”
SegmentsTarget market verticals”Enterprise SaaS”, “Healthcare”
MotionsGTM strategies binding offering, narrative, and persona×segment cells”Enterprise Healthcare Net-New Motion”
Proof PointsStats and validations”58% cost-per-meeting reduction”
CompetitorsCompetitive vendors”Lavender”, “Unify”
AlternativesNon-product substitutes”Manual spreadsheets”, “Do nothing”
Buying TriggersPurchase readiness signals”Series B fundraise”, “New CRO hire”
ObjectionsRecurring pushback with reframe and response”Too expensive”, “We’re doing this in-house”
ReferencesCustomer success stories”Acme Corp — 3x pipeline in 90 days”
Playbooks are deprecated and have been replaced by Motions.

​
How entities connect

Library entities are designed to reference each other. Offerings — Products, Services, and Solutions — define what you sell. Personas define who buys and uses them. Use Cases describe the problems they solve. Segments identify where to find those buyers. Motions bind these together into executable strategies — each Motion contains Motion Playbooks (narrative angles) and Motion ICPs (persona×segment cells with their own narratives, learnings, and recommended evidence). Alternatives, Competitors, Buying Triggers, and Objections cover the full surface of what stops or starts a deal, and the analytics layer feeds real conversation evidence back into every one of them. When an agent runs — whether it’s qualifying a prospect, generating a sequence, or prepping for a call — it traverses these relationships to pull the right context for that specific situation. The agent doesn’t guess. It reads your strategy. The analytics pipeline closes the loop: every call, email, and deal outcome flows through Events → Findings → Insights → Reports, with findings linked back to the Library entities they reference so your strategy evolves with what’s actually happening in the market.

​
What makes the Library different from a CRM

A CRM stores account and contact records. The Library stores your strategy — the reasoning behind who to target, what to say, and why your offering wins. CRM data tells you Acme Corp has 500 employees and is in Series C. The Library tells you that Series C SaaS companies with a new CRO are your highest-converting segment, that they care about time-to-pipeline, that your strongest proof point is the 58% cost-per-meeting reduction at a similar company, and that the objection you’re most likely to hear is “we just hired BDRs to do this in-house” — along with the reframe that works. Agents need both. But without the Library, they’re just doing enrichment. With it, they’re executing your strategy.