In this episode, Mike Brewer sits down with Joe Porritt of Brodsky, who has spent 20 years in multifamily, moving from brokerage to running lease-ups for Related in Chicago to his current focus on Brodsky’s tech stack. Joe explains why operators spend most of their decision time on assembly, where a human has to stay in the loop, and how he’d build an operating model from scratch if he could start with the decisions instead of the software.
Because every hour spent stitching dashboards together is an hour judgment never gets.
Timestamps:
0:00 — Joe on why judgment, not data, is now the bottleneck
2:07 — Twenty years: brokerage, Related lease-ups, then Brodsky
4:50 — Vetting a vendor: start with the problem, then talk to site teams
9:28 — Brodsky Neighbors and the bet on resident referrals
11:37 — The survey: how many neighbors do you know by first name?
16:54 — Assembly, and the hours spent gathering before deciding
18:36 — “I don’t want to be the integration layer anymore”
20:15 — Where the human stays in the loop: exceptions, context, accountability
32:52 — The automated leasing decline with nobody to call
36:49 — The operating model Joe would build from scratch
Joe has more data than he’s ever had. What he doesn’t have is time, because most of it goes into pulling numbers out of systems that don’t talk to each other. His best call, the 2018 bet on getting residents to know each other’s names, came from noticing something no dashboard was built to show.
This newsletter goes further than the episode has room for. It looks at the regional who has quietly become the human API between the CRM and the PMS, and what that costs a portfolio. Then it lays out Joe’s from-scratch operating model step by step, and where a decision machine fits into it.
Read it here ⬇️
I Quit Being The Integration Layer Before It Quietly Became My Whole Job
The Line That Called Every Multifamily Operator Out

