Rules of the House
This applies to everyone in the room, whether you're demoing or just watching. Two minutes, and then you know how the hour works.
Ten people. One hour. No slides.
Five people demo, ten minutes each, on a clock everyone can see. The rest of the hour is questions. That's the whole format.
Seats are capped at ten and approved by hand. This is EO members and people they vouch for, because trust is the product: we trust you as a human before we trust your demo.
We start.
On time. If you're presenting, come with your screen share already sorted and your thing already running: there's no setup window before we begin.
We're done.
We end when we said we'd end.
Six of them. They're short.
Camera on.
This is humans teaching humans, so we look at each other. Life happens, but the default is on.
Screen hygiene. Assume everything is public.
AI capture is everywhere now. Before you share, close client tabs, notifications, and anything with a customer name, a credential, or a number on it. If you'd regret it being published, don't put it on screen.
Private group, possible public audience.
Anyone on this call may clip, post, edit, or riff on what happens. That's the deal you agreed to when you signed up, so show up accordingly.
If you demo, you leave something behind.
This is the one that makes the hour worth an hour. Anything you show, you hand over a piece the rest of us can actually use, and you drop it in the chat during your ten minutes, while everyone's still looking at it.
The link comes from Colton.
Seats are approved by hand, so please don't forward the invite. If you want to bring someone, just say so and they get their own seat.
Just watching is a real answer.
Nobody has to present. Come, take what's useful, use it Monday. Show up next time with something to show.
What "leave something behind" actually means.
Three ways to do it. All of them count, so pick whichever fits what you built. The most raw thing you can share isn't the most useful thing, so aim for reusable.
Copyable, runnable, generic.
What you built with your specifics stripped out. A template repo, an exported n8n or Zapier workflow, a shared Claude project or custom GPT, a duplicable Airtable base. The test: could someone use it Monday without asking you a single question?
Instructions, no code required.
A markdown file or a public gist: what it does, what it saved you, the tools and rough cost, the setup steps, and your exact prompts verbatim. If your build isn't code, this is exactly the right answer.
How the pieces connect.
A diagram or screenshot of how it all fits together, the tools you used, and the key prompt. Pasted in chat.
Leave-behinds land in a shared org at github.com/ai-open-house so the room can still find your thing six months from now. Linking to your own repo is fine. Nobody has to hand over code.
Run a secrets scan before anything goes public. Exposed API keys get found and drained by bots within minutes. The presenter kit has a copy-paste prompt that does this for you, first, on purpose.
Working faster.
Time saved and agent autonomy. Systems that monitor, edit, and act on your behalf. Claude and GitHub are the required core. Everything else is fair game.
Come with questions. If you see something you want, ask for the repo. That is the entire point of the room.
The kit has the minute-by-minute.
Rules of the house get you in the room. The presenter kit gets you through your ten minutes: the clock, the options, the stack card, and copy-paste AI prompts that publish your leave-behind for you.
Presenter kit → Submit a demo