vestige/demo/PITCH-FINAL-spoken.md
Sam Valladares 37c240a964 docs(demo): THE pitch — final condensed cut (~45s, networking-format closer)
Sam's locked stage pitch for a multi-pitch event + separate networking hour.
Keeps the World Cup soccer analogy (the weapon that makes anyone get "causally
upstream"), the detonation line + silence, "realizes", and "next layer of the
dev stack". Closer fits reality: "come find me after, I'll show you in 30s" (demo
is 1:1 at networking on a pre-loaded laptop, never installing on their system).
Two seams closed: "hours"->"days", "agents that touch" (plural). Added networking
playbook: pre-warm the seeded demo, demo from strength, the pilot-hook answer for
"does it work on mine?".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 11:07:56 -05:00

4.2 KiB

Vestige — THE PITCH THAT CHANGED EVERYTHING (final, condensed cut)

Sam's stage pitch — ~45-50s spoken, for a multi-pitch event with a separate networking hour afterward. Solo founder, first person, no slides/terminal on stage (the demo happens 1:1 at networking on Sam's pre-loaded laptop). Two seams closed from the draft: opener "hours"->"days" (matches "days ago"), and "AI agents that touch" (plural). NAME = Vestige.


THE PITCH

Your bug was born days before it crashed — but you just can't remember where.

When production breaks, you lose days hunting a bug. The cause is usually a quiet change you made days ago that looks nothing like the error it created.

Today's memory systems fail here, because they look for what looks like the problem. But a root cause never looks like the bug it creates.

[beat]

It's like blaming a goalie for a 90th-minute World Cup goal — when the real failure was a silent midfield turnover fifteen minutes earlier. They're searching the goal line. Vestige traces the match backward.

A 2024 Nature paper proved the human brain rewinds time to link a sudden shock to the quiet memory that caused it. Vestige does the exact same thing for software.

Everyone else built a memory that remembers. I built the first one that realizes. Millions of AI agents that touch production will hit this wall. That's not a feature — that's the next layer of the dev stack.

I'm Sam. I created Vestige from my tiny Chicago apartment — the first memory that finds the cause, not the lookalike.

Come find me after. I'll show you in thirty seconds.


THE LINES THAT WIN THE ROOM

  • Opener (pattern interrupt): "Your bug was born days before it crashed — but you just can't remember where."
  • The detonation (THE line): "A root cause never looks like the bug it creates." → beat of silence after.
  • The soccer proof (the secret weapon — makes ANYONE get it): "...blaming the goalie for a 90th-minute goal when the real failure was a midfield turnover fifteen minutes earlier. They're searching the goal line. Vestige traces the match backward."
  • The category (the quotable): "Everyone else built a memory that remembers. I built the first one that realizes."
  • The TAM (the money line): "That's not a feature — that's the next layer of the dev stack."
  • The closer (fits the networking format): "Come find me after. I'll show you in thirty seconds."

STAGE RULES

  1. NEVER open with "Hi, I'm Sam, thanks." Walk out, hold the room one beat, THEN the opener. Your name comes near the END.
  2. The detonation line — say it, then a real beat of silence before the soccer line.
  3. The soccer analogy is your weapon — deliver it conversationally, like you're explaining it to a friend. It's what makes a NON-engineer get it instantly.
  4. "Built it alone, from a Chicago apartment" is a flex. Own it.
  5. End on "I'll show you in thirty seconds." Don't say thank you. Let it hang.

NETWORKING (the demo happens HERE, not on stage)

  • The stage pitch's only job: be the MOST memorable founder so they seek you out in the networking hour, out of all the other pitches.
  • Have the seeded demo (./demo/postdict-demo.sh) ALREADY RUNNING / pre-warmed on your laptop so when someone walks up you show it in ~10 seconds, no boot fumble.
  • Demo from STRENGTH: show YOUR seeded scenario (instant, reproducible). Do NOT promise to debug their codebase live — Vestige has to be recording their history first. If asked "does it work on mine?": "it has to record your history first — give me your repo for a day and I'll show you it catch a real one." (That's the pilot hook, said 1:1, never from stage.)

DELIVERY MAP

  • "born days before it crashed" — land "born" with weight.
  • "a root cause never looks like the bug it creates" — then a real beat of silence.
  • soccer line — conversational, build to "Vestige traces the match backward."
  • "It runs locally" energy on "Vestige does the exact same thing for software."
  • "the first one that realizes" — let it land.
  • "the next layer of the dev stack" — slow, final. Mic-drop.
  • "I'll show you in thirty seconds." — quiet, confident, then stop.