O Teste de Estresse do Investidor Cético: Transforme Seu Pitch nas Dez Perguntas Mais Difíceis que Você Realmente Vai Enfrentar
Porque é que este prompt importa
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.
Para que o usamos
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.
Resultado
- 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.]
A maioria dos prompts de prática de pitch produz incentivo disfarçado de feedback: um modelo treinado para ser útil tende a suavizar sua crítica, a menos que explicitamente instruído a não fazer isso. Este prompt funciona porque atribui um papel adversarial específico — «um sócio de venture capital cético e experiente que rejeitou a grande maioria dos pitches que viu» — e dá a esse papel uma razão estrutural para permanecer adversarial durante todo o processo: ele precisa classificar as perguntas por quão ameaçadoras são ao negócio, o que força as piores perguntas a subirem ao topo.
A estrutura de três partes para cada pergunta — a pergunta em si, o risco que ela investiga e um framework de resposta forte — é o que transforma uma lista de perguntas assustadoras em algo com que você pode realmente se preparar. A maioria dos prompts de "gerar perguntas difíceis" para na pergunta.
A restrição que exige que pelo menos duas perguntas abordem seu ponto fraco autoidentificado existe porque fundadores costumam estar certos sobre onde seu pitch é fraco, mas errados sobre quão a fundo isso será investigado.
A restrição contra perguntas genéricas descartáveis importa porque um prompt sem ela tende a produzir perguntas seguras e de livro de texto — «qual é seu diferencial competitivo?» — que qualquer fundador já ensaiou.