Billables AI vs Brightflag: how they compare in 2026
Billables AI and Brightflag sit on opposite sides of the same invoice. Billables AI writes the time entry inside the law firm. It watches activity across Microsoft 365, Google Workspace, Adobe, Zoom and the browser and infers what was billable, how long it took, which matter it belongs to and how to describe it. Brightflag reads the invoice that results for the corporate legal department paying it, classifying every line by phase and activity and checking it against that department's billing guidelines. Brightflag's analysts review lines its model is unsure of. Billables AI's terms keep only activity metadata and the generated time records, not the underlying emails and documents, and cap liability at a year's fees or $1,000. Its plans run from $47 to $169 per user a month. Brightflag names AI21 Labs and Anthropic's Claude behind its generative features, states ISO 27001, SOC 1, SOC 2 and ISO 42001 certification and sizes its subscription to outside counsel spend. Billables AI names no model provider and no certification.
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.
What Billables AI delivers is a set of inferences: deciding which activity in a stream of email, documents, calls and browsing is billable, calculating a duration without any timer input, matching each piece of work to the right client and matter, reconciling overlapping and multitasked activity, and writing a narrative in the timekeeper's own style. The company describes machine learning models adapting to each user's billing preferences and narrative writing style over time. There is no conventional product beneath it and no content asset. The alternative the vendor names is manual timekeeping, and a customer on its own page contrasts the product with timekeeping applications that merely compile time from screenshots.
Brightflag was founded in 2014 on machine learning that reads legal invoices, and that model sits at the center of the product. A supervised model, refined on labeled invoice text for more than a decade, reads every line item narrative and classifies it by phase of work and activity on an extended UTBMS framework. A rules engine then checks each line against the customer's billing guidelines and flags violations, rate discrepancies and duplicate entries before a reviewer opens the invoice. Generative features sit on top of that core. AI invoice summaries arrive in approval emails, Ask Brightflag answers questions about spend data, spend forecasts predict budget overruns, AI built vendor profiles support panel management and RFPs, and generative AI produces matter summaries. Workflow, budgets, accruals, matter management and reporting surround the AI, and approved invoices flow to accounts payable. Without the classification model, Brightflag would be a conventional electronic billing system.
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.
The published figures are business outcomes, more billable time captured and less time spent on billing, not how often the system attributes work to the right matter or writes a narrative that survives review. No figure is published for matching, duration or narrative accuracy, and no evaluation or test method is described. Section 6.3 of the terms states that output may not always be accurate and that the customer must review it for accuracy and appropriateness before relying on it. Nothing describes how an entry traces back to the activity that produced it.
Flags in Brightflag trace to evidence a reviewer can open. Each flag ties an invoice line to the billing guideline rule it breaks, and the reviewer sees both on the invoice review page. Brightflag's internal analysts supervise the classification model, reviewing cases where it is not yet confident in its interpretation and feeding corrections back to it. Ask Brightflag answers only from the organization's own spend data, and a filter explainer shows how it interpreted each question, so a user can check that the results match the query. Users report a wrong answer with a thumbs down for Brightflag's team to investigate. The generative AI terms say outputs are produced probabilistically, may not always be accurate and should not be relied on as a sole source of truth. Brightflag's FAQ says LEDES and PDF invoices are processed with equal accuracy, and the figures it publishes are savings and returns from a Forrester study rather than accuracy rates.
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.
Under a heading of human guided automation, Billables AI says a user's time reports are visible only to that user, and any billable record can be edited or deleted before it is exported or shared, so nothing the system infers about a lawyer's day reaches a billing administrator or partner until the lawyer releases it. Section 6.3 of the terms requires the customer to review output for accuracy and appropriateness before relying on it. Nothing says what the system decides without a prompt, what threshold governs whether activity is classed as billable, what happens to activity it cannot attach to a matter, or whether bulk approval is available.
In Brightflag the AI reviews and a person, or a rule the customer sets, approves. Invoices route by matter, value or practice area to designated approvers, and approving from an email summary does not bypass workflow rules. Customers can configure automatic approval for invoices that meet set criteria, and the FAQ says most customers auto approve invoices under $5,000 with no guideline violations, which can be about 30 percent of invoices. Invoices that fail set criteria can be rejected automatically. Flagged lines go to the customer's reviewers, and lines the model is not confident about go to Brightflag's own analysts. Approved invoices flow to accounts payable, and approvals sit in an audit trail. The MCP connector is read only, so approvals, edits and rejections happen inside Brightflag. The generative AI terms leave the customer to decide where human review is appropriate and bar using the features to automate decisions with a legal or material impact on an individual.
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.
Eight customers speak on the record with name, title and firm: Tycko & Zavareei, Mohan Groble Scolaro, Pulse Law, Zigler Law Group, Finch & Hammer, Kronenberger Rosenfeld, Corporate Law Partners and Acevedo Belt, across managing partners, a COO, office administrators and directors of operations. Three attach a figure to a named person: a managing partner reporting at least ten percent more time captured, a chief executive reporting thirty percent, and a founding partner saying he recouped his annual investment in two days. Aggregate claims are footnoted to a 2025 pilot program, and the vendor itself labels one statistic as unsubstantiated. No baseline is defined for more time captured, no sample size or firm count is given for the pilot, and the aggregate figures differ across the vendor's own pages, 10 to 30 percent in one place and 15 to 30 percent in another.
Named customers and figures fill Brightflag's success stories. In the nine months after switching, SMBC's Americas division saved $2.7 million by applying its discount agreements and outside counsel guidelines consistently. It also saved more than 300 labor hours by replacing a Word and email matter opening process with a request form. Lufthansa raised outside counsel guideline compliance by 5 percent in a single quarter and now assigns budgets to more than 80 percent of its matters, up from 20 percent. Syngenta recouped the equivalent of 10 percent of its gross legal spend in the first half of 2021, and Dropbox spends two days less on accruals each month. Each figure is the customer's own account, without a stated method. A Forrester Total Economic Impact study commissioned by Brightflag found a 387 percent return over three years for a composite organization and a 4 percent average saving from billing compliance.
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.
The product watches a lawyer work in email, documents and calls. Section 1.9 of the terms says Billables AI stores only metadata about user activity and the generated billable records, and will not store or retain underlying work product such as documents or emails, which the home page repeats as not storing privileged data. Section 1.9 also names data isolation and confirms the customer controls its data and can access, delete and manage it, and section 1.6 limits the vendor's use of Customer Data to providing the service. Section 4 gives mutual confidentiality with notice on compelled disclosure. No model or AI provider is named, so whose model reads the activity stream is not stated, and no retention period is stated for the metadata and records kept.
Brightflag's generative AI terms address training for its generative features. Customer data is not transferred to the third party model developers, who cannot and do not use inputs or outputs to train their models, and Brightflag will not fine tune the model instances it operates. Brightflag's own classification model, refined since 2014 on labeled text from actual legal invoices, sits outside those terms, and Brightflag does not name the source of that text. Vendor benchmarking uses data aggregated across Brightflag customers. Data is encrypted at rest with AES 256 under AWS Key Management Service and in transit with TLS 1.2 or higher. Access runs through SAML single sign on, SCIM provisioning and four client roles, from ordinary users who see only their own matters and invoices to administrators, and access can be limited to set IP ranges. Brightflag staff reach customer data only as needed under a role based access policy. Ask Brightflag answers only from the organization's own legal spend data, which its help article presents as keeping that data confidential. The security page and the generative AI terms treat customer data as confidential without separate treatment of privilege or work product.
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.
Billables AI gives no legal advice and creates no legal work product, but its central promise, that firms capture ten to thirty percent more billable time, bears on billing judgment: whether fees are reasonable, whether time inferred from an activity stream was properly billable to that client, and whether narratives written by a model accurately describe what the lawyer did. Nothing on the home page, in the terms of service, the footer or the solution pages for timekeepers, managing partners and legal administrators engages any of this. No bar rule, ethics opinion or fee reasonableness principle is named, and no guidance is given on reviewing machine surfaced time before billing it. The closest language is section 6.3's requirement that the customer review output for appropriateness.
Outputs are not legal, tax or other professional advice or a substitute for it, and may not always be accurate, under Brightflag's generative AI terms. The customer decides whether outputs suit its use case and where human review is appropriate. The terms bar using the features as a general purpose chatbot, to automate decisions with a legal or material impact on an individual, or for anything that does not directly support the platform's primary functions. Brightflag sells to corporate legal departments, and Ask Brightflag is open only to administrator and overview roles. The billing rules it applies come from the customer's own outside counsel guidelines rather than from Brightflag. The terms set no jurisdiction limits for a product that reviews invoices from firms in many countries.
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.
No responsible AI page, framework or principles is published on the home page, in the full terms of service, the privacy and site terms, the footer or the three solution pages. No one is named as accountable for model behavior, no account of evaluation before model changes is given, and no certification such as ISO 42001 is claimed. Nothing addresses uneven output, although the system classifies which activity is billable and adapts to each user's patterns, so it may perform differently across practice areas, working styles and roles, and a model that learns from a user's history will reinforce what that history contains. Nothing says whether the adaptation is checked for drift or for systematic over capture or under capture. The only related statement is section 6.3, which requires the customer to review output and so assigns responsibility without describing a control.
Certification to ISO/IEC 42001, the standard for AI management systems, appears on Brightflag's FAQ. An article on its site by Michael Dineen, its director of data science, updated in April 2026, says it is among the first legal technology providers to meet the standard. The article says Brightflag has built the standard's principles into its AI product development and internal governance. The FAQ says each AI feature is designed with a confidentiality, privacy and security focused approach. Its security page, which lists ISO 27001, SOC 1 and SOC 2, does not include ISO 42001, and no certifying body, certificate date or scope appears on the open pages. The article lists bias detection and mitigation among the standard's requirements, and Brightflag reports no testing or bias results of its own. The article commits Brightflag to protecting customer data, deploying AI that is transparent, auditable and trustworthy, and improving its AI systems in line with legal and ethical standards. Governance is presented through the certification, without a named owner inside Brightflag.
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.
Section 1.9 of the terms commits to encryption in transit and at rest, strict access controls, routine audits and vulnerability testing, secure coding, continuous monitoring and data isolation, and limits what is held: only metadata about user activity and the generated billable records are stored, and underlying work product such as documents and emails is not stored or retained. The home page adds user opt ins per connected tool, single sign on to third party applications and audited access logs, and section 1.9 confirms the customer can access, delete and manage its data. No retention period is stated for the metadata and records kept, no subprocessor is named, and no incident or breach notification practice is published. A trust center is linked from the home page.
Brightflag publishes its security controls and leaves several data handling terms to agreements it signs with each customer. Data retention and deletion are configurable to each customer's requirements, and the privacy notice keeps basic customer account data for six years after a relationship ends. Data is encrypted at rest and in transit, staff access follows a role based access control policy, and the platform is penetration tested by CREST certified testers and scanned for vulnerabilities continuously. Customer data is backed up to AWS data centers as part of business continuity. The privacy notice says all subprocessors, including AI subprocessors, are listed in Brightflag's data processing agreement and in its trust center, which Brightflag opens on request. Brightflag commits to notify customers and regulators of a suspected breach where the law requires it. Customers can track application actions in the product and request fine grained audit logs. Brightflag's 2021 announcement scoped its SOC 1 report to invoice approval and accruals management.
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.
Section 7 of Billables AI's terms caps liability at the greater of fees paid in the prior twelve months or one thousand dollars, and excludes lost profits, business interruption and other indirect damages. Section 5.2 gives the customer an intellectual property infringement indemnity covering United States and Berne Convention rights, with defined exclusions, and section 5.1 sets the reciprocal obligation. Section 6.1 warrants that the service will perform in all material respects as documented for the whole term, a functionality warranty rather than an as is disclaimer. Support and uptime are referenced at section 1.10. The indirect damages exclusion protects only Billables AI, the sole remedy for breach of warranty under section 6.2 is prompt correction, with no refund, credit or termination right, and no insurance position is stated, while the uptime service level sits in an unpublished Service Description.
An intellectual property indemnity comes with Brightflag's generative AI terms. If a third party claims an output or a generative feature infringes its rights, Brightflag indemnifies the customer against damages finally awarded by a court, provided Brightflag can defend the claim. The indemnity excludes customer modifications, combination with other technology, customer inputs, known infringement, patented inventions in outputs and trademark use of outputs, and the terms state no cap. Otherwise the features and outputs are provided as is, with accuracy not warranted. Liability caps and exclusions for the platform sit in Brightflag's subscription agreement, which is signed with each customer and not published. The generative AI terms, last updated 6 March 2025, are incorporated into that agreement and take precedence over it for generative features.
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.
Microsoft 365 including Outlook and Teams, Google Workspace, Adobe, Zoom and the Chrome and Edge browsers are the named connections, covering email, calendar, documents, calls and browsing. The customer chooses which tools to connect, in what is described as a two click setup with custom built integrations, so capture is opted into tool by tool. Entries leave only after the timekeeper releases them. No practice management or billing system is named on the vendor's own pages; third party sources name several. No connector list, API reference or developer documentation is published.
Each connection and what it does is named on Brightflag's integrations page. Approved invoices go to Coupa, Workday, NetSuite, Dynamics 365 and other accounts payable systems, with payment statuses returned to Brightflag, and the page also lists SAP Ariba, SAP S/4HANA and Oracle Fusion. The FAQ describes three finance routes, which are email with a cover page, CSV batch files over SFTP on an hourly, daily or weekly schedule, and the API. Integrations with iManage and NetDocuments link matters to document workspaces, and Jira tickets and Xakia intake submissions create matters. Okta and Microsoft Entra handle sign in and user provisioning. Law firms submit LEDES 1998B or LEDES 98BI version 2 files, PDF invoices or global e invoicing XML. An API and an MCP server connect AI tools such as Claude, Microsoft Copilot, ChatGPT and Gemini, and every role and access restriction set in Brightflag applies in the connected tool. The connector is read only, so approvals, edits and rejections stay in Brightflag.
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.
Nothing published says where the platform runs or how customers are separated. No cloud provider, hosting region or country is named, no residency option is offered, processing is not distinguished from storage, and no on premises or customer cloud option exists. Section 1.9 names data isolation without describing a tenancy model or mechanism. The platform connects into a firm's email and document systems and processes a continuous stream of activity from client work. A trust center is linked from the home page.
Hosting for Brightflag's cloud software is a multi tenant AWS environment, with data centers in Ireland, the United States and Australia. The data center follows the customer's location and where its data originates, and the privacy notice says a customer can choose to host platform data in the European Economic Area. Websites are hosted in the European Economic Area. Generative features run from Brightflag's own AWS environment, and the terms say data does not leave that environment. The region where generative processing runs for each customer is not stated. Customer data is backed up to AWS data centers for business continuity, a security operations center monitors the infrastructure, and Brightflag publishes a system status page.
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.
Billables AI's home page has a security section stating the company is serious about security and links to a trust center on its own subdomain. No certification is named on the home page, in the terms or in the footer: no SOC 2, ISO 27001 or other standard, no auditor or report period, and no penetration testing program beyond the routine audits and vulnerability testing in section 1.9. The security commitments are concrete and sit in the agreement rather than on a badge page.
ISO/IEC 27001:2013 certification and annual SOC 1 Type 2 and SOC 2 Type 2 reports appear on Brightflag's security page, with SOC 2 covering security, availability, processing integrity, confidentiality and privacy. Its FAQ adds ISO/IEC 42001, which the security page does not list. Encryption keys are managed in AWS Key Management Service. The certificates, independent test reports and security and privacy policies sit in a trust center that Brightflag opens to prospects and customers on request. The open pages give no auditor, report period or certificate date. The security page still cites the 2013 edition of ISO 27001, whose transition period to the 2022 edition ended in October 2025. Penetration tests come from CREST certified testers. Employees take mandatory security and privacy training when they join and during employment, and Brightflag runs regular phishing simulations. It states compliance with GDPR, CCPA and CPRA. Brightflag acts as a data processor for personal data in the platform, and Ireland's Data Protection Commission is its supervisory authority.
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.
No model, version or provider entity is named, and nothing states whether any component is built in house or reached through a third party. Nothing describes where inference runs, what any provider may retain, or whether customers would be told if the model set changed. Section 1.7 of the terms refers to methods, techniques or models in the abstract when permitting use of aggregated deidentified usage data. No subprocessor list exists in the agreement or anywhere else. The system reads a lawyer's email subjects, document activity and calendar to infer what work was done, and nothing published says whether that stream reaches a third party model provider or stays inside Billables AI's own systems.
Invoice summaries run on AI21 Labs' summarization model and Ask Brightflag on Anthropic's Claude, per Brightflag's generative AI terms. Both run from Brightflag's AWS environment, data does not leave that environment, and the model developers receive no customer data. The terms say the models may change from time to time and ask customers to check the terms periodically, while Brightflag's promise of notice covers material changes to the terms themselves. The terms, last updated 6 March 2025, list two features, and Brightflag now also markets generative matter summaries, AI built vendor profiles and Ask Brightflag on the invoice review page. Users agree to AI21's Responsible Use Policy and EULA, Anthropic's Usage Policy and Commercial Terms, and AWS's Responsible AI Policy and service terms. Invoice classification runs on Brightflag's own supervised model. No model versions are given.
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.
Billables AI's pricing page lists three plans charged per user a month. Single, at $47, captures time from one workflow such as email and connects to a practice management system. Standard, at $109, captures time across email, calendar, browser, meetings and documents and adds training, onboarding resources and analytics. Premium, at $169, adds delegated access, single sign on, prebill review, unlimited questions to its insights layer and compliance checks. Each plan is marked 15 percent off with yearly billing, and the page sets no minimum number of users, no minimum term and no setup fee, with custom pricing for volume. Section 1.1 of the terms points customers without a signed order to a plans page at billables.ai/plans, which returns a 404, while the prices sit on the pricing page. Section 2.2 sets monthly invoicing with late interest at 1.5 percent a month, section 3.1 renews automatically unless thirty days notice is given, and section 1.2 offers trials as is, without indemnity, support or warranty.
How Brightflag charges is set out in its FAQ without figures. Customers pay a fixed one time implementation fee and an annual subscription based on their annual outside counsel spend, and quotes are sized to that spend. Upgrades, maintenance, support, ongoing training, additional users or vendors, storage, bandwidth and custom reports carry no extra charge. Average implementation takes six weeks for first time buyers and ten weeks for replacement buyers, according to a Forrester Total Economic Impact study. The same study is the source of the savings figures on Brightflag's pages, including roughly $160,000 a year from billing compliance. Brightflag has no pricing page.
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.
Three dedicated solution pages address timekeepers, managing partners and legal administrators, and the named customers include managing partners, chief executives, office administrators and directors of operations. The buyer type is stated broadly as lawyers, consultants and professional services providers. No jurisdiction is named, which leaves unstated whether the product handles activity in languages other than English or billing conventions outside the US. No practice area is mentioned and no firm size range is given, though the named customers are small and midsize firms rather than large ones. Nothing states what the product does not cover, including the limit that work performed away from a connected application cannot be captured.
Corporate legal departments buy Brightflag, from high growth companies to global enterprises with complex, multi jurisdictional operations. Its FAQ names technology, financial services, healthcare, manufacturing, energy, consumer goods and education among the industries it serves. Its stories cover SMBC, Lufthansa, Syngenta, Dropbox, Docker, AIB, Ocado and Ironclad. The buyers are in house legal and legal operations teams and their finance counterparts. Brightflag has offices in Dublin, New York and Sydney, hosts data in Ireland, the United States and Australia, and runs tax workflows for North America, Europe and Asia Pacific. The product covers outside counsel spend, matters, vendors, budgets, accruals and reporting. Contract drafting and legal advice sit outside it, and law firms take part only as vendors submitting invoices.
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?
No clause in Billables AI's terms addresses training on customer content either way. Section 1.6 limits the vendor's use of Customer Data to providing the service. Section 1.7 permits use of Usage Data to improve the service and any methods, techniques or models, but Usage Data is defined as diagnostic, performance and telemetry data in aggregated deidentified form, which excludes the customer's work content. Section 1.9 gives the quoted commitment that underlying documents and emails are not stored, keeping only activity metadata and the generated billable records.
The silence takes the form of an improvement right over telemetry that names models but never names training; no policy page addresses training either.
Brightflag's Supplemental Terms of Use for Generative AI Features, last updated 6 March 2025, are incorporated into each customer's subscription agreement and take precedence for generative features. Under them, customer data is not transferred to the third party model developers, who cannot and do not use inputs or outputs to train their models. Brightflag will not use customer data to fine tune the model instances it operates.
The terms cover invoice summaries on AI21 Labs' model and Ask Brightflag on Anthropic's Claude. Brightflag's own classification model, refined since 2014 on labeled text from actual legal invoices, sits outside them, and Brightflag does not name the source of that text. Vendor benchmarking uses data aggregated across Brightflag customers. The terms also bar customers from using the features to build competing products or train competing AI models.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Section 1.9 of Billables AI's terms limits storage to metadata about user activity and the generated billable records, and commits that documents and emails are not stored or retained. It also confirms the customer controls its data and can access, delete and manage it, giving a deletion route on demand. Section 1.6 says Customer Data may be irretrievably deleted if the account is terminated, a warning rather than a commitment, which affects a customer needing historical time records after leaving.
No period is stated for activity metadata, generated entries or narratives during the term, and no retention setting is described. A data processing addendum is mentioned at section 1.8 as agreed between the parties and is not published.
Brightflag's security page says data retention and deletion are configurable to each customer's requirements, and that its retention management keeps records no longer than needed. The privacy notice keeps basic customer account data for six years after a relationship ends, for tax and legal purposes, and profile and support data for the life of the account. The generative AI terms set no separate period for invoice summaries or Ask Brightflag questions and answers, which run inside Brightflag's AWS environment.
Deletion at the end of a contract is governed by the subscription agreement and data processing agreement Brightflag signs with each customer.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Section 1.9 of Billables AI's terms names data isolation among its security practices, and its home page says customer data is isolated and anonymized. Neither says what is isolated from what: customers, users within a firm, or matters. A user's time reports are visible only to that user until released, a boundary per timekeeper inside the firm. The product attributes a lawyer's whole day across clients and matters, and nothing published addresses whether a conflicted matter's activity could reach a user who should not see it.
Four standard client roles make up Brightflag's own permission model. Ordinary users see only matters where they are a participant or internal matter lead, and invoices for those matters or in their approval workflow. Department overview users see only the departments in their profile, overview users see all matters and invoices without admin settings, and administrators see everything and manage configuration. Matter teams control which members can access each matter, and a user without access to a workroom asks the customer's Brightflag administrator to be added.
Email approval works only for invoices at the reviewer's own stage of the approval process. Ask Brightflag is open only to administrator and overview roles, and the MCP connector applies every role, access restriction and data boundary configured in Brightflag. iManage and NetDocuments integrations link matters to document workspaces.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Section 4 of Billables AI's terms permits disclosure of Confidential Information as required by law or court order, conditioned on the quoted terms, so the customer is told and the vendor must try to narrow what goes out rather than simply comply. The duty is mutual and survives termination under section 3.4. The clause protects Confidential Information, defined by marking or by what the recipient should reasonably have known was confidential, not Customer Data as a category, so whether it covers a demand for a firm's time records is left to interpretation. Notice is prompt rather than advance, so the customer may learn of a disclosure only after it happens.
Under the privacy notice, Brightflag may disclose any information to government officials as necessary to comply with laws and orders if compelled. It may answer a request where it believes, in its reasonable discretion, that the request is lawful and disclosure reasonably necessary. It may also disclose personal data to respond to subpoenas, court orders or legal process. The notice states no commitment to tell the customer when that happens.
Brightflag acts as a processor for customer data in the platform, and any notice term would sit in the subscription agreement and data processing agreement it signs with each customer, which stay off its website. Brightflag issues no transparency report.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Billables AI supplies no content collection and claims none. The input is the customer's own activity from its connected applications, so there is no licensed database or third party content behind any output. The system must recognize client and matter identifiers to attribute work, and nothing says where its client and matter list comes from or how it is kept current.
The customer's own invoices, matters and billing guidelines are what Brightflag's AI works on, and Ask Brightflag answers only from the organization's own spend data. The vendor management page offers data aggregated across Brightflag customers, while advanced vendor management describes benchmarking and firm performance analysis built entirely from the customer's own invoice history. Brightflag's data science team developed the classification model over ten years on labeled text from actual legal invoices, and its patent covers that model.
The timekeeper rates report draws on Brightflag's database of billions of dollars of analyzed outside counsel spend, broken down by firm size and practice area. Brightflag does not say how that pooled data is anonymized or which customers contribute to it. No primary law collection sits behind the product.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
The product retrieves and cites no legal authority. Nothing on the home page, in the terms of service, the footer or the three solution pages describes a check that the client and matter data the system assigns work to stays current, though an entry assigned to a closed matter or outdated client code would be wrong.
Invoice review against billing guidelines, not case law citation, is Brightflag's work, so a citator sits outside the product. The rules it applies come from the customer's own outside counsel guidelines, and keeping them current is the legal team's work. Brightflag offers a sample set of outside counsel guidelines as a starting point. Its tax engine checks that the correct tax rates were applied when an invoice is submitted and sends the right tax code to accounts payable.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Nothing on the home page, in the terms of service, the footer or the three solution pages describes what the system does when it cannot determine an answer, and no confidence indicator is shown to the user. Nothing states what happens to activity the system cannot attribute to any client or matter, whether it is surfaced as unassigned, silently dropped or guessed at, or whether an entry the model is unsure about is flagged differently from one it is confident in. The review gate before export gives the user the last word without showing where the system was least sure.
Lines the classification model is unsure of follow a stated route in Brightflag. Brightflag's internal analysts act as expert supervisors, reviewing cases where the model is not yet confident in its interpretation and providing corrective feedback. Ask Brightflag shows how it interpreted each question through a filter explainer, and users report a wrong answer with a thumbs down for Brightflag's team to investigate. Ask Brightflag is open only to administrator and overview roles.
Its help article asks users to confirm that results match the query, such as checking that only rejected invoices appear when they asked for rejected invoices. Brightflag's FAQ says LEDES and PDF invoices are processed with equal accuracy. Customers see flags, summaries and answers without a confidence indicator.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin, and reporting drawing on it, record no case naming Billables AI or Billables Inc., and no billing or fee dispute involving the product appears in the public record. This is a statement about the public record rather than a finding about the product. The platform generates time entries and billing narratives rather than legal citations, so its characteristic failure is an entry attributed to the wrong matter or a narrative describing work inaccurately.
That surfaces as a client fee objection, a write down at review before billing, or at worst a fee dispute or disciplinary complaint, none of which is indexed anywhere comparable to a court sanctions tracker.
The AI Hallucination Cases database maintained by Damien Charlotin, which records court decisions worldwide that address hallucinated AI content and the tool involved where known, has no entry naming Brightflag or Ask Brightflag. Brightflag reviews legal invoices and produces flags, summaries and spend analysis rather than court filings.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No public material on the home page, the terms of service, the footer or the three solution pages for timekeepers, managing partners and legal administrators engages guidance from any professional body. Nothing names the duty to charge a reasonable fee, the guidance on billing for time actually expended, or any state bar opinion on automated or reconstructed timekeeping, and no newer guidance on generative AI is cited in connection with machine written narratives that a client will read as the lawyer's own description of their work.
The only related published language is the contractual requirement at section 6.3 that the customer review output for accuracy and appropriateness, which allocates the duty without naming what governs it.
Professional conduct material from Brightflag is written for the client paying the bill. Its sample outside counsel guidelines, in a newly updated edition, add a clause giving the legal department visibility into outside counsel's use of AI. Its outside counsel AI strategy guide helps legal teams encourage good use of AI by firms, set guardrails and measure the effect on legal service delivery. The rules Brightflag enforces are the customer's contractual billing guidelines.
None of this material names a bar opinion, such as ABA Formal Opinion 512, or a professional rule on reasonable fees or billing for AI assisted work.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Billables AI's central published claim is that firms capture ten to thirty percent more billable time than under their previous methods, alongside a ninety percent reduction in time spent writing narratives, so the bill goes up rather than down. Efficiency and revenue claims are published with no disclosure treatment attached. Nothing addresses whether a client is told that narratives on their invoice were machine written, whether entries surfaced by inference rather than recorded at the time are identified as such, or how a firm should satisfy itself that newly captured time was properly billable to that client.
The product generates a record of time for each matter, which is not a record of AI assisted work, and nothing marks which entries the model produced.
Brightflag is the payer's record of outside counsel fees. Its AI reads and classifies every invoice line, the rules engine flags breaches of the customer's billing guidelines, and reviewers approve, adjust or reject before approved invoices go to accounts payable. Customers can approve invoices automatically when they meet set criteria, such as invoices under $5,000 with no guideline violations. The tax engine itemizes tax jurisdictions, types and rates on each invoice, and each invoice is processed in one currency.
Budgets, accruals and forecasts track spend against plan, and approved invoices go to accounts payable by API, batch file or email. Lufthansa uses the auto reject function so that non compliant invoices no longer reach its in house lawyers. Brightflag's sample outside counsel guidelines include a clause on outside counsel's use of AI, and the guidelines a customer adopts are translated into rules the system checks.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Billables AI's full terms of service are public, including section 1.9's commitment that underlying documents and emails are not stored or retained, encryption in transit and at rest and data isolation, and section 4's confidentiality and compelled disclosure notice terms. No subprocessor list exists, no AI or model provider is named, and the data processing addendum is described at section 1.8 as agreed between the parties, not published. A trust center is linked from the home page.
The model providers a client might ask about are named in Brightflag's generative AI terms, attached to its help center article. AI21 Labs supplies the invoice summary model and Anthropic's Claude runs Ask Brightflag, both from Brightflag's AWS environment with no data passed to the developers. The privacy notice says every subprocessor, including AI subprocessors, is listed in Brightflag's data processing agreement and in its trust center, which Brightflag opens on request.
Users of the generative features also agree to each provider's acceptable use terms, which the terms list. Certificates, independent test reports and security policies sit in the same trust center.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Nothing on the home page, in the terms of service, the footer or the three solution pages addresses disclosure of AI involvement, and no record identifying which entries or narratives a model produced is described as available or exportable. The usual forum is a fee audit, a client billing guideline review or a fee dispute rather than a court. Every entry starts as a machine generated draft that the timekeeper may then edit or delete, but nothing states that the difference between entries accepted as generated and entries materially revised is captured, retained or exportable, and no audit trail of edits is described. Time records export to billing systems, but that is the work record rather than a record of how it was produced.
Each invoice decision leaves a record in Brightflag. Flags tie each line to the guideline or rule it breaks, such as a billing rule violation or a rate discrepancy. Approval workflows record each approval, and customers can track application actions in the product and request fine grained audit logs. Brightflag's SOC 1 report, scoped in 2021 to invoice approval and accruals management, tests the controls behind that record.
Each invoice's approval workflow, with its approvers, is visible on the invoice, and email approvals follow the same workflow rules. Ask Brightflag shows how it interpreted each question, and the MCP connector is read only, so outside AI tools cannot change the record. The record covers billing decisions rather than a per document account of which model produced which output. Brightflag's output is invoice flags and spend analysis, which reach a court mainly in a fee dispute.
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.
- Primary Law Corpus Provenance
- Good Law Verification
- Bar Guidance Alignment
Which one fits
Choose Billables AI if
- Nobody at the firm is writing time down. Billables AI connects to the applications where work happens, including Microsoft 365 with Outlook, Teams and Word, Google Workspace, Adobe, Zoom and the Chrome and Edge browsers. It separates billable work from everything else, calculates a duration without start and stop input, matches it to the client and matter, reconciles overlapping activity and writes the narrative. The customer connects each tool, and the product learns each timekeeper's preferences and writing style.
- The lawyer sees the entry before anyone else does. A user's time reports are visible only to that user, who can edit or delete any record before it is exported or shared. Section 6.3 of the terms requires the customer to review output for accuracy and appropriateness before relying on it, and the intelligence layer shows firm leaders approval status by user, client and matter.
- You do not want your emails on a vendor's servers. Section 1.9 of Billables AI's terms limits storage to metadata about user activity and the generated billable records, and commits that underlying work product such as documents and emails is not stored or retained. The same section confirms the customer controls its data and can access, delete and manage it, and section 1.6 limits Billables AI's use of customer data to providing the service.
Choose Brightflag if
- You want arriving invoices measured against your own rules. Brightflag's supervised model classifies every invoice line by phase and activity, and its rules engine checks each line against the department's outside counsel guidelines. Each flag ties to the rule it breaks, lines the model is unsure of go to Brightflag's analysts, and approval workflows sit between a flag and a payment before approved invoices flow to accounts payable.
- Your assurance review covers the AI itself. Brightflag's FAQ states ISO/IEC 42001 certification for its AI management system, and its security page lists ISO 27001 and annual SOC 1 Type 2 and SOC 2 Type 2 reports. SOC 2 covers all five trust services criteria, and the certificates and reports sit in a trust center opened on request.
- You want the controls and the AI providers named. Brightflag encrypts data at rest with AES 256 under AWS Key Management Service and in transit with TLS 1.2 or higher. SAML single sign on works with six named identity providers, SCIM handles provisioning and removal, and access can be limited to set IP ranges. Its generative AI terms name AI21 Labs for invoice summaries and Anthropic's Claude for Ask Brightflag.
In summary
Billables AI
Billables AI records a lawyer's billable time without the lawyer recording it. It connects to Microsoft 365 with Outlook, Teams and Word, Google Workspace, Adobe, Zoom and the Chrome and Edge browsers, separates billable work from the rest and calculates durations without timers. It then matches work to the client and matter, reconciles overlapping activity and writes the narrative in each timekeeper's style. Section 1.9 of its terms limits storage to activity metadata and the generated billable records. Time reports are visible only to the timekeeper until released, and an intelligence layer shows firm leaders hours, realization and approval status. Plans run from $47 to $169 per user a month.
Brightflag
Brightflag is a legal spend and matter management platform for corporate legal departments, founded in Dublin in 2014 and owned by Wolters Kluwer since June 2025. A supervised model reads every line of every invoice narrative and classifies it by phase and activity, and a rules engine checks each line against the department's outside counsel billing guidelines before reviewers approve. Matter and vendor management, budgets, accruals, spend forecasts and reporting sit around it. Ask Brightflag answers spend questions on Anthropic's Claude, and invoice summaries run on an AI21 Labs model, both inside Brightflag's own AWS environment, with no customer data passed to the model developers. Brightflag states ISO 27001, SOC 1 Type 2, SOC 2 Type 2 and ISO 42001 certification. Pricing combines an implementation fee with an annual subscription based on outside counsel spend.
Questions buyers ask
Are Billables AI and Brightflag alternatives to each other?
No. They sit on opposite sides of the same invoice. Billables AI creates the time entry inside the law firm, inferring what was billable from the lawyer's own activity across email, documents and calls. Brightflag reads the invoice that results for the department paying it and checks every line against that department's billing guidelines. A narrative Billables AI writes for a firm can end up as an invoice line that Brightflag's model classifies for the client. From the AI Legal Index, based on each vendor's own published materials as of October 9, 2026. No vendor pays for placement.
What does each actually infer?
Billables AI infers whether work was billable, how long it took without a timer, which client and matter it belongs to, and how to describe it in the timekeeper's own style. Brightflag infers what each invoice line describes, classifying it by phase and activity on an extended UTBMS framework, then applies the department's guidelines to it. Both make judgments about the same work from opposite ends of the billing relationship, one for the firm and one for its client. From the AI Legal Index, based on each vendor's own published materials as of October 9, 2026. No vendor pays for placement.
Who sees the output before it goes anywhere?
On Billables AI, only the timekeeper, who can edit or delete any record before it is exported or shared. On Brightflag, flags reach reviewers inside the legal department, lines the model is unsure of go first to Brightflag's analysts, and approval workflows decide what is paid. Customers can auto approve invoices that meet set criteria, such as those under $5,000 with no guideline violations, which the FAQ says can be about 30 percent of invoices. From the AI Legal Index, based on each vendor's own published materials as of October 9, 2026. No vendor pays for placement.
What does each say about the data it holds?
Billables AI's terms keep only activity metadata and the generated billable records and commit that documents and emails are not stored. The customer can access, delete and manage its data, with no period stated for what is kept. Brightflag makes retention and deletion configurable to each customer's requirements, encrypts data with AES 256 under AWS Key Management Service and keeps basic account data for six years after a relationship ends. Its generative features run inside its AWS environment, and model developers receive no customer data. From the AI Legal Index, based on each vendor's own published materials as of October 9, 2026. No vendor pays for placement.
What do Billables AI and Brightflag both leave unpublished?
Neither publishes an accuracy rate for the inference each is sold on, whether matching time to a matter or flagging an invoice line. Neither names a bar opinion or rule on billing for AI assisted work, although Brightflag's sample outside counsel guidelines give a department visibility into a firm's use of AI. On prices they differ, since Billables AI lists plans from $47 to $169 per user a month and Brightflag sizes its subscription to outside counsel spend. On models, Billables AI names no provider and Brightflag names AI21 Labs and Anthropic's Claude. From the AI Legal Index, based on each vendor's own published materials as of October 9, 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.
Billables AI markets capturing 10 to 30 percent more billable time than a firm's previous method, and a 90 percent reduction in time spent writing narratives. Its terms do not say whether clients are told that narratives were machine written or which time entries came from inference. Brightflag's generative AI terms state that outputs are not legal advice and leave human review to the customer, and its sample outside counsel guidelines add a clause on outside counsel's use of AI. The Billables AI agreement points a customer without a signed order to a plans page at billables.ai/plans for fees, and that address returns a 404, while the prices sit on its pricing page. Billables AI's support and uptime levels sit in a Service Description that section 1.10 of its terms references. Brightflag's platform liability terms sit in the subscription agreement it signs with each customer. Neither vendor reviewed this page.