Built to Run

It started with a small mistake—a property manager sent an email intended for one resident to another. The kind of error that happens in any operation, any industry. What should have been a quick apology and correction became something else entirely when the manager, instead of owning the mistake, got defensive. The response was dismissive—a “well, actually” that implied the resident was also in violation of their lease. It was the wrong move. And in another era, it probably would have resulted in a tense phone call, maybe a complaint to the regional manager, and an eventual resolution.

Instead, the resident turned to ChatGPT.

Over the following weeks, what had been a straightforward interpersonal misstep escalated into a sustained, AI-fueled campaign. The resident—and I want to be clear about this, because it matters—was an intelligent, reasonable person using the tools available to them in a way that was genuinely effective. They used AI to research their rights, draft formal demands, cite local ordinances, and build a detailed case that touched every aspect of their tenancy. They demanded specific disclosures based on their reading of a recent change to local law—a reading that turned out to be a misunderstanding, though an understandable one given how vaguely the new regulation had been written. They set deadlines for responses. They threatened escalation through specific regulatory channels. The emails were well-structured, legally precise, and relentless.

Multiple staff members across different levels of the company got pulled into the situation. Outside legal counsel was engaged. Formal responses were drafted, reviewed, and sent in both directions. Weeks of time and thousands of dollars in resources went to managing a situation that had started with a single misdirected email.

The situation eventually made its way to me. I reached out to the resident and asked if we could meet in person—no agenda beyond answering their questions with full transparency. We sat down together, had an honest conversation, and within an hour the resident told me what I’d suspected: they were never angry about the underlying issues. They were frustrated by how the property manager had responded to their initial concern. The dismissiveness. The defensiveness. The feeling of not being heard. Everything that followed—the legal research, the formal demands, the escalation—was a reasonable person using powerful tools to force a response that should have come from the beginning.

Things resolved amicably. But I kept thinking about what that situation revealed—not just about AI, but about where property management is right now.

That resident wasn’t unusual. They weren’t litigious by nature or looking for a fight. They were a normal person who discovered that a free AI tool could do in minutes what used to require an attorney and hundreds of dollars. And that discovery is not going back in the box. Every resident in every unit in your portfolio now has access to the same capability. The question isn’t whether they’ll use it. Some of them already are.

That’s one dimension of the shift. The work hasn’t just gotten harder—the environment around the work has fundamentally changed.

The regulatory landscape has grown more complex. Fair housing enforcement has expanded. State and local landlord-tenant protections have tightened. Habitability standards have become more specific and more aggressively enforced. New regulations are routinely enacted without clear implementation guidance—lawmakers pass the law and leave property management companies to figure out how to comply, often on short timelines and with ambiguous requirements. The situation I described earlier involved a resident citing a recent change to local law that they had misunderstood—but it’s hard to blame them when the industry itself was still sorting out what the law required. And the consequences of getting it wrong have escalated dramatically. Courts and juries have shown an increasing willingness to impose severe penalties for what amount to procedural errors—not bad faith, not negligence, just imperfect execution of increasingly complex requirements. The margin for operational error—an inconsistent screening process, an undocumented accommodation decision, a lease violation notice with the wrong language—has narrowed to the point where a single misstep can cost more than a year’s worth of operational improvements.

The technology has kept changing, too. Every property management software provider is bolting on AI features because it’s the trend of the moment. Your team is using ChatGPT on their phones whether you’ve sanctioned it or not. The trade publications are running breathless articles about how artificial intelligence will transform multifamily operations. And in the middle of all of it, you’re trying to run a property management company—leasing units, handling maintenance, managing people, keeping residents satisfied, staying compliant, and somehow finding time to think about the future of the business while the present is consuming every available hour.

I’ve heard PMC owners joke about having “our AI talk to their AI” when situations like these arise. It gets a laugh because there’s truth underneath it—the instinct to match tool with tool. But that situation I described didn’t resolve because of a better email or a sharper legal response. It resolved because someone sat down with the resident and had an honest, human conversation. The old playbook—pick up the phone, show up in person, listen—isn’t gone. But it’s no longer sufficient on its own. You still need the human skills. You also need the systems that prevent a single misdirected email from becoming a weeks-long legal escalation in the first place. And the property manager at the center of it all is the same person who also needs to lease three units this month, coordinate a turnover, manage a maintenance backlog, and deal with two new hires who still don’t know where to find the after-hours emergency procedure.

The pressure is cumulative. No single change broke the old way of doing things. But the accumulation—more complex regulations, more informed residents, more demanding technology, more turnover, more properties, more everything—has made it impossible to run a modern property management operation on tribal knowledge, improvisation, and the heroic effort of a few key people. I’ve talked to operators who are good at this work, who care deeply about doing it well, and who are exhausted not because the work is too hard but because the systems supporting them haven’t kept up with the demands being placed on them.

If you’re feeling overwhelmed, you’re not behind. You’re in the same place as nearly every PMC owner, operator, COO, director of operations, regional manager, and senior leader out there.

Why are we always reacting instead of getting ahead of things? Why does every property seem to run differently? Why does everything break when someone quits or takes a vacation? Why can’t we keep good people? Why am I still answering the same questions I answered last month?

If any of those sound familiar, you’re asking the right questions. The problem isn’t that you don’t have the answers. It’s that your operation doesn’t have the systems to make those questions stop recurring. The fundamental challenge hasn’t changed: how do you build an operation that runs consistently, efficiently, and without depending on any one person—including you—to hold it together? What’s changed is the cost of not solving it. The margin for running on momentum has disappeared.

That’s what this book is about. Not theory. Not inspiration. A practical, specific plan for getting your operation off of adrenaline and onto systems.

Who this book is for—and who else it helps

This book is written for the people who run property management operations. Owners who built their companies from the ground up and feel the operation slipping as it grows. COOs and directors of operations who know the systems aren’t where they should be but can’t get ahead of the daily demands long enough to fix them. Regional managers who see the same problems at every property and don’t have the authority or the bandwidth to solve them structurally. Emerging leaders who came into the industry during or after COVID and are trying to build the skills that used to be developed over years of in-person mentorship.

It’s for companies managing 300 units and companies managing 10,000. The problems are the same. The scale is different, but the physics are identical: when knowledge lives in people’s heads instead of systems, when processes vary by property and by person, when tools are half-configured and communication is scattered, the operation bleeds time, money, and good people in ways that never show up on a P&L.

The industry right now has people at every point on the experience spectrum, and they’re all dealing with versions of the same challenge. There are operators who’ve been doing this for fifteen or twenty years—people with deep instincts, strong relationships, and the kind of people skills you can’t teach—who built their careers in an era when you could run a great operation on personal knowledge and direct communication. The work changed around them, and the systems they never needed before are now the difference between an operation that scales and one that’s held together by the owner’s personal attention. There are also operators who entered the industry during or after COVID, who are digitally fluent and comfortable with new tools, but who missed the years of in-person mentorship and on-the-ground experience that used to develop the foundational skills of the profession. Both groups have something the other needs. And both groups will find something in this book that addresses the gap they feel.

If you’re just getting started—building a company from a small portfolio, hiring your first team, figuring out how to systematize before the growth outpaces you—this book gives you the playbook to build right from the beginning. The companies that invest in their operational foundation early grow faster, retain better people, and avoid the painful retrofitting that consumes operators who scaled first and systematized later.

If you’re already running a mature operation and you know the systems aren’t where they should be—maybe you’ve been meaning to document your processes for years, maybe you’ve been through a software rollout that didn’t stick, maybe you’re watching competitors adopt tools and practices that you haven’t gotten to yet—it’s the same playbook. You’re just starting from a different place. And it’s not too late. I’ve worked inside operations that had been running on tribal knowledge and improvisation for a decade. The turnaround, when it happens, is faster than most people expect—because the problems are well-understood, the solutions are proven, and the team is usually more ready for change than leadership realizes.

This book becomes especially critical if you’re navigating a period of change—leadership transitions, market shifts, ownership changes, retirement planning, succession planning, expansion into new markets, mergers, acquisitions, or preparation for a sale. In every one of these scenarios, the value of an operation that runs on documented systems rather than individual knowledge goes from “important” to “essential.” A buyer evaluating your company, a successor stepping into your role, a partner coming in through a merger—they’re all inheriting your operation. If that operation lives in your head and the heads of your key people, it’s fragile, it’s discounted, and it’s a risk. If it lives in systems, it’s transferable, it’s scalable, and it’s worth more in every scenario. The frameworks in this book aren’t just about running better today. They’re about building something that has value independent of the person at the top.

But this book isn’t only for leadership. If you’re a frontline property manager, a leasing agent, or a maintenance coordinator and you picked this up, I want you to feel seen. The problems described in these pages—the searching for answers that should be documented, the inconsistent processes, the onboarding that amounts to “good luck, you’ll do great,” the daily friction of systems that don’t support you—these are your problems. You live with them. You’ve built workarounds for them. You’ve probably stopped mentioning them because nobody seemed to be listening. This book gives you the language to describe what’s broken, the framework to propose what should change, and the evidence that it doesn’t have to be this way. Bring it to your leadership. Recommend it to your owner. It was written with you in mind, even if the action items are directed at the people who can authorize the investment.

And if you’re a property owner—not an operator, but someone who owns the asset and hires a management company—this book is a lens. The five components of a well-run operation described in Chapter 3, the seven assessment areas in Chapter 2, the cost categories in Chapter 1—these are the questions you should be asking of any management company, whether you’re evaluating your current one, interviewing prospective ones, or assessing how you do business yourself. A well-run operation protects your asset. A poorly-run one erodes it in ways that don’t show up on a financial statement until the damage is done.

What this book is—and what it isn’t

This is a practitioner’s book, not a consultant’s book. I still work inside property management operations every day at a mid-size regional property management company in Southern California—roughly 7,000 units across more than 200 multifamily properties. I’m not just in the boardroom. I continue to work in leasing, day-to-day site-level property management, resident interactions, maintenance coordination, and frontline operational tasks—not because I have to, but because it keeps me connected to what the work actually feels like. It’s easy to build frameworks from a distance. It’s harder to build them while you’re also handling a resident complaint, troubleshooting a work order, and processing an application with a co-signer in a different state whose screening paperwork keeps breaking the software. I do both, deliberately, because the moment I stop doing the frontline work is the moment my advice starts drifting from reality.

I’ve been a platform administrator, a process designer, a training developer, a help desk, and the person who fields the call at 9 PM when a rollout isn’t working. The frameworks in this book aren’t theoretical. They come from building, breaking, and rebuilding operational systems in real portfolios with real teams and real constraints.

I also run Bridging Main, an operational efficiency consultancy for property management companies. That means I have a perspective that spans both the inside of a single large operation and the patterns I see across the industry. When I describe the problems in this book, I’m describing things I’ve lived. When I describe the solutions, I’m describing things I’ve built and maintained.

This book will give you a complete framework for assessing your operation, building the systems it needs, and sustaining the results as you grow. You’ll find specific, actionable guidance—not principles you have to figure out how to apply, but concrete steps you can take, frameworks you can implement, and tools you can use. Michael Gerber, in his landmark book The E-Myth Revisited, wrote decades ago about the difference between working in your business and working on it. That distinction hasn’t changed. What’s changed is the complexity of the environment you’re trying to build systems inside of—and the specific operational challenges facing property management companies have never had a dedicated playbook. Until now. If you read this book and never contact me, you should still be able to meaningfully improve how your operation runs. That’s the standard every chapter is written to.

What this book won’t do is sell you on a particular technology, a specific software platform, an AI tool, or the idea that any single product will solve your problems. Tools matter—including AI. But tools are only as good as the operation underneath them. And the operation is only as good as the experience it creates for the people inside it—your property managers, your leasing agents, your maintenance coordinators, and the residents they serve. The numbers in this book are real and the frameworks are practical, but underneath all of it is a simple belief: the people who work inside property management operations deserve systems that help them do good work, not systems that make the work harder than it needs to be.

The framework

Every chapter in this book follows a three-phase methodology that structures how I think about operational improvement: Assess, Build, Sustain.

Assess means figuring out why everything feels harder than it should. Not what you think is happening, but what’s actually happening—at the property level, in the daily workflows, in the gap between how leadership sees the operation and how the frontline experiences it. Most PMC owners know something is off. The assessment makes it specific: where time is being lost, where money is leaking, where risk is hiding, and which problems to fix first for the biggest impact.

Build means constructing the systems so your operation doesn’t depend on any one person’s memory, availability, or heroic effort to function. Documented knowledge, standardized workflows, configured tools, trained people, and clear communication channels. Not all at once. In the right sequence, starting with the highest-leverage work and building momentum from early wins.

Sustain means making sure the improvements actually stick—instead of quietly unraveling like every other initiative you’ve tried. Every operational improvement is an asset that depreciates without maintenance. Documentation goes stale. Processes drift. Costs creep back. Tools fall out of adoption. Sustaining isn’t the boring epilogue to the exciting implementation—it’s the phase where the compound returns accumulate. And it’s the phase most PMCs skip, which is why so many improvement initiatives produce temporary results that fade within a year.

These three phases structure the book. Chapters 1 and 2 are the Assess phase—understanding the problem and diagnosing your operation. Chapters 3 and 4 are the Build phase—implementing systems and managing the change. Chapter 5 is the Sustain phase—creating capacity, protecting gains, and building the maintenance discipline that makes improvements permanent. Chapter 6 addresses AI and technology as an accelerator across all three phases. And Chapter 7 gives you a practical starting point based on where you are today.

A word about AI

You’ve probably picked up this book partly because you’re feeling pressure to do something about AI. Everyone in the industry is. The vendors are shipping AI features. Your competitors are adopting them. Your residents are using them—as that opening story illustrated. And you’re wondering whether you’re falling behind.

Here’s what I want you to understand before we go any further, because it shapes everything in this book: AI is a multiplier. It amplifies whatever it touches—structure or chaos.

If your operation runs on documented processes, standardized workflows, clean data, and trained people, AI will make it faster, more consistent, and more capable. Knowledge retrieval becomes instant. Communication drafting becomes effortless. Routine decisions get handled before a human needs to touch them. The foundation you built gets accelerated.

If your operation runs on tribal knowledge, inconsistent processes, scattered communication, and software that’s half-configured, AI will amplify all of that. It will retrieve outdated information confidently. It will automate broken workflows at scale. It will draft communications using language nobody reviewed. It will produce analysis from messy data that looks sophisticated and means nothing—or worse, that is presented with total confidence and is completely wrong. You’ll spend money on tools your team doesn’t trust, conclude that AI doesn’t work for property management, and fall further behind the competitors who built their foundation first.

The work of getting your operation AI-ready—documenting processes, standardizing workflows, cleaning up your data, building communication frameworks—is the same work that makes your operation better with or without AI. That’s not a coincidence. It’s the whole point. The operational foundation is the investment. AI is the accelerant—think of it like electricity. When the wiring is sound, it powers everything. When it’s not, it starts fires. This book builds the foundation first, because everything else depends on it.

How to read this book

You can read it straight through. The chapters build on each other, and the narrative is designed to take you from understanding the problem through diagnosing your operation, building the systems, making changes stick, and sustaining the results.

You can also skip to where it hurts. If you already know your documentation is a mess, start with Chapter 3. If you’re in the middle of a failed software rollout, Chapter 4. If your turnover is killing you and you can’t figure out why, Chapter 5. If you picked up this book because of AI anxiety, Chapter 6 will tell you honestly whether you’re ready and what to do if you’re not.

Either way, I’d encourage you to read Chapter 7 last. It’s the practical chapter—where to start Monday morning, based on your company’s size and operational maturity. It works best after you have the full picture.

Let’s start with what the chaos is actually costing you. The number is larger than you think—and most of it is preventable.