Case 29 · Graduation Day
CoordinationOS
There is a real secret here — "who is actually prompting these prompters? It tends to be humans," so the transcript is the signal, and every org needs its own partial brain — but the pitch buries it under seven dependency names, hands its only traction line ("Holy shit, this is cool. We need this") to the coordinator to deliver seventeen minutes later, and ends on "we can be the co-design partner" trailing off instead of an ask.
01 Scorecard · 12 dimensions
02 Klaff 5-lens audit · 1.5/5
THE ONE REORDER — Put the investor-pull story in the founder's own mouth in minute one, and put an ask where "we can be the co-design partner" currently evaporates.
03 Delivery
311 fillers ("uh" ×120, "like" ×80, "um" ×75, "actually" ×17) across a three-speaker slot; the pitch proper ends at ~7:45 and the remaining 17 minutes are an unscripted retrospective. Pace is fine — length and density are the problem.
04 Beat-by-beat
| Time | Beat | What works | The fix |
|---|---|---|---|
| 0:00 | Open + problem | "Each human has a team of hundred agents" — the right problem in one image | Cut "let's just think about how things are happening today." Open on the hundred-agents image or the investor-pull story |
| 0:46 | Cohort trust boundaries | "Think of an accelerator cohort like Shape Rotator... different trust boundaries" — grounds the abstraction in the room itself | Name the felt cost: what went wrong, for whom, because teams couldn't see each other |
| 1:06 | Shape Rotator OS + requirements | "Andrew does not like filling any forms... everything ambient" — design constraint as story; "who is actually prompting these prompters?" is the secret | The secret is the headline, not a requirement footnote — move it to sentence three |
| 2:35 | Architecture phase 1 | Ontology to resolve aliases, a classifier for "who can this data be shared with" — real, specific work | Semantic vs. episodic memory is a lecture, not a pitch. One sentence: it remembers who, and it remembers what happened |
| 4:11 | Partner roll-call | Synclave, Tinycloud, BitRouter, Smithers, Teleport Router — cohort-native integration is genuinely collaborative | Five dependencies in sixty seconds reads as risk, not strength. Collapse to one sentence; say what CoordinationOS itself owns |
| 5:12 | The loop | "Track every... accept or change or evaluation... to understand each user's individual preferences" — the differentiated part | Give one concrete learned preference; "frontier model and a small memory model" is roadmap, cut it |
| 6:02 | Dossier + Hermes | "A dossier... generated with provenance to where each thing is coming from" — the demo-able core | "I don't... want to just show the UI" plus an agent "plugged in... in the last few hours" undercuts it. Show one rehearsed question answered with provenance |
| 6:29 | Wedge + market | Coordinator first "because it's complementary and it's a positive sum game"; roadmap to Flashbots-like orgs, then VC/PE | Right wedge logic, zero numbers. One named next customer beats the topology tour |
| 7:45 | "Thank you" | — | The pitch ends with no ask. This is where the ask goes |
| 7:59 | Retrospective (to 24:35) | The best material in the slot: "shooting for the moon... not even like leaving ground," the IP ban, "we have no product," "Holy shit, this is cool. We need this," the 19-day rebuild | Seventeen minutes of it makes the founder a bystander in his own traction story. Fold sixty seconds into the pitch, spoken by Shashank; cut the rest |
05 The gaps investors block on
- No ask — no amount, no use of funds, no next step. The slot ends on "it may be the same pain point that many people share."
- No business model — the coordinator wedge is explicitly positive-sum/free; who pays across the Flashbots → VC → PE roadmap is never said.
- Traction is secondhand — "We need this" and "co-design partner" are quoted by Tina about unnamed investors; no name, no signature, no pilot. Tina also says on stage: "we have no product."
- The dependency stack — Synclave, Tinycloud, BitRouter, Smithers, Conclave, Teleport Router, Codex, Hermes — a DD reviewer will ask what CoordinationOS owns when any one disappears.
- The differentiator is admitted unsolved: "managing the permissions correctly has been a challenge we are trying to actively address."
- A 19-day-old product sharing a slot with its own eulogy — the room may remember V0's failure story better than V1's promise.
Become the portfolio operator's brain. The pitch names three markets in ninety seconds — research orgs like Flashbots, venture capital, private equity — while every ounce of spoken pull points at exactly one buyer: the portfolio operator. Tina's investors saw the cohort view and said "Holy shit, this is cool. We need this"; accelerators offered to be "the co-design partner"; Tina offered on stage, "I can hand you my customers." Customers volunteered themselves for the operator wedge; nobody asked for the general Coordination OS. Pick it out loud and make research orgs customer #2.
“CoordinationOS gives every portfolio operator a private brain of their cohort — built ambiently from meeting transcripts, permissioned per team, provenance on every insight — starting with [confirm: first named accelerator/VC design partner].”
06 The rewritten pitch
When investors saw a map of this cohort — who's building what, who's converging with whom — their reaction, verbatim, was: 'we need this.' [confirm: which investors, via Tina — get one nameable] Here's why they can't have it yet from anyone else. Every operator of a portfolio — an accelerator, a fund, a research org — now runs many teams, and every team runs a swarm of agents. The agent traces show execution. The humans prompting those agents are the real signal — and the only ambient record of humans is the meeting transcript.
CoordinationOS builds each organization a private brain from its transcripts. An ontology resolves who's who and which project is which — even when both change mid-cohort. A classifier decides who each insight may be shared with, so the coordinator's brain and each team's brain are deliberately different. And every dossier carries provenance: this line from that meeting, this one from GitHub. Ask it what you're allowed to know, and it answers. Ask it what you're not — and it refuses.
We rebuilt this from a first commit nineteen days ago and ran it on this cohort's own meetings — every team, every trust boundary, live.
We're signing [confirm: N] design partners — the accelerators and funds who've already asked [confirm: names] — and raising [confirm: $X and milestones] to ship them the permissioned brain. I'm Shashank. If you run a portfolio, find me before you leave the room.
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
- Pick the wedge out loud — portfolio operators — and say the one-sentence in every pitch. The three-market tour dies today.
- Write the ask — amount, use of funds, 3 milestones. The slot currently ends on someone else's trailing sentence.
- Take Tina's customers: "I can hand you my customers" was said on stage — convert it into one named, signed design partner and say the name yourself.
- Move the traction into the founder's mouth — "investors said 'we need this'" is Shashank's line now, with a source, in minute one.
- Compress the slot to 3 minutes; the retrospective becomes one 60-second before/after beat inside the pitch, everything else goes.
- Collapse the dependency roll-call to one sentence and name what CoordinationOS itself owns: the ontology and the permission layer.
- Script and drill the first 90 seconds — 8.1 fillers per 100 words ("uh" ×120, "like" ×80, "um" ×75) says the open was improvised.