AI Keynote Speaker for Leadership Teams Who Want Practical, Not Hype

The center of every talk I give is live demonstration on the audience's real work, not canned examples from a fictional startup. Before the event, the scoping process surfaces the documents your people actually touch—a board pre-read, a difficult customer email, a forty-page contract, a meeting-notes mess—and I rebuild them in anonymized form. On stage, the room watches the full working loop in real time: the brief an executive would give a new hire, the first draft the tool returns, and the pushback that turns a generic answer into a usable one. Live demos carry a small risk, and I take the risk deliberately, because when a tool stumbles the room learns how to correct it. That unscripted moment usually teaches more than any polished slide, and it is the moment audiences remember on Monday morning.

The second segment of the keynote is the guardrails conversation, and it is the part most AI talks skip entirely. Non-technical leaders do not need a legal seminar; leaders need a working answer to one question—what can we safely put into these tools, and what stays out? I give the room the same rule of thumb my coaching clients use: treat anything you paste as shared with an outside vendor, and get your company's written policy straight before sensitive material flows. The guardrails segment covers the difference between consumer and business plans in plain English (see Anthropic's commercial terms for one vendor's business-side terms), the categories that never belong in a prompt, and the shape of a one-page usage policy a leadership team can actually adopt. Leaders consistently tell me this fifteen minutes is what turned their team's private anxiety into a shared, workable set of rules.

Every keynote ends with a concrete 30-day fluency path, because inspiration fades by Friday and a plan survives. The path is the same arc I use with one-on-one coaching clients, compressed for a room: in week one, each leader picks one real task they already owe someone and briefs the tool the way they would brief a person; in weeks two and three, the leaders run that task and one more, pushing back on first drafts instead of accepting them; by day thirty, each person has saved two or three prompts proven on their own work. Attendees receive the path as a one-page handout they can pin to a monitor. The handout matters more than the applause. A room that leaves with a plan and a page of working prompts is a room that is still using these tools a quarter later.

The talk is built for rooms of roughly twenty to two hundred leaders in industries where AI is not the product—manufacturing, distribution, construction, logistics, professional services, healthcare administration, regional banking, and similar businesses. Three settings fit especially well. A leadership offsite, where the executive team needs a shared, honest picture of what these tools can do before anyone sets strategy. An industry association meeting, where owners want to know what peers are actually doing rather than what the headlines claim. And a company all-hands, where the goal is to replace quiet anxiety about AI with a practical first step every employee can take. The common thread is a non-technical audience whose time is scarce and whose skepticism is earned.

Just as honestly: this keynote is not for every room. A deeply technical engineering audience looking for model architecture will find the talk too plain, and a room expecting a futurist spectacle will find it too practical. The event organizers who get the most from a booking are the ones who want their people working differently the following week—not entertained for an hour. If the audience is a mixed one, with a few technical staff among mostly non-technical leaders, the talk still lands; the demonstrations are real enough that the engineers respect them and plain enough that everyone else follows them.

I am a teacher, not a futurist, and the talk is built like a lesson rather than a performance. There is no AI coach bot demo, no slideshow of predictions, no promise that everything changes by Tuesday. The measure I hold myself to is what the room does the following week: whether the CFO actually runs the board-prep prompt she watched on stage, whether the owner who was quietly anxious now has the outside-vendor rule and a policy conversation scheduled. Audiences get honesty about limits as part of the show—the tools fail on stage sometimes, and the room learns the correction, which is the actual skill. Calm, practical, and slightly unglamorous is the register, because that is what real adoption looks like inside a company.

The credibility behind the talk is teaching reps, not stage credits. I spend my working weeks coaching founders and executives on these tools, on their real documents, and the keynote is that same material scaled to a room. The examples stay current because they come from live practice, and the answers to audience questions come from having watched many smart leaders hit the same walls your audience will hit. You will not hear invented statistics or borrowed case studies from this stage—if I do not know something, I say so, because a room of experienced leaders can tell the difference instantly.

If you are planning a leadership offsite, an association meeting, or a company all-hands and the descriptions above sound like your room, the booking link below is the whole next step—send the date window and the audience, and we will schedule the scoping call. If you are not sure whether your event fits, send the note anyway. An honest no is part of the service, and I would rather give it early than waste your planning cycle.

If your organization needs more than an hour on stage—training for the whole team, or one-on-one work with individual executives—the related pages below cover those paths, and the scoping call can point you to the right one either way.