Objection Planning: Preparing for Investor Questions

Friday Notes is our weekly note on evidence, claims and decisions. This one is about the questions that come after the pitch.

A VC firm looks at roughly 100 companies for every deal it closes.

That's from a 2016 survey of 885 institutional venture capitalists at 681 firms, by Paul Gompers, Will Gornall, Steven Kaplan and Ilya Strebulaev, later published in the Journal of Financial Economics. The same survey found the average deal took 83 days to close, with 118 hours of due diligence and 10 reference calls along the way.

Every stage of that funnel is a conversation: a first meeting, a partners meeting, weeks of due diligence. Each one is a set of questions. You can't control what they ask. You can make sure very little of it is a surprise.

Objection planning means writing down the hardest questions an investor will ask about your deck, before the meeting, with the evidence for each answer and the part of the challenge you'll concede. Build it as a four-column rebuttal matrix. Then have someone who didn't write the deck attack it, record the session, and fix whatever made you pause.

What Objection Planning Is

Objection planning is preparing, in writing, for the questions most likely to sink your pitch. It's a working document nobody outside the company sees, and it sits behind the deck the way workings sit behind a set of accounts.

It matters because the decision gets made in conversation. Here's how the deal funnel looked in that survey, counted per closed deal:

Look at the drop between meeting management and the partners meeting, and again before due diligence. Those are conversations. Each one is a chance for a question you haven't thought through.

Founders who raise often plan the meeting around those questions. One who says they've pitched hundreds of investors, writing on r/startups in August 2026 after helping a fund review pitches, put it this way:

Kevin Hale, then a partner at Y Combinator, made the case for clarity in this 2019 Startup School lecture. The clip starts at his section on being clear, which is the first thing a good answer needs:

Play Video (Loads YouTube)

The Three Types of Investor Question

Investor questions tend to fall into three types: evidence, assumption and risk. Each needs a different kind of preparation, so it's worth sorting your list before you start answering.

• Evidence questions test where a number came from. "Where does that figure come from?" "Is that gross or net?" "What's the sample size?"
• Assumption questions test the logic between your data and your conclusion. "That market size assumes 15% penetration. Why is that achievable when others at scale have reached 4%?"
• Risk questions test what happens if the thesis fails. "If your biggest customer churns in month 18, what do your unit economics look like?"

You can prepare fully for the first two. The third is where unprepared founders get hurt, because a risk you haven't considered at all suggests a gap in how you think about the business.

You can predict a lot of the questions from what investors say they weigh. In the same NBER survey, the team was by far the most cited factor:

So expect questions about why you are the right people as much as questions about the market. Sequoia's guidance on writing a business plan is a useful checklist here, because every section it asks for is a place questions come from. "Why now?" is one. Its advice reads: "The best companies almost always have a clear why now?" If your deck can't answer that in a sentence, put it at the top of your list.

Michael Seibel's short 2019 video for Y Combinator on how pitching investors differs from pitching customers is a good reminder of why. Investors are asking a different question from your buyers:

Play Video (Loads YouTube)

Building Your Rebuttal Matrix

A rebuttal matrix is a structured document, built claim by claim. For each slide in your deck that contains a quantified claim, you fill in four columns.

The fourth column is the one founders skip. Almost every investor challenge contains a valid point. Admitting it before they do tends to work better than defending against it, because it shows you've already looked at the weakness.

This example is built to show the shape of a completed row. The figures aren't from a real company. The numbers change for every deck, but the four columns and the honest concession stay the same.

Column three is where most of the work goes. If the source behind a number is weak, the matrix tells you before an investor does. My advice is to fix the claim rather than polish the answer. Our earlier Friday Notes on choosing the right benchmark category covers the most common way a good number turns into a bad claim.

Red-Teaming Your Own Deck

Red-teaming means attacking your own thesis as hard as a well-informed, slightly sceptical investor would. The goal is to find the questions you can't yet answer well, and answer them before you're in the room.

The idea comes from defence planning, and the UK's Red Teaming Handbook, published by the Ministry of Defence (third edition, 2021), is a practical guide to it. It defines red teaming as "the independent application of a range of structured, creative and critical thinking techniques to assist the end user make a better-informed decision". The word that matters is "independent". The handbook says that although individuals can do these exercises, "they are best conducted by a separate red team."

It's blunt about why. Arguing against your own plan, it says, "is difficult and involves some tricky mental gymnastics." It recommends someone "who has not been too involved in developing the plan" takes the devil's advocate role. You wrote the deck, so you're the worst person to attack it. A co-founder who didn't build the model, an adviser or a friendly angel will find things you can't see.

Two techniques from the handbook work well for a fundraise:

1. Devil's advocacy. Once the deck is done, someone argues that it fails and, as the handbook puts it, "more importantly identifies the reasons why."
2. A pre-mortem. Assume the partner meeting went badly. Define what "badly" means (no follow-up, a polite pass). Then list the two to six questions most likely to have caused it, and trace each one back to the slide that invited it.

Gary Klein described the premortem in Harvard Business Review in 2007. His point was that too many people are reluctant to speak up about their doubts while a plan is being made. Assuming failure up front makes it safe to say what's wrong.

The Confidence Asymmetry Problem

A founder who has already defended the thesis under hard questioning walks into a partner meeting with an advantage over one who hasn't. In the room, they hear questions they've answered once already.

The other side of that advantage shows up in founders' own words. This post from r/startups in May 2026 is a familiar one:

Preparation shows in how you answer. If you're working an answer out live, it gets long and wanders. This short clip from Dreamit Ventures makes the case for direct, short answers, and compares it to playing catch:

Play Video (Loads YouTube)

One more thing. Confidence built on a weak source is worse than no confidence at all. If an investor checks a number after the meeting and it doesn't hold, the confident answer becomes the problem. That's why column three of the matrix comes before rehearsal, not after.

Objection Planning in Practice

In practice, objection planning is a short sequence you can run in the weeks before a raise. Here's the order I'd follow.

1. List every claim. Every number, every "leading", every "fastest-growing", every logo. If it's on a slide, it's on the list.
2. Rank them by risk. Which claims would an informed investor most likely challenge, and which would hurt most if they fell over?
3. Fill in the matrix. Challenge, evidence and concession for each high-risk claim. Rewrite any claim whose evidence won't hold.
4. Run a red-team session. Someone else asks the questions. You answer out loud. Record it.
5. Run a pre-mortem. Assume the meeting failed, and name the question that did it.
6. Check the deck against everything else. Your website, one-pager and data room should say the same things. Investors notice when they don't.

Step six is the easiest to skip. Many investors research your claims before the first meeting, and I go through what they check in how investors verify startup claims. Our Series A claim checklist is a free way to run steps one and two.

Many of the hardest objections turn out to be positioning questions: who exactly this is for, and why you rather than the alternative. If those answers aren't settled, start with B2B positioning for established companies. No rebuttal matrix fixes an unclear answer to "who buys this?"

Rehearsing With AI Without Fooling Yourself

AI assistants are a cheap sparring partner, but by default they're on your side. That's the opposite of what a red team needs.

Researchers at Anthropic found that "five state-of-the-art AI assistants consistently exhibit sycophancy across four varied free-form text-generation tasks", in a paper titled Towards Understanding Sycophancy in Language Models. In plain terms, they tend to tell you what you want to hear. In April 2025 OpenAI rolled back a ChatGPT update it described as "overly flattering or agreeable".

You can still use them well. Give the assistant a role ("you're a sceptical partner at a Series A fund") and a task ("list the five questions most likely to end this meeting, strongest first"). Ask it to attack one claim at a time. Then check every fact it gives you, because a confident AI answer about your market can be wrong too. I wrote more about this in why ChatGPT says your idea is brilliant.

It's a useful first pass. It's not an independent challenger, and the handbook's point about independence still applies.

Where ThriveFinity Fits

We do the evidence half of this work. Release Assurance checks the claims in a deck, website, proposal or one-pager against named, dated sources before they go out, and a named verifier signs an Assurance Note.

Its Challenge step is a red-team pass in all but name. In the site's words, "We test every claim against what the evidence shows, using the objection an investor or a sceptical buyer would raise." Each claim is then tagged Verified, Supported, Flagged or Unverifiable.

• First Signal (free, under 1 hour): a quick read on your deck's claims, with no payment.
• Release Assurance Pack (£699, 3 business days): one asset checked, weak claims rewritten, and a signed Assurance Note.
• Release Assurance Suite (£1,749, 5 business days): your deck, one-pager and site checked against each other, which is step six above done for you.

We're not the right choice if you need pitch coaching, deck design, a financial model or legal advice on your raise. We don't run mock partner meetings either. A good adviser, an accelerator or an experienced angel is better for the rehearsal itself. What we can do is make sure that when you answer, the evidence behind it holds. You can see what that looks like in our sample Release Assurance report.

Pranav Unni

Founder · ThriveFinity Connect on LinkedIn →

Pranav Unni is the founder and lead verifier of ThriveFinity. He reads and signs every paid deliverable personally, and writes about go-to-market decisions for established B2B companies.