All case studies
Case StudyUpdated Aug 2026

Montrose Management: modernizing the systems behind a property portfolio.

Montrose's partners were copying every account out of a custom accounting system by hand. The first workflow in our ongoing modernization cut that quarterly task for one property to about 20 minutes plus review, while keeping the system the business relies on in place.

Montrose Management is a property-management company. Fewer than ten people manage roughly 20 apartment buildings. That lean structure keeps the partners close to every property, but it also means repetitive accounting work lands on the same people responsible for running and growing the business.

At the center of the operation is a custom accounting system built specifically for Montrose. It holds the business's history and supports the work it was designed to do. Its local data format, however, makes moving information into modern reports unusually difficult. Replacing it outright would introduce cost, migration risk, and years of institutional complexity all at once.

The system worked. Getting data out did not.

The quarterly trial balance made that constraint visible. Montrose could not produce a usable export for its reporting workbook. A partner had to find each account in the legacy system, copy the balance, determine whether it belonged in the debit or credit column, and key it into the correct place by hand.

The work was tedious and fragile. An account might be positive one month and negative the next. An unused account might disappear from the source entirely. A single mistyped number could survive until review. Montrose considers roughly 40 hours per property a fair estimate for producing the full set of financials that follows from the trial balance. About 20 of those hours go toward producing the P&L, cash flow statement, and balance sheet. Entering the trial balance itself generally took about 2 hours for each property, and it had to be done multiple times as journal entries changed the balances.

Quarterly trial balance

One controlled path from source to review.

Extract

Create a reliable source

01

Legacy system

02

PDF export

Generate the property trial balance and create a portable source file.

Prepare

Build the workbook automatically

03

Structured Excel

04

Map + validate

Normalize accounts, route each balance by sign, and flag exceptions for review.

Review

Keep judgment with the partner

05

Review-ready TB workbook

Check the flagged exceptions and approve the completed trial balance.

Positive balances land in debit. Negative balances land in credit. Missing accounts stay blank.

Before

~2 hours

Manual entry, often repeated

Now

20 minutes

Preparation, then partner review

Build the bridge before rebuilding the house.

We started by giving the legacy system a reliable export path. Then we built a controlled layer of formulas and a custom script that turns the resulting data into the trial-balance structure Montrose already uses. The quarterly workbook can now pull from that source instead of asking a partner to retype it.

Let the account balance decide where it belongs.

The workflow maps accounts by identity, then reads each balance's sign. Positive balances land in the correct debit field. Negative balances land in the corresponding credit field. If an account was not used during the period and does not appear in the source, the workbook leaves it blank rather than throwing an error or carrying forward an old number.

Use AI as a check, not the source of truth.

Formulas and deterministic rules control the accounting logic. The custom script adds validation, while AI checks help identify suspicious mappings and values for review. Montrose still approves the result. The difference is that the partner reviews a prepared trial balance instead of constructing one cell by cell.

โ€œWow. It's actually more accurate than I was. I'd keyed in some of the wrong numbers.โ€Montrose Management partner

A small workflow with portfolio-sized leverage.

On the first property, each trial-balance preparation that generally took about 2 hours now takes about 20 minutes, followed by review. Because journal entries can change the trial balance, the process may run multiple times during the reporting cycle. The time savings compound with each pass, while the controlled workflow reduces the risk of keying errors.

~40 hrs

Full financial cycle per property

~20 min

Current TB prep per pass, plus review

~100 hrs

Estimated annual time saved

Rollout today

One property proves the workflow. Nineteen show the opportunity.

The automation is live for one property. Montrose manages roughly 20 properties, giving the same quarterly workflow a clear path to portfolio-wide leverage.

1 live~20 properties
Montrose estimates that expanding the current trial-balance workflow across the portfolio could save roughly 100 hours annually. The broader 40-hour reporting cycle per property remains a separate opportunity for future automation.

The workflow is live for one property today, with roughly 20 properties presenting a clear path for expansion. Montrose estimates that expanding the current trial-balance workflow across the portfolio could save roughly 100 hours annually. Today's proof automates the repeated trial-balance entry within a larger reporting cycle that still takes about 40 hours per property. Producing the broader P&L, cash flow statement, and balance sheet from the trial balance still takes about 20 hours and remains a future automation opportunity.

The first proof, not the finished platform.

This engagement is still at the beginning. The trial balance was chosen because it was bounded, repetitive, and painful enough to create immediate value. It also proved that the custom system can participate in a modern workflow without exposing Montrose to a wholesale migration on day one.

From here, the same approach can move into more of Montrose's financial reporting: create reliable paths out of the legacy data store, automate deterministic work, use AI where it strengthens validation, and keep owners at the final judgment points. Each report becomes another piece of a modern operating layer built around the business Montrose already has.

The goal is not to make the core system look new. It is to stop its limitations from deciding how Montrose works today.

Is a legacy system trapping good data behind manual work?

We build practical bridges around the software your business still depends on, then automate the reporting and operations that consume the most valuable time.

Montrose Management - Property Management Automation Case Study | Buzzed Technologies