The Line That Called Every Multifamily Operator Out
👉🏼 “I’m the integration layer. I don’t want to be the integration layer anymore.”
Cool sentence to say out loud on a podcast when half your industry’s regionals are currently the integration layer and don’t even get severance for it.
If you caught the episode, this line probably hit a little too close to your Tuesday morning. If you didn’t catch it, ask your best regional what their actual job is. Not the title, the real one. The one where they’re the human API between your CRM, your PMS, and whatever your property manager just texted them at 7 am.
The Job Title That Is Not On The Org Chart
Let’s check the operator’s job, in full, before a single leasing decision even happens:
Pull the numbers out of the CRM
Cross-check them against what the property manager is actually seeing, because the CRM and reality frequently disagree
Call the leasing agent to ask what the report conveniently left out
Then, and only then, make an actual decision
Somewhere along the way, we started calling this “operations.” It was never operations. It’s data entry with a fancier job title and worse hours.
IF your most experienced person is spending their mornings reconciling three dashboards before they can make one call,
THEN here’s the uncomfortable math: you are paying senior salary for junior labor.
You hired judgment and you’re using it as a search engine.
Every hour spent being the integration layer is an hour not spent noticing anything. And noticing is the entire job once the data patchwork is gone.
This week’s guest has a story that shows exactly what that looks like when a person actually gets the room to do it, years before he ever put a name to the problem.
The Win-Win Story You Missed By Skipping The Episode
If you skipped this week’s The Intelligence Fabric episode, you missed a genuinely good story, the kind you don’t usually get in a leasing report, and it’s the exact opposite of the dashboard-chasing we just described.
Back in 2018, one operator decided to spend money on something no occupancy report would ever ask for: getting residents to actually know each other’s names.
Mixers.
Local business partnerships.
Events on the amenity floor.
And so much more.
On paper, this looks like someone lost the marketing budget in a poker game. It was, in fact, a very deliberate bet. A year later, they surveyed thousands of residents. One question sat at the center of the whole thing.
👉🏼 How Many People Do You Know In Your Building By First Name?
That’s the actual question they asked, word for word, and then they tracked every single respondent through their renewal decision.
The correlation was almost embarrassingly clean. Residents who knew their neighbors renewed more. Some of them renewed at real rent increases and said, out loud, that the increase felt easier to swallow because of the community they’d built.
Nobody was staring at a dashboard when this decision got made. There was no dashboard flagging “invest in first names” or any report saying “residents who know each other stay longer.” There was just a person, standing in a building, noticing something a spreadsheet was never built to notice, and choosing to act on it a full year before any proof existed.
That’s what the job looks like when it isn’t assembly. That’s judgment, and it only had room to happen because nobody was busy being the integration layer that week.
Keep that story in your pocket for a second, because it’s about to explain why you can’t automate this next part away.
Where The Human Actually Earns Their Seat
Keeping a person in the loop doesn’t mean stationing a human next to every routine renewal. That’s a waste of a good operator, and it defeats the entire point of automating the routine stuff. The human’s job is narrower and more specific than that: they show up for the one renewal that doesn’t fit the pattern, the one resident whose situation changes the whole math.
And this is how the situation looks like when that person is missing, and it’s not hypothetical.
A prospect went through a fully automated leasing experience. Self-guided tour, no leasing agent trailing them around the building, streamlined app, everything smooth right up until the application.
Then they got declined. No explanation. No number to call. Because, in the guest’s words, the staff had probably been eliminated by that landlord and replaced with the systems running the whole leasing funnel.
Turns out the applicant had simply mistyped their income on the form. A five-minute fix. Except there was nobody on the other end to catch it, explain it, or walk them through it. As the guest put it, all that prospect needed was a human in the loop to deal with the exception, and there wasn’t one to be found.
That’s the exact moment automation stops being impressive. Consistency and speed are great right up until you hit a wall, and then the only thing you actually want is somebody to talk to.
Watch the full episode for how that story actually resolves, because the ending is worse than you’re picturing right now.
Why Accountability Without Authority Doesn’t Work?
That story is also the cleanest possible explanation of why accountability without authority doesn’t work. Somebody at that company was presumably accountable for that decline. But if nobody was reachable, nobody had the authority to actually fix it in the moment, which means the accountability was decorative.
Real accountability means a person double-checks the thing before it costs you a resident, and real authority means that same person is actually allowed to reverse the call when they’re wrong, on the spot, without a meeting.
Even a decision your system gets right ninety-nine times out of a hundred still needs a human free to catch the hundredth, the way this one landlord clearly wasn’t set up to. New York’s regulations change almost weekly, which is a fair reminder across every market that “consistent” was never supposed to mean “nobody’s home.”
Standardization still has a job here, and it’s a smaller job than people assume. It exists to kill the pointless variance between properties, the different ways two leasing offices handle the identical situation for no good reason. It was never meant to replace the person who catches the fat-fingered income field before it turns into a lost resident and a bad story.
The One Line Worth Screenshotting
Everything above collapses into one sentence from the episode that deserves to live on a sticky note.
The bottleneck in multifamily was never the data. It’s judgment, and it’s getting to better decisions faster with the judgment operators already have.
Every operator on earth has more portfolio data right now than at any point in this industry’s history, and somehow the person with the best instincts is still stuck stitching it together by hand before they can act on it.
What That Actually Looks Like Once You Build It
Here’s the part worth sitting with, because our guest didn’t stop at naming the problem. He described the fix, without ever calling it a product, because it wasn’t one to him. It was just how he’d design his operation if he could start over.
Start with the decisions, not the departments.
Figure out who actually has the authority to make each one, and say so out loud instead of leaving it fuzzy.
Build one single trusted source for the data instead of three dashboards and a spreadsheet nobody trusts.
Let the routine, repeatable stuff run on a clear playbook so nobody’s reinventing the wheel every Tuesday.
And send the high-impact, unusual situations to a human, fast, with every piece of context already attached, so the only decision left is yes or no.
Then measure what happened, every time, so the whole thing gets smarter instead of just faster.
That sequence has a name in this industry, and it’s worth knowing even outside this newsletter. A reconciled data layer that sits on top of the stack you already run, Yardi, RealPage, your CRMs, your ILSs, so every number is finally trusted enough to act on, is called an Intelligence Fabric.
What runs on top of that fabric, taking a decision you make over and over, bringing the numbers together, recommending the call, waiting for your yes, then carrying it out and remembering what happened for next time, is called a Decision Machine. One fixes the numbers. The other uses them to make the call. Neither works without the other.
Nobody’s actually asking for another dashboard. What your portfolio needs is a decision that shows up already assembled, reasoning attached, so the only job left is the one no system can do: weigh the exception, own the call, move on with your morning.
That’s the shift. A system that hands you a decision, not one that hands you homework, so judgment finally gets to spend its time being judgment instead of being a search function.
What’s the job you’ve been secretly doing underneath your actual title?
Reply and tell us. We read every single one.
Two systems get built here: one that reconciles the numbers, one that acts on them and remembers outcomes. The strongest decision in this piece happened before either existed; someone noticed something with no data to back it up and made the call anyway. What system holds the reasoning for that kind of decision once the person who made it is gone?