COMMERCIAL REAL ESTATE · UNDERWRITING AND DILIGENCE

Automate underwriting and diligence in commercial real estate

A data room is two hundred files, and the pro forma always works because the assumptions were chosen so that it would. OutcomeCatalyst turns a scanned T-12 into general ledger detail, tests market rent against leases that actually signed rather than asking rents, checks each assumption against the deals you already closed, applies the gates your investment committee uses, and drafts the memo with every figure traced to the page behind it.

What it does

Underwriting and diligence, in plain terms

A data room is two hundred files and the answer is spread across a scanned T-12, a rent roll tab and sixty page leases. The broker's pro forma always works, because the assumptions were chosen so that it would. This tests each of those assumptions against a source document and produces the memo, not just a variance list.

Turn a scanned T-12 into GL detail
A trailing twelve arrives as a PDF image. It becomes structured general ledger lines, so real estate taxes, total opex, economic vacancy and trailing NOI are figures you can test rather than a picture of figures.
Use signed leases, not asking rents
Market rent in an OM is an assertion. What comparable space actually signed at is a fact, and the gap between the two is usually where the deal is won or lost.
Check it against your own book
Precedent from deals you already closed is the most relevant comp set you have and the one least often used, because nobody has time to pull it. Every assumption is placed against what your own transactions support.
Apply the IC gates the same way every time
The committee has criteria. Applying them consistently to every deal, rather than to the deals that made it far enough for someone to bother, is what makes the pipeline comparable.
How it works

From a data room to a tested underwriting, in four steps

Your model stays your model. This tests the inputs before they reach it.

1
Connect the data room and the comps
Files from Box or SharePoint, signed lease comps from CompStak, trades and submarket movement from CoStar, taxes and liens from county records, and your own closed deals.
2
Read every file, not the summary
The T-12, the rent roll and each lease are parsed into figures and terms: in-place rent, expiries, escalations, recovery structure, utility recovery and operating expenses by line.
3
Test each assumption against a source
Every input is checked against signed leases rather than asking rents, trailing actuals rather than pro forma expenses, and recent trades rather than a stated cap rate. Each variance cites the page behind it.
4
Produce the memo the committee reads
The output is a drafted investment memo with the comp set, the T-12 pages and the county records attached, with each assumption traceable so the reasoning can be challenged.
Why it matters

Why underwriting capacity decides what you buy

A pro forma is a marketing document that has already survived its own review. The assumptions were selected to produce a number the seller wants, which is not dishonest so much as structural. Every OM in the market works on its own terms.

What is unusual is that the evidence to disprove it typically sits in the package the broker themselves provided. A T-12 scan supporting different expense numbers than the summary page is the normal case rather than the exception, because nobody expects the scan to be read line by line.

The real constraint is that underwriting properly takes weeks of analyst time, so it gets spent on the deals that already look best. That is circular. The deals that look best are the ones whose marketing worked, and the ones worth a closer look are often the ones nobody had hours for.

Consistency compounds the problem. When two analysts underwrite two deals in two different spreadsheets, the outputs are not comparable, and a committee ends up choosing between two arguments rather than two assets.

The evidence that disproves the pro forma is usually in the package the broker gave you.
It sits in a scan nobody expected to be read line by line, which is why it stays there.
Agentic AI

Agentic AI in commercial real estate, without the hand-waving

Three words get used interchangeably by vendors and they do not mean the same thing. The difference decides whether the work gets done or just gets read.

A chatbot
Answers a question you asked. Nothing moves, and the work still sits with the person who asked.
Automation
Fires a fixed rule the same way every time. It holds until a document arrives in a layout nobody mapped, which in this business is most of them.
An agent
Reads every file in the data room, tests each assumption against your underwriting standard, drafts the memo, and hands it to the committee with the sources attached.

Most agentic AI pilots in underwriting stall for a reason that has little to do with the model. An agent asked whether a pro forma is credible needs the rent roll, the T-12, the leases, the comps and your own variance history on similar assets. That sits in a data room, an accounting system, a market subscription and somebody's spreadsheet. With no path between them the agent accepts the broker's numbers, which is the one thing it must never do.

The agents here are deliberately narrow. Each has one job, a defined set of sources it may read, a written standard to check against, and a person who approves before anything leaves the building. That is what makes them safe to run against real money, and it is why they survive an audit.

The data layer

The data layer agentic AI actually needs

Every workflow above runs on one layer. Building it is most of the work, and it is the part nobody demos.

Entity resolution
One asset appears as a street address, a parcel number, an entity name and a fund code. Tenants appear as a legal entity in the lease and a trade name in the rent roll. Nothing joins until those are the same thing.
A real assets ontology
Parcel, asset, entity, lease, tenant, option, covenant, loan, and the dates that govern each. A general purpose model does not know that a co-tenancy clause changes what an anchor lease is worth.
Provenance on every field
Each number carries the page it came from, whether that is a lease clause, a T-12 line or a GL code. A committee that cannot trace a figure will not sign off on it.
Governance and permissions
The layer inherits your access rules. What an agent can read is what the person it works for can read, and every read is logged.

This is the part most vendors skip, because a layer does not demo well. It is also the reason one piece of infrastructure carries origination, underwriting and reporting at once, instead of three tools each rebuilding the same context badly and disagreeing with each other.

It compounds. The second workflow stands up faster than the first and the fifth faster still, because the entities, the ontology and the connectors already exist. Most of what a new workflow needs is already in the layer.

More on the same layer

What else runs on the same layer

Once the layer exists these are weeks of work rather than months, because they read the same resolved entities.

Lease abstraction at scale
Options, escalations, co-tenancy and recovery terms pulled from every lease, not only the ones someone had time for.
Comp and assumption testing
Every pro forma assumption tested against signed comps and against your own history on similar assets.
Precedent from your own book
What your closed deals actually support, available at the moment you are underwriting rather than afterward.
Covenant and maturity watch
Loan covenants and maturities tracked against performance, showing the trajectory rather than the breach.
Diligence completeness
What the data room is missing, flagged before the committee date rather than during it.
Post-close variance
Where the asset diverged from the underwriting, traced to the line item and the assumption behind it.
The systems it reads

Built for the stack a diligence team already runs

These are the sources referenced in the workflow above. Document formats vary by data room and are handled as they arrive.

Data room
Two hundred files in mixed formats
T-12 scan
Trailing twelve, often a PDF image
Rent roll
In-place rent, term and expiry per unit
Lease documents
The clauses that move NOI
CompStak
What comparable leases signed at
CoStar
Trades and submarket movement
ARGUS
The model the assumptions feed
Your closed deals
Precedent from your own book
IC criteria
The gates the committee applies
County records
Taxes, liens and assessment history
Box and SharePoint
Where diligence files live
Excel models
The analyst work product today
Common questions

Questions investment committees ask first

Does this replace ARGUS?

No, and it is not trying to. ARGUS models the assumptions you give it and does that well. The problem sits upstream, in whether those assumptions match the record. This tests each input against comps, trailing statements and public records before it reaches your model.

How reliable is extraction from a scanned T-12?

Confidence is scored per line item and anything low is surfaced for human confirmation rather than used silently. Every figure links back to the page it came from, so an analyst verifies in seconds instead of re-keying.

Does it make investment decisions?

No. It produces a tested underwriting and a drafted memo with sources attached. The committee decides. Every variance traces to a comp, a statement line or a filing, so the reasoning can be argued with.

What if our underwriting standards are not written down?

Then that is the first piece of work, and it is worth doing regardless. In practice most of the standard already exists in how the committee actually behaves, and the exercise is to make that explicit rather than invent it.

How is this different from an offshore analyst team?

An offshore team gives you more hours at the same consistency risk, because two people still read two leases two ways. The difference here is that the same standard applies to every file, and every figure keeps a link to its source.

Can we test it against a deal we already did?

That is the usual starting point and the one we recommend. Run it against a deal you underwrote by hand and compare. It is the fastest way to see where it agrees with you and where it does not.

What about the leases on assets we already own?

Same layer, different workflow. Every lease is read for expiry, escalation, option and recovery terms, so exposure is dated rather than discovered at renewal.

AI underwriting for commercial real estate: common questions

What does AI underwriting test?

Each assumption in the pro forma against a source document. Market rent goes against signed lease comps, operating expenses and economic vacancy against the trailing statements in the package, real estate taxes against county assessment, and the exit cap against recent trades in the same submarket. Every variance cites the page it came from.

Where does the data come from?

From the data room and the subscriptions you already pay for. The T-12, rent roll and leases from Box or SharePoint, signed comps from CompStak, trades from CoStar, taxes and liens from county records, and precedent from your own closed deals.

How is this different from ARGUS?

ARGUS models the assumptions you give it and does that well. The problem sits upstream, in whether those assumptions match the record. This tests each input before it reaches your model, so ARGUS is running on numbers the evidence supports rather than numbers the seller chose.

Unified operating layer to harness artificial intelligence. Connect fragmented data, create agentic workflows, enable faster decisions across your company.

© 2026 OutcomeCatalyst. All rights reserved.

Unified operating layer to harness artificial intelligence. Connect fragmented data, create agentic workflows, enable faster decisions across your company.

© 2026 OutcomeCatalyst. All rights reserved.

Unified operating layer to harness artificial intelligence. Connect fragmented data, create agentic workflows, enable faster decisions across your company.

© 2026 OutcomeCatalyst. All rights reserved.