Agent

Diligence pack review

Every transaction has the same two problems: nobody can find the document, and nobody is sure what is still outstanding. This agent indexes the whole data room, answers questions with the page cited, and keeps a running list of what your diligence checklist asks for but the room does not contain. The deal team stops trading emails about where things are.

How it runs

Step by step

01

Connect the data room

The room is connected read-only, with rights limited to the deal team working on that transaction.

02

Load your diligence checklist

Your own checklist becomes the agent's list of required items, split by workstream: title, tenancy, planning, environmental, building.

03

It indexes every document

The whole room is read and mapped to the checklist, including the documents dropped in late and out of order.

04

The team asks in plain English

Questions are put the way they would be asked across a desk, and each answer arrives with the document and page behind it.

05

It lists what is missing

The gap list names each unanswered checklist line and what would satisfy it, refreshed as new documents land.

06

The transaction lead approves the list

Nothing is raised with the other side until the transaction lead has read the gap list and decided what to ask for.

The harness

Exactly what this agent can see, touch and change

The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.

Context

What reaches the model

Transaction managers and acquisitions surveyors running diligence on a deadline, and the lawyer who keeps being asked whether a document has arrived.

Escalation

When it asks a person

The transaction lead approves the gap list before anything is raised with the other side

Applications & Rights

Which tools it uses, and what it may do in each
DropboxRead only
SharePointRead only
Google DriveRead only
SlackWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.

Who it’s for

Transaction managers and acquisitions surveyors running diligence on a deadline, and the lawyer who keeps being asked whether a document has arrived.

What you’ll need

  • The data room connected read-only
  • Your diligence checklist supplied
  • A deal channel for the agent to post in
  • A transaction lead to approve

What you get

  • A searchable index of the room
  • Cited answers to diligence questions
  • A live gap list by workstream

What it doesn’t do

It reports what is in the room and what your checklist has not been answered by. It gives no legal or technical opinion, and a document it has not been given cannot be indexed, however confident the seller is that it was sent.

How you get it

We build the first one with you

Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

Co-build

Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Manual data room reviewSpreadsheet diligence trackers
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Can it read the room if we only have portal access?

It reads what you can export or sync to a connected store. Where a portal blocks that, teams usually mirror the room into their own document store, which is what the agent then indexes. We work that out in the build rather than assuming access.

Does it flag risk, or just gaps?

Gaps against your checklist, plus anything that contradicts another document in the room. Judging whether something is a risk to the deal is the transaction lead's call and the agent does not make it.

What happens when documents arrive late?

The index and the gap list update as the room changes, so the outstanding list stays current instead of being rebuilt each Monday. The team sees what closed and what is still open.

Who can see the answers?

Only people with rights to that room. The agent inherits the underlying permissions, and each deal is scoped separately so one transaction's content is not reachable from another.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.