Skip to content

Case study · AI Agents & Automation

Turning weeks of investor reporting into hours

Each quarter, a real estate investment firm rebuilt its investor update decks by hand: chasing partner files, reconciling inconsistent spreadsheets and PDFs, then formatting slides. Stallwart replaced the manual middle with an automated reporting workflow.

The approach
  1. 01Intake
  2. 02Document processing
  3. 03Structured extraction
  4. 04Narrative generation
  5. 05Deck render
  6. 06Human review
Client
a real estate investment firm
Problem
Quarterly investor decks assembled by hand from inconsistent partner files, taking weeks.
Approach
An automated reporting pipeline: intake, document processing, structured extraction, AI narrative, presentation-ready output.
Verified result
Weeks of reporting reduced to hours

The problem

Every quarter the firm produced operational update decks for its investors. The inputs arrived as whatever each partner happened to send: spreadsheets with different layouts, PDFs, exported reports, none of them agreeing on structure. Someone had to open each file, read it, reconcile it against the others, and retype the numbers into a slide template.

The work was slow, repetitive, and easy to get wrong. Most of a reporting cycle went to data consolidation and formatting rather than to the judgment the firm actually wanted its team spending time on: reviewing the numbers and the story they told.

The reality behind the problem

Standardizing the inputs is the obvious move, and the firm had tried it: mandate one spreadsheet layout for every partner, and consolidation becomes mechanical. That fix depended on every partner changing how they report, quarter after quarter, and that dependency is exactly what broke. The files kept arriving in whatever shape each partner preferred.

Adding people to the consolidation step scales the cost rather than removing it. The weeks went to reading inconsistent files and retyping numbers, work that grows with every partner and every quarter. More hands make the same slow, error-prone process faster for one cycle and no cheaper for the next. The fix had to read the messy data itself, not police how it arrived.

What was assumed

Reporting is slow because the data is messy.

What Stallwart asked

What if the system read the messy data, and people reviewed the result?

The desired outcome

The goal was not a prettier deck. It was to take the weeks of consolidation out of the cycle while keeping a person on the judgment that matters.

  • Inconsistent partner files read and mapped into one consistent data model, without mandating a format.
  • Consolidation and formatting automated end to end, so no number is retyped by hand.
  • Quarter-over-quarter comparison reliable, because every input lands in the same structure.
  • Investor-grade narrative generated from the structured numbers, ready for review rather than drafting.
  • A person in control of the final numbers and commentary before anything reaches investors.

The system we designed

Stallwart built an automated investor-reporting workflow. It manages partner uploads and tracks each reporting session, then applies document processing and AI-driven interpretation to spreadsheets, PDFs, and reports that do not share a format. Inconsistent inputs are cleaned and mapped into one consistent data model, so properties aggregate correctly and a quarter can be compared against the last.

From that structured data, the system generates investor-grade narrative: performance summaries and the kind of executive commentary a team would otherwise draft by hand. The output is rendered into a presentation-ready deck against the firm's slide template, leaving people to review insight rather than assemble it.

How it works

  1. 01

    Normalize inconsistent inputs

    The hardest part was not the slides, it was that no two partner files agreed. AI-driven interpretation reads spreadsheets, PDFs, and reports without rigid per-file rules, then maps them into a single data model so aggregation and quarter-over-quarter comparison are reliable.

  2. 02

    Separate extraction from judgment

    Consolidation and formatting are automated end to end. Narrative is generated from the structured numbers, so the team's time moves from retyping data to reviewing what it means.

  3. 03

    Keep a person on the output

    The deck is produced automatically but reviewed before it goes out. Human-in-the-loop review stays on the part that carries judgment and risk, which is the commentary and the final numbers.

The workflow

From partner files to a reviewed deck.

  1. 01

    Intake

    Partner uploads, session-tracked

  2. 02

    Document processing

    Spreadsheets, PDFs, reports read automatically

  3. 03

    Structured extraction

    Cleaned into one consistent data model

  4. 04

    Narrative generation

    Summaries and investor-grade commentary

  5. 05

    Deck render

    Presentation-ready against the firm's template

  6. 06

    Human review

    People check insight, not formatting

Each stage is automated; a person reviews the result instead of assembling it.

Architecture

What sits underneath.

The workflow sits on four layers, each doing one job in the path from a partner upload to a reviewed deck.

01

Intelligence

AI-driven interpretation reads spreadsheets, PDFs, and reports that do not share a layout, and narrative generation drafts summaries and commentary from the structured numbers. This is the layer that turns messy inputs into meaning.

02

Orchestration

The pipeline manages partner uploads, tracks each reporting session, and moves a quarter's inputs through intake, extraction, narrative, and deck render in order. It is what keeps a reporting cycle moving from file to finished draft.

03

Governance

Human-in-the-loop review sits on the output: a person checks the generated numbers and commentary before anything goes to investors. This layer draws the line between what the system drafts and what a person approves.

04

Production

Rendering against the firm's slide template, session tracking, and the consistent data model make the workflow something the firm runs every quarter rather than a one-off script. It is the layer that keeps the output presentation-ready and repeatable.

The hard parts

Where the engineering judgment was.

01

Interpret messy data instead of mandating a format

Forcing every partner onto one template had failed before. Reading inconsistent files with AI removed the dependency on partners changing how they work.

The trade-off

Interpretation needs review on edge cases, which is why a person stays on the result.

02

Automate the consolidation, not the decision

The expensive, error-prone work was reconciliation and formatting. Automating that frees the team for review without handing over judgment.

The trade-off

The system drafts commentary; it does not approve it. A human still signs off.

Reliability & guardrails

How it avoids the wrong call.

The risk in automated reporting is a wrong number reaching investors. The guardrails keep the system from making a decision it should not.

Grounded in the submitted files

Narrative is generated from the structured numbers extracted from partner files, not written freely. Every figure in the draft traces back to an input, so commentary cannot drift from the data it describes.

A person on the judgment

Consolidation and formatting are automated, but the generated numbers and commentary are reviewed before anything goes out. Review stays on the part that carries judgment and risk, not the mechanical work.

Edge cases surfaced, not guessed

Interpreting inconsistent files needs review where a file is ambiguous. The system flags what it could not map cleanly rather than guessing silently, so a person decides the hard cases.

Consistent structure across quarters

Inputs are mapped into one data model, so a quarter aggregates the same way as the last. Comparison stays reliable because the shape of the data does not change with the shape of the files.

Productionization

What turns it from a demo into software.

What turns the workflow from a working demo into software the firm runs every quarter.

Session tracking

Each reporting cycle is tracked as a session, so the state of a quarter's intake and processing is visible rather than held in someone's inbox.

Observability

The pipeline reports which files were read, what was extracted, and where interpretation needed a person, so a stalled or ambiguous input is visible before the deck is due.

Template-bound output

Decks render against the firm's own slide template, so the output is presentation-ready and the format does not have to be re-fixed each quarter.

Repeatable intake

Partner uploads run through the same managed intake every cycle, so a new quarter starts from a known process rather than a fresh scramble for files.

The result

Weeks of worknow takehours

Consolidation and formatting that used to run for weeks each quarter now complete in hours, which is roughly an 80% reduction in the time it takes to produce a deck. The firm's reporting structure stays consistent across quarters because inconsistent spreadsheets, PDFs, and reports are normalized into one data model, cutting the manual transcription errors that used to creep in.

The team's effort moved from assembling decks to reviewing insight, which is the work the firm wanted it doing in the first place.

Ownership & handover

What you receive, and keep.

The reporting workflow is the firm's to run, with nothing held back.

  • Source code for the intake, document processing, extraction, narrative, and deck-render stages.
  • Infrastructure as code for the pipeline and its storage.
  • Runbooks for running a quarter, handling ambiguous files, and reviewing output.
  • Documentation of the data model and how inconsistent inputs map into it.
  • The firm's slide template wired into the render stage, so decks come out in the firm's own format.

What we learned

The insight that generalizes: when a process is slow because its inputs are messy, the fix is rarely to force the inputs into shape. It is to build a system that reads the mess and leaves people the judgment. Automating the consolidation and keeping a person on the numbers moves a team from assembling a report to reviewing it, which is the work that was worth their time all along.

This work connects to

  • AI Agents & Automation
  • AI reporting automation
  • Intelligent document processing
  • Workflow automation
  • Human-in-the-loop systems

Frequently asked

What is AI investor reporting automation?

It is a workflow that takes the raw inputs behind an investor report, such as partner spreadsheets, PDFs, and exported reports, and automates the consolidation, structured data extraction, and narrative generation that teams usually do by hand, producing a presentation-ready deck a person then reviews.

How does the system handle inconsistent spreadsheets and PDFs?

It uses AI-driven interpretation rather than rigid per-file rules. Files that do not share a layout are read, cleaned, and mapped into one consistent data model, so properties aggregate correctly and each quarter can be compared against the last.

Does automation remove human review from reporting?

No. Consolidation and formatting are automated, but a person reviews the generated numbers and commentary before anything goes to investors. The automation handles the repetitive work; judgment stays with the team.

How much faster is automated investor reporting?

For this firm, work that previously took weeks each quarter now completes in hours, about an 80% reduction in deck-creation time. The gain comes from automating data consolidation and formatting, not from cutting the review that carries judgment.

Spending weeks assembling a report before anyone can read it?

Bring the workflow and the messy inputs. We build the pipeline that turns them into a reviewed result.

Last updated: October 13, 2026