One deal, too many tools: why deal workflows are consolidating

Ask an advisor running four transactions at once how the third one is tracking. Most will get you an answer, though it might take a while. They open the data room, then a spreadsheet to check which questions are outstanding, then email to work out which bidder has gone quiet. Some time later, you may have a reliable picture. Or you may not. 

That is what fragmentation looks like in practice. One transaction, running across several systems that were never built to talk to each other. The documents sit in the data room. The Q&A is tracked in a spreadsheet. Which bidders are still warm sits in somebody's inbox, or in their memory. Every piece is somewhere sensible. None of it is in the same place. 

On a single transaction, it is an annoyance you can work around. It becomes a bigger problem once a team is carrying five, six or more at the same time, with bidders coming in and out across multiple deals. Getting a snapshot of the whole book of work is close to impossible, and what people are working from is only as good as the last time someone assembled it.

What fragmentation costs

Lost hours are the obvious cost. But drawing from our decades of experience in this space, we know that the more serious issue is the risk to the deal itself. 

When documents live in one place, and the record of who has seen them lives in another, the gap between the two is where mistakes happen. A file goes to a bidder who should not have had it yet. A question gets answered with information that the party has never been given. Some of that is recoverable, and some of it is not. 

There is another cost. Bidders come in and drop out of a process, and maintaining competitive tension depends on noticing that movement early. When it takes effort to see who is engaged and who has gone cold, people check less often. A bidder whose interest is fading is useful information on Tuesday. Less so by the following Friday.

In short, the work has outgrown the tools it was being run on. Ansarada's own transaction data points to deals taking longer to complete up from 11.8 months in the first half of 2025 to 13.4 months in the first half of 2026, and the volume of material moving through each process has grown with them. 

Stitching more tools together only adds more connections to manage. Integrations pass data between systems, which helps, but somebody still has to sit down and assemble the answer. That work disappears when the platform is built as one system from the start.

Ansarada has facilitated more than 60,000 critical transactions across 170 countries, is trusted by four of the Big Four and 85 of the ASX 100. One pattern is consistent across that work. We know that the deals that run cleanly are the ones where nobody has to go hunting for the current position.

One release, many benefits

This is what we have been working towards with Ansarada OS, the operating system for every deal. Ansarada OS brings several improvements together as one connected platform experience.

Intelligence. The Ask AiDA entry point sits in the platform navigation. Users can open Ask AiDA from the platform experience, with AiDA remaining scoped to the selected or most recently accessed room and role. This is prompt-first dealmaking. The starting point becomes a question, and the answer comes back in seconds. An advisor can ask which documents cover change-of-control provisions and have an answer in seconds, drawn only from the room context they already have. 

AiDA is permission-scoped and read-only. It does not reason across rooms and cannot change permissions or send Q&A answers. It is incapable of learning from your deal: customer document content is never used to train any model.

Clarity. One home replaces a set of separate URLs, so data rooms, AiDA and subscriptions all begin and end in the same place. 

Control. Eligible subscription owners have clearer access and can manage routine changes directly in the platform. Administrators can also restore redacted documents in bulk from Manage Documents. Instead of requesting support to process a large number of documents, admins can select an entire room, specific folders or individual documents, and begin the unredaction process themselves.

Speed. Bulk import lets a team export the scoped questions, draft answers offline in Excel where they are collaborating anyway, then bring the batch back in one upload. On a batch of 200 questions, that removes two to three hours of copying and pasting. Answers arrive as drafts, so review, approval and disclosure work as they did before.

Together, these changes improve buyer confidence in the deal process. When information is complete, accessible and well understood, you are far less likely to be caught off guard at a critical moment in the process.

What this changes for advisors

Taken together, they add up to what advisors ask us for, which is total confidence, clarity and control from preparation to close. You know what is happening on each deal in real time without rebuilding the picture first, and fewer places for a version to go astray means fewer surprises at the point that matters.

In a competitive process, a disclosure error can reset a negotiation or even lose you a bidder. Fragmentation slows a team down, and it also puts the outcome and the advisor's name on the deal at risk.

That is what an operating system for every deal means in practice. It is dealmaking, designed for the AI era.