Operations improvement for property management companies
Property management runs on volume: requests, work orders, renewals, statements. When the workflows behind that volume are manual or disconnected, the symptoms are familiar: slow responses to tenants, maintenance coordination by phone tag, owner reports assembled by hand at month end, and a team that grows every time the portfolio does.
Talk through an operating problemCommon operating problems in property management
Tenant requests scattered across channels.
Phone, email, portal, text, with no single queue and no clear owner.
Maintenance dispatch by memory.
Vendor selection, scheduling, and follow-up living in someone's head instead of a workflow.
Owner reporting as a monthly scramble.
Data that exists in your systems, assembled by hand every month.
Renewals and collections handled reactively.
Dates known months in advance, worked at the last minute.
Staffing grows at the same rate as the portfolio.
If every increase in units requires more coordination staff, the current process may not be scaling.
An engagement here follows one workflow end to end, most often the path from tenant request to completed work order to owner statement. At each handoff the questions are the same. Who owns this step, what does it wait on, where is the same information entered twice, and what does the delay cost. The fixes are measured in the operation's own numbers: response and completion times, work orders closed without callback, statements out on time.
Fix the workflow before adding tools
A focused Operations Diagnostic on one workflow, typically tenant-request-to-resolution or the monthly owner-reporting cycle: one to two weeks, fixed fee, findings quantified, a 90-day plan. Fix Sprints implement the priorities with a baseline and the agreed measurement. Where your existing property management software is underused or disconnected, the Diagnostic identifies exactly where integration or automation would pay for itself. What a Diagnostic covers · how engagements run.
Operating background
From Brad Berlin's operating career. Not BMG client outcomes.
- Support resolution time cut from about 26 minutes to about 90 seconds at MyCarrier, by redesigning intake and routing workflows.
- At project44, Brad launched 26 new LTL API connections in under nine months across an ecosystem of more than 350 integrations.
What the work looks like on the maintenance and vendor path
An illustration of BMG's method. Not a client engagement.
The exception is the workflow
Most tenant requests are ordinary: reported, assigned, scheduled, completed, closed, billed. The ones that consume the day are the exceptions. The vendor who never confirms. The unit nobody can access. The repair that turns out to require an owner decision. The invoice that arrives at a different number than the estimate. A workflow designed only for the ordinary case pushes every exception onto a person, and that person quietly becomes the process.
What gets followed
One work order end to end, and then a deliberately chosen handful of exceptions of each type above. The questions are the same at every step: who owns it right now, what is it waiting on, how would anyone know it is stuck, and what does the wait cost in vendor time, tenant patience, or owner trust.
Where the design usually changes
Four places. A single intake queue, so requests stop arriving through four channels with no owner. Named states for a work order that include the exception states, so "waiting on vendor" and "waiting on owner approval" are visible rather than inferred. A written approval threshold, so a coordinator knows the dollar figure above which an owner decision is required and stops asking case by case. And an aging rule, so anything past its expected duration surfaces on its own instead of surfacing when the tenant calls a second time.
Vendor coordination is its own workflow
It is not a footnote to maintenance. It has a scheduling handoff, a confirmation, a completion record, and an invoice reconciliation, and each one is a place where work can stall silently. Where a scope of work is stable and repeatable, the confirmation and the follow-up chase are strong candidates for automation, with a person still approving anything that touches money or an owner relationship.
How it is measured
Time from request to assignment, assignment to completion, and completion to owner statement. Work orders closed without a callback. The share of work orders that entered an exception state, and how long they stayed there. Statements out on time. Baseline first, then one change at a time.