A

Ajax

Take the models out and there is nothing to sell. The capture layer produces a stream of activity across documents, email, browser, calls, calendar and meetings. Everything the buyer pays for happens after that, when a model reads the content of the work, decides which matter it belongs to, groups fragments together and writes a narrative in the timekeeper's own voice with an activity code. The vendor draws the line itself, contrasting its product with tools that record activity without writing entries.

The engine that turns a client's outside counsel guidelines into limits on wording is model work too. Without any of it, what remains is a timesheet of raw activity that a lawyer still has to write up.

For a timekeeping product, accuracy means whether an entry is right: the right work, the right matter, the right duration, and a narrative that describes what happened. The method is described. The vendor says it reads the content of the work rather than window titles or calendar subjects, clusters activity scattered across the day on one matter into a single entry, and identifies the client and matter by matching what is on screen against a live map of the firm's matters.

It also publishes a figure, twice in an explainer of 7 July 2026: matter matching is right about 92 percent of the time and improves as the system learns a firm's people, documents and topics. Publishing a figure below 100 is candid, but it is not something a reader can test. There is no sample, period, method or definition of a correct match, and nothing says what happens to the rest beyond the lawyer's review catching them. No figure is published for the narratives themselves, as distinct from matter matching.

The review step is built into the product, not just advised. Nothing the model writes reaches the firm's billing system on its own. Entries are drafted through the day, only the timekeeper can see them until they release them, and release is a deliberate act. The timekeeper can edit or delete any entry and stop capture with one click, and the vendor says nothing is captured until they choose to resume. The FAQ also answers supervision the other way: the firm cannot see a timekeeper's hours before release.

The rest of the control structure is not published: no point at which the model declines to write an entry, nothing on what happens after a wrong entry goes out, and no statement of what the system may not be used for.

Deployment evidence is extensive, but undated and without method. Ten firms are named with practice area, city and a figure. They include Almazan Law in Florida at 1.1 extra billable hours a day, Poole Huffman in Georgia at $32,000 recovered a month, Kirker Davis in Austin at $4,639 per timekeeper a month, Pines Federal at $42,000 a month, King Law at 121 active users across 24 offices, and Quill & Arrow at 270 professionals.

Named attorneys are quoted for each. Sixteen more testimonials carry names, titles and firms, and the vendor says fourteen customers went on to invest personally. But no case study carries a date, and no method is given for the return multiples, so figures like 67x and 58x cannot be checked or compared.

For a product that reads everything on a lawyer's screen, the published commitments are substantial, with one structural gap. The addendum of 5 August 2026 prohibits training, retraining or fine tuning on customer data and binds the named model providers to the same. Raw data is deleted after 30 days and processed data after 60, and everything is deleted within 30 days of termination. Confidentiality runs both ways in the terms.

Access is handled at the level this product needs: drafted entries are visible only to the timekeeper until released, and capture stops with one click, which is the control a lawyer on a sensitive matter needs. The vendor says in its own words that its users handle privileged client data. But privilege and work product are not addressed as such, and nothing covers separation by matter, which matters when a timekeeper is screened off a matter the capture would otherwise read.

A real position on review before billing is published, and it lives in the wrong place to earn more. An explainer of 7 July 2026 states that the lawyer's job shrinks to review, check the drafts, fix what's wrong, release to billing; that this does not mean the software bills for you; and, answering whether the output is accurate enough to bill from, that the entries are drafts until a lawyer approves them, which is what keeps billing defensible.

The same page answers whether lawyers still review entries before they are billed with a plain yes, and says drafts stay drafts until the lawyer approves them. That engages the duty this product actually raises, which is the lawyer's responsibility for a narrative the client will read as their own account of their work. Three things hold it here. The position sits in a category explainer on the blog, not in the terms, the product pages or anything a customer signs.

The fee rules the vendor names elsewhere are never connected to its own product. And nothing addresses found time, flat fees, or what a client is told about how the entry was written.

Nothing is published about how the models are governed. No one is named as accountable for what they write, nothing describes testing before a change ships, no evaluation results appear, and the privacy policy says plainly that the vendor does not test, verify or endorse AI outputs. Nothing addresses whether entry quality holds up across practice areas, seniority, or work that leaves little digital trace, which is the obvious question for a product whose output becomes a bill.

The closest thing to governance is the outside counsel guideline feature, which shows extracted rules to the firm with a link to the source page before they take effect, but that governs the client's rules, not the model.

All five elements are published in specific terms. Retention: raw data is deleted after 30 days and processed data after 60, stated the same way in the terms, the privacy policy and the addendum, and changeable only by written customer instruction. Deletion: everything is deleted or irreversibly anonymized within 30 days of termination. Access: SAML 2.0 and SCIM provisioning through the firm's identity provider, central control, automated onboarding and offboarding, and entries visible only to their author until release.

Subprocessors: seven are named, including the model providers. Incidents: notice to the customer within 48 hours of becoming aware, with a commitment to remediate. Encryption is AES-256 at rest and TLS 1.2 or better in transit. One inconsistency: the security FAQ says the vendor does not store customer data, while the agreement and addendum publish the 30 and 60 day windows.

What is published disclaims the exposure rather than allocating it. The service is provided as is, with no warranty of any kind and no undertaking that it will be error-free; AI outputs are expressly not guaranteed to be accurate, complete or suitable for any purpose, and the privacy policy adds that the vendor does not test or verify them. Liability is capped at the fees paid in the preceding twelve months and indirect, incidental, special, consequential and punitive damages are excluded.

No indemnity of any kind runs from the vendor to the customer, not even for intellectual property, and no insurance is mentioned. For a product whose output is a bill a client will scrutinize and a lawyer will sign, nothing published says what happens if an entry is wrong.

The integrations are real and named, and the depth stops at a sentence each. Eight billing and practice management systems are supported by name, each with its own page: Clio, MyCase, Filevine, PracticePanther, SurePoint, Centerbase, Actionstep and Soluno, with the claim that most other billing systems work too. What moves is clear enough: released time entries with matter, activity code and narrative already applied, out of Ajax and into the system of record.

An explainer of 7 July 2026 goes further and calls two-way sync with all eight table stakes, without saying what comes back the other way, or what happens to an entry edited in the billing system after release. On the capture side the product connects to work email, Microsoft Teams or Slack, calendar, Zoom and supported VoIP platforms, with RingCentral, Dialpad and VXT named. What an implementer would need next is not published: no field mapping, no sync behavior on edits or deletions, no error handling, and no API documentation, which the vendor offers to share with a technical team on request.

The product is clearly delivered from the cloud, and neither tenancy nor residency is answered. There is a desktop app and a hosted service behind it. Nothing published names a hosting provider, region, data center or tenancy model, or separates where the software runs from where captured work sits. The addendum comes closest. It says customer data may be processed in the United States and other countries where the vendor operates, naming no other country and offering no choice, and commits to standard contractual clauses for European transfers and Australian privacy law for Australian ones.

For a product that reads privileged documents across a firm's whole working day, a security reviewer has nothing published to start from.

The certification is stated plainly, but the evidence behind it cannot be reached. The security page claims SOC 2 Type II certification, describing independently audited security controls, data handling and infrastructure, and the terms add CASA certification. Independent audits, penetration testing and round the clock endpoint monitoring are also claimed. None of it has detail behind it: no auditor is named, no report period, scope or date is published, and there is no trust portal or route to the report. The only offer is a security review call, booked through the same form as the sales demo.

The providers are named, and the disclosure stops there. The addendum lists seven subprocessors and three of them are model providers: OpenAI, Anthropic and Google Gemini, alongside BaseTen for model serving, Amazon Web Services, Vercel and PostHog. The same section binds all of them not to retain or use customer data for their own training or fine tuning, which is the part a firm's client would ask about. What is absent is everything downstream of the name: no model or version is identified, nothing states which provider handles which part of the work, nothing says where inference runs, and no commitment is given to notify customers when any of it changes.

The shape of the deal is published in detail and the number is not. There is no pricing page; the vendor answers the question in a post of its own titled how much Ajax costs, and answers it structurally: priced per seat rather than firmwide, because a firm should not pay for timekeepers who keep their own system, with a stated expectation of 70 to 80 percent take-up; contracts are annual; a two-week pilot on the firm's real work comes before any commitment.

Elsewhere the vendor frames cost against return, saying one recovered hour per user per month covers the subscription and that payback typically lands inside eleven days, and describes itself as premium-priced in its category. The exact figure depends on firm size and seat count and is quoted on a call. No list price, no tiers and no range appear anywhere on the estate.

Coverage is shown through customers rather than claimed. The named firms span workers' compensation and insurance defense, general practice, family law, personal injury and business litigation, firms with several practice areas, lemon law, community association work and federal employment law. They are in Florida, Colorado, Virginia, Texas, the Carolinas, Tennessee, California, Georgia, Maryland and the District of Columbia, and range from solo and boutique practices to 121 users across 24 offices and 270 professionals.

The real limit is implied, not stated: the product is built for timekeepers who bill by the hour and work on a screen, so contingency work, flat fee work and work done away from a computer fall outside it. Nothing published says so, or names practice areas or firm sizes the vendor does not serve.