Build · Create · Writing & Content

Founder's VC Diligence Question Bank

The founder walks into the meeting with a complete, categorized interview script for vetting this specific investor: every question names the signal it is fishing for and the red-flag answer that should give pause.

You receive: A JSON object { targetInvestor, questions[] } where targetInvestor names the investor you entered and questions[] is an array of { questionId, category, question, signalSought, redFlagAnswer }, all non-empty, with category exactly one of: fund_profile, investment_style, deal_flow, process, organization, value_added

Part of Pitch Investors

What's verified: STUD verifies the deliverable is a JSON question bank naming your target investor (the targetInvestor value must be non-empty and, ignoring case and punctuation, match the investor name you enter), with at least the minimum total questions (default 12, capped to the 1 to 200 range), every question tagged with exactly one of these six categories: fund_profile, investment_style, deal_flow, process, organization, value_added, every required category covered with at least the per-category minimum (default 2, capped to the 1 to 20 range; if you leave the category list empty or invalid, all six categories are required), every question carrying a non-empty questionId, question, signalSought, and redFlagAnswer, no duplicate questionIds, and no duplicate question wording (compared case- and punctuation-insensitively). Submissions over 200000 characters are rejected. These checks are presence, count, and uniqueness checks only: STUD does NOT judge whether the questions are insightful, whether the signals or red flags are correct, or anything about the investor itself. Your company description, stage, and focus notes are context for the operator, not enforced criteria.