VIRTUA / Insights

Operations

Operations Affects Financials: What Ten HVAC Calls Taught Me About Running a Building

VIRTUA / Operating perspectives

There’s a question I ask every property management owner I work with. You take care of the owners. You take care of their assets. You take care of everything that keeps those assets running.

But who’s taking care of you? Who’s taking care of your company?

Most of the time the honest answer is nobody, because there’s no time. And that has a cost you can measure.

I learned this the hard way

Before VIRTUA, I worked inside property management companies, usually in one lane, one department. Some of those portfolios were 1,600 units, which in practice meant far more tenants than that. I always did well in those roles, and the reason was simple: I built systems for myself. It was the only way to keep track of that much without losing things.

Then I took on a commercial building in New Jersey, and every problem came to me.

I couldn’t step away from my computer. When my family called to tell me what was going on in their lives, I’d have to say: I can’t be present right now. That wasn’t the life I wanted, and it wasn’t the reason I got into this work.

So I built a system for the building. Where requests land, which vendor handles what, what happens when. The decisions I was making over and over in my head became rules.

Once the daily work stopped running through me, I could finally see the building. The expenses. The issues that kept repeating. The vendors who weren’t performing — and I had to let some of them go and bring in vendors who worked at the level we needed. I started working on leasing strategy and capital planning. I built real relationships with the tenants. The previous owner had never invested in that building. We started increasing its value.

That’s where I became a firm believer in one idea: operations affects financials.

Ten HVAC calls, one building

Here’s what reactive looks like in dollars.

At that building, I kept dispatching a vendor for the same HVAC problem. A call comes in, a vendor goes out, an invoice gets paid. I was closing tickets. I wasn’t solving anything.

When I finally stopped and asked what the actual problem was, the answer was the unit. Replacing it cost between $12,000 and $14,000. That’s a real number, and it’s a big one. But it’s one decision, instead of an open-ended stream of dispatches that never fixes the cause.

Now run that across a portfolio. Say a dispatch costs you $300 and the same unit has needed one ten times this month. Nobody on your team is doing anything wrong — they’re responding to what’s in front of them. They just don’t have time to step back and notice it’s the same problem, ten times.

That’s the hidden tax of reactive operations. Not only the repeat repairs, but the fact that no one has room to see them as a pattern.

How messy operations drain margins

The same thing happens everywhere in the business, quietly:

Slow lead responses stretch vacancy. Every day a unit sits empty comes straight out of net operating income.

Disorganized vendor dispatch. Duplicate invoices, and vendor performance nobody is actually watching.

Rules that live in people’s heads. Every absence becomes a risk.

Clean, systemized operations lower monthly overhead. And they protect the thing your owners actually care about: the value of the property.

The rules in your team’s heads are a financial risk

One of my clients had a Section 8 portfolio in Memphis. The owners weren’t happy with their property manager’s performance, and they couldn’t let her go.

She was the only one who knew why an applicant got accepted or rejected, how the Section 8 packages were put together, who to send them to, and when to follow up. If she left, all of it left with her. The owners were held hostage by their own operation.

We extracted it. The approval thresholds, the credit criteria, the income requirements, the Section 8 contacts. Every decision she made from memory became a rule the system holds.

Every property management company runs leasing, maintenance and collections in roughly the same shape. But everyone’s rules are different. One owner won’t approve anyone who earns less than three times the rent or has an eviction on record. Another is more compassionate: if an applicant had debt in the past but is paying on time now, that’s fine. Neither is wrong. What’s risky is when those rules exist only in someone’s head.

I say this to every founder, in property management or not: never let one person, however much you trust them, hold all the information about how your company runs. Maybe they’ll never leave. Maybe they’ll get a better offer, and you should be happy for them. Either way, your company shouldn’t stop when they walk out the door.

The operator trap

Tony Robbins has made the point that founders start businesses to create freedom, and then end up trapped as operators — working in the business every day because they’re the only one who knows how it runs.

I see that in almost every owner I meet. It’s understandable. It’s your company, your reputation, and you want it done right. But the way out isn’t doing more. It’s building a system that holds how you decide, so the business can run the way you would run it, without you in every loop.

When I map a company, I look at seven things: information, people, process, rules, technology, automation and controls. Most property management companies only have people and technology.

Closing tickets versus protecting assets

You can run a property management company that closes work orders and fills units. That matters. But you can also be the company that tells an owner: we handled your operations, and we also noticed this unit has cost you ten dispatches this quarter, so here’s what we recommend instead.

That’s a service of excellence. And you can’t deliver it while you’re reacting to every day.

None of this means replacing your property management software. Your PMS holds the record. What’s missing is a system of action alongside it — synced to it, holding your rules, doing the repetitive work — so your team has room to think about the asset.

The process is always the same: diagnose how you run today, map it, architect how it should run, then build and automate. It’s work. It’s also the only way I know to stop being the bottleneck in your own business.

If there’s a repair your team has fixed five times this year, DM me ROOT.

Your next building should not expose the same operating problems.

Start with a conversation about where your company is relying on memory, delayed approvals, scattered tools or recurring escalation. If there is a fit, we begin with an operational diagnosis.

Discuss an operational diagnosis ↗Or email Sonia ↗