EO members only · Capped at 10 · One hour · Cameras on

AI Open House

Real humans demoing real things they built with AI.

 
Next session Date announced soon
Request a seat
Why this exists

The forums, the Reddit threads, and the WhatsApp chats aren't helping me.

We're all in threads with smart people swapping AI tools and links. But it's hard to sort what's fun and interesting from what's useful and productive. Two dozen messages a day, and no time to figure out which of them would actually help my own workflow, my own builds, my own creations.

Love the tools. Love them more when someone shows you exactly how they used them. An hour with a human who already built the thing beats a week of reading about it, every time.

The hour

Ten in the room. Five on the clock.

Ten people in a private room. Five of them present, ten minutes each, and every minute of it is pointed at one question: is this actually useful to me? Cameras on, the whole time.

10 PEOPLE

The room

Capped at ten so it stays a conversation. Cameras on, since we're talking to each other.

5 DEMOS

Ten minutes each, on a visible clock

Five presenters, and the clock is up where everyone can see it. It keeps us honest and gets everybody their turn.

0:00-1:00

Run it. Don't explain it.

Screen already shared, thing already running. Trigger it and let us watch the output appear. No background, no company intro, no architecture. Seeing it do something in the first minute is what makes the other nine land.

1:00-2:00

The claim, with a number

What it does in one sentence, then the time math. "It used to take me 3 hours a week. It now takes 12 minutes of review." Not "it saves a ton of time." Give us hours.

2:00-5:00

The workflow, step by step

This is the part the room actually wants. Narrate the real chain, naming the tool at each step: a client emails me, then Zapier catches it, then it lands in Airtable, then Claude drafts it at 6 AM, then I review one line and send. Someone in the room should be able to sketch it on a napkin by 5:00.

5:00-7:00

The build

The stack, the prompt that mattered, what broke, what you'd do differently. Get technical here.

7:00-7:30

Drop your leave-behind

Link in the chat. Say what it is, and what someone has to change to make it theirs.

7:30-10:00

Questions, then we move on

Real back and forth. At 10:00 we hand off to the next person.

AFTER

Stick around

The hour ends on time. Breakouts and hangs afterward for anyone who wants to go deeper.

House rules

Give to get.

Anything you think is proprietary probably isn't. The next reasoning model drops next month, and someone will rebuild your shit in a tenth of the time. So we'd rather move fast together than sit in solo silos. Four rules:

01Demo first

A working thing, live. We want to watch it run, not hear about it.

02Share a piece

Whatever you show, you offer something the room can use: a repo, template, prompt, config, or written instructions. Shared with the group. It doesn't have to go public.

03Post your stack card

Six lines: what it does, the AI, the stack, where the code lives, what it costs to run, and what you're sharing.

04Do the time math

Tell us what it saved you: hours per week, hours per project. Money saved is a bonus. Money made is a future theme.

CAMCameras on

This is humans teaching humans, so we look at each other. Life happens, but the default is on.

RECOn recording

Assume something is always listening. Before you share your screen, close anything personal or sensitive: your tabs, your notifications, your file names.

CLIPPrivate group, possible public audience

Assume anyone on the call may clip, post, edit, or riff on what you share and what happens in the room. By joining, you're fine with that: you waive any claim to footage or likeness of you from the session, and you're not going to make it a problem. Show up like a private room with a public audience, because that's what it is.

The give

What are you willing to hand over?

Three ways to do it. All of them count, so pick whichever fits what you built. The only thing worth optimizing for: not the most raw, the most reusable.

A template

Copyable, runnable, generic.

Same thing you built, with your specifics stripped out. Someone clones it, points it at their use case, and it runs. A template repo, an exported n8n or Zapier workflow, a shared Claude project or custom GPT, a duplicable Airtable base. The test: could a person in this room use it Monday without asking you a single question?

your business stays yoursone setup, reused forever
A recipe

Instructions, no code required.

A markdown file or a gist: what it does, what it saved you, the tools and rough cost, the setup steps, and your exact prompts pasted verbatim. Someone rebuilds it themselves in an afternoon. If your thing isn't really code (a Zap, an n8n flow, a prompt system, an agent setup), this is exactly the right answer.

30 min of workan AI writes most of it
A map

How the pieces connect.

A screenshot or diagram of how it all fits together, the list of tools you used, and the one prompt that made it work. Pasted in the chat during your ten minutes.

5 min of worka whiteboard photo counts

Whichever you pick, have it ready before the call and drop it in the chat during your ten minutes, while everyone's still looking at the thing. Afterward, it tends not to happen.

The library

A catalog of cool shit we built.

Every session feeds the library: the demo, the repo, and a short summary of how it works and what it saved. If you're generous enough, mirror your repo to the shared GitHub org so others can replicate it or rip it off respectfully.

STATUS

Open. Session 001 is on the shelf.

Every guest has a page: what they demoed, their stack card, and the piece they left behind. It's all in a public repo on purpose: fork it, pass it around, show your team. Guests keep their own pages honest by pull request.

aiopenhouse.co/guests github.com/ai-open-house/house-guests
Next session

Session 003 · date announced soon

Sessions 001 and 002 are in the books. The next date is not set yet: we’re reworking how the room shares work before it opens back up. Fridays, 3:00 to 4:00 PM Central, one room, one link, handed to you by a human. Get on the list below and the date lands in your inbox first.

THEME

Work faster: time saved and agent autonomy

Systems that act like a chief of staff: monitoring, editing, augmenting, and acting on your behalf. How much of your week did you actually get back?

Claude required GitHub required Everything else fair game
Get in

Request an invite.

Right now this is for EO members, because trust is the whole product: we trust you as a human before we trust your demo. Rooms are capped at ten to keep it a conversation.

No registration forms, no approval queues. A human hands you the room link. Ask for a seat below and it lands in your inbox.

Two things to know before you sign up. Cameras stay on for the hour. And this is a private group with a possible public audience: anyone here may clip, post, or riff on what happens. Show up accordingly.

Request a seat.

Ten seats a session. Tell us who you are and what you're working on. Sixty seconds.

Presenting · pick one
Future sessions
House rules · all three required

Not ready for a seat? Stay in the loop instead. A note when the next session opens, the occasional recap of what got shared. That's the whole arrangement.