Turning Property Data Into Smarter Operating Decisions

Most commercial real estate owners are not short on software. They are short on control. The data exists somewhere — in AppFolio, accounting systems, leasing tools, maintenance workflows, construction updates, spreadsheets, inboxes — but when the moment comes to make an operating decision, teams still chase information manually. That gap is where performance leaks out of an asset. In Episode 38 of Peak Property Performance®, Bill Douglas spoke with David Berneman about what happens when an owner-operator stops accepting out-of-the-box limitations and starts building operational intelligence from the data already inside the business. You can listen to the full episode here.

Owning the Workflow Starts With Owning the Data

David’s team had been using AppFolio for nearly 15 years. That is not a short-term experiment. That is a system deeply embedded in the daily operations of a real estate company. But after that much time, the limitation became clear: the standard software could only take them so far. They wanted better reporting, more relevant KPIs, and workflows that matched how their company actually operated.

“After using AppFolio for nearly 15 years, we realized we wanted more control over reporting, KPIs, and workflows. API access gave us the ability to build processes tailored to our business instead of relying solely on out-of-the-box functionality.”

That answer should get every owner’s attention. The issue was not that AppFolio had no value. The issue was that the business had matured beyond a vendor-defined operating model. At a certain point, owners need their systems to reflect their strategy, their reporting logic, their risk tolerance, their resident experience, and their internal handoffs. If the only way to see performance is through a dashboard someone else designed, you are not really operating from your own intelligence.

This is the reframe we come back to again and again at OpticWise: If you don't own your data & digital infrastructure, your vendors do. That does not mean every owner needs to become a software company. It means the owner needs clarity on where critical data lives, how it moves, who controls access, and how it supports decisions. That is the foundation of the PPP 5C™ framework — Clarify, Connect, Collect, Coordinate, Control. David’s story is a strong example of moving from “we use the system” to “we control how information supports the business.”

From an owner/operator perspective, this is a strategic shift. You are not buying tools just to modernize. You are building an operating advantage. From an architect’s perspective, the key mechanism is integration: API access, clean data flows, and interfaces that reduce friction instead of adding more screens. When those two perspectives line up, the conversation changes from “What software should we buy?” to “What do we need our data to do?”

The Move-Out Problem: A Simple Workflow With Real Operational Consequences

The first operational problem David described was not flashy. It was move-outs. That is exactly why it matters. Move-outs touch multiple departments: property management, maintenance, accounting, leasing, potentially construction, and sometimes ownership or asset management depending on the asset. The work is routine, but the coordination burden is real. One missed handoff can delay turns, create resident frustration, slow collections, or leave teams working from different versions of the truth.

David explained that communication gaps would occasionally appear because the information needed to travel across departments. The data existed, but it was not flowing automatically to the people who needed it. Someone had to move it manually, send a message, update a spreadsheet, check a system, or remind another team. That is not a people problem. That is an infrastructure problem.

“Once you have API access, you can build bridges between systems. The data exists — it just isn't flowing where it needs to go without someone manually moving it.”

Bill called it out directly in the conversation: this is the classic example of data sitting in one system while people need it in another, with manual steps in between. We see this constantly across commercial real estate portfolios. A property manager enters an update. Maintenance needs it. Accounting needs a trigger. Leasing needs visibility into availability. Construction may need to know whether a heavier scope is required. Leadership wants to understand turn time and cost across the portfolio. But unless the workflow is intentionally connected, each department ends up creating its own workaround.

That is where the “Coordinate” step in the PPP 5C™ framework becomes practical. Coordination is not a meeting. It is not another weekly report. It is designing the movement of information so the right action happens at the right time. In David’s move-out example, better coordination means the workflow itself carries the information forward. A notice to vacate should not sit idle in one system waiting for someone to remember the next step. It should trigger tasks, alerts, updates, and reporting across the departments that depend on that event.

Custom Workflows Only Work If People Actually Use Them

One of the most useful parts of the episode was David’s honesty about implementation. Building a workflow is not the same as building a workflow people want to use. In theory, automation sounds clean: connect the systems, move the data, trigger the task, produce the report. In practice, adoption depends on the daily experience of the people doing the work.

David said the amount of time required surprised him. Not because the concept was hard to understand, but because refinement takes effort. Creating the workflow was one layer. Building interfaces that felt natural to employees was another. His team used AI tools to accelerate development, but speed did not eliminate the need for iteration. That is an important distinction for owners evaluating where AI fits into operations.

Bill put it plainly: there is a gap between a workflow that technically works and one people will actually adopt. Drew would say this is where architecture meets behavior. A system can be logically correct and operationally useless if it makes the user’s day harder. If an employee has to click through too many fields, re-enter information, interpret unclear statuses, or maintain a shadow spreadsheet “just in case,” the workflow has failed even if the integration technically runs.

David’s line was the operator’s truth: if the interface creates more friction than it removes, people find workarounds. That is why data & digital infrastructure cannot be treated as a back-office IT exercise. It has to be designed around how the business actually runs. Who touches the process? Where do errors happen? What information is needed at the point of decision? What should be automated, and what still requires human judgment?

This is also where many CRE organizations get AI wrong. They start with the tool instead of the operating problem. David’s team used AI to accelerate development, but they still had to do the hard work of shaping workflows around real users. That is the right posture. AI can help, but it does not replace operational clarity. If anything, AI makes clarity more important because automation at scale can amplify either good process or bad process.

Turning System Data Into Operating Intelligence

Where this gets practical is in the difference between “having data” and actually using data to run the asset. Most owners already have rent rolls, work orders, delinquency reports, lease dates, renewal notes, vendor invoices, capital project updates, and leasing activity. The problem is that those details often sit in separate places. One team exports a spreadsheet. Another team keeps a tracker. Someone else knows the story behind the numbers but has to explain it in a meeting. That is not intelligence. That is institutional memory under stress.

David’s approach was to pull operational data out of the core system and use it in ways the business could act on. API access became the bridge between the system of record and the actual operating rhythm of the company. That meant they could create reporting that matched their internal questions, not just the software’s default categories. Which units are creating repeat maintenance friction? Which properties are trending toward collection issues earlier than the monthly report shows? Where are leasing, maintenance, and accounting decisions affecting each other?

“The API let us take the information already in the system and use it in a way that made sense for how we operate. We were not trying to replace the system. We were trying to make the data more useful.”

That distinction matters. We see too many owners treat every limitation as a reason to rip and replace a platform. Sometimes replacement is necessary. But often, the first move is not a new system — it is better architecture around the systems already in place. Clarify what decisions need support. Connect the systems that hold the inputs. Collect the right data in a consistent way. Coordinate the workflow across departments. Then Control the environment so the owner, not the vendor, defines how performance is measured.

Why Custom Workflows Are Not Just an IT Project

One of the biggest traps in commercial real estate is treating data & digital infrastructure as a back-office technology issue. It is not. It is an ownership issue. If your asset managers, property managers, accounting team, leasing team, and maintenance team are all working from different versions of the truth, that affects NOI. It affects resident satisfaction. It affects lender reporting. It affects how fast leadership can make decisions when conditions change.

This is where Bill’s owner/operator lens and Drew’s architecture lens meet. The owner’s question is, “What do we need to know to run the business better?” The architect’s question is, “How should information move so that answer is available without heroic manual effort?” When those two questions are asked together, the conversation changes. You stop debating whether a dashboard looks nice and start asking whether the workflow creates accountability, speed, and confidence.

For example, a maintenance request is not just a maintenance request. It may be an early signal of a capital issue, a resident experience issue, a vendor performance issue, or a budgeting issue. If that work order lives only as a closed ticket in one system, leadership may never see the pattern. But if the data is structured and connected, the same request can inform preventive maintenance planning, renewal risk, vendor scorecards, and capital allocation. That is the difference between recordkeeping and operational intelligence.

“You can start to see patterns that are hard to see when everyone is just looking at the default screens. Once the data is accessible, you can ask better questions.”

That is also why ownership matters. A vendor dashboard can show what the vendor decided to show. Your operating model may require something else entirely. Maybe your team needs a weekly exception report. Maybe regional managers need portfolio comparisons. Maybe executives need one view that combines collections, leasing, maintenance, and cash flow. Those are not abstract technology wants. Those are management needs. And they should be designed around how the business actually runs.

Actionable Takeaways for CRE Owners

The lesson from David’s experience is not that every owner should immediately build custom software. The lesson is that owners should stop accepting disconnected data as normal. Start with the business outcome. What decisions are slow, unclear, or overly dependent on manual follow-up? Where does your team spend time reconciling numbers instead of acting on them? Where are you relying on one person’s memory because the system does not tell the full story?

Then apply the PPP 5C™ framework in sequence. Clarify the operating questions that matter most. Connect the systems where the answers live. Collect data in a consistent structure so reports are trustworthy. Coordinate the workflows across departments so information moves with the work. Control access, governance, and reporting logic so the owner maintains command of the environment. This is how data & digital infrastructure becomes part of asset strategy, not just software administration.

For many owners, the best first step is an audit of the current operating stack. List the core systems. Identify what data each system holds. Map the manual exports, spreadsheets, email handoffs, and recurring reports that keep the business moving. Those workarounds are not just annoyances. They are clues. They show you where your infrastructure is not keeping up with your operating model. Once you see those gaps clearly, you can decide whether the answer is configuration, integration, process redesign, or a more significant platform change.

If you want a deeper framework for thinking this way, the Peak Property Performance® book lays out how owners can connect building performance, digital systems, and operating outcomes. And if this conversation resonated, the Peak Property Performance® Podcast includes more operator-to-operator discussions with leaders solving these problems in the real world.

The practical takeaway is simple: do not let your operating intelligence be limited by someone else’s default dashboard. Your portfolio has its own strategy, risks, workflows, and performance levers. Your data & digital infrastructure should reflect that. Start by identifying one high-friction workflow — reporting, maintenance, leasing, collections, capital projects, or vendor management — and ask what information your team needs, where that information lives, and who currently controls it. That conversation alone will reveal where performance is leaking.

Because in today’s market, better operations are not created by adding more tools. They are created by owning the infrastructure that allows the right people to make the right decisions faster. If you don't own your data & digital infrastructure, your vendors do. The owners who understand that will not just have cleaner reports. They will have a stronger operating platform for Peak Property Performance®.

About OpticWise: OpticWise provides owner-controlled data & digital infrastructure for commercial real estate — from PPP Audits to portfolio-wide intelligence. See how we operate or read customer outcomes.