Built world
The deal is not waiting on a model. It is waiting on a complete file.
Leasing, acquisitions, dispositions, and closings still run through email threads, shared folders, and the person who knows which version of the rent roll is true. Copilot in the inbox does not close that gap.
How I see it
Real estate deals still wait on an incomplete packet
South Florida real estate is a coordination business. Brokers, asset managers, lenders, counsel, and operators all touch the same packet. Time sits in gathering, interpreting, and chasing, not in the moment someone walks a property.
AI is useful on the packet: extracting terms, assembling a deal room, flagging missing items, drafting the next follow-up, and writing status back to the system of record. It is not useful as a 'smart building' story that never touches the operating calendar.
The first workflow should be frequent enough to compound: a lease file, a due-diligence checklist, a vendor packet, or a recurring reporting pack. A trophy acquisition that happens twice a year will not pay for the system.
Keep humans on price, relationship, and risk acceptance. Move the assembly work. That is operating leverage in a market that already has enough meetings.
Common mistakes
What teams usually get wrong.
Starting with a property chatbot
A resident or investor Q&A bot is visible. The expensive work is the file that still is not complete on Friday.
Treating every deal as unique
The asset is unique. The packet steps usually are not. If you cannot see the repeatable path, you have not mapped it.
Leaving the CRM as a graveyard
If the new path does not write back, people will keep the email thread as the system of record.
A useful diagnostic
Five questions before you fund the work.
Which packet runs every week: leasing, closing, reporting, or vendor onboarding?
Start there. Do not start with a one-off acquisition.How many people touch a completed file, and how much of that time is chase?
Chase time is usually the leverage.What does a stalled closing or vacant day cost?
If that number is material, cycle time is the metric, not 'AI adoption.'Is there one owner who can change how the packet is assembled?
A deal team with no owner will keep every unofficial path.Which terms must a person still accept?
Price, concessions, and legal risk stay human. Assembly should not.
Economic model
Packet delay costdays the file sits incomplete × carrying cost, vacancy, or labor sitting on the critical path
If delay cost is small, pick a higher-volume file. Real estate AI should move a number an operator already watches.
Three credible paths
How far should you go?
Do not force one solution. Choose the path the economics, the risk, and the organization can support.
Improve the work you already have
Keep the process mostly intact and use AI on the bottlenecks that create delay, rework, or follow-up.
The workflow is already sound and a few steps create most of the friction.
Gains are usually incremental. The operating economics do not change much.
Redesign the workflow around AI
Question every handoff, queue, and duplicate step, then rebuild the process around what AI can now do.
The process grew over years and coordination now costs more than the work itself.
Requires process change, clearer ownership, and a willingness to retire old steps.
Put an agent on a high-value outcome
Give an agent responsibility for one valuable result across systems, with humans at the control points that require judgment, authority, or risk acceptance.
The workflow is high-value, variable, multi-step, and worth engineering for production.
Needs stronger architecture, evaluation, controls, and monitoring. This is not a prompt project.
When this is the wrong next step
Do not start with a sector program.
- The only request is a marketing site assistant.
- There is no repeatable packet, only relationship work.
- Counsel will not allow documents in any approved tool.
- Nobody can say which version of the file is authoritative.
A useful next step
Bring one expensive workflow from this industry.
We guide the implementation, go deep on the technical path, and stay hands-on through operations — or tell you when a simpler answer is better.
Discuss an AI opportunity