When should you use it?
- You review a large number of listings each week for a defined set of buyers
- Offering memorandums and rent rolls arrive as PDFs
Not for: Valuations or pricing advice to clients; the poster found AI weak there and verifies everything
What do you need, and what do you get?
You need
- Your buyers' criteria (location, unit count, price, value-add vs stabilized)
- New listings with offering memorandums and rent rolls
- Your own comp data (the poster keeps it in a sheet)
You get
- A short daily list of matches with the reason each fits
- Key rent roll figures: units, average rent, occupancy, loss to lease
- A rough first-pass pro forma clearly labeled as unverified
How does it work, step by step?
- Write buyer criteria as rulesTurn each buyer's wants into checkable rules: ranges, must-haves and deal-breakers.
- Extract from the documentsHave it read each listing and rent roll into a fixed set of fields.
- Score and shortlistUse our prompt to compare each listing to every buyer and keep only real matches.
- Verify before you callCheck figures against the source documents and your own comps before contacting a buyer.
The prompt
Our own prompt, inspired by u/tayloravakian_LA on r/CommercialRealEstate and written to work in ChatGPT, Claude, n8n and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Screen today's listings for my buyers. Buyer criteria: {buyer_criteria} Listings with offering memorandum text and rent rolls: {listings} 1. For each listing, extract: address, price, units, unit mix, average in-place rent, occupancy, and any value-add notes. Cite the page or table for each number. 2. Check each listing against each buyer. List only real matches with the reasons; for near misses, name the one criterion that failed. 3. For matches, sketch a first-pass pro forma (income, expenses as stated, NOI, cap rate at asking) labeled UNVERIFIED. 4. Flag inconsistencies, such as unit totals that don't add up. No valuation opinions.
Inspired by u/tayloravakian_LA on r/CommercialRealEstate: What I've learned using AI as a multifamily broker. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Rent rolls are messy. Check unit counts and totals against the offering memorandum.
- Pro formas from AI miss local details, such as building condition or neighborhood changes. The poster still does valuations himself.
Our take
This is one of the more credible AI posts from a broker because it's as clear about failures as wins. The win is screening: hundreds of listings a week, each with a rent roll PDF, filtered against what specific buyers want. That's a matching problem an assistant handles well, as long as the criteria are written as rules and the extracted numbers are checked. The broker says the system surfaced three deals he would have missed, and that first-pass underwriting dropped from hours to minutes, though he still verifies everything. He's equally direct that valuations, generic outreach and negotiation didn't work, which is a useful boundary for anyone copying this. Our prompt keeps the AI on extraction and matching, labels any pro forma as unverified, and cites the page each number came from. In our dry run on three made-up offering summaries with rent rolls and two buyer profiles, it matched one listing to one buyer, rejected another for unit count, and flagged a rent roll whose unit total didn't match the summary.
Where the time goes back: Reviewing every new listing by hand turns into reading a short list of matches each morning.
FAQ
What did the broker say AI was bad at?
Do I need custom software?
Source and credit
Inspired by u/tayloravakian_LA on r/CommercialRealEstate. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- What I've learned using AI as a multifamily broker
- Creator
- u/tayloravakian_LA on r/CommercialRealEstate
- Published on
- Original date
- Aug 27, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Matched against rules, cited sources, and caught the planted inconsistency.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.