R

Robin AI

The models are the product. Review, redlining, the Word add in's Ask, Draft, Edit and Research modes, clause level risk analysis and repository search are all generative or machine learning capabilities. The vendor states a training base of more than 4.5 million legal documents and 100 million legal clauses. One qualification applies: the company also sells Managed Services combining the software with human legal review, so part of what it sells is people. The software product itself is model driven throughout.

Accuracy is asserted without measurement. Grounding exists in outline. The Word add in's Research mode is described as enhancing answers with authoritative, current information from a curated set of trusted legal sources on the web, and review output is clause level with risk flags tied to company standards. No accuracy figure, hallucination rate, test set or evaluation method is published, and nothing describes how retrieval reaches those trusted sources or how a reader opens and verifies one.

The headline claim across vendor material is a speed figure, 80 to 85 percent faster review, rather than an accuracy figure.

A real published commitment has the models working alongside a supervising lawyer, with documented review surfaces and no full control structure. The Word add in surfaces clause level recommendations as tracked changes, comments or highlighted text based on company standards, which a lawyer accepts or rejects in place. The four modes separate asking from drafting from editing, so the user chooses the level of intervention.

The Managed Services line puts the company's own legal professionals in the loop as a paid option, a literal form of oversight. Not located: any threshold at which the system defers, what it does on its own, and what the vendor commits to when an output is wrong.

Customer logos and press mentions stand in for evidence, with results quoted from an internal source. A customers page exists and press logos including the Financial Times, Bloomberg, Forbes and CNBC are displayed prominently, alongside investor logos including Google, Temasek and PayPal. The most specific published figure, review completed over 85 percent faster, is attributed to the vendor's own internal legal team testing its own add in rather than to a customer.

Searched the site, the customers page, the news and blog indexes and the guides and reports index and located no named customer deployment carrying figures, a date and an assessable method. Press coverage and investor backing are not deployment evidence.

Confidentiality is asserted in general terms, and the one commitment that matters carries a qualifier that changes it. The security page states that customer data will not be used for model training, fine tuning or other feature development without express consent. That is permission gated by consent rather than a prohibition. Real controls are published: AES-256 at rest, current TLS in transit, and a statement that data never leaves the vendor's AWS environment.

Not located: handling of attorney client privilege or work product, any segregation model between customers, users or matters, and any retention or deletion terms. For a product whose core use is taking in counterparty contracts at volume, the absence of a segregation statement is material.

The audience is lawyers and legal teams, and the terms carry a standard structure, but no position on the advice line is published. The site, the platform and services pages, the published terms and the privacy policy, searched, showed no statement on advice versus tooling, no treatment of competence or supervision duties, and no jurisdiction limits. That is despite the company operating across the UK, US and Singapore and marketing to multiple jurisdictions.

The Managed Services line, in which the vendor's own legal professionals review work for customers, raises the advice question more sharply than a pure software product would, and nothing published says how that service is scoped or supervised.

No governance position for model behavior is published: no named internal owner, no pre release testing regime, no published responsible AI or AI governance framework, no AI specific certification such as ISO 42001, and nothing on uneven output across matter types, parties or populations. The vendor publishes real security governance, which is a different subject.

A generic security posture covers the product without addressing what happens to documents and prompts after processing. Published and real: AES-256 at rest, current TLS in transit, security built into the development lifecycle, data replication across geographic locations with disaster recovery exercises and automated failover, and named monitoring tools in AWS CloudWatch, CloudTrail and Datadog. That is operational security described in useful detail.

Not located: any retention period for documents or prompts, any deletion control, a named subprocessor list, and an incident or breach notification practice. Anthropic and AWS are named as partners on the security page, which partly discloses the supply chain but is not a subprocessor list.

Liability is addressed only through published terms carrying a standard limitation structure. Terms and a privacy policy are published openly, so a buyer can read the allocation of loss before entering a sales process, which keeps this above a pure absence. Searched those documents, the security page and the trust center entry point and located no indemnity running to the customer for third party claims arising from output, no warranty on output, no stated liability cap figure and no insurance position.

Worth noting that the Managed Services line involves the vendor performing legal review work, which raises a distinct recourse question that published material does not address.

Integrations are claimed without documentation an implementer could use. The Microsoft Word add in is real, documented at user level in Robin University, and is the primary surface, alongside a browser application with a searchable executed contract repository. Beyond Word, third party sources describe CRM and CLM integration but no vendor integrations page is published, and no named connector for document management, contract lifecycle or e signature is published on the property.

A third party review notes limited file format support beyond Word documents. Nothing published describes what any integration moves, in which direction, or what an administrator configures.

Cloud delivery is stated, and neither the tenancy model nor the region is. The vendor says data never leaves its AWS environment and is replicated across multiple geographic locations for disaster recovery. That is a resilience statement rather than a residency one, and it arguably cuts against a customer wanting data confined to one jurisdiction. Not located: any named region, any residency the customer can choose, any tenancy model, and any statement of where processing happens as distinct from storage.

Other sources mention private cloud deployment options, which is not vendor material. For a UK founded vendor selling into the UK, US and Singapore, published residency options would be expected.

Certification is real and stated with an open access route, without scope or evidence. ISO 27001 and SOC 2 are both named as certified and GDPR compliance is stated. A trust center is published at a stable URL as a self serve route rather than a sales gate. Not located: any coverage period, audit scope, report date, SOC 2 type or named auditing firm. The security page writes ISO without a number in one place and ISO27001 in another.

The certification is stated clearly enough elsewhere that this reads as loose copy rather than a problem with the claim.

The vendor names a partner without disclosing the supply chain. Anthropic and AWS are both named as partners on the security page, and other coverage describes collaboration with Anthropic and AWS to build secure models, so a reader can infer the likely model provider. But naming a partnership is not the same as stating which model serves which task. Not located: which models are used in production, where they run, whether any other provider is involved, a subprocessor list, or any commitment to notify customers when the supply chain changes. The partner logo invites an inference that the published material does not confirm.

No pricing page exists, no rate is published, no unit of charge is stated and no tier structure appears. Every commercial path ends in a demo request. Vendor material refers to a free account with add in access and paid accounts with playbook customization, and tells buyers to speak to a member of the team to learn what paid accounts include, so even the split of features between free and paid is not published. Other sources describe subscription pricing without figures.

Coverage is claimed broadly without evidence that the breadth is real. Vendor material addresses in house legal teams, law firms and corporate clients across multiple jurisdictions. The practice focus is clearly contract work: review, drafting, negotiation and tracking obligations after signature, with other sources naming NDAs, service agreements, procurement and employment agreements. Offices are published in London, New York and Singapore.

No segmentation a buyer could use is published. There are no pages by firm size, industry or role, no statement of which practice areas or team sizes the product is built for, and no statement of what it is not built for. The customers page exists but does not resolve the segments claimed.