Aimdoc

The first A on this axis in the index, and it is earned by construction: the product is a conversational agent and there is no non AI remainder. Remove the model and nothing is left to sell, because the entire value is an agent that ingests a company's site and documents in minutes and then holds qualifying conversations with strangers.

What the AI does is documented rather than gestured at: ingestion of website content and uploaded material, question answering grounded in it, qualification against customer defined criteria, meeting booking, escalation triggers, session transcripts, intent capture and lead scoring.

The autonomy boundary is described in useful terms. The agent runs unsupervised against live visitors, but within customer defined qualification criteria, and the handover model is explicit: the agent recognises when a person is needed, notifies the team in Slack, and passes the conversation to a human. Routing to the right representative is rule based. What is not documented is containment. Nothing states what a misbehaving agent can commit to, what it is prevented from saying about price or product, or what stops a bad session once it is live in front of buyers.

Grounding is described, in that the agent is trained on the customer's website, documents and FAQs and suggests answers for gaps found in real sessions, which is more than nothing. The stack is not. No model or provider is named anywhere public, no version or update policy is stated, and the lead scoring logic that decides which conversations reach a representative is unexplained. A buyer cannot tell what is producing the words their prospects read.

A case study library and an ROI calculator exist, and the testimonial volume is high, but what is published is enthusiasm rather than measurement. The claims located run to increases in leads and bookings exceeding expectations and the tool paying for itself, with no conversion rate, no lift against a stated baseline, no sample and no period.

For a product whose whole promise is converting a known quantity of existing website traffic, a measured conversion rate against a holdout is the obvious evidence, and it is the one thing not offered.

Mostly inbound, which narrows the regulated surface: the visitor initiates and the agent responds. The product does extend to personalised outreach agents reachable by public link that customers place in emails, and nothing published addresses the sending obligations that come with that, or how consent captured in a chat session propagates into a customer's marketing suppression. No public enforcement action located.

Stronger than most vendors of this size and short of the top band on the question that matters here. Published: standard data processing agreement availability, data subject access request support, international transfer mechanisms, data minimisation and deletion of customer data on request. The gap is lawful basis for the people this product exists to identify.

The company markets anonymous visitor identification and account identification, and its published privacy documentation is a third party generated policy that says nothing about the basis on which an unidentified website visitor is resolved to a person or an account.

The knowledge side is unambiguous, since the agent is grounded in the customer's own website and uploaded documents. The identity side is not. Anonymous visitor identification and account identification are marketed capabilities, and no public material states where the identity resolution data comes from, whether it is licensed, contributed or reverse looked up from network signals, or who stands behind it. A buyer inherits that question along with the product.

Low exposure. The agent runs on the customer's own web property and inside the customer's own application, and reaches CRM, calendar and messaging systems through their documented interfaces. No automation of a third party network that prohibits it. No conformance position of its own is published, so the grade rests on architecture rather than a stated commitment.

The security program covers deletion on request, audit logging and least privilege access, which is the operational half. The cross client half is unanswered. Nothing published states whether visitor conversations, the questions prospects ask or the knowledge bases customers upload inform models or improvements that serve other customers, and no opt out or contractual exclusion is documented. For a product that describes its AI as continuously learning from successful interactions, that is precisely the question a buyer should ask before pointing it at their pipeline.

Nothing published states whether a website visitor is told at first contact that they are talking to software. The product ships configurable agent voice and persona across formal, casual and professional registers, and the customer testimonials the company features praise how human the agent feels, which is the marketing frame rather than a disclosure position.

Under the European Commission's final Article 50 guidance, in force since 2 August 2026, a system interacting directly with a person must disclose its artificial nature at first contact in the interface, and the obligation falls principally on the provider rather than the deploying customer.

Specific rather than logo listed: named object level behaviour in the major CRMs, creating and updating contacts, companies and deals in one and leads, contacts and opportunities in the other, plus calendar booking, Slack escalation notifications, webhooks and a REST API, with a public documentation site and an integrations page. Notably it also publishes an MCP server and a public agent gateway endpoint, so an external agent can query the sales agent directly. Depth thins on sync direction, field mapping and failure behaviour, which are not documented before purchase.

Multi tenant cloud described as running on the edge for response speed, which is a performance statement rather than a residency one. No hosting region, no European residency option, and no statement of where conversation transcripts and uploaded knowledge bases are stored. The security page refers to international transfer mechanisms where applicable, which acknowledges the question without answering it.

Genuinely good for a company this size. SOC 2 Type II certification is claimed with a dedicated trust portal, and the security page documents practice beyond the badge: background checks and security training, least privilege and role based authorisation, change management with peer review, vulnerability management, business continuity and incident response, TLS 1.2 and above in transit with encryption at rest, segregated production, secrets management, and backups with restore testing. Short of the top band on two points: the trust centre requires requesting access rather than serving documents, and no audit date or report recency is visible to an outsider.

An entry price is published, at 999 dollars a month for the first tier, alongside a 14 day free trial and an ROI calculator, with the two upper tiers quote only. One mechanical detail is worth a buyer's attention and is unusual enough to record: the pricing page renders its plans client side, so the served page reads as loading and the only price in the fetched document sits in the meta description. A vendor that publishes an MCP server and an agent gateway so machines can talk to its sales agent has left its own prices unreadable to a machine fetching the page.

Deletion of customer data on request is committed to on the security page, which covers one half of offboarding. The other half is missing: no documented export path for conversation transcripts, captured leads, intent data or the knowledge base a customer has built, no post termination data rights, no deletion timeline, and terms of service delivered through a third party policy generator rather than as negotiated commercial terms.

Sending is peripheral to a product that mainly answers rather than initiates, but it is not absent: personalised agent links are distributed by email and meeting confirmations flow to prospects. No sending infrastructure, authentication guidance or reputation practice is documented. Deliverability is neither claimed nor addressed.

The intended buyer is clear and the packaging corroborates it: business to business software companies with meaningful existing website traffic and a trial motion, positioned explicitly against the inbound conversion incumbents, with an entry price that rules out the smallest teams. A case study library and customer page back the claim. Geographic and language coverage is the gap, with no stated regional support, no language list for agent conversations, and no indication of where implementation help comes from.