According to McKinsey Global Institute, agentic AI will unlock $430 to $550 billion in value across real estate. Multifamily is not capturing it.

80% of organizations have deployed AI across at least one business function. Only 20% report a material financial impact. The industry is stuck in what McKinsey calls pilot purgatory: deploying, seeing marginal gains, never moving to transformation.

I spent several months studying why this happens. Looking at the patterns that keep showing up across owners, operators, and proptech leaders. Eight specific patterns that are stalling progress before it ever gets started. They're not technical barriers. They're not about capability. They're about how organizations think about and deploy AI.

The 8 Patterns

Pattern 1: Waiting for Perfect Data

The advice being passed around tells multifamily to fix their data house first. Get your core systems talking to each other. Resolve the conflicts between the two systems that are telling two different stories. Then invite AI in.

Multifamily has one of the most fragmented data landscapes of any industry. A leasing platform doesn't talk to the accounting system. The resident app doesn't sync with the maintenance system. Historical data lives in three different places, each version slightly different from the others. If all of that has to be resolved before you touch AI, many organizations will be waiting for years.

The real question is not "do we have perfect data?" The real question is: which workflow are you reimagining and what data does that specific workflow actually require? Start with a maintenance request workflow. Start with lease renewal coordination. Start with something bounded and specific. You will find that the data you need for that specific workflow is often more consistent than you think. You do not need to boil the ocean first.

Pattern 2: Waiting for Perfect Stakeholder Alignment

Most organizations believe they need everyone on board before they begin. In practice, that belief is one of the most expensive places to lose time.

Organizations spend months in alignment meetings. Regional leaders. Department heads. Cross-functional task forces. IT. Finance. Operations. Because AI is still largely theoretical for most people in those conversations, the alignment never fully arrives. Someone has a concern that nobody can fully address. Something feels risky. The group decides to loop in one more stakeholder before proceeding. Nothing starts.

There is one important exception: the person at the top has to be on board. Not necessarily an AI enthusiast, but someone who is open to seeing how AI can shape their vision for the organization. Without that, nothing else moves.

Beyond that single person, alignment does not come from meetings and planning sessions. It comes from results. Start with the people closest to the workflow you are reimagining. Show them the work. Let them see what changes. Let the results do the convincing. When the leasing team sees that an agent can handle 80% of lease renewal follow-ups, the regional director believes it. When the maintenance coordinator sees work orders being routed more intelligently, buy-in follows naturally. Real proof moves people faster than consensus ever will.

Pattern 3: Waiting for a Complete Governance Policy

Companies are being told they need a full AI governance policy in place before they can start. Map out risks. Establish approval workflows. Define accountability. Document everything.

Building a governance policy before anyone in the organization has actually worked with the technology is like writing the rules for a game nobody has played. The result is theoretical, built by committee, and approved by stakeholders who are trying to make decisions about something they have never experienced. It takes months. It gets approved. It immediately becomes outdated because reality looks nothing like what the policy anticipated. So the policy gets rewritten. All of that time gets lost twice.

The governance questions that actually matter are specific to how each agent operates and what decisions it makes. You cannot write meaningful governance for something you do not yet understand. Build your AI in a controlled environment first. Let your governance policy wrap around what you have actually built and what your organization actually values. The policy emerges from the work. It does not precede it.

Pattern 4: Assigning AI to the Technology Team

When a new technology lands on the executive agenda, it goes to the team that always handles technology deployments: IT, systems integration, and infrastructure teams.

With AI, that default assumption is one of the most consequential mistakes a company can make. AI is not a technology implementation. It is a business and organizational change initiative that requires reimagining how work gets done. It requires people with serious strategic chops at the helm. It requires someone who understands the business deeply enough to know which workflows are worth reimagining.

When technology teams lead, they build what is technically feasible. What they build may have nothing to do with what the business actually needs. The agent functions perfectly. The workflow never changes. The organization wonders why nothing feels different.

Pattern 5: Thinking Too Small About AI's Role

Most organizations are still asking the wrong question: where can we add AI to what we already do?

That question will always yield a small answer because it assumes the existing workflow is worth keeping. You end up with faster versions of workflows that might have been broken to begin with. Multifamily is currently chasing a fraction of the $430 to $550 billion in available value by layering AI onto workflows that were never designed for it in the first place. The gap between what the industry is deploying and what is actually possible is enormous.

AI requires a completely different frame. The question is: what would this workflow look like if it were redesigned from the ground up with AI at the center? That is not a minor shift. It changes who does what, when they do it, and why. It changes where decisions get made. It changes the role of the people who currently do the work. When you start with that question, the answers you arrive at are almost always larger and more strategic than what you would have found by layering AI onto an existing workflow.

Pattern 6: Keeping AI at the Leadership Level

Leadership goes heads down. They research AI. They decide it matters. They build a plan. And one day, they walk into a room and announce that AI is coming.

The team hears one thing: Are we being replaced? That fear is predictable and entirely avoidable. The moment people feel surprised or excluded from something that affects their work, you lose momentum. The moment they feel threatened, you lose trust. And once trust is gone, adoption becomes a struggle instead of an opportunity.

Transparency from the beginning, at every level of the organization, is the only way to build something worth trusting. People closest to the work need to understand what is happening and why. They need to know that their expertise is still valued. That conversation has to start early. It cannot start on the day the agent goes live.

Pattern 7: Leaving Out the People Who Know the Work Best

The people closest to the work know things no process map can capture. They know where the system breaks down and what workarounds have been in place for years. They know what the workflow looks like in real life versus on paper. They know the edge cases that happen once a quarter but cost the organization real money.

Leaving them out of the design process results in an agent built on assumptions rather than reality. When edge cases become failures and workarounds are never documented, the agent breaks in ways nobody anticipated. Worse, these same people are the organization's most important advocates for adoption. They are the ones who will use the agent every day. They are the ones who will decide if it is worth trusting. Cutting them out does not just produce a weaker agent. It produces one that the people who matter most will never fully get behind.

Pattern 8: Failing to Re-envision the Human Role

Most AI deployments have a detailed plan for the agent. Almost none have an equally detailed plan for the human working alongside it.

When organizations design an AI workflow, the focus is almost always on what the agent will do. The human role gets assumed. But assumption is not a plan. What actually happens is that nobody has defined what the human's new role actually looks like. Nobody established what happens when the agent hits a limit. Nobody built the feedback loops that tell the agent when it is making a mistake.

The result is predictable. Questions the agent cannot answer sit, waiting for a human response, with no defined process for who handles them or how quickly. Handoffs occur without anyone knowing. Gaps open up between what the agent does and what the human picks up. The gains expected are absorbed by everything that was never reimagined.

A human is supposed to oversee a process they no longer fully understand. A human is expected to catch errors from a system they were not involved in building. A human whose job has changed but whose role has never been clarified does not feel empowered. They feel uncertain.

Re-envisioning the human role has to be designed with the same level of intention as the agent itself. What does the human do now? What decisions stay with the human? What happens when the agent fails? How does the human provide feedback? These questions matter as much as anything else in the workflow.

Go Deeper

Each of these patterns manifests differently within every organization. The frictions they create are specific to your structure, your people, and your strategy.

We created an AI Momentum Guide that explores each pattern in detail with expanded analysis, real-world context, and the reasoning behind why these patterns emerge so consistently. It is written for owners, operators, and proptech leaders who are serious about moving past pilot purgatory.