Presenter Kit
Set up before you join.
- Test your screen share before Friday, not on the call. Start an empty Google Meet by yourself, share the tab you plan to show, and confirm it looks right. There's no setup window before we start.
- Have the thing already running and the tab already open when you join. Your ten minutes do not include setup.
- Have your leave-behind link already copied to your clipboard.
- Close client tabs, notifications, and anything with a name or a number on it.
Minute by minute.
The clock is up where everyone can see it. It keeps us honest and gets everybody their turn.
Run it. Don't explain it.
Screen already shared. Trigger the thing and let it work. We 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.
The claim, with a number.
One sentence on what it does, then the time math. Be specific. Give us hours, not "a ton of time."
The workflow, step by step.
This is the part the room actually wants. Narrate the real chain in order, naming the tool at every step. Say "then" a lot.
Somebody in this room should be able to sketch your workflow on a napkin by 5:00.
The build.
The stack, the prompt that mattered, what broke, what you'd do differently. Get technical here.
Drop your leave-behind.
Paste the link in the chat. Say what it is, and what someone has to change to make it theirs.
Questions.
Time's up.
No slides. Cameras on for the hour. Your leave-behind goes in the chat during your slot, not after.
What you leave behind.
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 removed. 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 someone use it Monday without asking you a question?
Instructions, no code required.
A markdown file or public gist: what it does, what it saved you, tools and rough cost, setup steps, and your exact prompts verbatim. Someone rebuilds it in an afternoon. If your build isn't code (a Zap, an n8n flow, a prompt system, an agent setup), 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.
Four words, and then you're fine.
| Term | What it actually means |
|---|---|
| Repo | A folder of files with a web address. That's the whole concept. |
| Public | Anyone with the link can read it. |
| Fork | A one-click copy of someone else's repo. |
| Template repo | A repo with a "Use this template" button. The most reusable option. |
Gist (gist.github.com): paste code or markdown, get a link. Two minutes, no repo needed. The right answer for a single script or a prompt pack.
The README is the leave-behind. Without one, nobody can tell what they're looking at.
Session 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.
Paste this in the chat with your link.
WHAT IT DOES: one sentence
AI / MODEL: e.g. Claude Opus 4.8 via Claude Code
STACK: languages, frameworks, platforms
WHERE IT LIVES: repo or gist link
COST TO RUN: rough monthly or per-use
TIME SAVED: hours per week or per instance
TIER SHARED: template / recipe / mapHand this to Claude or ChatGPT.
You do not need to learn Git. Paste one of these and it does the work, including scanning for API keys you don't want leaked.
If you have code
Publish this project to GitHub as a public TEMPLATE repository that
other people can copy and run for their own use case. I am not
experienced with GitHub. Go one step at a time and wait for my
confirmation before each step.
Project folder: [PATH]
What it does: [ONE SENTENCE]
Steps:
1. Check that git is installed and I'm signed in to GitHub. If not,
tell me exactly what to install or click.
2. FIRST, BEFORE ANYTHING ELSE: scan every file for secrets and
private data. API keys, tokens, passwords, .env files, client
names, customer data. List what you find. Tell me what to remove
or replace with placeholders. Create a .gitignore excluding .env
and credential files. Do not push until I confirm it's clean.
3. Genericize it. Replace my specific configuration, names, and
hardcoded values with clearly labeled placeholders so someone
else can drop in their own. This is the point of the exercise.
4. Write a README.md for someone who has never seen this project:
what it does in one sentence, what it saved me, what accounts or
API keys are needed and roughly what they cost, exact steps to
run it, and the key prompts if prompts are central to it.
5. Create a public repo, push, then tell me how to enable
"Template repository" in Settings.
6. Give me the final URL.If you have no code (Zap, n8n, prompts, custom GPT)
I built something useful with AI but there's no codebase. It's
[a Zapier zap / an n8n workflow / a prompt stack / a custom GPT /
an agent setup].
Ask me questions until you understand it, then write a single
markdown file that lets someone else rebuild it from scratch:
what it does, what it saved me, every tool and account needed with
rough costs, step-by-step setup, and my exact prompts verbatim in
a code block.
Strip out anything specific to my company or clients and replace it
with clearly labeled placeholders.
Then tell me how to publish it as a public GitHub Gist so I can
paste one link into a chat.Run the secrets scan before anything goes public. Exposed API keys get found and drained by bots within minutes. Both prompts above do this first, on purpose.
Tell Colton what you're showing.
Five slots, ten minutes each. Lead with the practical impact, not the architecture. Takes a minute, and it sets the running order.
Got it.
Colton will confirm your slot and the running order before Friday. If anything about the demo changes, submit this again and he'll take the latest one.