AG, Light Frame and Allocare: what survives a workflow change?
AI deployment, wealthtech funding and a software acquisition raise a practical question: can firms retrieve the instruction, reviewed version and approval?
The brief
Three developments put the continuity of professional work in focus. Addleshaw Goddard announced a Harvey collaboration with workforce access planned from January. Investor Tenity announced participation in Light Frame’s $5.1 million seed round. PwC confirmed the sale of Allocare to Volaris, a transaction that closed on 1 October. These establish plans, funding and ownership changes; they do not establish measured improvements in client outcomes. Our analysis is to ask what evidence survives when a workflow changes. For a legal review or portfolio instruction, can the organisation retrieve the original input, the version reviewed, the approval and the action taken? Buyers should request a demonstration of that chain using their own fictional scenario before treating a product announcement as operational assurance.
The full record
Addleshaw Goddard’s 9 November release says Harvey will be available to more than 3,400 people from January. It says 400 of its people tested leading platforms over three months, and that their feedback shaped improvements to source checking and preservation of reviewed work. These are the firm’s descriptions, not independently audited performance results. AG announcement.
Tenity’s 10 November release reports Light Frame’s $5.1 million financing and describes modular core-banking and portfolio software with live client operations in EMEA. As a participating investor, Tenity has a commercial interest. Its release supplies no comparable error-rate or client-outcome benchmark. Tenity announcement.
PwC, adviser to Allocare’s shareholders, says 100% of the shares were sold to Volaris and the transaction closed on 1 October. It says the brand and management team are retained. The announcement is evidence of a completed ownership change; it does not settle the terms of an individual customer’s contract. PwC transaction statement.
Our analysis: ask for the evidence after the change
Use one fictional instruction with an attachment and a later correction. Ask the proposed workflow to show which version a reviewer saw, which part was approved, who authorised the next action and what was subsequently changed. Then ask someone outside the original team to retrieve that history.
This review is different from asking whether the software has an audit log. The log needs to explain the business event. A timestamp recording that a user opened a screen does not by itself show what they approved. An exported summary should be checked against the original instruction and its attachments.
Ownership and deployment call for different questions
For a deployment, establish who decides that a new process is ready and what failures would prevent release. For a change of supplier ownership, identify the contractual notification, support route and any proposed change to service delivery. Do not infer a data migration, price change or service reduction merely from an acquisition announcement.
The useful procurement output is a short acceptance record: the scenario tested, evidence retained, unresolved gaps and owner of the decision. It should distinguish a demonstrated function from a promised future capability. This is an editorial test proposal. The Formal Record has not conducted the test or ranked these providers.
Read original firm, investor and transaction-adviser statements. Allocare’s closing date is 1 October, not its November news coverage date. Funding and deployment plans are not performance evidence. No interviews or product tests were conducted; the proposed acceptance exercise is our analysis.