The adoption numbers and the outcome numbers tell two different stories. Colliers reports that roughly 92% of CRE firms have piloted AI while only about 5% say they've achieved their AI goals — a spread Colliers calls the AI productivity gap. PwC and ULI's Emerging Trends in Real Estate finds the same shape: AI a stated strategic priority at over 90% of leading firms, active pilots at well over half, embedded results far rarer.
Why do CRE AI pilots stall?
Because most pilots are beside the workflow, not in it:
- The pilot summarizes documents into… another document, which someone re-keys into the tracker.
- The output has no review step, so nobody trusts it enough to act on.
- The pilot lives with one champion; when their attention moves, it dies.
None of these are model failures. They're integration and governance failures.
What separates the 5% that get value?
The pattern across the firms that graduate from pilots is consistent:
- A system of record exists first. AI output lands as structured data in the operating system, not prose in a memo.
- Governed autonomy. Suggestions are staged for human approval — which is precisely what makes teams comfortable using them. (Propose, never commit.)
- A narrow, daily wedge. One workflow that runs every week — broker updates, lease abstraction, deal capture — instead of a moonshot.
- An owner in operations, not in innovation.
Is "agentic AI" going to change this?
The industry expects autonomous multi-step agents to reach mainstream use in 2026–27, and they will genuinely widen what's automatable. But agents raise the stakes on exactly the thing pilots already lack: governance. An agent that can execute a workflow can execute a mistake at workflow speed. The bridge across the productivity gap isn't a stronger model — it's the boring machinery of staging, review, and audit that lets a firm say yes to automation without handing over the keys.
What should a mid-size firm actually do this quarter?
- Pick the one workflow the team does weekly and hates (broker updates is a common winner).
- Make sure its data lands somewhere structured — fix the record before the robot.
- Require review-before-commit on anything AI writes.
- Measure one number (hours to process, days to follow up) before and after.
That's how a pilot becomes an operation — and how you end up in the 5%.