Skip to content
← All case studies

AGENTS

Towne Properties

Agents and dashboards inside a property manager's operations

AGENTS & DASHBOARDS

Case 01 · Property managementCincinnati, OH

Towne Properties · Daily and weekly pricing reports from Yardi, EliseAI and the pricing sheet

Yardi, EliseAI and the pricing sheet feed a pricing report. The leasing lead signs it, and it is sent to the team.

PRICING REPORTS · LEASING LEAD SIGNS · SENT TO THE TEAM

8+ hours by hand → 10 minutes

per report; running about a month, against building it by hand in Yardi

Status
Live in 1 week
Signed by
Signed by Leasing lead

What was built

  • Daily and weekly pricing reports from Yardi, EliseAI and the pricing sheet
  • A reporting dashboard that mirrors the monthly report-pulling workflow
  • An AI program backlog, prioritized with leadership
  • A vendor AI roadmap review

Where it runs

  • Internal web app
  • Leadership review

Tools

  • Claude Code and the Claude API
  • Linear
  • Next.js

By hand, the daily pricing report takes 8+ hours of copying from Yardi, EliseAI and the pricing sheet. With the agent, it's compiled and checked, the leasing lead signs, and it goes to the team in 10 minutes.

01

The problem: the monthly report pull

Towne Properties manages communities from Cincinnati, and every month someone senior pulled the same reports from two systems by hand, lined them up, and read the story off the numbers — for a pilot group of properties whose results leadership was watching closely. The numbers mattered and the read was real. The ritual was the problem: a morning of pulling before a minute of thinking.

02

What was built

A dashboard that mirrors that monthly workflow exactly — the two systems' reports side by side, on one screen, refreshed on the schedule the team already keeps — so the read happens in minutes instead of a morning, and the definitions the team used to argue about are written down once.

Around it, an AI program backlog: the workflows worth automating next, ranked with leadership — management dashboards, ticketing and triage, scheduling — tracked in the open and built one at a time. And before any vendor's AI was bought, a roadmap review that keeps the vendor's claims, the publicly confirmed facts, and the open questions visibly separate.

03

The daily pricing report

The team also needed daily and weekly pricing reports, and building each one by hand in Yardi took 8+ hours. Now an agent pulls rents and occupancy from Yardi, leasing conversations from EliseAI and the team's pricing sheet into one report every morning, checks it against yesterday, and queues it for the leasing lead to sign before it goes to the team.

It takes 10 minutes per report. It went live in 1 week and has been running for about a month.

The red box is the only step with a person in it; every other step is an agent.

  • one piece of work
  • the agent
  • the only human in the loop
  • sent and logged
  • Simulated runs · example items, not client data

Case 01 · Towne Properties · property management

The daily pricing report, compiled before the leasing calls start.

Rents and occupancy from Yardi, leasing conversations from EliseAI and the team's pricing sheet come together in one report every morning, checked against yesterday, signed by the leasing lead.

Yardirents · occupancyEliseAIleasing conversationsPricing sheetthe team's spreadsheetAGENT 03compiles the dayChecked vs yesterdaychanges flaggedLeasing lead signssigns every hand-offHUMAN IN THE LOOPTO SIGN · 0In reps' inboxesbefore the calls
  1. Yardi. The property system of record.
  2. EliseAI. What prospects are asking, by property.
  3. Pricing sheet. Today's pricing decisions, where the team already keeps them.
  4. AGENT 03. Pulls the three sources into one report, property by property, every morning.
  5. Checked vs yesterday. Every figure compared with yesterday. Big moves are flagged, each with its source.
  6. Leasing lead signs. The leasing lead reads the flags and signs the report. A person signs here: LEASING LEAD.
  7. In reps' inboxes. Delivered before the morning calls, and logged.
Hover or tap a box to see what happens there.
Format of the run log · sample, no client data
    Handled
    0
    To sign
    0
    Signed
    0

    Format of the run log · sample, no client data

    04

    The person in the loop

    Nothing here replaces a decision. The dashboard shows the same numbers the same person used to pull, with the definitions written down once — the agent never redefines a number. The backlog is prioritized by leadership, not by the agent. The roadmap review ends in decision controls — approve, hold, needs confirmation — so a person, not a model, decides what goes ahead. The pricing report goes out only after the leasing lead signs it.

    05

    What's next

    The round-one priorities set with leadership: management dashboards first, then contract management, ticketing and triage, and a scheduling app — each one a pilot with its own approver, on the systems the team already runs.

    Credits

    Design, build and operation
    DH Studios