Case 31 · Graduation Day
Vibe Coding Room
The magic moment is real and happened live — a spoken sentence became a tree on the wall and the audience scanned the working mock in real time — but the pitch buries it under mic checks and camera fights, leaves its best thinking (the gardening metaphor, the 200-thoughts-per-minute problem) in the Q&A, and answers the room's one investor question with "Should it be commodified? Maybe somebody else can answer that question." Scored as if pitched to investors; on stage it was a demo for its own community, and as that it landed.
01 Scorecard · 12 dimensions
02 Klaff 5-lens audit · 1.5/5
THE ONE REORDER — Freeze a single 90-second demo path (speak the idea → tree spawns → mock appears → audience scans), run it single-player so the tracking holds, and let the presenter — not the emcee — close on "it's literally upstairs; come plant something."
03 Delivery
169 fillers ("um" ×66, "uh" ×52, "like" ×36, "actually" ×6). The ums spike wherever the hardware fights back — every recalibration buys another cluster. A frozen demo path deletes most of them for free.
04 Beat-by-beat
| Time | Beat | What works | The fix |
|---|---|---|---|
| 0:00 | Mic check | — | "Mic one, mic two… No, not thumbs up" eats the open. Start when the mic works. |
| 0:16 | "AI psychosis" open | "I still want to vibe code because I fully have AI psychosis" — a real laugh, a real hook | Follow it with the one-sentence definition of the room, which is never spoken |
| 0:40 | Demo mode fails | Owning it with humor keeps the room | Two minutes of ceded frame ("you're fucking up the camera"). Single-player mode; a human camera marshal. |
| 2:00 | Citibike prompt | "Build an app that shows me all the Citibikes in the Brooklyn area" — concrete, scoped, perfect demo seed | Keep forever |
| 2:19 | Wall tour (delta wall, ceiling) | "This is where you can really feel the psychosis" lands; crystals as research suggestions are the most original visual | One wall was enough while the build cooks — the tour never hands back a thread |
| 3:20 | Tree spawns the mock | The magic moment: "it spawned a tree… now it is presenting us with a mock" | Announce it in advance so the room watches for it — this is the spine of the whole pitch |
| 3:37 | Audience scans live | "The audience can even scan it… in real time" — phones out, participation | Pre-empt the Wi-Fi question in the setup line |
| 5:03 | Tech confession | Honest: Kinect now, LiDAR ideal, pluggable backends | Move stack talk to Q&A; end on the experience, not the caveats |
| 5:43 | Close | "Vibecoderoom.ai… have a good one" | No ask, no name. "I'm Ron. It's literally upstairs. Come plant something" is the close this earned. |
| 6:44 | Q&A: metaphor origin | The best material of the night: GitHub-worktree origin, "gardening for vibe coding," "not for power users… for non-technical people," 200 thoughts per minute | All of this belongs in the pitch proper, not in an answer |
| 9:21 | Q&A: business model | "Community to community" is at least a memorable refusal | "Maybe somebody else can answer that question" is the one answer an investor cannot use. Decide. |
05 The gaps investors block on
- No problem statement in the pitch — "AI psychosis" is a joke where a pain should be; the real one (200 thoughts per minute, 20 people, no way to see what's working) is spoken only in Q&A.
- The business question was declined on stage: "Should it be commodified? Maybe somebody else can answer that question."
- Demo reliability contradicts the thesis — multiplayer is the product, and multiplayer is what breaks the tracking, by the presenter's own account.
- No self-introduction, no team — the room learned the presenter's name from the emcee.
- The secret is misfiled: the non-technical wedge, the third-computational-space framing, and the smallest-prompt game all live in Q&A.
- No numbers of any kind — no users, sessions, projects built, or rooms. Even "how many trees has this room grown?" would be traction.
Community art or company — choose out loud. The presenter stood at the fork on stage and refused it: "Did I spend this time building it for businesses? No. I spent it building for my community." Option A — it stays community art: legitimate, coherent, and then it's a talk, never scored as a company again. Option B — commit to the one wedge he argued for with reasons: "this specific front end is not for power users. It is for non-technical people… a non-scary way to interact with it." A communal room where people who can't code speak ideas and watch them get built is a describable product with a describable buyer [confirm: who pays — venues, schools, studios, companies]. If investors are ever in the room again, it's B.
“Vibe Coding Room is the communal computational space where non-technical people build software together — speak an idea, watch it grow as a tree on the wall, and scan the working mock off the screen before you leave the room.”
06 The rewritten pitch
I'm Ron, and this is vibecoderoom.ai — it's literally upstairs. Here's the problem it exists for: put 20 people in a room with AI agents and you're hitting 200 thoughts per minute — ideas everywhere, and no way to see which ones are being built, which are working, and which died. Vibe Coding Room makes that visible.
You walk in, you speak an idea — 'build an app that shows me all the Citibikes in Brooklyn' — and it becomes a tree on the wall. While we talk, agents grow it: in about a minute the tree presents an interactive mock, and everyone in the room scans it on their phone and starts shaping it. Ideas the room keeps talking about keep getting built, automatically, the whole time you're there.
The front end is deliberately not for power users — it's a garden, not a terminal, because the people we built it for are non-technical, and a shovel is less scary than a shell. Under it, any agent loop plugs in — we run [confirm current backends] today — so your workflows come with you.
Today it's one room, running on Kinect cameras; multiplayer tracking is the hard problem and [confirm: the plan and date for the multi-camera/LiDAR setup] is how we solve it. [If company: We're raising $X to put the next N rooms in …] It's upstairs. Come plant something — I'll be there in fifteen minutes.
Brackets are the founder's homework — the copy is done, the proof is theirs to supply. Every claim must match what's actually built.
07 Do these before the next take
- Make the decision — community art (then stop taking investor questions) or the non-technical-wedge company (then answer them). "Maybe somebody else can answer that question" is retired permanently.
- Promote the Q&A into the pitch — the 200-thoughts-per-minute problem, the gardening wedge, and "communal computational space" are the pitch; the wall tour is the appendix.
- Freeze one 90-second single-player demo path — multiplayer stays off-stage until the tracking survives it, by his own diagnosis.
- Say your name. First sentence. The transcript's only "Ron" comes from other people.
- Deliver the upstairs invitation as the close, personally — it's the best ask available to a talk, and it was left to the emcee.
- Filler drill — 7.7 per 100 words (um ×66, uh ×52, like ×36), clustered around every recalibration; most of it disappears when the demo stops needing rescue.