BigHand vs Foundation AI: how they compare in 2026
BigHand and Foundation AI both run law firm operations but are not usually weighed against each other. BigHand sells work routing, resourcing and financial software to large firms. Foundation AI files every document a high volume firm receives. On what they publish, they are near mirror images. Foundation AI publishes how its AI works and where a person checks it. Each field it extracts carries a calibrated confidence score, uncertain results go to a reviewer, and on matter matching it states that it does not guess. BigHand is the reverse. Its DPA sets a retention period for each product and names every subprocessor, and its trust center lists ISO 27001, ISO 27701 and SOC 2 Type 2, audited by A-LIGN. Its AI turns timecard narratives into structured phase and task data.
Which one fits
Choose BigHand if
- You need to route support work and see demand, capacity and cost. BigHand Workflow Management routes tasks to the right resource, added AI email routing in 2026, and comes in Standard, Plus and Advanced tiers with published feature lists for each.
- Your security review wants privacy certification as well as security. BigHand names ISO 27001, ISO 27701 and SOC 2 Type 2 with A-LIGN as auditor, Cyber Essentials Plus and an ICO registration number, and its DPA names every subprocessor with where it processes data.
- You want inconsistent timecards turned into pricing data. BigHand Impact Analytics uses machine learning to convert time entry narratives into structured phase and task data for pricing, staffing and billing quality, and BigHand reports 81 percent of the AmLaw 200 among its customers.
Choose Foundation AI if
- Your firm receives thousands of documents by post, fax, portal and email. Foundation AI captures each one, reads it, matches it to a matter, names and files it to your convention, and routes and tasks it, tracking every step.
- You want uncertain results sent to a person rather than guessed. Foundation AI scores every field against calibrated confidence thresholds, passes confident results straight through, and holds the rest in a review screen with the uncertainty highlighted.
- You run a personal injury, workers' compensation or disability practice on a common case system. Foundation AI publishes integrations for CASEpeer, Clio, Filevine, Litify, SmartAdvocate and Smokeball, and names firms with results, including Acumen Law cutting about 120 hours a week of document work to roughly five.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.
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.
BigHand combines financial, document and workforce applications, with AI concentrated in particular products. Impact Analytics converts timecard narratives into structured activity data for pricing, staffing and billing analysis. Workflow Management turns Outlook messages into support tasks and routes them by skills, availability and workload. Speech recognition handles voice instructions, while Matter Pricing includes AI enabled timecard analysis alongside budgets and financial scenarios. BigHand acquired Ayora in August 2026, with the first integrated pricing capabilities expected later that year. Much of the catalog still functions through conventional dashboards, forms, accounting connections and document tools. AI extends that broader operational suite rather than constituting every product's core.
Take the models out and what is left is a mailroom. The platform's published architecture is the product. Fine tuned language models, retrieval, vector search, business logic, taxonomies specific to each jurisdiction and deterministic guardrails evaluate each document from several angles, and the results are reconciled and calibrated into a confidence score for every field. Classification, matter matching and extraction are all model work. The vendor argues the point directly: general purpose models look impressive in demos and fail silently in production, because categories overlap, taxonomies are hierarchical and a wrong model sounds as confident as a right one.
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.
Impact Analytics classifies time entries within a consistent code set, with additional task detail through UTBMS+. Its results support matter cost analysis and staffing decisions rather than legal authority. The DPA describes testing sample customer timecards, reviewing coding accuracy, adjusting the system and repeating the exercise before automatic processing begins. That is a defined quality procedure, though BigHand gives no acceptance thresholds, test results or error distribution for it. Financial dashboards make transformed data available for review and export without demonstrating a source link for every classification. A separate Ayora masking accuracy claim concerns anonymization, not the correctness of BigHand's billing analysis.
For an extraction product the question is whether a value traces back to the document and whether the system knows when it is unsure, and both are addressed with real method. Every classification, match and extraction is evaluated against calibrated confidence thresholds, results from several analytical routes are reconciled, and the confidence attaches per field rather than per document. Matching is described the same way, using names, dates, addresses and claim and policy numbers through custom models, retrieval and guardrails. What is not published is a number: no accuracy, precision or error rate from the vendor, no test set and no evaluation an outsider could check. The only figures are customer-reported, such as the 98 percent accuracy quoted in the Stockwell Harris story.
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 service notice requires human review and verification of AI output affecting customer deliverables, reporting or core services. Matter Pricing keeps final pricing decisions with people and provides scenario modeling, budget versions and live financial views for that work. Workflow Management automatically routes support tasks, while teams can redistribute work and follow its progress. PrebillManager separately lets firms require attorney or biller approval and undo edits through its history. These are practical review surfaces, although the notice does not map each AI feature to a required approval step. BigHand does not describe stops for uncertain classifications or recovery after an incorrect automated routing decision.
What runs alone, what stops it and how a person checks it are all published together. Confident results move straight through; anything below the calibrated threshold is held and surfaced in the review interface with the uncertainty highlighted, and on matter matching the vendor states plainly that when confidence is low it does not guess but offers the most likely matches for a person to confirm. The escalation route is described at the organizational level too, with most firms centralizing review in an operations team rather than spreading it across case managers. Execution is bounded by firm-defined rules for routing, tasking, deadlines and escalation, and every action is tracked. The vendor's own summary is that the platform does not remove humans from the process, it removes the wrong work from humans.
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.
Dickinson Wright's Impact Analytics account names COO Michael Kolb and analytics director Renee Morris, who describe gaining greater insight into staffing, time recording and pricing. Their account combines early benefits with plans for using the data, without a measured change in outcomes. Other named users include Tasktop's Amyli McDaniel, who attributes task level cost transparency to the analytics, and Kaiser Permanente's Tamara Morgan, who describes work with BigHand's team. Workflow Management separately attributes a turnaround reduction from 99 hours to 18 to Charles Russell Speechlys. Those workflow results do not isolate the contribution of the newer email routing models or Ayora integration.
Named firms, named people, described deployments and figures are published at a stated scale. Seven customer stories on the homepage attach the customer, the individual and their title to each outcome. Nyman Turkish reports more than 12 times the document processing productivity, Miller Dawson Sigal & Ward went from five or six hours a day to fifteen minutes, and Acumen Law from about 120 hours a week to roughly five. Stockwell Harris reports work five times faster, with 8,000 dollars a week saved and 400,000 dollars of temporary staff spend avoided. The Floyd Skeren study, read in full, sets out the firm's prior process across ten offices, the system it integrates with and the staffing change. It reports 350 percent more document processing efficiency and 81 percent fewer nonbillable hours, with a downloadable version. Around forty firm logos appear across the platform and integration pages, and the vendor states seven years of operations, hundreds of firms and millions of documents a month. No story gives the measurement method behind the percentages.
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.
Customer Data Access terms restrict support and implementation access to its agreed purpose, require confidentiality and keep copied information apart from other data. Customers can revoke that permission, triggering cessation of access and destruction of copies within 72 hours. The service notice prohibits using customer and personal data to train external, public or third party foundation models. The DPA still permits timecard quality testing and service improvement, with ChatGPT testing requiring express customer instruction, so internal model adjustment remains allowed in those forms. Matter level ethical walls and specific privilege or work product protections are not described across the suite.
Every document that reaches a firm flows into the product, from medical records and liens to pleadings, demand letters and client correspondence, with no stated account of what happens to them. There is no customer agreement on the estate: the Terms and Conditions govern the website and the Privacy Policy covers website visitors and their contact details by its own terms. No statement is published on whether firm documents train or improve the models, how long they are held, whether they are segregated between firms, or what happens to them when a customer leaves. The one adjacent claim, made in a feature block on a case study page, is that the company is SOC 2 Type 2 certified and HIPAA compliant.
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. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
BigHand's financial tools help firms classify work, construct budgets and edit bills. Its service notice requires verification of AI output that affects deliverables, reporting or core services, and Matter Pricing leaves final decisions to people. Neither statement assigns a lawyer a specific duty to validate machine coded work, fee narratives or charges before billing a client. Cost transparency and fair budgeting appear as product benefits rather than a framework for professional competence, fee reasonableness and AI disclosure. The website's general information disclaimer concerns website content. It does not define the professional responsibilities that accompany the operational AI used in a firm's fee process.
Professional responsibility is absent from how the product presents its own risks. The product makes decisions that bear directly on a lawyer's duties, classifying a pleading, matching a document to a matter, deciding who is alerted to a time-sensitive notice, and the estate frames the risk in operational terms, missed deadlines, misfiled documents and missed liens, without ever addressing supervision, competence or what the firm remains responsible for. There is no statement that the output is not legal advice, no description of what a reviewer is expected to check, and no guidance on the firm's responsibility when a document is routed to the wrong person.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
BigHand's Artificial Intelligence Management System governs AI processing under its service notice, which requires human verification, identifies automated interactions and prohibits training external foundation models on customer data. The timecard quality procedure adds a concrete testing sequence before automatic deployment, including sample review and system adjustment. An AIMS Manual and Statement of Applicability are listed in the trust center behind an access request. Their contents and the acceptance criteria for individual models are not available in the open notice. Impact Analytics supports equitable work allocation, but no test results assess classification differences across lawyer groups or identify who approves model releases.
The approach is published in detail, and the governance around it is not. The platform page explains how model behavior is controlled: several analytical routes reconciled against each other, deterministic guardrails, taxonomies specific to each jurisdiction, calibrated confidence thresholds and human validation of results with low confidence. Nobody is named as accountable for model behavior, nothing describes what is tested before a model or taxonomy change ships, and no evaluation results are published. Nothing addresses whether accuracy falls unevenly across document types, practice areas, languages or handwriting quality.
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.
The DPA sets separate retention rules for Workflow, Matter Pricing, Resource Management, analytics and Ayora, and lists processors with their activities, data access and locations. Staff access is denied by default, follows a formal request process and ends within a day of departure. Security event logs have a minimum 30 day retention period. Customer Data Access terms add a 72 hour deadline to end access and destroy copied material after revocation. A breach notification procedure is identified in both the annex and trust center, but the procedure requires access approval. Its customer notice deadline and incident handling commitments therefore remain unknown.
Document handling inside the platform has no stated terms. No retention period, no deletion commitment, no encryption statement, no access control description, no subprocessor list and no incident practice is published; there is no security or trust page on the estate, and the privacy policy addresses website visitors, saying only that reasonable administrative, physical and technical controls are adopted and that the company is GDPR compliant. The certification claim on a case study page is the closest thing to a statement.
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.
Customer Data Access terms apply the liability limitations from the separate BigHand Agreement to implementation and support access. They also require destruction of copied confidential data after permission is revoked. The referenced agreement's financial cap, indemnity and warranty are not included in the open access terms or DPA annexes. Trust center insurance entries identify available certificates without exposing the cover amounts or claims conditions. These materials provide no remedy for incorrectly coded time, a mistaken price recommendation or misrouted work. Website disclaimers address the website itself, so they do not supply the missing allocation of liability for the operational products.
Loss from a misfiled document or an alert that never fires falls to no named party. The Terms and Conditions cover the website: they disclaim warranties, exclude consequential damages, cap liability at whatever the user paid to access the site, and require the user to indemnify Foundation AI. No customer agreement, service level commitment, accuracy warranty or indemnity for the product is published, which leaves the risk the vendor's own marketing names, missed deadlines and missed liens, allocated nowhere on the published record.
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.
Workflow Management accepts Outlook email requests as structured support tasks, then distributes work according to skills, capacity and workload. Firms configure their forms and routing processes with BigHand during implementation and can change them afterward. PrebillManager carries attorney edits through billing review, with changes processed into the accounting system and a reversible edit history. Matter Pricing imports historic matter data and tracks actual costs against budgets through financial and time recording connections. Word and document management connections are included in Document Creation packages. BigHand does not document field mappings, authentication requirements or supported source systems for each financial connection.
Integration is the point of the product and it is documented per system. CASEpeer, Clio, Filevine, Litify, SmartAdvocate and Smokeball each have their own page; the Filevine page describes what actually moves, matching documents against parties, case numbers, claim numbers and dates held in Filevine, filing into matter folders, alerting the people the firm nominates, and writing extracted fields such as parties, senders, treating providers and dates back into Filevine to drive calendaring. Elsewhere the platform tags the originating message in Outlook or Gmail, matches Salesforce objects and Filevine collections, and feeds Domo and Power BI. What is missing is the engineering detail: no API or developer reference, nothing on authentication, sync direction or failure handling, and no named certification in any partner marketplace.
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.
Installed BigHand software runs on the customer's infrastructure, where the customer controls retention and local security. Hosted services use region specific Azure or Innovate Cloud9 infrastructure, with AWS supporting Digitory analytics and backups kept in the chosen hosting region. The processor annex distinguishes hosting from support and development access, including international personnel and specified invitation only access. Azure OpenAI anonymization for AutoCoder has named regional options. Ayora separately uses AWS and a processor list that identifies Google for generative features, but lists corporate headquarters rather than all processing locations. The suite has substantial regional detail without a complete location map for every current AI feature.
Where and how the platform runs has no stated answer. No hosting provider, region, tenancy model or residency option appears anywhere, and the only deployment language found is a claim on a case study page that the software integrates with existing hardware and core systems. For a platform that ingests a firm's entire inbound document stream, including medical records, a buyer has nothing to evaluate.
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.
A downloadable A-LIGN certificate identifies BigHand Limited's ISO 27001:2022 management system, certificate ISMS-BI-040925. Issued November 6, 2025, it expires November 20, 2027 and covers development, provision, support and SaaS maintenance across BigHand entities serving professional and healthcare customers. The certificate names London and Chicago locations and includes internal legal, HR, finance and IT operations. It is available directly through the trust center. The center also lists ISO 27701, SOC 2 Type 2 and penetration testing material, with some resources requiring access approval. The certificate verifies the scoped management system; it does not certify the accuracy of individual AI outputs.
The certification is claimed, and only just. A footer badge links to the AICPA's general SOC page on every page of the site, and a feature block on a case study page states that Foundation AI is SOC 2 Type 2 certified and HIPAA compliant. There is no security page, no trust center, no auditor named, no report period or scope, and no route to request the report; the HIPAA claim, which matters for a product handling medical records in injury and workers' compensation matters, appears only in that one block.
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 processor annex names Azure OpenAI for removing identifiers from AutoCoder and Digitory datasets, plus OpenAI ChatGPT for testing sample timecards only on express customer instruction. Azure supplies hosted speech recognition, while AWS hosts Digitory analytics. Ayora's separate security page identifies Google for generative AI features and a self hosted small language model for masking, without naming its family. These disclosures identify several different roles, so hosting and anonymization should not be confused with the model that classifies work. BigHand does not name the engines behind timecard coding and email routing. Processor update notices carry no commitment covering every underlying model change.
The architecture is described, and the models are anonymous. The platform page names the components: fine tuned large language models, retrieval, vector search, custom models, deterministic guardrails and proprietary methods. That describes the shape of the system while identifying no model, version or provider and saying nothing about where inference runs. No commitment to notify customers when models change is published.
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.
Workflow Management proposals depend on the number of licenses, access to features and the firm's configuration. Its Standard, Plus and Advanced tiers distinguish basic workflow from forms, reporting, timesheets and utilization features. Speech recognition, outsourcing, the service provider gateway and SDK are optional additions. Other packages cover resourcing, document creation, metadata, matter pricing and business intelligence, with feature differences visible across tiers. No license rate, minimum purchase or renewal uplift is stated. Implementation and training are scoped through a separate consultancy proposal. The license basis makes the structure clearer than a price request alone, while actual recurring and setup costs remain quote dependent.
No pricing is published at any level: no pricing page, tier, rate, trial or unit of charge, whether documents, pages or mailboxes. Every route on the site ends at a demo booking or a call.
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.
Law firm operations teams use BigHand for support work, resourcing, document production, financial reporting, pricing and prebill review. Impact Analytics also serves corporate legal departments analyzing outside counsel spend, with task based cost information and staffing insights. Workflow Management has users in healthcare, property and financial services as well as law, while the index profile concerns its legal workflows. Named legal users range across regional and international firms, including Dickinson Wright, Charles Russell Speechlys and Withers. The products work on the customer's operational records rather than a jurisdiction specific legal research collection. Country availability by product and minimum firm size are not fully defined.
The coverage is stated concretely by practice and by document type. The vendor publishes models, taxonomies and workflows for personal injury, workers' compensation, SSDI, VA, property claims, bankruptcy and immigration, and names the document classes it is trained to recognize, correspondence, discovery demands, pleadings, medical reports and event notices, with a separate Claims Operations product for insurers. The customer roster matches the claim, dominated by injury, workers' compensation and insurance defense firms from solo practices to Morgan & Morgan. What is not published is the boundary: no statement of which practice areas, document types or firm sizes the platform handles poorly, and nothing on jurisdictions outside the United States.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
The service notice prohibits training external, public or third party foundation models on customer and personal data. That promise does not expressly cover every internal model. DPA annexes allow timecard service improvement and quality testing, including system adjustments; ChatGPT testing requires the customer's express instruction. Neither permission alone states a right to train models. Ayora also has a foundation model training prohibition in its own policy.
The open service notice supplies the explicit restriction, while the full BigHand Agreement is not available to establish its contractual incorporation.
No customer agreement is published; the Terms and Conditions govern the website and the Privacy Policy covers website visitors. The platform description says the models are fine-tuned and that the system learns from validation, without saying whose documents that learning uses.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Workflow audio and attachments normally remain for up to 52 days after task completion; customers can extend that period by up to a year where the feature is available. Unfinished tasks can persist until completion, deletion or termination. Other product windows differ, including three months after termination for Matter Pricing and four for AutoCoder personal data. Ayora uses 30 days with backups up to 90. These are product specific controls and deadlines. No universal zero retention setting covers every AI input, generated result and service record.
No retention period is stated for the documents the platform processes, the extracted data or the tracking record of every action taken, and no deletion commitment on termination is published. The privacy policy's retention paragraph addresses personal information collected through the website.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
The service notice states that customer and personal data processed by AI is isolated. Administrators govern Workflow Hub visibility through user permissions, and Matter Pricing includes role based access. Support access is separately controlled through confidentiality terms, formal requests and limits on copied information. Those measures do not explain how an AI request is restricted to one client's matters or how a financial system's ethical walls carry into analytics.
No detailed wall inheritance or matter exclusion procedure accompanies timecard coding, email routing or the proposed Ayora pricing integration.
The platform routes documents by role and matches them to matters, contacts, providers and staff roles, so it plainly holds a view of who should see what, but nothing published describes a permission model, whether it inherits the practice management system's access controls, or how a matter walled off inside a firm is kept out of the wrong queue.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
The North American privacy policy permits disclosure for legal requests, investigations, court orders and other specified business purposes. The service notice adds that requests from law enforcement and regulators are validated before personal information is disclosed. It does not commit to telling the customer beforehand or giving time to challenge a demand. No transparency report provides the history of requests received.
The support terms' confidentiality and access revocation provisions constrain ordinary service access, without adding a notice commitment when information is sought by a third party.
Nothing addresses what happens if a customer's documents are subpoenaed from Foundation AI. The only disclosure clause located sits in the website terms and concerns material submitted through the site, which the vendor may disclose to comply with legal obligations or governmental requests, without notice or attribution; it does not reach the documents the platform processes for a firm.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Impact Analytics classifies the firm's timecard narratives and transforms billing information into task and cost data. Matter Pricing uses historic matters and current financial records to construct budgets and monitor delivery. These inputs come from customer operations, rather than an identified collection of cases or statutes. UTBMS+ is a coding approach, not a primary law corpus or license. No legal publisher, corpus update schedule or rights basis is attached to the AI classifications. The models' training datasets are also distinct from the customer records they analyze.
Provenance here is about the vendor's own classification scheme, since the documents themselves come from the customer. The platform works on the customer's own inbound documents against the vendor's jurisdiction-specific taxonomies; no external legal corpus is involved, and the taxonomies' sourcing is described only as seven years of document operations practice.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
BigHand's financial analytics interpret work descriptions, costs and staffing information. PrebillManager supports editing bills, while Matter Pricing compares planned and actual financial performance. None of these functions supplies later history treatment for a legal authority. Document Creation's clause bank and template tools likewise do not identify a citator or an automatic legal currency assessment. Correcting a billing code or refreshing matter cost data serves a different purpose from determining whether an opinion has been overruled. No good law verification feature accompanies the described AI workflow.
A document router has no case law to check. The product classifies and files documents rather than citing legal authority, so no subsequent-history check arises and none is described.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Timecard quality testing reviews sample classifications and adjusts the system before automatic processing begins. The service notice also requires human verification of AI output affecting deliverables and reporting. Neither description states how the live classifier handles an entry it cannot confidently code, or what email routing does when a request is ambiguous. No confidence value, abstention message or automatic referral rule is described for those situations.
Ayora's separate masking accuracy percentage is a security claim, without establishing uncertainty behavior for pricing recommendations or billing classifications.
The abstention path is described plainly and it is the center of the product's design. Every match, classification and extraction is scored against calibrated confidence thresholds; confident results pass straight through and the rest are held, with the uncertainty highlighted in the review interface for a person to resolve. On matter matching the vendor states that when confidence is low the system does not guess, and instead surfaces the most likely matches for the team to confirm. No published evaluation or observable demonstration of that behavior was found.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No entry in the AI Hallucination Cases database names BigHand, Digitory Legal or Ayora as of October 16, 2026. Their described capabilities concern operational work such as timecard coding, price analysis and task routing. The absence of a court record about fabricated citations says nothing about whether those outputs are correct, and it is not a statement about every kind of dispute involving the companies. Legal authorities are not the stated output of the financial products considered here; erroneous financial classifications raise a separate accuracy question.
The AI Hallucination Cases database kept by Damien Charlotin holds no entry naming Foundation AI as the tool used. Foundation AI files documents rather than drafting filings.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
The service notice addresses data isolation, mandatory human verification and AI governance, while financial product descriptions emphasize cost transparency and budget control. Neither connects those practices to a named legal ethics opinion or conduct rule. There is no explanation of how a lawyer's duties change when AI reclassifies time or supports a fee estimate. BigHand's commitment to ethical and nondiscriminatory AI processing concerns its general management framework.
It does not provide a firm with guidance on professional competence, client consent or disclosure of AI assistance in billing.
Ethics opinions and bar guidance bear naturally on how a law firm handles its documents, and this product engages with neither. Nothing engages a lawyer's professional duties. The risks the vendor names, missed deadlines, misfiled documents and missed liens, are framed as operational and financial, and no rule of professional conduct, ethics opinion or bar guidance is mentioned.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
PrebillManager shortens billing review and keeps an edit history, while Impact Analytics transforms timecard data to support pricing and client cost transparency. Workflow Management can record effort on completed support tasks. These records are not described as distinguishing AI performed work from human work within each client's fee record. No fee guidance explains how saved time or automated classification should affect charges to clients.
Although Impact Analytics has a corporate legal use case, the broader BigHand financial suite also serves the law firm preparing and collecting the bill.
The published case is about the firm's own economics rather than the client's bill: an 81 percent reduction in non-billable hours, staff redeployed to billable work, and a partner quoted on reducing non-billable hours while increasing billable ones. The work the platform replaces is overhead a firm generally cannot bill, and nothing published addresses whether the platform cost is passed through to clients as a case expense.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The DPA annex lists processors by activity, accessed data and processing location, including Azure OpenAI anonymization and expressly authorized ChatGPT testing. Ayora's linked list separately identifies Google generative features, AWS hosting and support services. The service notice adds the foundation model training restriction and required human review. A firm can use those materials to explain several parts of its information flow.
No client facing AI disclosure or consent package combines the relevant product, providers, processing geography and conditions into a complete outside counsel approval pack.
No subprocessor list, model provider list or client-facing disclosure material is published, and there is no trust page or request route.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
PrebillManager preserves edits and messages, and Workflow Management provides task ownership and activity trails. The service notice requires review of AI output affecting deliverables, but does not describe retaining the particular verification decision with the generated result. No export joins the model used, input sources and human approval for each passage or classification. These operational records can help reconstruct work, without constituting an AI certification for a court or regulator. The product descriptions do not supply a filing disclosure template or an equivalent client certification workflow.
A real processing record exists, built for firm oversight rather than for a court. The platform tracks each document and every action taken within it, from capture, matching, classification and validation through filing, routing, task creation and delivery, with per-field confidence scores, built-in dashboards, custom reports and feeds into Domo and Power BI. What is not recorded is which model produced a determination, so the record shows what happened and who confirmed it rather than what the AI did.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- UPL and Professional Responsibility Posture
- Primary Law Corpus Provenance
- Good Law Verification
- Bar Guidance Alignment
Product updates
The latest logged changes from each vendor, newest first, each linked to its source.
BigHand
-
Performance evidence
In a BigHand case study, Penningtons Manches Cooper reports that matters run through BigHand Matter Pricing achieve 12% better recovery than matters outside it, based on the firm's own reporting.
Source
In summary
BigHand
BigHand, from BigHand Limited of London with BigHand Inc in Chicago, sells operational and financial software to law firms across sixteen products. They cover workflow management and task routing, resource management, dictation and speech recognition, document creation, metadata management, business intelligence, matter pricing, budgeting and prebill review. Its AI sits in Impact Analytics, which turns timecard narratives into structured phase and task data, and in AI email routing. According to the AI Legal Index, BigHand reports 81 percent of the AmLaw 200 as customers and names ISO 27001, ISO 27701 and SOC 2 Type 2.
Foundation AI
Foundation AI, from Foundation Inc. of Irvine, California, runs the document operations of high volume law firms. Everything arriving by post, fax, portal or email is captured, read, matched to a matter, named, filed, routed and tasked, with every step tracked, and extracted data drives calendaring and damages records. Its customers are mostly personal injury, workers' compensation, disability and insurance defense firms. According to the AI Legal Index, Foundation AI scores its confidence in each extracted field and escalates uncertain ones to a reviewer. It names firms with results, such as Acumen Law cutting about 120 hours a week of document work to roughly five.
Questions buyers ask
Are BigHand and Foundation AI the same kind of product?
No. BigHand sells workflow, resourcing, document and financial software mostly to large law firms, with AI in timecard analytics and email routing. Foundation AI processes the whole inbound document stream of high volume injury and claims firms. Foundation AI publishes how its AI is checked, while BigHand publishes how customer data is protected. From the AI Legal Index, based on each vendor's own published materials as of October 12, 2026. No vendor pays for placement.
How does Foundation AI handle documents it is unsure about?
It scores every classification, match and extracted field against calibrated confidence thresholds. Confident results pass straight through, and the rest are held in a review interface with the uncertainty highlighted. On matter matching the vendor states that when confidence is low it does not guess, and offers the most likely matches for a person to confirm. From the AI Legal Index, based on each vendor's own published materials as of October 12, 2026. No vendor pays for placement.
Does BigHand use customer data to train its AI?
BigHand's DPA lists time sheet data, including client and matter descriptions, among the data it uses to improve its products and services, and allows quality assurance testing on sample customer data. Neither the DPA nor the privacy policy uses the word training. Foundation AI says its fine tuned models learn from validation. From the AI Legal Index, based on each vendor's own published materials as of October 12, 2026. No vendor pays for placement.
How does BigHand secure client data?
BigHand names ISO 27001, ISO 27701, SOC 2 Type 2 and Cyber Essentials Plus, with A-LIGN as auditor, publishes an ICO registration number, and claims HIPAA and NHS data security compliance. Its reports are released through an access request in its trust center. Foundation AI claims SOC 2 Type 2 and HIPAA compliance on one case study page. From the AI Legal Index, based on each vendor's own published materials as of October 12, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
Three points to weigh. Neither vendor publishes a customer agreement. Both publish website terms only, so neither page can state what either stands behind when a document is misfiled or a time entry is miscoded. Foundation AI's SOC 2 Type 2 and HIPAA claims appear on one case study page with no auditor or scope. BigHand's audit reports sit in its trust center, so its attestation details rest on its stated certifications, badges and privacy policy. Neither vendor reviewed this page.