Leasing and Occupancy Dashboard for Multifamily Owners Built in Claude

A multifamily company can hold 15 years of underwriting, marketing and operational documents and still have no live answer to a simple question: how full are we, and what is slowing the units that are empty?

This is a Claude build for the CEO of a multifamily real estate investment company. It is written for real estate investors and teams who own the data but cannot see it. On the call we turned to leasing, construction and the company's own history. We report no outcome, and we say what was built and what was only planned.

The situation

The company's knowledge base held 15 years of deal underwriting, marketing materials, pitch decks and operational documents. All of it was written for people. None of it was set up for an AI to read and use.

On the operations side, there was no dashboard for leasing and occupancy, and none for construction progress. Down units, meaning vacant units that are being turned over, cost revenue every day they stay empty, and nothing in the company's dashboards measured it.

What was missing

Three things were missing, and each one blocked the next.

• A readable archive. The documents lived in a cloud file storage account that Claude could not yet read.
• A single statement of priorities for Claude to work from.
• Live operations views. Leasing, occupancy and construction progress had no dashboard, and the effect of slow unit turns on revenue had no measure.

What we built

We built the priorities and the views first, and connected the archive the same day.

• A priorities document in Claude that supersedes all other priorities in the system. The CEO reviews it weekly and refines it with Claude.
• A leasing and occupancy dashboard.
• A construction progress dashboard.
• A connection to the cloud file storage knowledge base, with full read access so Claude can use the history as context.
• A scheduled task, planned for each Monday, to export data from the operations system and refresh the dashboards.
• Skill files, recorded and created as an ongoing activity, because they are the foundation for the rest of the AI system.

What changed

We have no outcome to report. The dashboards and the archive connection were built, and setting up the Monday data refresh was the next task on the list.

We also planned a key-to-key velocity dashboard, which was not yet built. Key-to-key speed usually means the time between one resident handing back the keys and the next resident receiving theirs, and it measures the revenue lost from down units directly. The last step was a leadership demo with two other company leaders to get buy-in before a formal engagement. Once they agreed, the plan was to move to a full build across departments.

What to take from this

This section is advice for your own company. Before you build a dashboard, decide what it is for. A written statement of priorities, reviewed weekly, gives every later request something to be measured against.

Pick one metric that connects operations to money. Turn time on vacant units is a good candidate for a multifamily owner, since every extra day is lost rent. Then connect your history last, once the dashboards show you which questions your old documents need to answer.

Finally, write skill files as you go. Recording how work is done, step by step, is what lets an AI repeat it next month. In this build that recording continued as an ongoing task, because the skill files are the foundation for the rest of the system.

Frequently asked questions

What is a key-to-key turnover dashboard?

Key-to-key measures the days from one resident handing back the keys to the next receiving theirs. It shows how much revenue slow unit turns cost. We planned this dashboard as the next step and had not built it when we reviewed.

How do you make 15 years of documents usable by AI?

In this build, we connected the company's cloud file storage knowledge base to Claude with full read access. That gives Claude the history as context. We did not report results from it yet, and we added skill files as the ongoing foundation.

Why write a priorities document before the dashboards?

A priorities document tells the system what matters most, so later requests are ranked against it. The CEO reviews it every week and refines it with Claude, which keeps it current without a separate planning project.

How do the dashboards stay current?

A scheduled task was planned for each Monday to export data from the operations system and refresh the dashboards. That means the views are as current as the last export, and a live data connection would be the next improvement.

If you own the data but cannot see occupancy, turns or construction in one place, book a 30-minute AI follow-up and reporting audit. We map your reports to the views that would make them useful.