Due Diligence on Your Own Firm: The AI Readiness Assessment No One Is Doing

Every CRE PE firm has a rigorous process for evaluating the assets it acquires. Rent rolls, operating statements, lease abstracts, environmental reports, title work, zoning analysis — the diligence checklist exists because the cost of missing something is too high.

Almost no firm applies the same rigor to evaluating its own operations.

That's the paradox I see repeatedly: firms that would never close on a property without understanding every line item of its operating budget haven't mapped how their own team's time gets allocated, where institutional knowledge lives, or which workflows are bottlenecking their ability to grow. They know their assets intimately. They don't know their own firm with the same precision.

This matters right now because the firms that understand their own operational architecture are the ones positioned to build AI infrastructure that actually works. And the firms that don't are the ones paying the verification tax — spending more time correcting AI output than they would have spent doing the work manually.

The five questions

When I sit down with a CEO or CIO for the first time, I walk through five questions. They're simple to ask and surprisingly hard to answer with precision. But the answers reveal, with uncomfortable clarity, where the firm's operational ceiling is — and where AI infrastructure can raise it.

1. Where does senior time go?

Ask your CIO to track one week in detail. Not calendar appointments — actual work. How many hours went to reviewing raw data versus making decisions? How many hours went to assembling information versus analyzing it? How many hours went to formatting deliverables versus creating the content that goes in them?

At most mid-market firms, the answer is uncomfortable: fifty to sixty percent of CIO-level time goes to tasks that don't require CIO-level judgment. Not because the CIO wants to spend time on them, but because nobody else can do them to the required standard, and no system exists to handle them automatically.

The insight: every hour of senior time spent on assembly work is an hour not spent on the deal structuring, LP relationships, and strategic decisions that actually grow the platform. The revenue impact of misallocated senior time is invisible but enormous.

2. Where is institutional knowledge locked?

If your head of acquisitions left tomorrow, how much of the firm's deal evaluation framework walks out the door? If your IR lead left, could someone else produce the next quarterly report to the same standard? If the principal who's been with the firm since Fund I retired, where does fifteen years of market intuition go?

At most firms, the honest answer is: critical knowledge lives in people's heads, in email threads, in spreadsheets on personal drives, and in undocumented assumptions that "everyone just knows." This is a key-person risk that no LP wants to underwrite, and it's an operational fragility that compounds as the firm grows.

The insight: institutional knowledge that isn't captured in systems is institutional knowledge that can't be leveraged. It can't train new hires efficiently. It can't scale across offices. And it can't feed the AI systems that would multiply its value.

3. What's the time from deal identification to IC-ready?

Map the actual elapsed time from the moment a deal opportunity enters the pipeline to the moment it's ready for investment committee discussion. Then decompose that timeline: how much of it is active analysis, and how much is waiting — waiting for comps, waiting for data assembly, waiting for the model to be built, waiting for someone to have bandwidth?

At most firms, the answer is two to four weeks — and sixty percent of that time is waiting, not working. The analyst is working on three other things. The market data needs to be pulled from four different sources. The comparable transactions need to be assembled manually. The model template needs to be populated before the real analysis can begin.

The insight: speed to IC isn't about working faster. It's about eliminating the dead time between steps. In a competitive market, the firm that gets to IC in three days instead of three weeks sees more deals, makes better decisions, and wins more often — not because they're smarter, but because their process doesn't have gaps.

4. What does your quarterly reporting process actually cost?

Not the direct cost — the opportunity cost. How many person-hours go into producing each quarterly report? How many of those hours are data assembly versus narrative writing? How many senior hours get consumed reviewing and correcting drafts? What else would those people be doing if the reporting process took two days instead of two weeks?

At a typical mid-market firm with fifteen to twenty active investments, quarterly reporting consumes eighty to one hundred twenty person-hours per cycle. Four cycles per year means four hundred to five hundred hours annually — roughly a quarter of a full-time employee's entire year, dedicated to assembling and formatting information that already exists in the firm's systems.

The insight: quarterly reporting is the single largest recurring time sink in most firms' operations, and it's almost entirely assembly work. The narrative judgment — explaining performance, contextualizing variance, framing the outlook for LPs — is maybe twenty percent of the total effort. The other eighty percent is data gathering, calculation, formatting, and reconciliation.

5. Could your platform absorb twice the current AUM?

This is the question that matters most for firms thinking about their next fund. If you doubled your assets under management tomorrow — same team, same systems, same processes — what would break first?

At most firms, the answer comes quickly: reporting would break. Then deal screening. Then portfolio monitoring. Then LP service quality. The team would work longer hours for a while, then quality would start to slip, then something would fall through the cracks at exactly the wrong moment.

The insight: your honest answer to this question is your growth ceiling. Everything above that line requires either more people or better infrastructure. The firms that choose infrastructure are the ones that scale. The firms that choose headcount are the ones that hit the emerging manager trap.

What the answers tell you

If you run this assessment honestly, you'll end up with a clear map of three things: where your team's time is being consumed by work that doesn't require their judgment, where your institutional knowledge is vulnerable, and where your processes would break under increased scale.

That map is your AI infrastructure roadmap. Not a technology roadmap — an operational roadmap that happens to be enabled by technology. The starting points are always the workflows where time savings are highest, error risk is lowest, and team buy-in is easiest to build. The deeper integrations come later, once the foundation is proven and the team trusts the system.

The firms that do this assessment before they implement AI build infrastructure that actually works. The firms that skip it and go straight to deploying tools end up with scattered experiments that don't compound — and a verification tax that makes the whole initiative feel like it isn't worth the effort.

The diligence you apply to evaluating a $50 million acquisition is the same diligence you should apply to evaluating your own $2 billion platform. The returns on getting it right are at least as high.

Back to all insights