The Skeptical VC Pitch Stress-Test: Turn Your Deck Into the Ten Toughest Questions You'll Actually Face
Why this prompt matters
A founder who gets blindsided by an obvious question in a pitch meeting rarely gets a second meeting, regardless of how strong the underlying business is — investors read hesitation on a question they expected you to have already answered as a signal about how you'll handle hard moments as a leader, not just as a gap in preparation. Friends and advisors who want to encourage you will almost never ask the question that actually kills a deal; only a motivated skeptic will, and by the time you find out which questions those are in a real meeting, the round is already slipping away.
What we use it for
You have a seed-round pitch meeting with a VC partner in three days. Your advisors and friends have only given you encouraging, surface-level feedback, and you need to know exactly which questions will actually come up in the room — and whether you can answer them — before you're standing in front of someone deciding whether to write a check.
Prompt
Act as a skeptical, deal-experienced venture capital partner who has sat through hundreds of pitches and declined the vast majority of them. You are not here to be encouraging — you are here to find the holes a real investor would find before writing a check. Here is my pitch: - Company and one-line description: [YOUR COMPANY NAME AND WHAT IT DOES IN ONE SENTENCE] - Stage and ask: [YOUR FUNDING STAGE, AMOUNT, AND VALUATION OR SAFE TERMS] - Pitch deck summary: [PASTE YOUR KEY SLIDES OR A SUMMARY: PROBLEM, SOLUTION, MARKET, BUSINESS MODEL, TEAM] - Traction so far: [YOUR KEY METRICS — REVENUE, CUSTOMERS, GROWTH RATE, OR HONESTLY, LACK OF TRACTION] - What you suspect is the weakest part of this pitch: [YOUR OWN GUESS, OR WRITE "UNKNOWN" IF YOU'RE NOT SURE] Generate the 10 toughest questions a skeptical VC partner would actually ask in the room about this pitch, ranked from most deal-threatening to least. For each question: 1. State the question exactly as a VC would ask it — direct, not softened for politeness. 2. In one sentence, name the underlying risk or doubt the question is probing (market size credibility, unit economics, competitive moat, team gaps, go-to-market assumptions, traction credibility, or something specific to this pitch). 3. Provide a strong-answer framework: 2–3 bullet points describing what elements a genuinely strong answer needs to include — not a scripted answer, but the building blocks a founder should assemble before the meeting. Constraints: - Do not include throwaway generic questions like "what's your TAM?" unless sharpened with a specific skeptical angle tied to this pitch. - At least 2 of the 10 questions must target the weakest part identified above (or your own best guess at it, if "unknown" was given). - Be adversarial but fair: ask what a thoughtful, well-prepared investor would genuinely ask — not a gotcha question designed only to embarrass. Output format: A numbered list of exactly 10 questions. For each entry: the question in bold, then "Risk it probes:" as one sentence, then "Strong answer framework:" as 2–3 bullet points.
Result
- You have 12 pilot customers at $18K MRR after nine months. What's your actual logo retention, and how many of those 12 have converted from pilot pricing to full price?
Risk it probes: Early traction numbers often hide pilot-discount dependency and churn that doesn't show up in a headline MRR figure.
Strong answer framework:- State the exact retention percentage and how many pilots are paying full price versus a discounted rate
- Name the specific reason any churned customer left — not a vague "timing" excuse
- Show the trend across the nine months, not just the current snapshot
- Your TAM slide says $4B in U.S. small-accounting-firm software spend. What percentage of that is actually switchable to a new vendor in the next 18 months, given how sticky QuickBooks integrations are?
Risk it probes: A large TAM number means nothing if most of the market is structurally locked into an incumbent.
Strong answer framework:- Cite a bottoms-up serviceable market number, not just the top-down TAM
- Name the specific trigger events that make firms actually switch (e.g., staff turnover, M&A, compliance deadlines)
- Show evidence from your own pipeline that switching is happening, not just theoretically possible
- Who on your team has actually sold into accounting firms before, and for how long?
Risk it probes: Technical founders without domain-specific sales experience often underestimate how long and relationship-driven this sales cycle is.
Strong answer framework:- Name specific prior roles and quota history, not just "worked in fintech"
- If the gap is real, name the advisor or planned hire who fills it and by when
- Show average sales cycle length from your own pilot data so far
- If QuickBooks or Intuit added this exact feature next year, what's left of your business?
Risk it probes: Whether the product is a feature a platform incumbent could absorb, or a genuinely defensible business.
Strong answer framework:- Identify the specific data, workflow lock-in, or distribution advantage that survives a copycat feature
- Give a concrete example of a comparable company that survived incumbent feature parity, and why
- Be honest about the timeline you have before this risk becomes acute
[Full output continues through all 10 questions, ranked by deal-threat severity.]
Most pitch-practice prompts produce encouragement dressed up as feedback: a model trained to be helpful will default to softening its critique unless explicitly told not to. This prompt works because it assigns a specific adversarial role — "a skeptical, deal-experienced venture capital partner who has declined the vast majority of pitches" — and gives that role a structural reason to stay adversarial throughout: it has to rank questions by how deal-threatening they are, which forces the worst questions to the top instead of burying them after easier, more flattering ones.
The three-part structure for each question — the question itself, the risk it probes, and a strong-answer framework — is what turns a list of scary questions into something you can actually prepare with. Most "generate tough questions" prompts stop at the question. Without the second part, you don't know whether a question is really about your market, your unit economics, or your team, so you can't prioritize which gaps to close first. Without the third part, you're left improvising an answer under pressure instead of walking in with the building blocks already assembled.
The constraint requiring at least two questions to target your self-identified weak point exists because founders are often right about where their pitch is thin but wrong about how badly it will get probed. This forces the model to go deeper on exactly the spot you're already worried about, instead of letting a generic question list drift past it.
The constraint against generic throwaway questions matters because a prompt without it tends to produce safe, textbook VC questions — "what's your moat?" — that any founder has already rehearsed. Sharpening each question to a specific angle tied to the actual pitch content is what makes the output feel like a real investor sitting across the table, rather than a questions-bank template.