L

Legal Decoder

The models turn billing prose into data, and a rules engine does the judging. Legal Decoder's own framing is that UTBMS codes tell you what was billed but not what happened, so its technology reads the narrative itself: entries are parsed, categorized, enriched, standardized and then evaluated against more than 45 proprietary compliance flags. Aperture adds a natural language interface on top, and the vendor is explicit that the AI agents decide what data and calculations a question needs while a separate deterministic engine does the arithmetic.

Underneath the language work sits an analytics platform of flags, benchmarks and indices that would still run on structured invoice feeds without any model reading prose.

The method is described in detail and the performance is not measured. Aperture's published answers show an Analysis Request Breakdown setting out the data used for the response, and every figure is computed by a deterministic engine rather than the model. The underlying flags are documented down to the individual rule. Worked examples in the published bankruptcy retrospective show which entries triggered which flag and why.

What is asserted rather than tested is quality. The site describes the methodology as validated by courts and says Legal Decoder is the only invoice review technology accepted at the federal court level, without citing a decision or naming a court. No accuracy, false positive or agreement rate for the flags is published.

The product flags and a person decides, and the review surface is the flag itself. Every flag attaches to an individual line item with the rule that fired, and users drill from an index category to a timekeeper to the entry, so each conclusion can be checked against the billing record behind it. Aperture is described as sticking to observations and suggested next steps by default and producing a specific action plan only when asked.

Users hold read only permissions, so nothing in the analysis can alter the underlying billing data. What is not published is any threshold or confidence level at which a flag fires, or guidance on what a flagged entry may not be used for when it becomes the basis of a fee objection or a write down.

The numbers are real and the customers are not named. The published Allied Nevada Gold retrospective analyzes a named Chapter 11 case: over fifty invoices and 2,000 pages covering 10.7 million dollars in fees, 14,755 line items and 135 timekeepers across eight named law firms, with over 21,000 flags and roughly 2.4 million dollars identified as unrealized savings, and findings for each firm set out with percentages. That is a demonstration on public court filings rather than a customer deployment; the firms analyzed are the subjects, not the buyers.

The other success stories, including an AmLaw 100 firm's risk management program and the Toys "R" Us fee review, describe the customer only by segment, and the homepage quotes are attributed to roles rather than people.

The confidentiality commitments are specific to the one thing this product handles, and they sit outside any agreement a buyer can read. Invoice narratives describe matters, clients and strategy, and Aperture's published answers address that directly. Identifying fields such as matter, client and attorney names are tokenized before any data reaches the model, so the model sees strings like Matter_ABCDEF. Tokens cannot be reverse engineered, new identifiers are generated each session rather than held in a persistent vault, and results are remapped inside Legal Decoder's own environment.

The vendor also states that data is never used to train models and that users hold read only permissions. Nothing published addresses separation between customers, or privilege or work product in the narratives. Both the Terms of Use and the Privacy Policy state that client processing is governed by separate master services and data processing agreements that are not published.

The line between analysis and judgment is drawn in the vendor's own words. The published methodology states that the technology neither provides legal advice nor operates as a referendum on the quality of legal services provided or the outcome delivered by outside counsel. That is the relevant disclaimer for a product whose output is used to challenge another lawyer's fees. The Terms of Use dated 21 January 2026 add that website content is not legal advice and creates no attorney client relationship.

What is missing is the other half. Nothing addresses the duty of the person acting on a flag, whether a fee examiner, a general counsel or a billing partner, or what review a flagged entry should get before it becomes an objection or a write off.

How the system works is explained; how it is governed is not. The Aperture material is open about mechanism. It says the model plans the analysis and never calculates, that tokenization happens before processing, and that the underlying data is parsed, categorized, enriched, standardized and evaluated in sequence. Nobody inside Legal Decoder is named as accountable for the flags or the models, nothing describes what is tested before a rule or release ships, and no evaluation results are published.

Nothing addresses whether flags fall unevenly across practice areas, firm sizes or timekeeper seniority, which matters for a product whose output is used to question individual lawyers' bills.

One question is answered precisely and the rest are not. The Aperture material says the product is not a system of record and does not store, own or act as the repository for billing information, which should remain in the customer's electronic billing or matter management system. It also says users have read only access. Beyond that, no retention period for what Legal Decoder does hold, no deletion commitment, no encryption statement, no subprocessor list and no incident practice is published.

There is no security or trust page anywhere on the site. The Privacy Policy dated 21 January 2026 covers website visitors and marketing only, and states that client processing sits under separate agreements that are not published.

Nothing published says who bears the loss if a flag is wrong. The Terms of Use dated 21 January 2026 govern the website: they disclaim warranties, exclude indirect and consequential damages and require the user to indemnify Legal Decoder, and they address the website rather than the analysis a customer buys. The Privacy Policy points client processing to master services and data processing agreements which are not published, and no warranty, indemnity, cap or insurance position covering the product is published.

For a product whose output is used to reduce another party's fees, nothing addresses the consequences of a mistaken flag.

No integration into the systems legal billing already runs through is published. Aperture is described as a complementary analytics layer rather than a replacement for an electronic billing or enterprise legal management system, and the customer's system is expected to remain the system of record, but nothing names a single one of those systems, describes how invoice data reaches Legal Decoder, or documents an API, file format or connector.

There is no integrations page and no developer documentation; the Partners page describes commercial partnerships with alternative legal service providers and consultancies rather than technical connections.

Nothing published says where the software runs or where invoice data is held. The product is reached through a web portal, and no tenancy model, hosting provider, region or residency option appears anywhere; the Privacy Policy addresses website data and says nothing about where client processing happens. Buyers in this market routinely send an entire outside counsel spend file, which makes the absence a live question for a procurement review.

No independent security attestation is published. There is no security page and no trust center on the estate, and no SOC 2, ISO 27001, penetration test or named auditor is mentioned on any page; the only security language is the Privacy Policy's statement that reasonable administrative, technical and physical safeguards are maintained and that no system is completely secure.

The model is referred to and never identified. The Aperture material describes data being sent to an LLM after tokenization and says potentially sensitive fields are protected before any data reaches the AI model, which tells a buyer that a third party model is in use without saying whose. No model, version or provider is named, nothing states where inference runs, and no commitment to notify customers when the model changes is published.

The vendor's own distinction, that the model plans and explains while a deterministic engine computes, limits what the unnamed model actually decides.

No price, rate or unit of charge is published: there is no pricing page, tier, rate per invoice or per dollar reviewed, or trial, and every route ends at a scheduled call. Pricing Decoder is a product for pricing legal work, not a statement of what Legal Decoder costs.

Three buyers are addressed with separate pages and different arguments: corporate legal teams justifying outside counsel spend, law firms defending rates and realization, and bankruptcy fee examiners reviewing fee applications, with the bankruptcy work documented in detail against the US Trustee Program's 2013 guidelines. The analytical coverage is specific too, with the flag set organized into staffing efficiency, workflow efficiency and billing hygiene and individual rules named.

What is not stated is the boundary: nothing says which billing formats, jurisdictions, languages or alternative fee arrangements the analysis handles poorly, or what happens with billing that is not hourly.