How to catch property management problems early: the Optimus story

Challenge

Optimus is a property management company whose operation had grown past what anyone could keep an eye on — and nothing was watching in their place. Utility spikes arrived as bills, overdue rent aged toward collections, and vacant units sat past their turn windows.

Solution

Five workflows, from unwatched to automatically checked, with zero headcount added

Optimus had grown past what anyone could keep an eye on — and it showed up in five places at once. Every problem was already expensive by the time someone noticed it.

The team wasn't careless. The checking simply lived in people's heads: whether an exception got caught depended on who happened to look, and when. A problem's cost is mostly a function of how long it goes unnoticed — and unnoticed was the default state.

The properties couldn't pause while a fix was built. The watching had to go on rails around the live operation — every exception defined, every threshold agreed, every alert owned — without hiring anyone to do it.

Utility spikes showed up as bills. A running toilet or failed thermostat ran for a full billing cycle before anyone saw the number.

Overdue rent aged quietly. Balances slid toward collections because chasing depended on someone remembering to look.

Maintenance tickets breached their windows silently. The first signal of an at-risk SLA was the breach itself.

Lease expirations arrived as surprises. Renewals were scrambled at the deadline instead of worked as a pipeline.

Vacant units sat past their turn windows. The vacancy loss compounded daily, and nobody could say exactly why.

The work behind the results

This was operations consulting, not a software installation. Trampetti first sat with the Optimus team to define what counts as an exception in each workflow, at what threshold it escalates, and who owns the response — then built those rules into automated checks running on defined schedules. The property management workflow automation is the implementation detail; the operating discipline is the deliverable.

Utility exceptions caught before the bill Consumption is tracked per property, and unusual spikes are flagged the week they appear — reviewed before the next billing cycle, not after the bill lands.

Delinquency that escalates itself Every balance is checked against defined aging thresholds. Overdue accounts escalate automatically to the right team member at each threshold — no one has to remember to chase, and no balance quietly ages into a write-off.

Maintenance deadlines defended, not documented Open work orders are monitored against response and resolution SLAs. The responsible team is alerted while a ticket can still be saved — not in a post-mortem after the breach.

Lease renewals worked as a pipeline Upcoming expirations surface on a defined lead-time schedule, so renewal conversations start early instead of being scrambled at the deadline.

Unit turns flagged while there's still time Vacant-unit cycle times are tracked against a target window; any unit running long is flagged before the vacancy loss compounds.

All five checks run on defined schedules and route to a named owner. Nobody was hired to run any of it — the team's hours go to responding, not looking.

5: Workflows taken from unwatched to automatically checked
0: Headcount added to operate the checks
One: Accountable owner for every alert
Auto: Exceptions surface on schedule, not by accident

How to catch problems while they're still cheap to fix

Growth in property management doesn't fail loudly — it leaks: a billing cycle here, an aged balance there, a unit that sat two extra weeks. Property management automation done right is not a platform purchase; it's the operating discipline of deciding what deserves attention and wiring the noticing so it can't be forgotten. Three lessons from how Optimus did it:

Automate the noticing before the doing. The expensive gap wasn't task execution — it was discovery time. A problem's cost is mostly a function of how long it goes unnoticed; buy back that interval first.

A threshold nobody agreed to is an alert everybody ignores. Set thresholds with the team that has to answer them, and give every alert exactly one owner. An alert that goes to "the team" goes to no one.

You don't need new software to stop finding out late. Every check here ran on systems Optimus already owned. The missing piece was never a tool — it was the definitions, thresholds, and owners the tools had nothing to enforce.

Results