Introductions & Landscape
Who's in the room, what we're each wrestling with, and where this is heading.
The kickoff. We mapped who's adopting AI in their CRE workflows, which tools show up most, and what concerns members bring to the table — from data security to client comms to the hype-vs-reality gap.
Foundations of AI for CRE Professionals
The conceptual grounding — what these models actually do, and don't.
Karan walked the group through how large language models work, what they're good at, and where the failure modes show up in CRE workflows specifically. Heavy on examples, light on hype.
The AI Advantage in CRE: What Smart Leaders Are Learning
Leadership patterns — who's actually moving, and what they're doing differently.
A look at the firms and individuals quietly building a real edge with AI — what their adoption playbooks look like, where they're focusing first, and the cultural shifts that separate experimentation from operational change.
Stop Copying & Pasting Your Way Through the Day — Here's How to Automate It
Where your time actually goes, and how to get it back with automation + AI.
Kaitlyn Study (South Street & Co.) on cutting the small, repetitive work that eats your day — building a digital assistant before you hire, plus real automation examples you can copy.
You Already Have Copilot: Let's Make It Earn Its Keep
Practical AI for the way CRE actually works.
Ashley Pyle (GadellNet) on getting real hours back from Microsoft 365 Copilot — Basic vs Premium, the "racetrack not race car" mindset, Frame · Focus · Finish in Copilot, and a live lease workflow across Word, Excel, and Teams. Leave-behind: the prompt pack, demo kits, and the AI Opportunity Worksheet.
From Data Dump to Deal Flow
Building a prospect list you'll actually work.
Ivy Marguerite ran it live on a member directory: check the platform's terms before you touch it, filter inside the platform rather than in the prompt, research every company across four layers with a source on each one, then score Fit and Reach and work the list top down. Recap, recording, all six prompts, the build sheet, and the agent setup guide are all posted.
- A 60-second permission check you can run on any page before you use it.
- Six prompts to copy, with your own criteria swapped in.
- An interactive build sheet that scores and sorts your list for you.
Build Your Own AI Chief of Staff
Stop re-explaining yourself to your AI every morning.
Michelle Hamilton introduced hers, live, by name. George runs on Claude Cowork, reads her calendar, email, Drive, Slack and meeting transcripts, and hands her six lines every morning: what is on the calendar, what cannot slip, what will slip if she does not touch it, who has waited longest, the one decision only she can make, and what got handled overnight. He drafts. He never sends. The recording is posted, along with the seven-step build, the two portable Markdown files, the four Ds of governance, seven copy-ready prompts, and the full sixteen-question FAQ Michelle wrote afterwards.
- Two files that belong to you, portable between Claude, ChatGPT and Copilot.
- Seven prompts covering the whole build, from first connection test to the Friday self-review.
- Sixteen answered questions, every one sourced to current product documentation.
AI Without the Anxiety
Security, safety, and terminology for CRE decision-makers.
Most AI conversations start with tools. This one starts with the questions that should come first: what the words actually mean, who can see your data, and how much to trust what comes back.
Anthony Peters, IT Systems Manager at BranchPattern, walks through the working vocabulary of AI in plain language: tokens, models, context windows, grounding, hallucinations, agents, permissions, and prompt injection. Then he separates two questions that often get blurred together. Security asks who can access your data and where it can go. Safety asks whether an output is reliable enough for what you’re about to do with it. Both matter, for different reasons.
The session also looks at the three paths firms tend to take with AI adoption (technology-first, liability-first, and people-first) and what changes when you stop using AI as a tool and start delegating work to it. The work moves faster. The accountability doesn’t move at all.
You’ll leave with:
- A shared vocabulary, so you can follow, and push back in, conversations with IT, vendors, and leadership.
- The “fenced yard”: what actually defines the boundary around your firm’s data (account, contract, access, connections) and why that boundary isn’t a guarantee.
- A permissions reality check: AI can surface anything you already have access to, including files you forgot you could open. You’ll get three checks to run before any team pilot.
- A delegation mindset: define the result, provide the context, verify what comes back.
Presenter
Anthony Peters
IT Systems Manager · BranchPattern