Josef

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.

Josef sells three products: Josef Q for AI question and answer, contract automation, and workflow automation. Only the first is model-driven. The contract and workflow modules are template and rules automation that predate the AI layer, and they are what the L’Oréal case study’s 66% turnaround figure actually rests on. Josef Q is not peripheral — it has its own login at q.joseflegal.com, four dedicated product pages and its own named customers at adidas, Bupa and Cityblock Health — but remove it and a working no-code document and workflow platform remains. That is the B band precisely: the models are the engine of a core capability layered on a product that would still function without them. 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.

Grounding is real and specifically documented. The AI controls page states Josef Q is a closed-domain system answering only from uploaded content, and the source list shows the exact page, paragraph and clause an answer drew on, so a reader can open and check the support. A document pre-processing engine is described as scanning and optimising uploaded content before indexing. No measured accuracy figure and no test set is published anywhere, which is what holds this at B. Two limbs of the higher bands do not apply to this product class: Josef Q retrieves the customer’s own policies rather than primary law, so grounding to primary authority and citation-status checking are not capabilities it claims. Against that, the audit trail page carries an unqualified “No hallucinations!” claim, which is marketing running ahead of the mechanism. It does not drop the grade to D because it sits alongside a described architectural control and a published refusal path rather than standing alone. Read 1 September 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.

The control structure is published in unusual detail for this lane. The AI controls page documents human-in-the-loop moderation over every answer, source addition and removal in a Moderation tab, a Tuning Lab for tone, length and spelling convention, and Smart and Follow-up Suggestions that shape what end users ask. The stop rule is published and specific: outside the uploaded corpus the tool answers “Sorry, I don’t know.” The audit trail page adds that all user questions and generated answers are tracked and stored. What is missing for A is the route back to human judgement — no escalation path from an unanswered question to a lawyer was located on any product page read on 1 September 2026 — and no thresholds or distinct autonomy modes are published. B rather than A on the absent escalation route, not on the review surfaces, which are the strongest part of this record.

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.

Attribution and figures are both present, which is more than most of this pull manages. The L’Oréal case study names Candy Welsh, Legal Counsel, and reports a 66% drop in contract turnaround, one contract moving from over an hour to 20 minutes, 100-plus such contracts a year, and roughly two weeks of work saved annually. Further named deployments carry named officers: Katherine Roseveare, General Counsel at adidas, across 65,000-plus people; Claire Nuske, Head of Legal Operations at Bupa, with 40-plus self-service tools; Wendy Chow, General Counsel at Cityblock Health; Sheila Dusseau, Head of Global Legal Operations at Ferring Pharmaceuticals. What keeps this at B is that no case study read on 1 September 2026 carries a date, and the 66% figure is given with no statement of how it was measured or over what period, so a reader can assess neither the method nor the currency.

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.

No customer agreement is published. The home page, security page, FAQ, website terms and privacy policy were read on 1 September 2026 and a clause-language search was run; the only two published instruments are website terms and conditions and a privacy policy dated 15 February 2024, and that policy states it applies to Josef as a controller rather than to customer content held as a processor. What is published is real but general: the FAQ states customers retain full ownership of their data and Josef acts as custodian, and the security page states AES-256 at rest and TLS 1.3 in transit with Josef-held server-side keys. Nothing addresses training on customer content, tenant separation, or privilege and work product treatment. The in-house band amendment does not rescue this, because for an in-house buyer the requirement is tenant-level separation and no separation of any kind is documented. C rather than D because the ownership and encryption commitments are published and readable before signing; C rather than B because the commitments that decide this axis cannot be read in advance at all.

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 only disclaimer located is scoped to the wrong thing. The website terms and conditions state that content on the Josef website is provided for information purposes only, which addresses the marketing site rather than the output of a tool answering policy questions for employees. Meanwhile the product is described in advice terms: the Josef Q demo panel offers to provide scalable guidance and advice, and the FAQ describes legal aid organisations and boutique firms using Josef to deliver client-facing onboarding, wills and guidance tools to members of the public. No jurisdiction limit, no statement of who may rely on an answer, and no consumer-facing disclosure requirement were located on any page read on 1 September 2026, and ABA Formal Opinion 512 is not mentioned. C rather than D because a disclaimer does exist in the terms; C rather than B because it does not reach the product, and the client-facing uses the vendor advertises are exactly where the advice line bites hardest.

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, the three product pages, the AI controls page, the audit trail page, the security page, the FAQ, the website terms and the privacy policy were all read on 1 September 2026. There is no responsible AI page, no named internal owner, no pre-release testing regime, and no ISO 42001 or equivalent. Nothing addresses whether answer quality varies across topics, document types or populations. The moderation and review controls are real but they are an oversight mechanism already graded on Autonomy, and the band excludes security controls as a different subject, so neither can be spent here. The chief executive’s published article on context engineering is a design argument, not a governance disclosure.

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.

Access control is documented and the rest is not. The security page states AES-256 encryption at rest, TLS 1.3 in transit, Josef-held server-side encryption keys and regular access audits, alongside OWASP and ASD secure coding frameworks, automated vulnerability scanning and annual third-party penetration testing. What happens to uploaded documents and prompts afterwards is not addressed: the privacy policy retains service data for the duration of the business relationship and an unstated period after, deletion is described only as securely deleting or anonymising once no legitimate business need remains, and no incident practice is published anywhere. The subprocessor list is not published — the privacy policy says it can be provided on request, and no self-service portal or instant-download route was located on 1 September 2026, so under the three-tier rule it earns no credit. C rather than B because two of the five elements the band names are absent outright and two more are stated without a period or a mechanism.

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.

Nothing published on who bears the loss when an answer is wrong. The only liability clause located sits in the website terms and conditions and excludes liability arising from use of the Josef website, limited where it cannot be excluded to resupply of the relevant services or information. That is a website clause, not a position on product output. No master subscription agreement, customer agreement, service level agreement, warranty or indemnity was found. The escalation ladder was run on 1 September 2026: the footer was checked across six rendering pages and offers only the website terms, the privacy policy and a cookie notice, and a search on customer-agreement clause language returned no Josef instrument. This is an established absence rather than a retrieval failure, so it is graded rather than left unwritten under R7.

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.

Thirteen integrations are named and grouped by function, and the direction of travel is described: policies sync in from SharePoint and Confluence, data is pulled from Airtable and Google Sheets, and captured information is pushed out to Slack, Teams, SharePoint and Salesforce. The legal systems are what matter in this lane and they are present — HighQ, Xakia, Dazychain and Actionstep are all named. The Xakia entry goes furthest, describing Josef bots launched from Xakia’s internal client portal so that requests stay managed within Xakia. Two integrations carry linked walkthroughs, for Actionstep and Xakia. B rather than A because no documentation an implementer could use was located: no developer index, no field mapping, and no statement of what a firm must configure, with the integrations page answering any unlisted case by inviting a conversation with the team. Read 1 September 2026.

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.

The security page and the FAQ both state data residency options in the US, Europe, the UK and Australia, a four-region commitment stated consistently in two places. The tenancy model is never stated: nothing published says whether customers sit in shared or separate instances. Processing location is not addressed as distinct from storage, and there is a tension a buyer should read before signing. While the security page offers regional residency, the privacy policy tells users their personal information may be transferred and processed outside their country including in the United States, relying on standard data protection clauses for EEA and UK transfers. The two are not necessarily inconsistent, since the privacy policy governs Josef as controller rather than the platform tenancy, but no document read on 1 September 2026 reconciles them. B on the second limb of the band: residency is offered without the processing location being addressed.

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.

SOC 2 Type II is stated on the security page, the FAQ and the home page, and the privacy policy states SOC 2 Type I and II. Annual third-party penetration testing is stated, as is GDPR compliance and ISO certification of the underlying server infrastructure. Absent is everything that would let a buyer check any of it: no auditor is named, no scope or coverage period is given, no report or summary is offered by any route, and no trust centre exists — no Vanta, SafeBase or equivalent portal was located on 1 September 2026, including through the footer and navigation of pages that render. B rather than C because the standard is named in prose rather than appearing only as a badge image; B rather than A because there is no access flow to the evidence at all, not even a gated one.

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.

Josef acknowledges a large language model underneath and never says whose. The chief executive’s published position is that an LLM alone cannot be trusted and needs context engineering, and the audit trail page refers to GenAI engineering, but no model, no model provider and no inference location is named on any page read on 1 September 2026. Hosting region and ISO-certified infrastructure are published, but a hosting location answers where the software runs rather than whose model sees client content, and cannot be spent on this axis. There is no commitment to notify customers if the underlying model changes. The only route to the supply chain is the subprocessor list the privacy policy says is available on request.

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.

No pricing information at any level. There is no pricing page: the navigation and footer were checked on 1 September 2026 across the home page, the Josef Q and integrations pages, the security page, the AI controls page and the FAQ, and none carries a pricing entry. Every commercial path is a demo booking or a contact form. No tier names, no packaging structure, no unit of charge and no figure are published, so a buyer cannot learn what is being charged for, let alone how much. D rather than C because C requires the shape to be visible with only the number withheld, and here neither the shape nor the number is published.

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 set out by segment with named customers in each, which is unusually concrete. The FAQ and the customer navigation name five segments — in-house legal, global law firms, boutique and NewLaw firms, legal aid organisations and community legal centres, and law schools — each with its own page and named users: L’Oréal and Bumble in-house, Orrick and Herbert Smith Freehills among firms, Hive Legal and Polaris Lawyers in NewLaw, Housing Court Answers and Everyday Justice in legal aid, and Cornell, NYU and the University of Pennsylvania in education. Document types are named too — NDAs, MSAs, employment agreements, powers of attorney and client onboarding forms — with Q&A use cases grouped under commercial, privacy and data, legal operations and HR. B rather than A because the limits are not stated: the FAQ’s position is that anything repeatable can be automated, government use is not addressed, and no page says where the product stops. Read 1 September 2026.