Most lists of AI use cases in commercial real estate are written to sell you something. The valuations feed a data subscription, the lead scoring feeds a CRM, the generative copy feeds a marketing suite, and every entry conveniently ends at a checkout page. A 10-person brokerage does not need a shopping list. It needs a map of where AI actually touches its week, sorted by the work rather than the product, with an honest note on which cases a trained person can run today and which require software the firm has to buy or build. That gap between activity and usefulness is wide: NAR’s 2025 Technology Survey of 49,233 members found 68% now use AI tools, yet only 17% report a significant positive impact on their business. This field guide is built to close that gap at a small firm.
One piece of orientation before the guide. The point of cataloging use cases is not to adopt all of them; it is to recognize the two or three that fit your firm and get a team fluent enough to run them. The full 90-day arc of building that fluency sits in our CRE AI training playbook, and the broader argument for why a small shop can out-operate a much larger competitor runs through the small-firm manifesto. This piece is the inventory those two draw on: what the work actually looks like, function by function.
How to Read This Field Guide
Every use case below carries three tags, because a capability you cannot act on is not a use case. The first tag answers the question that actually decides your budget: does this need a tool you subscribe to or build, or can a trained person do it with a general assistant like ChatGPT, Claude, Gemini, or Microsoft Copilot? Most firms discover that a surprising share of their week falls in the second column, which is the cheapest and fastest place to start.
The second tag is data safety. A small brokerage handles NDAs, unexecuted terms, and client financials, so each case is marked as public-safe (works fine on listings, comps, and hypotheticals) or confidential (touches data that should never land in a personal free account). The third tag is effort-to-value: whether the case pays off in week one or belongs to a later automation stage.
This matters because the failure mode at a small firm is not picking a bad tool. It is buying access to five of them and building capability in none. JLL, surveying more than 1,500 CRE decision-makers, found 88% of firms piloting AI but only 5% hitting their program goals. Read the right way, this guide helps you hunt for the few cases worth doing well, not collect all of them.
The Inbox and Client Communication
The inbox is where most small brokerages should start, because the work is high-volume, text-based, and mostly public-safe. Drafting a first-pass reply to a tenant inquiry, turning three bullet points into a polished prospecting email, or rewriting a terse note into something a client will actually respond to are all training, public-safe, week-one cases. A broker who can describe the tone and the ask gets a usable draft in seconds and edits from there.
Two adjacent cases sit one notch up. Summarizing a long email thread before a call, and drafting a call recap or follow-up from your own notes, are equally training-based but often touch deal specifics, so they are confidential and belong in a business-tier account with training data turned off. None of these require special software. They require a person who knows how to ask.
Where a tool earns its place is volume and integration. Microsoft Copilot inside Outlook can draft and summarize without your data leaving the Microsoft tenant, which suits an Office-based shop. A dedicated CRM such as HubSpot or Apto adds AI to logging and sequencing. Those are worthwhile once the manual version is a proven habit, not before.
Listing and Marketing Production
Marketing is the most over-sold function in every AI listicle, and also one of the most genuinely useful for a lean team. Drafting a property flyer narrative, writing the long-form description for an offering memorandum, generating three subject-line variants for a blast, and repurposing one write-up into a LinkedIn post are all training, public-safe, week-one cases. Listing copy is public by definition, which makes it the safest possible sandbox for a team that is still learning.
The tool tier here is real and specific. Buildout and Crexi build generative drafting into the listing and OM workflow, so the copy is produced where the deal already lives rather than in a separate window. That integration is the value, not the writing itself, which a trained person can do in a general assistant for the cost of the subscription they already have.
One caution belongs in this section. AI-generated marketing copy is confident and fluent, which means an untrained user will ship an error in a property’s square footage or zoning without noticing. The skill that makes this case safe is knowing what to verify, which is exactly the difference training builds and a tool alone does not.
Deal Screening and Underwriting Support
Screening is where a small team feels most outgunned by institutional competitors, and where careful AI use closes the most ground. Turning a broker’s marketing package into a one-page screening summary, drafting the assumptions section of an underwriting memo, and stress-testing a set of inputs by asking an assistant to argue the bear case are training cases that a fluent analyst runs today. Because they involve deal economics, they are confidential and belong in a business-tier tool.
The line to hold is that the assistant supports judgment, it does not supply it. An AI can restate a rent roll and flag that a lease expires inside the hold period; it cannot decide whether that risk is priced correctly. Used as a fast first reader, it lets a two-person deal team screen more opportunities without adding headcount, which is the actual competitive gain.
The tool tier is genuine but heavier. Platforms like Dealpath organize pipeline and diligence, and data providers such as CoStar and Placer.ai supply the comps and foot-traffic inputs a model needs. These are tool, confidential, later-stage cases: valuable, but a spend you make after the manual screening habit proves which inputs you actually rely on.
Lease and Document Review
Document review is the use case that most rewards a firm running on PDFs. Asking an assistant to pull the key economic terms out of a lease, list the options and escalations, or compare two versions of a clause is a training, confidential, high-value case that turns an hour of squinting into a few minutes of checking. Small firms without a paralegal feel this one immediately.
The honesty this section demands is about accuracy. A general assistant reading a single lease you paste in is fast but fallible, so a trained user treats every extracted term as a draft to verify against the source, never a final answer. That verification habit is the whole skill; without it the case is a liability, not an asset.
The tool tier exists for scale. Purpose-built lease-abstraction and document-intelligence products handle stacks of files with audit trails and confidence flags that a general chat window does not. For a firm abstracting the occasional lease, a trained person is enough. For one processing a portfolio, the software pays for itself, which is a build-or-buy decision the firm-wide adoption sequence is designed to time correctly.
Market Research and Prospecting
Research is a strong training, public-safe category that a lean team can exploit immediately. Compiling a submarket overview, drafting talking points on a tenant’s industry before a pitch, and summarizing a long market report into three takeaways are all week-one cases that run on public information and a clear prompt. The output is a starting brief, not a citable source, so a fluent user checks any figure that will end up in front of a client.
A specific caution: a general assistant will sometimes invent a plausible statistic. The trained response is to treat every number it produces as unverified until you have seen it in an actual source. This is a fluency problem, not a tool problem, which is why the same case is a time-saver for a trained team and a credibility risk for an untrained one.
The tool tier is your existing data stack. CoStar, Crexi, and firms like HelloData and Placer.ai are where verified numbers live; the assistant’s job is to help you frame and summarize, not to replace the subscription that holds the ground truth.
The Back Office
The back office is quieter but it is where standardized, repeating work makes AI most durable. Drafting a CAM reconciliation explainer for a tenant, turning a rent roll into a plain-language summary, and producing a first draft of an investor update from your own figures are training, confidential cases a fluent ops person runs with a business-tier account. The inputs are sensitive, so the account discipline matters more here than anywhere else.
This is also the function where the jump from prompting to real automation makes the most sense, and the only place a small firm should consider a custom build. When a report is high-volume and fully standardized, hand-prompting it one at a time becomes the bottleneck, and a purpose-built workflow, or an off-the-shelf platform for reporting and reconciliations, starts to earn its cost. That is a tool or build, later-stage decision. Until then, the back office runs on the same fluency as everything else: a trained person and a clear instruction.
Which Use Cases to Start With
Start with the inbox and listing copy, in that order. Both are high-volume, both are mostly public-safe, and both let the team build the verify-everything reflex on work where a mistake is cheap. A firm that gets those two into daily use has proven the habit and can extend the same skill into deal screening and document review, where the payoff is larger and the confidentiality stakes are higher.
Resist the urge to buy a tool for each case on this list. The through-line of every section is that most of these are unlocked by a trained person with one general assistant, not by five subscriptions. The specialized platforms — Buildout, Dealpath, CoStar, a document-intelligence product — are real, but they are decisions you make after fluency has shown you which workflow justifies the spend. The move that makes this guide worth anything is picking the two or three cases that fit your firm and getting the team genuinely fluent in them, rather than admiring the whole catalog and adopting none of it.
Frequently Asked Questions
What are the best AI use cases for a small brokerage?
The best starting use cases are drafting and summarizing in the inbox, and producing listing and marketing copy. Both are high-volume, both work safely on public information, and both let a team build the habit of checking AI output on low-stakes work. From there, the highest-value cases are lease and document review and deal-screening support, which save the most time but touch confidential data and require a business-tier tool and a trained user. The best use case for any given firm is whichever high-cost workflow its people run most often, which is why mapping the week matters more than copying a generic list.
Which AI use cases need a paid tool versus just training?
Most day-to-day text work needs only a trained person and one general assistant: drafting emails, writing listing copy, summarizing documents, and building research briefs all run in ChatGPT, Claude, Gemini, or Microsoft Copilot. A dedicated tool earns its cost when volume or integration is the constraint — abstracting a portfolio of leases, generating copy inside the listing platform, or organizing pipeline diligence. The practical rule is to treat training as the default and a purpose-built product as the exception you justify after the manual version is a proven habit.
Is it safe to use AI on confidential deal data?
It can be, with two rules. First, use the business tier of a major assistant, which offers settings that keep your inputs out of model training, rather than a personal free login. Second, write a one-page policy stating which tools are approved and what data may be pasted: public listings and hypotheticals are generally fine, while client names tied to financials, unexecuted terms, and anything under NDA need the protected account or stay out entirely. Confirm the current terms for whichever tool you approve, since these settings change.
Do I need different tools for each use case?
No, and treating each use case as a separate purchase is the most common way small firms waste money on AI. One general assistant, run by a trained team, covers the large majority of the cases in this guide across every function. Specialized platforms are worth adding only where a specific high-volume workflow justifies one, such as document-heavy lease abstraction or listing production inside a marketing suite. The durable investment is the skill, which transfers across tools; the tool itself is replaceable.
How long before these use cases save real time?
The text-drafting and summarizing cases save time in the first week, because a person who can describe a task gets a usable draft immediately. The larger gains, in document review and deal screening, arrive over a few weeks as the team learns which tasks the assistant handles well and builds the reflex of verifying its output. Anyone promising firm-wide transformation from a single afternoon is selling attendance, not capability; real time savings track the habit, not the tool purchase.
What does it cost to get a small team using these?
The lightest path is a business-tier assistant subscription, which is a modest per-seat monthly cost, plus the time to get the team fluent. As a market orientation, structured training in AI fluency for a small team generally runs from the low thousands to the low tens of thousands of dollars. Custom workflow automation, the back-office endgame, is typically a low-six-figure engagement depending on scope, though an off-the-shelf proptech subscription can be far less. The sequencing protects the spend, because you only reach the expensive options after you know which workflow warrants them.
Which use cases should a brokerage avoid for now?
Avoid anything that puts unverified AI output directly in front of a client or into a binding document without a human check — an unread market statistic in a pitch, an unchecked lease term in a memo, or auto-sent client email. These are not bad use cases; they are cases that require a trained user, and running them untrained is where firms create the errors that scare them off AI for a year. Avoid, too, buying a specialized platform before the manual version of that workflow is a proven habit.
Can AI replace a broker or analyst on my team?
No. Every use case in this guide supports a person’s judgment rather than substituting for it: the assistant drafts, summarizes, and flags, while a broker or analyst decides what the deal means and what to do about it. The competitive gain for a small firm is throughput — screening more deals, turning documents around faster, keeping communication tight — with the same headcount. A trained team plus AI out-produces a larger untrained one, which is the advantage a lean shop is actually buying.
Where to Start
The first move is not adopting a use case; it is mapping where your firm’s hours actually go and which of the cases above would genuinely change your week. That map is exactly what a free AI-readiness assessment produces: a working session that identifies your highest-cost workflows, flags the confidential-data rules you need before anyone starts, and tells you honestly whether you need a full workshop, a lighter course, or just clearer rules for the tools your team already has. Book a free AI-readiness assessment and you will leave with a shortlist of the two or three use cases worth doing well at your firm, and a clear read on which ones pay off first.
Arthur Wandzel
