Octave's context graph models what you sell, who needs it, and why. It connects buyer pains to the outcomes they want and the capabilities you offer, giving your team and agents a shared foundation for deciding what matters in each deal.
Thousands of users at leading companies including
Your GTM strategy, built for agents
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
Thousands of users at leading companies including
Heading
Production-ready, beyond the first build
Context infrastructure is like a free puppy: getting it is the easy part. Then come permission changes, broken integrations, and new requirements every time your strategy evolves.
Octave includes
Version control, user permissions, auditable changes, workflows for updating and extending your graph, authoring tools that generate context variations, integration maintenance, and SOC 2 audited controls.
Learn more about the pitfalls of DIY context →Entity layer: Start with the business you know
Your library defines what you sell — products, services, and solutions — and who you serve through personas and segments. Use cases, competitors, alternatives, objections, and proof complete the picture.
Each entity has a specific role. Together, they capture where you believe you fit and the case you can make to each buyer. Learn more about entities →
Add custom entities, properties, and tags to match the model to your business.
Concept layer: Give shared ideas a shared meaning
Octave decomposes your entities into shared atomic concepts: buyer pains, desired outcomes, and product capabilities.
The same pain can connect several personas to capabilities across multiple products. Typed, directional relationships describe how those concepts connect, with a rationale for each link. Your agents can follow why a capability matters to a particular buyer.
Example: Finance leader (persona) experiences Manual reconciliation (pain), which is addressed by Automated matching (product capability), which enables Faster close (desired outcome).
Motion layer: Match the message to the buying situation
Above the entity layer, playbooks combine your offering with specific personas and segments to guide the message.
Motions adapt that guidance for the way you’re selling. A net-new opportunity needs a different approach from an expansion or a push to displace an incumbent.
Connect your ontology to real deals
Your context graph connects your strategy to the accounts and contacts in your CRM.
When you have a prospect call, Octave’s Intelligence Engine resolves who is speaking and maps their comments to your graph. That connects individual buyer needs to patterns across similar personas, segments, and use cases.
A playbook messaging cell combines
Offering
Project management SaaS product
Persona
CMO
Segment
Financial services company
Motion
Displace an incumbent competitor
Suggestions: Keep your strategy grounded in the market
Suggested updates
Surface as new evidence challenges or extends your strategy. Octave's Intelligence Engine analyzes daily customer interactions alongside market trends and competitor news.
Authorized teammates
Approve or reject changes through MCP or the Octave UI, so your strategy evolves with evidence while your team controls what changes.
Significance thresholds
Help distinguish meaningful patterns from noise, comparing incoming evidence with your context graph to find gaps and contradictions worth reviewing.
Learn about the context graph's other half