Unpopular opinion for an AI company: AI should never touch EOS facilitation.
No AI running L10s. No bot in the session room. Implementers don't want EOS 2.0 — the method works because a human runs it.
Think about what actually happens in a great session. The implementer reads the room. They notice the COO went quiet when the integrator issue came up. They decide, in the moment, that the scheduled agenda matters less than the tension nobody's naming. They hold the line when the team wants to skip the hard conversation. None of that is information processing. It's judgment, presence, and earned trust — and it took years to build.
An AI can't do that. More to the point: it shouldn't try. The moment a bot is running the room, the room stops being the thing clients pay a premium for.
But here's what the same implementer is also doing, and shouldn't be: they're the scribe, the context database, and the follow-up machine for every client at once. They're the one reconstructing last quarter from a notes doc at 10 p.m., chasing the to-dos, holding six companies' worth of rocks and issues and people in one head.
That work is real, it's constant, and none of it is the craft. It's the tax on the craft.
That's the line we build on. Sessions are sacred. Everything around them is fair game.
We hold this line as a principle, not a roadmap gap. It's not "facilitation features coming later." It's never. The line is the whole point: it's what lets an implementer hand off the between-sessions machine without ever wondering if the machine wants their chair.
This was never about doing less. It's about being a better implementer — sharper prep, faster follow-through, more present in the room.
The best version of you walks into a session with everything reassembled, nothing dropped, and full attention on the eight people in front of you. That's what the work around the session is for. That's the only part we touch.