Meet Elena. She's the managing partner of a value-add multifamily sponsor in Denver: six assets, 38 LPs, $50M in committed capital, and a team of four. Reporting is nobody's job, which means it is everybody's job for three weeks out of every thirteen. You are not looking for AI to write your LP letter. You are looking to stop rebuilding the plumbing every quarter so the three weeks go back to asset management.

Over two hours you build Elena's reporting workflow and run it against a closed quarter. Accounting exports become a reconciled dataset. Fund structure and waterfall mechanics get encoded once. Variance becomes written commentary, asset by asset, including the deal that missed. The letter and capital account statements come out formatted and on-brand. Then the LP questions arrive and get answered against the same dataset in minutes.

The part you spend the most time on is the part most AI reporting demos skip entirely: making sure the numbers are right. A reporting workflow that produces a confident wrong figure is worse than no workflow at all, and the difference between a demo and something you can really run is a verification layer you trust enough to put your name on.

What you'll build

• A reconciled quarterly dataset built live from a trial balance, six inconsistent rent rolls, and a bank statement

• A fund-literate instruction set encoding waterfall tiers, an 8% pref compounding annually, and a JV ownership split

• A verification pass that catches a wrong figure before it reaches an LP

• A finished LP letter, capital account statements, and fund performance summary in your firm's voice

You'll learn how to

Turn accounting exports into a reporting dataset

Pull trial balances, operating statements, rent rolls, and bank reconciliations into one reconciled quarterly dataset, without changing how your books are kept or who keeps them.

Teach the workflow of your fund once

Encode entity structure, LP roster and commitments, and waterfall mechanics so capital account math comes out right every quarter instead of being re-derived by hand.

Keep the numbers honest

Build a review step that catches a wrong figure before an LP does, so the workflow earns the trust it needs to run unsupervised.

Draft commentary from variance

Move from budget-to-actual tables to written explanation, with the workflow flagging what moved, proposing why, and surfacing the two or three questions that genuinely need an asset manager's answer.

Write in your firm's voice

Turn an existing LP letter into a format specification, section order, metric hierarchy, disclosure conventions, and tone, so reports come back sounding like your firm rather than like a language model.

Absorb the long tail

Answer one-off LP questions and document requests against the same dataset in minutes, which is where more IR time goes than anyone accounts for.

Questions about the workshop?
View FAQs on format, access, recordings and more: FAQs

The Quarter That Just Closed

What actually lands on a reporting desk: a trial balance from the accountant, six rent rolls in three different formats, a bank statement, a mid-quarter refinance nobody documented cleanly, and one asset behind on lease-up. You start from the mess rather than a tidy sample file.

Building the Quarterly Dataset (Live Build)

Getting the workflow to normalize inconsistent exports into a single reconciled dataset: consolidated results, asset-level NOI, occupancy and leasing activity, debt service coverage, and a flagged list of items that do not tie. You see the ties that break and how they get surfaced instead of quietly averaged away.

Encoding the Fund (Live Build)

Writing the instructions that make the workflow fund-literate: waterfall tiers, an 8% pref compounding annually rather than simple, the JV where the fund owns 62% of an asset, the management fee basis, the reporting calendar. Done once, reused every quarter.

Keeping the Math Verifiable

Where the workflow is allowed to calculate and where it must cite a source cell, how to build the verification pass, and what a good review step actually looks like when the person reviewing has forty minutes rather than a day. You run the pass live and catch what it got wrong, because it will get something wrong.

Writing the Commentary (Live Build)

Building the skill that turns variance into explanation for each asset: what moved, why, what management is doing about it, and what to expect next quarter. Including the underperforming deal, where you work on getting honest language rather than the softened non-answer AI defaults to.

Assembling the Package (Live Build)

Producing the finished quarterly deliverables: the GP letter in the firm's voice, the fund-level performance summary with charts, per-LP capital account statements reflecting the mid-quarter refinance distribution, and the asset appendix. Plus staging distribution and updating the data room.

The Long Tail

Three LP emails arrive. One asks how their capital account changed after the refi and how gross-to-net compares to the original projection. One wants K-1 timing. One wants a rent roll. All three answered against the dataset already built, before the fourth email arrives.

Running It Next Quarter

Turning a one-time build into a repeatable cycle: what to hand an analyst, what to keep as a partner-level judgment call, how the workflow adapts when the fund adds an asset or a side letter changes a reporting obligation, and where the real time savings land once the setup cost is behind you.