Brokerage ops

Turn the hour-long Friday status report into a shared Claude skill connected to email, Teams, and SharePoint

Savoy Companies, a Dallas apartment owner-operator that manages more than 7,000 units, gave its top 20 people a Claude Team subscription and loaded Claude with context before anyone wrote a prompt: the org structure, how the firm formats internal and external documents, and shared Claude skills the whole organization uses. Co-founder Barrett Linburg's example is the Friday update. The head of development used to spend an hour every Friday assembling a status report for the two founders. Now Claude, connected to that executive's email, Microsoft Teams, and SharePoint, runs a shared skill and produces the Friday report in about five minutes. Linburg says some of the 20 users still don't really understand AI and the skills work anyway. The founders also file the Friday updates into a shared Obsidian vault so Claude can read last week's updates and flag issues. Savoy does not use AI to talk to tenants, vendors, or subcontractors. The time figures are Linburg's account and were not audited by the publication.

At a glance

Tools used
ClaudeObsidian
Category
Brokerage ops
Audience
investor, team lead
Difficulty
No-code setup
Source
The Dallas Apartment Owner Who Was Quoted $1 Million for a Dashboard, Then Built It Himself in Claude Code
AI for CRE Collective (Editorial Desk) · Article · Jul 14, 2026
First step
Pull up the last three Friday status reports one person on your team wrote, and list the sections they always contain and the inbox, chat, and folder each section's facts come from.

Compliance note: The report goes to the owners under the employee's name, so the employee reads and corrects the draft before sending. Give the skill read access only to the mailboxes and folders the report actually needs.

Suggested prompt

Written by this directory, inspired by the source. Replace the [bracketed] parts.

Help me build a reusable Claude skill called Friday Status Report. Here are three past Friday reports as examples of the format and tone: [paste]. Each week the skill should read my email, Teams messages, and SharePoint project folders from Monday through Friday of the current week and produce the same sections in the same order: [list sections, for example each project's status, decisions needed from the owners, schedule changes, budget changes, open risks]. Rules: use only facts found in those sources, name the email or file each item came from, mark anything you could not confirm as UNCONFIRMED, and never invent a date, dollar amount, or status. Before you write the skill, ask me which projects and folders are in scope and who receives the report.

Share on X Read the source

← All use cases