Robin AI

AI Centrality

How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.

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's stated training base is more than 4.5 million legal documents and 100 million legal clauses. One qualification worth recording rather than discounting: the company also sells Managed Services combining the software with human legal review, so part of what it sells is people. The software product graded here is nonetheless model driven throughout.

Citation Accuracy and Hallucination Disclosure

Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.

Accuracy is asserted without measurement. Published grounding exists in outline: the Word add in has a Research mode described as enhancing answers with authoritative, up to date 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. What is not published is what makes this axis work: no accuracy figure, no hallucination rate, no test set, no evaluation methodology, and no description of 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. Searched the site, the platform pages, the security page, Robin University and the guides and reports index on 29 Aug 2026.

Autonomy and Oversight Model

What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.

A real published commitment that the models work alongside a supervising lawyer, with documented review surfaces, short of the full control structure. The Word add in is described as surfacing clause level recommendations as tracked changes, comments or highlighted text based on company standards, which a lawyer accepts or rejects in place, and the four modes separate asking from drafting from editing so the user chooses the level of intervention. The company's Managed Services line puts its own legal professionals in the loop as a paid option, which is an unusually literal form of oversight. Not located as of 29 Aug 2026: any threshold at which the system defers, what it does on its own, and what the vendor commits to when an output is wrong.

Operational and Outcome Evidence

Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.

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 on 29 Aug 2026 and located no named customer deployment carrying figures, a date and an assessable method. Press coverage and investor backing are not deployment evidence.

Privilege and Confidentiality Posture

How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.

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 a consent gated permission rather than a prohibition, and it is the weakest training position located on this index so far. 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 as of 29 Aug 2026: attorney client privilege or work product handling, any segregation model between customers, users or matters, and any retention or deletion terms. For a product whose core use case is ingesting counterparty contracts at volume, the absence of a segregation statement is material.

UPL and Professional Responsibility Posture

Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point.

The intended audience is lawyers and legal teams and the terms carry a standard structure, but no position on the advice line is published. Searched the site, the platform and services pages, the published terms and the privacy policy on 29 Aug 2026 and located no statement on advice versus tooling, no treatment of competence or supervision duties, and no jurisdiction limits, 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 perform review work for customers, raises the advice line question more sharply than a pure software product would, and nothing published addresses how that service is scoped or supervised.

AI Governance and Bias Disclosure

Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

Searched the site, the security page, the trust centre entry point, the platform pages, the blog, the news index and the guides and reports index on 29 Aug 2026. No governance position for model behaviour was located: 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. Rebuttable with a single link.

AI Safety and Data Stewardship

Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.

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 integrated through the development lifecycle, data replication across geographic locations with disaster recovery exercises and automated failover, and named monitoring tooling in AWS CloudWatch, CloudTrail and Datadog. That is operational security described at a useful level of detail. What this axis asks for and did not locate as of 29 Aug 2026: 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 is a partial supply chain disclosure rather than a subprocessor list.

AI Liability and Recourse

What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.

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 centre entry point on 29 Aug 2026 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.

Practice Systems Integration Depth

How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.

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 was located, and no named connector for document management, contract lifecycle or e signature was located on the property as of 29 Aug 2026. 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.

Deployment Model and Data Residency

Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.

Cloud delivery is stated and neither the tenancy model nor the region is stated. The vendor publishes that data never leaves its AWS environment and that data is replicated across multiple geographic locations for disaster recovery, which is a resilience statement rather than a residency one and arguably cuts against a customer wanting data confined to a jurisdiction. Not located as of 29 Aug 2026: any named region, any customer selectable residency, any tenancy model, and any statement of where processing happens as distinct from where data is stored. Third party sources mention private cloud deployment options, which is not vendor material and does not move this axis. For a UK founded vendor selling into the UK, US and Singapore, published residency options would be expected.

Security Certifications and Trust Center

Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.

Certification is real and stated with an open access route, short of scope and evidence. ISO 27001 and SOC 2 are both named as certified and GDPR compliance is stated, and a trust centre is published at a stable URL as a self serve route rather than a sales gate, which under the three tier test is materially better than absent. What was not located as of 29 Aug 2026 is any coverage period, audit scope, report date, SOC 2 type designation or named auditing firm. Note the vendor writes ISO without a number in one place on the security page and ISO27001 in another; the certification is stated clearly enough elsewhere that this reads as loose copy rather than a claim problem, and it is recorded rather than concluded on.

Model Supply Chain Disclosure

Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.

The vendor identifies a partner without disclosing the supply chain. Anthropic and AWS are both named as partners on the security page, and third party 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 as of 29 Aug 2026: 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. Graded on what is published rather than on the inference the partner logo invites.

Commercial Transparency

Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.

Checked the site navigation, the platform and services pages, the customers page and the footer on 29 Aug 2026. No pricing page exists on the property, no rate is published, no unit of charge is stated and no tier structure appears. Every commercial path terminates in a demo request. Vendor material references a free account with add in access and paid accounts with playbook customisation, and directs the reader to speak to a member of the team to understand what paid accounts include, so even the feature split between free and paid is not published. Third party sources describe subscription pricing without figures.

Firm and Practice Coverage

Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.

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, and the practice focus is clearly contract work: review, drafting, negotiation and post signature obligation tracking, with third party sources naming NDAs, service agreements, procurement and employment agreements. Three offices are published across London, New York and Singapore. What was not located as of 29 Aug 2026 is any segmentation a buyer could use: 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.