The warm-up nobody does
Founders rehearse the pitch. Almost nobody rehearses the six questions that actually decide whether a partner leans in or reaches for the door: why now, why you, does 10% return the fund, what stops a fast-follower, who signs the first cheque, does revenue survive a month off. Pitch Dojo is a two-minute drill for exactly those six, built as a single self-contained HTML file with no backend.
Two chairs, not one
Most pitch prep only trains one side of the table. Pitch Dojo trains both.

Get grilled. A seed partner fires the six questions one at a time. Every answer is graded sharp, okay or dodge, and a credibility meter moves live as you choose: +15 for the sharp answer, +5 for the generic-but-true one, -15 for the dodge that sounds fine and says nothing. The feedback names why the sharp answer works, not just that it does, because the generic version of most of these answers sounds fine in the room and only fails on reflection.
Grill the VC. The seats flip. You ask the six questions founders rarely think to ask back, on reserves, on real value-add, on process and timeline, on what a pass would look like, and you have to call whether the partner's answer is a green flag or a rehearsed dodge before the reveal shows you both side by side.

Why both directions matter
A founder who can only answer well is still exposed on the other side of the table, because a fund's own answers are pitches too. "We add a lot of value and have a great network" is exactly as rehearsed as "we're passionate about the space," and it costs a founder real time and real terms if it goes unchallenged. Training the read, not just the answer, is the part most pitch prep skips.
Every question in both modes traces back to a fixed rubric: named, dated specifics beat true-but-generic claims, and true-but-generic claims beat warmth with nothing behind it. The scoring logic and the content are both plain, inspectable arrays and pure functions, asserted by a small self-test suite (?test in the URL) rather than left to run untested.
Stack
Single HTML file, no backend, no dependencies. Deployed as a static Vercel app.