AI for Multifamily Asset Managers
Why AI is an asset manager's lever, not a leasing trick
Most of the AI conversation in multifamily is happening at the property level: chatbots, lead nurture, AI leasing agents. That's the wrong altitude for what you do. Used well, these tools take half the friction out of how an AM actually spends a week.
This module is educational. AI tools produce confident-sounding output that can contain factual, legal, or numerical errors. Verify every number, name, date, citation, and regulatory claim before it leaves your desk. Anything that goes to an owner, investor, vendor, or resident is your work product, not the AI's. Full disclaimer.
An asset manager's week is roughly four things. Reading reports and translating them into questions. Writing. Owner memos, variance comments, renewal narratives, board updates. Building decisions out of incomplete information. And holding property management accountable to a standard. AI is genuinely useful for the first two and the fourth. It is genuinely not useful for the third, and that's the part the marketing material won't tell you.
This module is about using two tools, ChatGPT and Claude, to compress the work that pays you nothing extra to do well. Variance memos, owner narratives, vendor letters, monthly briefings, draft scopes, meeting recaps. The same output, in 20% of the time, written in your voice. The time you get back goes into the work that only you can do: deciding what to push on, what to drop, what to spend on, what to defend, when to fire the vendor, when to hold the rate.
The asset managers who are getting the most out of AI right now aren't the ones using it the most. They're the ones who picked two or three repeatable tasks, made the output reliable, and stopped. The compounding return is in depth, not breadth.
What these tools actually are
ChatGPT and Claude are large language models. The plain-English version: they're software trained on enormous amounts of text that learned to produce coherent, useful writing on demand. They are excellent writing assistants. They are not search engines, not databases, and not auditors. They don't verify facts. They don't check your math. They will sound certain about things they're wrong about.
For your work, that means you use them to write, structure, summarize, and organize. You don't use them to pull current rents, run live financials, or replace your judgment on what a variance means.
What this module covers
Foundations first: the two main tools, when to reach for each, where the leverage actually is. Then prompting and voice training, so the output is something you'd put your name on. Then multi-tool workflows that compound. Then the Cowork environment and Skills, the next layer up, where you stop typing prompts and start handing files to a saved process. The module closes with three tools you can use today: an ROI calculator, a prompt builder, and a Skill planning worksheet.
ChatGPT vs. Claude: when to reach for which
They're not competitors. They're specialists. Knowing which one to open for which task is the single highest-leverage thing you'll learn in this module.
Most people pick one and stop. That's a mistake. The output gap between using the right tool and the wrong tool, for a given task, is large enough that a 5-minute decision about which one to open compounds across a week into real time.
ChatGPT
- Built by OpenAI. The default in most people's heads.
- Fast first drafts when tone doesn't matter much.
- Brainstorming. Give me 8 options, not the right one.
- Structured lists, tables, and checklists from messy notes.
- Web research (paid tier with browsing).
- Short, punchy copy: subject lines, ad headlines, captions.
Claude
- Built by Anthropic. The one that sounds more like a person.
- Long-form writing (memos, narratives, SOPs) that holds voice.
- Reading and summarizing uploaded files (T12, lease, owner deck).
- Following complex multi-part instructions reliably.
- Writing in your style after you load a style guide.
- Powers Cowork: desktop app with file access and Skills.
The simple rule
ChatGPT for fast and rough. When you need a defensible first draft in three minutes and you'll edit anyway.
Claude for considered and long. When the output has to sound like you, when there's an uploaded document to digest, or when the instructions have multiple moving parts.
When in doubt: if the work would normally take you more than 20 minutes and the tone matters, open Claude. If it would take 5 minutes and you just need a starting point, open ChatGPT.
Where each one fails
Both tools will produce confident, well-formatted output that contains specific factual errors. ChatGPT does this more often, especially with numbers, dates, lease clauses, and state-specific regulatory language. Claude does it less often but does it. Neither tool should ever produce a number that ends up in an owner deliverable without you having sourced that number yourself.
Any number, name, date, or quoted regulation that came out of an AI tool gets verified before it leaves your desk. The output looking polished is not the same as it being correct.
Cost and access
Free tiers of both exist and are usable. The paid versions (~$20/month each) unlock the things you'll actually want: longer file uploads, web browsing on ChatGPT, the desktop app and Cowork on Claude. If you're going to use these tools weekly, the paid versions pay for themselves the first time you compress a budget memo from two hours to twenty minutes.
The highest-value starting points for an AM
Don't try to AI everything. Pick the two or three places where the time-cost-to-quality tradeoff is most embarrassing. Start there.
The mistake to avoid: trying to use AI for everything at once. You'll get spotty results, lose confidence in the tool, and quit. Instead, look at your week and find the tasks that meet three conditions: you do them at least monthly, they take real time, and the output is judged on clarity and professionalism rather than originality. Those are the wins.
| Task | Time saved / month | Best tool |
|---|---|---|
| Monthly variance commentary (drafting + tightening) | 3–6 hours | Claude |
| Owner monthly memo / narrative | 2–4 hours | Claude (with voice guide) |
| Summarizing long T12s, owner decks, or vendor proposals | 2–4 hours | Claude |
| Drafting renewal letters / NTV-save outreach | 1–2 hours | Claude |
| Turning property visit notes into a written report | 1–2 hours per visit | Claude |
| Drafting scopes of work for value-add bids | 2–3 hours per project | ChatGPT then Claude |
| Weekly call recap → action items for PM | 2–3 hours | ChatGPT or Claude |
| SOPs you've been meaning to write for two years | 3–5 hours per SOP | Claude |
Your first week
Pick the one task on that list that you most resent. The one you put off until Sunday night. Open one of the tools, describe the task the way you'd describe it to a new analyst, and run it. Edit the output. Note what the AI got wrong, what it got right. Run it again the next week with the same prompt, slightly tightened. By week three the prompt is stable, the output is reliable, and you've recovered an evening.
Don't add a second task until the first one is dialed in. Depth before breadth. Every time.
The variance memo is the most underrated use case for an asset manager. PM software produces the numbers. AI produces the prose. You produce the judgment about what to push on. Once that workflow is clean, every other writing task collapses in the same way.
Writing prompts that get work-grade output
There's no magic to prompting. There's a small set of moves that consistently produce useful output and a larger set of habits that produce generic mush. Learn the five moves and you're 90% of the way there.
The five-part structure
Every prompt that produces good output has the same skeleton:
Context
Who you are, what you're doing, what the world looks like. "I'm an asset manager for a 280-unit Class B in suburban Atlanta. We're underwriting the property at a 7.2 cap on stabilized NOI."
Task
The specific thing you want the AI to produce. Not "help me with my budget." "Write the operating expense assumptions section of a 2026 budget memo, three paragraphs."
Audience
Who's going to read it. An owner, a board, a property manager, an investor. "The reader is the fund's investment committee. They want defensible logic, not enthusiasm."
Constraints
Length, tone, format, what to avoid. "Under 300 words. Direct, no hedging. Don't use the words 'best-in-class' or 'value-add proposition.' Use plain numbers, no jargon."
Material
The actual data, document, or notes you want the AI to work from. Either pasted into the chat or uploaded as a file. The output quality is almost entirely a function of how good the input material is.
A weak prompt vs. a strong one
That gets you a generic page of LinkedIn-grade prose about "managing variances effectively." Useless. Now compare:
The second prompt gets you 80% of a usable memo on the first try. Five minutes of editing and it's out the door. The first prompt gets you something you'd throw away.
Iteration is part of the work
Almost no prompt produces the right output on the first try. The skill is in how you respond to the first output. The wrong move is to retype the whole prompt. The right move is to tell the AI what was wrong with the draft and what to do differently:
Habits that produce mush
- "Help me with…" is too vague. State the task as an instruction.
- No audience specified. Output will sound like it's written for nobody.
- No length constraint. Output will be three times what you wanted.
- No tone instruction. Output will default to corporate LinkedIn.
- No material provided. The AI will invent details that sound plausible.
- Asking for "best practices" will get you a Wikipedia entry, not a useful answer.
Training Claude on your voice
The single move that turns Claude from a useful tool into something that ghost-writes for you is a style guide. Twenty minutes of setup, paid back every week for the rest of your career.
If you've ever read an AI-written email and known immediately that it was AI, it's because no one told the AI how to sound. Default output is polite, formulaic, and faintly robotic. That's fine for an internal checklist. It's wrong for anything that goes to an owner, an investor, or a vendor relationship you've spent years building.
A style guide is just a chunk of text you paste at the start of a Claude conversation. It contains a few real samples of your writing, plus your own notes about what's distinctive about your voice. Once Claude has it, everything else you write in that conversation comes out sounding like you.
Build the guide once
- Find 3–5 emails, memos, or letters you've written in the last year that you were genuinely happy with. Not your best. Your most representative. The way you actually sound on a good day.
- Paste them into a Word doc, separated clearly. Save it as
style-guide.txtsomewhere you'll find it. - Add a short list of notes (three or four bullets) about what's distinctive. "Short sentences. No filler openers. Direct but warm. I don't use the word 'certainly.'"
- Test it in Claude with the prompt below. Iterate on your notes section until the test output sounds right.
- Paste the finished guide at the start of any Claude conversation where you want output in your voice.
Use the guide for renewal letters and owner memos
Two places the style guide pays off immediately: anything an owner reads, and anything a long-term resident reads. Both of those readers can tell when something is templated, and both lose trust when they spot it.
When to refresh the guide
Every six months or so, replace one of the samples with something newer. Your voice changes. The way you wrote two years ago isn't the way you write today. Keeping the samples current means the output stays current.
The biggest unlock from a style guide is psychological. Once you know the AI can write in your voice, you'll start using it for things you wouldn't have considered automating: a difficult vendor email, a tough call recap, the year-end note to a long-term owner. The work that requires care is the work where compressing the time actually matters.
Multi-tool workflows that compound
The biggest output gains come from handing work between tools. Use ChatGPT to generate raw material fast, then pass it to Claude to refine in your voice. Or the reverse. The tools are specialists. Treat them that way.
Workflow 1: Monthly variance memo
The variance memo is where most AMs lose the most time. This workflow takes it from a two-hour slog to about twenty minutes.
Workflow 2: New scope of work for a value-add bid
Scopes are repeatable, but every property has its own quirks. The handoff lets you start from a strong base and customize.
Workflow 3: Weekly call recap → action items
If you take notes during the weekly call with PM, this workflow turns them into a clean recap email with action items in two minutes, including who owns what and when it's due.
Workflow 4: Owner narrative from a stack of source docs
For quarterly investor updates or year-end narratives that need to pull from multiple sources (the operating report, the budget, the rent roll, the leasing report), Claude is the right tool because it handles uploaded documents directly.
Every time a prompt produces exactly what you needed, paste it into a doc labeled "AI Prompts: keepers." Within a quarter you'll have a personal library of 10–15 prompts that handle 80% of your repeatable writing. Your team can use them too. This is how the leverage compounds.
What Cowork actually is
If chat is AI you talk to, Cowork is AI that does work for you. It's a desktop app that reads your actual files, writes new ones, and runs saved processes you've defined.
Everything in the previous sections required you to copy, paste, and edit. Cowork takes a different posture. You point it at a folder on your computer, drop files in, and tell it what to do. It reads the files directly, produces output files, and saves them back. No copy-paste. No re-running prompts. The output of one task becomes the input of the next without you in the middle.
Cowork vs. the web app
Claude.ai (browser)
- Web interface. No install.
- You paste content into the chat manually.
- Great for one-off writing and learning the tools.
- Every conversation starts cold.
Claude Cowork (desktop)
- Native app. Reads files in a folder you select.
- Builds Excel, Word, PDFs directly to disk.
- Supports Skills: saved automated workflows.
- Can run on a schedule.
- Where the real AM leverage lives.
How a folder works
You point Cowork at one folder. Claude can read, create, and edit anything inside it, like a team member with access to a shared drive. It cannot see anything outside that folder. That boundary is the whole security model: you control access by controlling what lives in the folder.
Most AMs end up with a folder structure that mirrors their workflow:
Claude reads file names as context. A file named 2026-04-owner-report-maplewood.pdf tells Claude exactly what it is. report.pdf tells it nothing. The naming discipline pays you back every time you ask for analysis across multiple files.
What Cowork can't do
It can't log into your PM software. It can't pull live data from a portal. It can't see your inbox unless you connect it explicitly through a plugin. If your PM software exports a CSV, PDF, or Excel, that export is the bridge between your tools. That's enough for almost every AM workflow worth automating.
Getting started
- Install the Claude desktop app from
claude.com. Cowork is built in. - Create a folder on your computer following the structure above. Start with one property.
- Point Cowork at the folder. Drop one PDF in. Ask Claude to summarize it. See what happens.
- Browse the built-in Skills. Several already cover multifamily workflows: monthly reporting dashboards, budget builders, rent comp surveys.
- Once you've used the built-in Skills for a month, you'll know which one of your own workflows is the right candidate for a custom Skill.
Anatomy of a Skill
A Skill is a saved process that turns a recurring task into a one-line command. Every Skill is built from the same three pieces. Understand the three, and you can read any Skill, edit any Skill, and eventually write your own.
A Skill is a text file. No code, no programming, no IT involvement. It lives in a folder inside your Cowork directory. When you tell Claude to run the Skill on a file, Claude opens the text file, reads the instructions, and executes them.
The three parts
Trigger description
When this Skill should run. Claude reads it to decide whether to use the Skill when you describe a task. The good ones name the input, the task, and the output.
Instructions
The step-by-step process Claude follows. Ordered, unambiguous, written the way you'd explain the task to a new analyst on day one.
Output definition
What the final output is: file format, name, structure, columns, tone, formatting. Without this, the Skill produces something different every time.
What a Skill file looks like
Below is a simplified example for a monthly reporting Skill, one that reads an owner package PDF and produces an Excel dashboard. Look for the three parts.
Every instruction starts with an action verb. The output definition is specific enough that two runs on different months would produce identically structured files. That consistency is the entire point. A Skill that produces a different format each time is worth roughly the same as a saved prompt.
Skill vs. saved prompt
A saved prompt is a template you paste into Claude each time and modify. A Skill is something Claude executes automatically. You point at a file, name the Skill, and the output appears. The difference is small to describe and large in practice. After a month, every saved prompt is a tax you keep paying. A Skill is a one-time investment.
Building and testing your first Skill
The reason most custom Skills fail is that they get written before the workflow is clearly defined. This is the planning framework, the writing standard, and the testing loop.
Pick a good candidate
Not every task is a Skill candidate. The good ones share three traits: predictable schedule, consistent input format, and consistent output.
| Trait | Good Skill candidate | Not a fit |
|---|---|---|
| Frequency | Monthly variance memo, weekly leasing summary, quarterly investor narrative | One-off dispositions analysis |
| Input consistency | Same export format from PM software every time | Sometimes PDF, sometimes email, sometimes verbal |
| Output consistency | Always the same Excel template, same columns | Output shape changes based on the audience |
The Input / Process / Output framework
Before you write a single word of SKILL.md, answer three questions as specifically as you can. These answers become the skeleton of the Skill. The Skill planner tool at the end of this module walks you through the same three questions.
Describe the file Claude will start with. Format, source, what it looks like. "A CSV exported from RentManager's delinquency screen, with columns for Unit, Resident Name, Days Past Due, Current Balance, Last Payment Date, and Notes" is far better than "a delinquency report."
List every step Claude takes between input and output. In order. Include the logic. "Flag anyone over 30 days in red. Exclude residents on an active payment plan. Sort by days past due descending." If a step needs judgment, describe what that judgment looks like.
Describe the deliverable. File format, file name, columns, sort order, formatting. Then describe what Claude says to you when it's done: a one-line confirmation, a list of flagged items, or a question to review. That closing message is how you know the Skill ran correctly.
Strong instructions vs. weak ones
| Weak | What Claude does with it | Strong |
|---|---|---|
| "Summarize the delinquencies." | Paragraph one time, table the next, bullets the third. | "Build a table with columns: Unit, Resident, Days Past Due, Balance, Risk Level, Action." |
| "Flag high-risk residents." | Picks its own threshold. Inconsistent. | "Flag as High Risk: 31+ days past due AND no active payment plan." |
| "Save the file." | Saves anywhere, names it anything. | "Save as Delinquency-Summary-[Month]-[Year].xlsx to outputs/." |
Use Claude to help you write the Skill
You don't write the SKILL.md alone. You describe the workflow to Claude and Claude writes the file. This prompt is the one that does the heavy lifting:
The testing loop
No Skill is right on the first run. Test it against a sample input. Ideally last month's actual file, where you already know what the output should look like. Then refine. The refinement prompt:
A Skill that nails it on the first test is rare. Two to three iterations is normal. After that, the output is consistent enough that you can trust it without close review every run.
Scaling Skills across your team
A Skill that works for you becomes ten times more valuable when your whole team runs it. The mechanism for sharing is intentionally simple. The standard for what gets shared is intentionally high.
How sharing actually works
A Skill is a folder containing a SKILL.md file. To share it, you share the folder. Drop it in a shared Google Drive, OneDrive, Dropbox, or whatever your team already uses. The person receiving it adds the folder to their Cowork skills directory. The Skill is immediately available.
No installation. No IT involvement. If your analyst can copy a folder, they can use the Skill.
Building a portfolio Skills library
Once you have more than two or three Skills, organize them. The structure below works for asset management teams with multiple properties or multiple AMs.
When you share a Skill, include the sample file you tested it with. The next person who picks it up can run it against the sample to confirm it's working before they trust it on live data. This is the single highest-value addition to a shared Skill. It turns "should work" into "I just saw it work."
When to build new vs. refine existing
As the library grows, you'll face a recurring decision: tweak an existing Skill or build a new one. The answer:
- Same input, slightly different output: refine the existing Skill. Add a column, change the sort, add a tier.
- Different input, or substantively different logic: build a new Skill. Don't make one Skill carry two workflows.
Trying to make one Skill handle many variations produces instructions that are hard to read and prone to inconsistent output. Simple, focused Skills outperform ambitious multi-purpose ones every time.
Scheduling
Cowork can run Skills on a schedule. The most useful scheduled tasks for an AM team:
| Task | Cadence | Output |
|---|---|---|
| Owner dashboard build | Day after owner package drops | Excel KPI dashboard in your review queue |
| Variance memo draft | Same morning | First-pass narrative in your inbox |
| Rent comp survey | First Monday of month | Excel comp file across your competitor set |
| Expiring lease alert | Every Monday | List of leases expiring in next 60 days + renewal status |
Standards for what gets added to the team library
A team library is only as good as the worst Skill in it. Before any Skill goes into the shared folder, it should meet three standards:
- It's been run successfully against three different inputs by the author.
- It includes a sample input file and the expected output for that sample.
- The SKILL.md names the author and the last-updated date so changes can be traced.
Six months of building one Skill per month gets you to a library of six. That doesn't sound like much. It's enough to handle nearly all the repetitive analytical work in a small portfolio. The leverage shows up in what your team does with the time it gets back, not in how impressive the library looks.
AI ROI calculator
Estimate how much time AI is actually saving across your portfolio, and what that time is worth at your team's loaded cost.
Pick the tasks your team has automated (or plans to). The calculator estimates time saved per month, the value of that time at your team's loaded hourly rate, and the payback period on the $20/month per-seat cost of the paid tools.
Your inputs
Tasks you've automated
Check each task your team uses AI for. Adjust the hours/month per seat if your reality differs from the default.
Estimated impact
The "value of time saved" is theoretical recovered capacity. Whether it shows up on your P&L depends entirely on what your team does with the time. If it goes to higher-value work (more properties, deeper analysis, better decisions), the ROI is real. If it disappears into longer lunches, the ROI is zero. The tools don't make that decision. You do.
Prompt builder
Fill in the five fields. Get a structured prompt out the bottom. Copy it, paste it into ChatGPT or Claude, and you're done.
This is the five-part structure from Section 4, made fillable. Use it the first few times you write a prompt for a new task. Once you've internalized the structure, you won't need the tool, but it's a useful crutch while the habit forms.
Your prompt
Updates as you type. Click Copy when ready.
The material field is where most prompts fall apart. The more specific and concrete the input data, the more specific and concrete the output. Vague material in, vague output out. Every time.
Skill planner
A fillable worksheet for the Input / Process / Output framework. Work through it before you write a single line of SKILL.md. The output is a ready-to-send brief that Claude can turn into the actual file.
Most failed Skills failed at the planning stage. The author skipped the thinking and went straight to instructions. This worksheet forces the thinking. When you're done, paste the generated brief into Claude with the prompt from Section 9 and you'll have a working draft.
Identity
Input
Process
Output
Your Skill brief
Updates as you type. Copy and paste into Claude with the "Have Claude draft your SKILL.md" prompt from Section 9.
Pick one workflow. Plan it with this tool. Have Claude write the SKILL.md. Test it against last month's actual file. Refine. Use it for a month. Then, and only then, pick the second workflow. Depth before breadth. Always.