Skip to content

Speaking

Talks on building AI systems that survive reality

I speak to engineering teams, leadership offsites, and conferences about designing intelligence infrastructure that preserves human judgment at enterprise scale.

Topics I speak on

Where I add the most

Four themes I have thought about long enough to be useful on. Each can be shaped for a technical audience, a leadership audience, or the harder mixed room.

Enterprise AI architecture

What it takes to build generative and agentic systems that survive real complexity - compliance, scale, latency, and the cost of being wrong. The patterns that hold, and the ones that quietly fail in production.

Context intelligence

Why an organization's context is its most valuable and most fragile asset, and how to treat it as durable, governed infrastructure rather than disposable conversation.

Decision architecture

Designing how organizations decide - the flow of context, authority, and accountability through the systems that produce judgment, and how AI changes that flow.

Security & governance

Governance as a first-class system property. Building provenance, legible reasoning, and accountability into autonomous systems so they never outrun the ability to answer for them.

Formats

How it can run

I tailor the format to the room and the outcome you need, not the other way around.

Keynote

20 to 45 minutes. A single sharp argument with the room - built for conferences and leadership offsites.

Workshop

Half or full day. Hands-on with your team's real architecture and decisions, not slides.

Panel

A substantive contributor who moves the conversation forward rather than defending a position.

Fireside

An unscripted conversation that goes deeper than a talk allows - best with a strong host.

What audiences take away

Useful the next morning

A talk should change how people work, not just how they feel for an hour. These are the outcomes I design every session around.

  • 01 A clear mental model for where AI actually belongs in consequential decisions - and where it does not.
  • 02 Concrete architectural patterns for systems that have to survive compliance, scale, and audit.
  • 03 A vocabulary for talking about context, governance, and accountability that a mixed room of engineers and executives can share.
  • 04 The failure modes to design against, drawn from systems that met reality rather than stayed in the demo.

For organizers

A short bio for your program

Mohit Rane is a Founding Architect for AI-native enterprise systems. He designs context intelligence, decision architecture, and security governance for organizations that have to think clearly under pressure - and writes and speaks about building intelligence infrastructure that preserves human judgment as more of the work passes through AI.

Get in touch

Have an audience that needs this?

Tell me about the event, the room, and what you want them to leave with. If it is a fit, I will say so plainly - and if it is not, I will point you somewhere better.

Or follow the thinking between talks: