Streamline 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 platform underneath is a rules engine and the models sit on top of it. Intake forms, conditional routing, approval chains and SLA timers are described as no-code configuration built on rules, and legal operations teams set them without engineering — that is conventional workflow automation and it predates the AI layer. What the models drive is real and sold as core: AI email intake, automatic classification of every request by type and urgency, a Slack intake agent, the Knowledge Bot, the Velo copilot, an MCP connector, and clause evaluation against a negotiation playbook with one-click redlines. Remove the models and a working intake, matter management and reporting platform remains, which is what the company shipped first. B on the band exactly. Pages read 1 September 2026.

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 and never measured in a form an outsider could test. The home page carries a product illustration contrasting 48% review accuracy for an auto-routed process against 92% for an AI-reviewed one, but it appears inside a dashboard mockup with no test set, no definition of review accuracy, no sample size and no date, so it is a marketing graphic rather than a published benchmark and is not treated as one. Nothing else on the AI feature pages, the security page or the home page publishes an evaluation or names a failure mode. The primary-authority and citator limbs of the higher bands do not apply, since the product classifies and routes legal requests and evaluates clauses against a customer playbook rather than retrieving case law. C: accuracy asserted without measurement.

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 stated division of labour with customer-owned controls. The how-it-works section commits that automated workflows handle routine tasks while attorneys step in where judgement is required, and that every action is logged and reportable; the agentic automation section frames it as saving human judgement for novel issues. The controls are real and configured by the buyer: approval chains, escalations and SLA tracking are set by legal operations without engineering, conditional logic routes work to a named team or an agent, and role-based access is scoped by team, matter type and function. A complete audit trail covers every request, decision and action. Held at B because no threshold is published at which an agent stops and hands over, nothing states which actions run unattended versus which require sign-off, and the approval chains govern the legal work rather than the AI’s own actions.

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.

Named customers and figures are both present but they do not meet in the same place. Case studies name the organisation and the outcome: Cityblock Health revamped its legal service model with a 40% reduction in operating expenditure, Hims runs a 30-person legal team on the platform, and Accordion built its legal function on it. Individual users are named with titles and employers — Ilan Hornstein, VP and Deputy General Counsel at 8x8; JP LaMunyon, Senior Legal Manager at Favor; James Harmoush, Senior Counsel at Redwood; Rita Zupancic at Super.com — but those are testimonials without figures. The four headline metrics, 10x faster intake, 50% reduced resolution time, 40% outside counsel savings and 65% reduction in response times, carry no denominator, no customer attribution and no date. B rather than A because nothing read on 1 September 2026 is dated and no method is published for the aggregate claims. G2 ratings and awards were excluded as directory material.

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.

Substantive on training and segregation, silent on what the model provider retains. The commitment that Streamline does not train AI models on client data is published twice, on the home page and in the FAQ. Segregation is addressed with more specificity than most of this lane: role-based access control is scoped by team, matter type and function, and the security page states that legal users have access to legal-only notes reserved for the legal team, which is a real internal boundary rather than a generic permissions claim. Encryption is AES-256 at rest and TLS with 256-bit in transit, and the subprocessor list is published openly. The gaps: the no-training commitment sits on marketing surfaces and the Terms of Use are robots-disallowed, so whether a matching contractual term exists was not established and no finding is made either way. Nothing states what Clearlaw, the named LLM licensor, may retain. Privilege is addressed only by the terms disclaiming it, which is graded on UPL rather than spent here.

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.

A dedicated, product-scoped clause rather than a website disclaimer. Terms of Use clause 2.3, headed that Streamline AI is not a law firm, states that it is not a law firm or an attorney, may not perform services performed by an attorney, is not a substitute for the advice or services of an attorney, and that no attorney-client relationship or privilege is created. The privilege point is worth a buyer’s attention on its own, since it is an express disclaimer rather than silence. The Terms of Use are robots-disallowed to automated retrieval and this clause was recovered through the search index, which is a limit on the reading rather than a gap in the vendor’s disclosure. B rather than A because nothing addresses the buyer’s own supervision and competence duties, no jurisdiction limits are named, and ABA Formal Opinion 512 is not mentioned on any surface read on 1 September 2026.

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.

No governance position located. The home page, security page, pricing page, subprocessor list, privacy policy and the recovered portions of the Terms of Use were read on 1 September 2026, and there is no responsible AI page, no named accountable owner, no pre-release testing regime, and no ISO 42001 or equivalent. Nothing addresses whether classification and routing behave evenly across request types, business units or requesters. The gap has teeth here because the AI decides how every inbound legal request is categorised by type and urgency and which team or agent receives it, so a systematic skew would show up as some requests being consistently deprioritised. Security controls and the SOC 2 attestation are a different subject under this band and are graded on Security Certifications.

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.

Most of the ground is covered and incident practice is the hole. Published: AES-256 at rest and TLS with 256-bit encryption in transit, production hosting on AWS, a third-party security agency engaged to review data security protocols, regular third-party audits, vulnerability testing and log review for suspicious activity, single sign-on with Google, Okta and OneLogin, role-based access, and a complete audit trail over every request, decision and action. The subprocessor list is published openly at a public URL with each supplier’s address, contact and purpose — the band’s commonest exception, and Streamline clears it. Retention is acknowledged in the privacy policy for the period necessary to fulfil the stated purposes with deletion available by email request, but no period is given. No incident or breach notification practice was located. One caution recorded rather than credited: the ISO 27001 and SOC 1, 2 and 3 reports cited on the security page belong to the hosting data centres, not to Streamline.

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.

A published position that allocates the loss entirely to the customer. The Terms of Use cap aggregate liability at the amount paid for the service to which the claim relates, or $100 where the claim does not relate to a product or service, and exclude liability to the fullest extent permitted by law with a carve-out preserving warranties and liabilities for New Jersey residents and residents of states that require it. The service, sites and user content are provided as-is without warranty, representation, condition or guarantee of any kind, express or implied. The only indemnity runs from the customer to Streamline. There is no warranty on output, no insurance position and nothing the buyer can invoke when a classification or a clause evaluation is wrong. C: liability addressed only through a limitation clause that disclaims the exposure the product creates. Clause text recovered through the search index because the Terms of Use are robots-disallowed.

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.

A real and legally specific integration set, documented by plan rather than by field. The pricing page names what each tier includes: Slack, Microsoft Teams, e-signature through DocuSign and AdobeSign, SSO and SCIM on the lower plan; storage through Google Drive, Box, OneDrive and SharePoint, a Jira custom channel, Salesforce, CLM integration with Ironclad, NetDocuments, and API access on the upper plan. Naming Ironclad and NetDocuments matters in this lane, because those are the contract and document systems in-house legal work already lives in, and tying each integration to a named plan tells an implementer what they must buy to get it. The FAQ adds that integrations are pre-built and that IT involvement is typically limited to integration configuration. B rather than A because what actually syncs and in which direction is not described; the dedicated integrations page was not opened on 1 September 2026 and is the rebuttal route.

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.

Deployment is stated plainly and residency is partial. Production servers are hosted by Amazon Web Services, named on the security page and confirmed by the subprocessor list, and the home page offers configurable data residency, with regional data hosting sold as a named add-on on the pricing page. The privacy policy states the default position clearly: Streamline is located in the United States, processing takes place in the United States, and data from users outside the US is transferred, processed and stored there under US standards, with model contractual clauses used for EU transfers. What is missing is which regions the add-on actually covers, at what price, and any statement of the tenancy model — the server isolation referred to on the security page is described as a property of AWS data centres rather than of Streamline’s own architecture. B on the first limb: deployment model stated clearly with partial residency detail.

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.

The certification is real and stated, and there is no route to the evidence. SOC 2 Type II is stated on the home page, the security page and the site footer, and GDPR compliance alongside it. No auditor is named, no coverage period or report date is given, no scope is specified, and no trust centre or portal exists — none was located through the navigation or footer of any page read on 1 September 2026, and there is no stated route by which a buyer could request the report. B rather than C because the standard is named in prose rather than appearing only as a badge image. The ISO 27001 certification and SOC 1, 2 and 3 reports referred to on the security page attach to the hosting data centres rather than to Streamline, and inherited infrastructure attestations are not credited to the vendor here.

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 supply chain is partly disclosed, and where it exists the disclosure is specific and ungated. The published subprocessor list states that Streamline licenses Clearlaw, Inc. to provide a large language model for its SmartParse product, which is a genuine model-supplier disclosure and more than most of this lane offers. The coverage is partial rather than complete: SmartParse is one capability among at least six the site markets as AI, alongside email intake, request classification, the Slack intake agent, the Knowledge Bot, the Velo copilot and clause evaluation, and no model or provider is identified for any of the others. AWS, MongoDB, Redis, Heroku and Google Workspace appear on the same list but are infrastructure and cannot be spent here. No inference location is stated for the named model, and no commitment to notify customers when the supply chain changes was located on 1 September 2026.

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.

The most complete pricing disclosure located in this pull. Both plans carry a figure: Pro starting at $22,900 and Enterprise starting at $26,900, published on an open page reachable without a demo or a form. The unit is stated on both — four core users included, 5,000 business users on Pro and unlimited on Enterprise — and the feature split between the plans is itemised line by line, so a buyer can see exactly what the extra $4,000 buys: storage integrations, Jira, Salesforce, Ironclad, NetDocuments and API access. Implementation is addressed rather than hidden: onboarding is stated to be included in every plan and the FAQ commits to roughly 60 days with a dedicated onboarding team. Three add-ons are named, Knowledgebot, Dynamic Docs and regional data hosting. What keeps this from being comfortable and is recorded as the weakness: the billing period is never stated, the figures are floors, and the add-ons carry no prices.

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.

Segment coverage is described precisely and the boundary is real. Five role pages are published — Chief Legal Officer, General Counsel, Assistant General Counsel, legal operations and counsel — alongside two team-size pages for small and scaling legal teams, and the product is positioned throughout as purpose-built for in-house legal rather than for firms. The FAQ states a genuine limit that most vendors avoid, distinguishing the product from a CLM and saying it connects to an existing CLM rather than replacing it, which tells a buyer where the product stops. B rather than A because practice areas are not enumerated beyond contracts and general legal requests, law firm and government use are not addressed at all, and the platform is described as covering every request type without saying which request types it handles poorly.