Agent

Underwriting brief

Underwriting starts with a pile of assumptions and ends with a number, and the argument is always about the assumptions. This agent reads the rent roll, the tenancy schedule and the deals your team has done before, then writes out each input with the document it came from. The model stays yours; what changes is that every input arrives already evidenced.

How it runs

Step by step

01

Connect the deal room

The agent is given read access to the data room, the tenancy documents and the folder holding your precedent deals.

02

Set your underwriting input list

Your team names the inputs that matter: passing rent, ERV, void assumptions, incentives, non-recoverables. The agent works to that list and no other.

03

It reads the tenancy position

Rent roll and schedule are pulled into a single view, tenant by tenant, with the document reference against each line.

04

It sets inputs against precedent

Each assumption is shown next to the terms your firm agreed on comparable deals, so the analyst can see where this one sits.

05

It flags thin assumptions

Inputs with no supporting document, or where the rent roll and the lease disagree, come back marked rather than smoothed over.

06

The deal lead approves

The brief is only filed and used in an investment paper once the deal lead has read the flagged items and signed it off.

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

Acquisitions analysts building a first cut of the model, and the deal lead who wants to see where each assumption came from before the paper is written.

Escalation

When it asks a person

The deal lead approves the brief before it is used in an investment paper

Applications & Rights

Which tools it uses, and what it may do in each
DropboxRead only
SharePointRead only
Google DriveReadWrites 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

Acquisitions analysts building a first cut of the model, and the deal lead who wants to see where each assumption came from before the paper is written.

What you’ll need

  • Deal room and precedent files connected
  • An agreed list of underwriting inputs
  • A location for the filed brief
  • A deal lead to approve

What you get

  • An assumption sheet with sources
  • A tenancy summary from the rent roll
  • A list of inputs with no evidence

What it doesn’t do

It does not build, run or check a financial model, and it produces no valuation. Where the rent roll and the leases disagree it shows both and asks, rather than picking one.

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 rent roll transcriptionAssumption logs kept by hand
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Does it plug into our model?

It writes the brief, not the model. Most teams keep their model exactly as it is and paste in from a sourced assumption sheet, which means the model's history and its checks are untouched. Where the assumption sheet lives is your choice.

What if the data room is badly organised?

That is the normal case and it does not stop the agent, because it indexes what is there rather than expecting a structure. Scans that cannot be read are reported as unreadable, not skipped quietly.

How does it know what our precedents are?

It reads the completed deal files you connect. In the co-build we agree what counts as comparable for your strategy, so the comparison is drawn from deals you would actually cite in a committee.

Who sees the brief?

Whoever your rights configuration allows. The agent inherits the permissions on the underlying folders, so an analyst without access to a given deal room does not get its contents through the agent.

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.