Octave

A short named connector set is documented, Salesforce, HubSpot, Gong and Clay, with Octave pushing positioning and messaging into those tools and Clay tables pulling live context back out. The platform's role is to supply context rather than to act; it is explicitly not a data or enrichment provider, and what it writes is messaging and strategy rather than authenticated operations in the buyer's systems.

Sourceoctavehq.com integrations sectionread 2026-09-01

Multiple agents run as one flow: the help center documents chained runs such as Qualify Then Sequence and Enrich Then Sequence, where one agent's output feeds the next, and agents are deployed into the buyer's own orchestrators (Clay, n8n, Zapier, Cargo) to run across full lists (learn.octavehq.com agent, MCP and orchestrator sections).

Sourcelearn.octavehq.comread 2026-10-01

Grounding is the entire product: it encodes your ICP, personas, use cases, proof points, and competitive positioning into a structured, queryable GTM brain that grounds every agent output and serves that context to other tools, a comprehensive knowledge grounding capability.

Sourceoctavehq.comread 2026-10-01

The customer bounds what the agents say: the Library and context graph the team authors, with version control and governance, is the source every agent draws on, and a test run shows what an agent will produce before it is deployed. No step where a person approves an agent's output or action before it is used is documented (octavehq.com and learn.octavehq.com).

Sourceoctavehq.comread 2026-10-01

The pricing page lists SSO plus RBAC on the Ultra plan, and the site footer carries SOC 2 Type II and AICPA SOC badges, so identity integration and a named role model sit beside a held attestation. Both are thinly documented: the access controls appear as a plan line rather than admin documentation. A trust center sits at trust.octavehq.com, but the SOC 2 report's scope and date are not published.

Sourceoctavehq.com/pricingread 2026-09-30

The help center documents an Activity Feed that surfaces agent runs and engagement events, so a team can see which agents ran. The documentation does not describe the feed showing a run's inputs, steps or tool calls, so what each agent did cannot be reconstructed (learn.octavehq.com index and help center).

Sourcelearn.octavehq.com/llms.txtread 2026-10-01

Nothing describes an agent retaining context from one sequence or research task to the next, and no scope or lifetime for agent memory appears. The Library, which the vendor calls the brain's memory, is the structured corpus of the customer's own strategy that every agent retrieves from, which makes it grounding rather than agent memory.

Sourcelearn.octavehq.com Library documentation and octavehq.com brain descriptionread 2026-09-01

Delivered only as a cloud SaaS platform with no self host, on premises, or in VPC deployment option documented.

Sourceoctavehq.comread 2026-10-01

A named set of prebuilt agents a buyer picks from, each a whole job: the Prospector, Enrichment, Qualification, Sequence and Call Prep agents, which the help center documents one by one and which run as pre built or saved agents from the app, the API or MCP, alongside a Skills Library. Remove any one and the others still stand (learn.octavehq.com agent and MCP sections).

Sourcelearn.octavehq.comread 2026-10-01

Agents run when someone calls them: from the in app playground, through the API or MCP, or from the buyer's own orchestrators (Clay, n8n, Zapier, Cargo), whose triggers belong to those tools. No event, schedule or webhook of Octave's own that wakes an agent is documented, and no market shift detection appears on the current pages (octavehq.com and learn.octavehq.com).

Sourcelearn.octavehq.comread 2026-10-01

The Sequence agent offers a stated choice of three model options, Pulse (simple offers, lowest cost), Echo (typical use, mid cost) and Harmony (complex context, highest cost), but names no model maker behind them, so the customer chooses a cost and quality tier rather than among providers (learn.octavehq.com Sequence agent section).

Sourcelearn.octavehq.comread 2026-10-01

The platform is built to be consumed from outside, and that is its stated purpose. An MCP server serves the customer's live personas, messaging and competitive intelligence to other agents and tools so context does not have to be hardcoded, which the vendor presents as a headline capability rather than an add-on. Alongside it sit a composable API with per-workspace API keys and an enterprise API tier, and a documentation site at learn.octavehq.com.

Sourceoctavehq.com MCP and API sections, learn.octavehq.comread 2026-09-01

Sequences carry a test configuration step, so a customer can run a sequence in test mode before it goes out, and messaging effectiveness is reported back so teams can iterate on positioning. No criterion is applied; nothing documents a scored comparison between message or playbook versions, a holdout, a pass condition that gates release, or an evaluation harness, so what exists is a preview plus after-the-fact feedback.

Sourcelearn.octavehq.com sequence configuration documentationread 2026-09-01

No action on an interface the vendor does not control is documented.

The prospector agent researches and contextualizes accounts, but the vendor states plainly that Octave is a strategy and context platform rather than a data or enrichment tool and does not supply verified emails, phone numbers or buying signals, so the research is reasoning over the customer's Library and account context rather than crawling the open web for records.

Distribution runs over an API and an MCP server, which are programmatic routes. No hosted or local browser, desktop session, remote computer control, scraping or third-party browser engine appears anywhere.

Sourceoctavehq.com product and positioning pagesread 2026-09-01