What should be in a keynote book of topics for real estate and AI conferences?

A keynote book of topics is the document conference programmers use to decide whether your material fits their event. It's not a bio, not a sizzle reel, and not a list of credentials. It's a menu of talks you can actually deliver, organized so a busy programmer can match you to their audience in under three minutes. For speakers in real estate and AI-adjacent markets, the bar for that document is higher than it used to be.

What a keynote book of topics actually is

Most speakers conflate this with a one-sheet or a speaker page. They're different documents for different moments in the booking process.

A one-sheet is a quick-look credential summary. A programmer skims it to decide if you're worth a longer conversation.

A keynote book of topics is what closes the conversation. It gives the programmer three to six fully described talks, each with a title, a short description, a target audience, and three to five specific takeaways the audience will leave with. It's a purchase menu, not a portfolio.

The strongest books I've seen, and the one I've built for my own speaking work, organize the topics around a coherent through-line. The programmer should be able to read three talk titles and immediately understand what territory the speaker owns. "AI-operated marketing for real estate operators" is a territory. "Motivation, marketing, and mindset" is not.

Why the real estate conference market is picky right now

Real estate conferences have been burned by keynote speakers who "do AI" the same way they used to "do social media" — with broad enthusiasm, no operational detail, and slides that age badly in six months.

The pattern I see most often: a programmer books someone with impressive credentials, the audience sits through 45 minutes of "AI will change everything," and the feedback forms say the same thing every time. Too abstract. Not practical. Didn't tell us what to actually do.

That feedback has shifted what programmers in this market are actively looking for. They want speakers who have shipped AI in a real practice. They want talks where the audience can leave and do something specific that week. They want material that ages reasonably well, which means it's built around principles and workflows rather than specific tool versions that may be obsolete by conference day.

The keynote book of topics needs to communicate all of that before the programmer ever gets on a call with you.

How to structure each topic in the book

Each talk entry should answer four questions for the programmer, in roughly this order.

What's the talk about, in plain language. One sentence. Not a tagline, not a clever phrase. "This talk is for real estate team leaders who want to understand how AI fits into their lead generation and marketing stack without buying a new tech subscription they won't use."

Who specifically is in the room. "Managing brokers and team leads" is more useful than "real estate professionals." Programmers are assembling a conference for a specific audience. If your description matches their attendee list, you're easier to book.

What the audience leaves with. Three to five concrete takeaways, stated as things the audience can actually do. "A framework for evaluating AI tools against your current workflow" is a takeaway. "A new perspective on the future of real estate" is not.

What formats and lengths it works in. If the talk runs as a 20-minute general session, a 45-minute breakout, and a 90-minute workshop, say that. Programmers have scheduling constraints they don't always explain upfront. Removing that friction closes more bookings.

The topics that tend to book in the AI and real estate space

I'll be direct about what I've observed from conversations with programmers and from tracking what sessions fill at conferences focused on real estate operations and SMB marketing.

Topics that book consistently share a few traits. They name a specific pain the audience recognizes. They promise operational takeaways, not just perspective shifts. They're attached to a speaker who demonstrably works in the space.

In practice, the topics with staying power in this market right now tend to fall into three categories. First, AI adoption for practitioners who aren't technical. Programmers need someone who can walk a room of realtors through AI workflows without the audience feeling talked down to or overwhelmed. Second, marketing system-building for lean teams. This resonates with realtors and brokerage operators who are under-resourced and tired of paying for things that require a full-time person to maintain. Third, the intersection of human judgment and automated systems. This is the nuanced talk that separates practitioners from enthusiasts. It's not "AI is amazing" and it's not "AI is dangerous." It's "here's where I use automation and here's where I don't, and here's how I make that call."

Topics that tend not to book in this market: anything that could have been written without recent field experience, anything titled around buzzwords the audience already distrusts, anything that sounds like it belongs at a general business conference rather than this specific industry.

The mistake most speakers make with their topic book

They write the book for themselves, not for the programmer.

A topic book full of talk titles that describe what the speaker finds interesting is less useful than a topic book organized around problems the programmer's audience is actively trying to solve. These aren't always the same thing.

The fix is to read the conference's past session list before you submit your book. Look at what topics they've programmed, what sessions had full rooms according to public post-conference coverage, and what their audience has publicly asked about online. Then frame your existing material through that lens. The content doesn't change. The framing does.

The other common mistake is treating the topic book as a permanent document. In a field like AI, a topic book that's 18 months old reads as stale. Programmers notice when your material doesn't reflect current conditions. Update it at least once a year, and flag when you've updated it.

What I include in my own topic book

My topic book covers the territory I work in directly: AI-operated marketing systems, the practitioner's view of AI adoption in real estate, and building marketing infrastructure for lean teams. Each talk connects to work I'm doing at Monstera Real Estate and in consulting engagements, which means the material stays current because my practice is current.

I organize the book so a programmer can see three things quickly. That I work in real estate actively, not historically. That my AI material is operational, not theoretical. And that the talks scale to different conference formats, from a tight keynote slot to a longer working session.

If you're building your own topic book, those three things are a reasonable north star regardless of your specific territory.

The book doesn't close every programmer. But it shortens the conversation with the right ones, and it stops the wrong conversations before they start. That's what a functional topic book is supposed to do.

---

FAQ

What is a keynote book of topics? A keynote book of topics is a curated menu of talks a speaker offers to conference programmers and event organizers. It typically lists three to six prepared talks, each with a title, a short description, the intended audience, and key takeaways. It's a sales document, not a bio.

How many topics should a speaker include in their keynote book? Three to six is the practical range. Fewer than three looks underprepared. More than six signals that the speaker hasn't found a niche. The strongest books organize topics into a coherent through-line so the programmer can see that the speaker owns a specific territory.

What makes a keynote topic book work for real estate conferences? Real estate programmers are looking for speakers who have practiced in the industry, not just observed it. Topics that connect directly to operational challenges realtors face tend to book more consistently than broad motivational topics.

Should a keynote book of topics include session formats? Yes. Conference programmers often need to fit a speaker into a 20-minute breakout, a 45-minute general session, or a 90-minute workshop. Showing that your material scales across formats reduces friction for the buyer. Note which topics work at which lengths.

What's the difference between a speaker one-sheet and a keynote book of topics? A one-sheet is a single-page summary of the speaker, used for quick evaluation. A keynote book of topics is longer and deeper, focused on the content menu rather than the speaker's credentials. Programmers use the one-sheet to shortlist and the topic book to book.

How often should a speaker update their keynote book of topics? At minimum once a year, and any time a major shift happens in your topic area. AI moves fast enough that a topic book from 18 months ago can read as dated. Programmers notice when your material doesn't reflect current conditions in the field.

---

Emma Pace — strategic marketing consultant, AI coach for realtors, keynote speaker. Realtor at Monstera Real Estate. Builds AI-operated marketing systems at emmapace.ca.