Octave

Remove the model layer and what remains is a wiki, and the vendor makes that argument itself rather than leaving it to be inferred. Its framing is that before this product a company's positioning lived in decks, documents and tribal knowledge, which is precisely the non generative version of the same thing, and the whole pitch is that structure without generation was never the problem.

Every named surface is generative or inferential: a builder that composes plays, a studio that writes messaging for each stage, managed agents for research, qualification and sequencing, a profile agent drawing insight from calls, emails and deals, and a graph that supplies context to other systems. The commercial model settles it, because the metered unit is credits consumed when agents run and when the system learns, and the platform fee buys the learning layer itself. This is a model native company by construction, not a document store with generation attached.

The oversight here governs what the model may read, and it is documented properly, which is a genuinely different answer from most of this index. Every offering, element and playbook carries an active or inactive state, and the vendor explains what that means: active pieces are turned on in the brain so the system learns from them and uses them when agents run, inactive pieces are turned off and unavailable.

Whole workspaces carry the same switch, and an inactive workspace is archived with its programmatic access disabled. Alongside that sit version control with full history on the library, workspaces described as distinct isolated areas each with their own access key, and role based access control at the top tier. A buyer can therefore say precisely what the agents are allowed to know.

Held off the top band on the other half of the axis: the input side is governed and the output side is undescribed. No approval queue, escalation threshold, containment rule or record of what an agent produced and acted on appears anywhere read.

One line in the pricing explanation implies more configurability than any other vendor in this block offers and still names nothing. Credits are consumed per agent run at a rate that depends, in the vendor's own words, on that agent's configuration and its model settings, which means models are selectable per agent. No provider, family, version, hosting arrangement or default is stated anywhere on the pages read.

A distinction worth drawing carefully, because the site invites the confusion: the named assistant products appearing in the navigation and the launch banner are consumers of this vendor's context rather than the models powering it, so a reader should not mistake a plugin for a disclosure. Public technical documentation exists at its own subdomain and was not read, and it is the flagged item most likely to move this row.

Two customers appear by name on the pricing page with attributed quotes, one of them carrying two quantified results, pipeline per marketing dollar up a hundred and thirty percent and pipeline per representative up a hundred and twenty two percent, linked through to a full case study. The second is a named revenue leader at a company that also appears in this index, with the company mark shown. A customer library sits behind them.

What lifts this above the ordinary is a caveat the vendor kept rather than cut. The quantified quote opens by attributing the gain to the customer's broader artificial intelligence transformation and then says this product's context made it possible, so the customer themselves scopes the claim to a wider programme and the vendor publishes it that way. Most vendors would edit that clause out. Held off the top band because two named customers is a thin base, neither figure carries a period, denominator or method, and the case study library was not read.

This product writes and does not send, so the axis reaches only part way, and the part it does reach goes unaddressed. Sequences across email, professional network and call scripts are generated here and then executed elsewhere, through the sequencers, orchestration tools and systems of record this platform connects to, which puts the sending obligation squarely on the customer and their other vendors.

What would still be gradeable is whether the generation layer carries any guardrail of its own, a statute referenced, a consent assumption stated, a suppression concept, or any constraint on what the messaging engine will write for a given jurisdiction, and none of that was located. A messaging system of record that governs what an entire company says to prospects is an unusually good place to put such a constraint, and no page read describes one.

The shelf is complete and properly signposted and it was not read, so this row records a flag rather than a judgement on contents. A privacy policy, a terms of service and a data processing addendum each sit at their own route in the footer, and a trust centre runs on its own subdomain. What raises the stakes is what the product ingests.

The profile agent is described as drawing autonomous insight from every call, every email and every deal, and the native connections run to two systems of record and a conversation intelligence platform, so recorded customer conversations and full deal histories flow into this system by design. Lawful basis, retention, sub processor identities, transfer mechanism and data subject routes were none of them established. Reading the addendum is the highest value check available on this vendor.

The core of this product has cleaner provenance than almost anything in its category, and two layers around it do not. The clean core is that the context originates entirely with the customer, their own site, their own positioning, their own calls and deals, and the vendor claims no contact database of its own.

An independent review states the point plainly, that there is no native lead data or enrichment here and a separate data layer is required, which is a limitation the vendor turns into an architectural virtue. The two unaddressed layers are real all the same. A prospector agent and an enrichment agent both ship as managed products, and where either sources what it returns is never stated, whether from the customer's own connected orchestration tool or from somewhere else. And real time market and competitive intelligence is sold as an inclusion at the top tier with no source, method, refresh cadence or licensing position attached to it anywhere.

Exposure is low by architecture and the attachments are official throughout. Nothing scrapes, rents an identity, rotates accounts or ships a browser extension. Connections run natively to two systems of record, a conversation intelligence platform and a data orchestration tool, all of them products the customer already licenses rather than surfaces worked around.

Outbound, the vendor publishes a versioned programmatic interface with technical documentation at its own subdomain, a protocol server, a command line kit and a plugin for a named agent runtime, which is deliberate integration rather than improvised access.

Held off the top band because no conformance position is stated for any connected platform, and because the prospector agent's method of acquiring what it returns is undescribed, which is the one place in this architecture where a platform question could arise unnoticed.

The stewardship question is sharper for this vendor than for most in this index, and the sharpest statement of it comes from a customer. Asked what the product holds, a named revenue leader answers that their understanding of their own market, the problems, the signals and the language, is their codebase, and that this is where they store it, version it and operationalise it.

The vendor agrees in its own terms, describing a self learning context layer and charging credits for the moments when the system learns. So the most proprietary asset a go to market team owns is deposited here by design. One structural answer is on record: workspaces are described as distinct and isolated with their own access keys, which addresses separation between a customer's own clients.

Whether learning stays inside a workspace, or whether the platform's brain improves for everyone from what any one company teaches it, is addressed nowhere on the pages read, and the processing addendum that would say so was not opened.

The generation happens here and the contact happens somewhere else, which splits the question and leaves the answerable half unanswered. Messaging for email, professional network and calls is composed by this platform from the customer's positioning and the prospect's context, then handed to a sequencer or an orchestration tool to deliver under a human representative's name.

No position is taken anywhere read on whether a recipient learns that the words were generated, which is the European obligation now in force for systems interacting with people, and the marking duty under that regime rests principally with the provider of the system rather than the deploying customer.

Held at this band because nothing manufactures an identity, substitutes a sender or celebrates concealment, and because the vendor's own framing is about accuracy of positioning rather than about seeming human.

The deepest programmatic surface in this index, and it earns the band because the integration surface is the product rather than an attachment to it. The vendor's entire thesis is that go to market context should be readable by every other system, and it ships accordingly: a versioned representational state transfer interface with public technical documentation at its own subdomain, five distinct interface surfaces enumerated as product rows covering agents, reading, the library, playbooks and workspaces, a protocol server for supplying context to any tool or agent, a command line kit, a plugin for a named agent runtime with a published skill set, per workspace access keys, and a data warehouse route as a named option.

Native connections run to two systems of record, a conversation intelligence platform and a data orchestration tool. A learning subdomain and a documentation subdomain both exist. The qualification, and it is real for a smaller buyer: the protocol server sits above the free tier, the system of record connections are reported as top tier only, and the free tier's interface access is narrow.

Hosting provider, country, region and residency options are absent from every page read, and the trust centre that would ordinarily carry them was not opened, so this row is flagged rather than settled. The corporate identity that is on record is thin but real: a named incorporated entity in the site footer, a dated funding round with named investors, and a professional network presence.

What a buyer would want against that is a jurisdiction, because this platform holds recorded conversations and deal histories drawn from connected systems, and because a data warehouse route implies the customer's own storage sitting somewhere specific in relation to the vendor's. Neither the origin nor the destination of any of it is stated.

A trust centre runs on its own subdomain and is linked from the footer of every page, which is the arrangement that separates a real security posture from a paragraph of assurance. Two marks sit beside it in the footer, an accounting body's service organisation control seal and a compliance platform's type two badge, and in product the vendor names federated sign on and role based access control as features rather than as promises.

Workspace level access keys give a further isolation boundary. The pricing philosophy line is worth recording because it makes a commitment most vendors avoid, that a buyer pays for intelligence and never for seats or security. Held off the top band because the trust centre contents were not opened, so no audit date, period, auditor, penetration test evidence, sub processor list or status page could be verified, the type is asserted by badge rather than in prose, and no responsible disclosure route was located. One tension a buyer should notice: security is promised as never chargeable while federated sign on and role based access control appear only in the top tier's inclusion list.

The published model is stated clearly and the numbers a buyer needs are mostly absent, which produces the failure mode this index has recorded before: apparent transparency that does not survive an attempt to budget. The structure is explained well, a flat platform subscription for the always on context layer plus metered credits consumed when agents act and the system learns, and the vendor is explicit that it does not charge per seat. Past that it thins out.

The served pricing page carries exactly one figure, fifteen hundred dollars a month starting, billed annually, for the top tier, and the comparison table beneath it enumerates allowances across three columns without attaching a price to the other two. The metered unit is undefined by the vendor's own account, since each agent consumes a different amount per run depending on its configuration and model settings, so nobody can convert an allowance into a quantity of work.

Bulk credit packs, engineering services and the warehouse route are named as additional and unpriced. And a buyer researching this vendor will find independent listings from earlier the same year reporting an entry tier at a tenth of the current published floor and a middle tier carrying twice the credits now shown, none of which reconciles with the page as it stands.

Portability is a named product capability rather than a contractual afterthought, and it reaches further down the ladder than usual. Exporting artefacts appears as a feature row available on every tier including the free one, version control with full history sits alongside it, and the library is retrievable programmatically through interfaces covering reading, the library itself, playbooks and workspaces. A data warehouse route is offered as an additional option at the top tier.

For a product whose whole value is a structured asset the customer builds, being able to read that asset out through an interface is the right answer to this axis, and the vendor gives it. Held off the top band on the contractual half and one practical limit. No post termination right, deletion timeline or retention period was located, and the terms and processing addendum were not read. And an independent review reports the export format as limited to a single document type, which for a versioned structured library is a lossy way out.

This platform sends nothing, so the axis reaches only as far as the structural note allows on a layer that composes rather than delivers. Sequences and messages are generated here and dispatched by the sequencer, orchestration tool or system of record the customer connects, which means sender reputation, warmup, volume governance, complaint handling and authentication all sit with those products rather than this one.

What is worth recording is the second order effect a buyer should think about, because it is specific to this architecture. A context layer that makes it fast to produce tailored messaging for ten accounts or ten thousand, in the vendor's own framing, removes the effort that used to limit volume, and nothing here carries a stated view on the pacing or restraint that ought to replace it downstream.

The buyer is described by function with unusual precision. Six roles each get their own page, marketing, growth and demand generation, engineering for go to market, revenue operations, sales and product marketing, and six use cases are laid out the same way, so a reader can locate themselves quickly and can also see that this is bought by several functions rather than one.

Workspaces are explicitly positioned for agencies running separate clients, users are unlimited at the top tier, and a customer library and a company manifesto fill in the rest. Held off the top band because the coverage half stays qualitative.

No employee or revenue band attaches to any tier, no region, industry or language coverage is stated, the count of teams using the product appears in a funding announcement rather than on the site, and there is no statement of who this would be wrong for. The published entry point functions as a de facto segment statement, and the pages never make that explicit.