← Raise Intel
·meeting prep

What questions will VCs ask me in a pre-seed meeting?

Short answer

The investor has already read the deck — you sent it before the meeting. The 5 minutes you get isn't to walk through slides. It's to tell your story. The rest is unpredictable Q&A, almost always digging into traction, why now, team, or defensibility. Most founders prep the deck and forget to prep the story or the deep-dive answers.

The deck got you the meeting. The meeting isn't about the deck.

If you walk into a pre-seed meeting planning to open your deck and walk through slides, you're already losing time you can't get back. The investor has seen the deck. You sent it before the meeting. If you didn't, you're starting behind.

The deck is the artifact that earned you 30 minutes. The 30 minutes is something else.

Before the meeting: the deck goes first

Cold outreach gets the one-page brief, not the deck — see How do I write a cold email to a VC for why attaching a full PDF deck to a cold email is dead.

But once a meeting is on the books, the rule flips. Send the deck. Calendar invite, confirmation email, day-before reminder — whichever channel works. The partner walks in having seen it. They're not evaluating you cold; they're evaluating you in context.

The exception is when the investor explicitly says "I'd rather hear it live first." Rare. Don't assume.

If you walk in and the partner hasn't read the deck anyway, the meeting is broken. Two choices: burn the first 5 minutes walking through the key slides (slow, defensive), or tell them directly — "I think we'd be more efficient if you read the deck first. Want to reschedule?" Founders almost always pick the first one. The second is sharper.

The 5 minutes is your story

Not a pitch. Not a deck walkthrough. Your story.

What that actually means:

Five minutes. Spoken, not read. Specific names, dates, numbers when you have them. The partner is listening for whether you're a founder they want to back — not whether your deck slides are well-designed.

Most founders rehearse the deck and never rehearse the story. The story is what the partner remembers in the partner meeting on Monday.

Then: unpredictable Q&A on four zones

After the story, the partner drives. They'll go deep on whatever they care about most. You can't predict the exact questions. You can predict the zones.

Four zones get probed in nearly every pre-seed meeting:

1. Traction

Whatever number you put in the deck — MRR, users, LOIs, design partners, retention — the partner will dig in. "Walk me through how you got there." Cohort math, channel attribution, repeat rate, when the curve started.

If your traction number doesn't survive a 5-minute deep dive, the meeting is over.

2. Why now

"Why hasn't someone built this already?" and "What changed in the last 12 months that opens this window?" If your why-now is "AI is changing everything" or "this market is huge," you've already lost. You need a specific shift — regulatory, technological, behavioral — that opened the window recently.

3. Team

"Why this team specifically?" Sometimes asked directly. Sometimes disguised as "tell me how you two met" or "what made you decide to start this."

What they're really asking: do you have unfair access, unfair insight, or unfair execution speed on this specific problem? The answer isn't your resume. It's one specific reason you're the right person, deliverable cold.

4. Defensibility / moat

"Why don't bigger, better-funded incumbents just build this?" The structural reason you can take a market they haven't taken.

Wedges that hold up: proprietary distribution, sequence advantage, regulatory access, technical asymmetry, a network nobody else has. Patentability is not a wedge. "Better UX" is not a wedge.

What gets probed less, but still gets asked

Tiebreakers. They don't decide. Weak answers confirm weak feelings.

How to actually prep

Four moves. The first three are the work; the fourth is the test.

  1. Send the deck once a meeting is on the books. Always. (Cold outreach gets a one-page brief, not the deck.) Confirmation email or calendar invite description.
  2. Write your 5-minute story. Not bullet points. A narrative. Practice it cold. Time it. Cut anything that isn't either specific or load-bearing.
  3. For every slide in your deck, prep three levels of answer. Question one is "tell me more about X." Question two is the follow-up after that answer. Question three is the follow-up after THAT. Most founders prep level one and get caught at level two.
  4. Pitch to people who will be brutal. Not supportive friends. Founders who've raised, operators who push back. Take notes on questions you couldn't answer at level three. Tighten those.

What never to do

Four moves that quietly kill the meeting:

FAQ

What if they haven't read the deck?

Ask. "Did you get a chance to look at the deck?" If no, offer to reschedule — or accept that the meeting just got harder and adjust. Don't pretend it doesn't matter.

Should I ever walk through the deck in the meeting?

Only if they explicitly ask you to. Most don't.

What if my story takes 8 minutes?

It's not tight enough. Cut. The 5-minute version is sharper than the 8-minute version. Always.

What if the partner starts asking questions before I finish the story?

Stop the story. Let them drive. They're more interested in their question than the rest of your narrative.

What if they don't ask anything?

Bad sign. Politely end early and move on. Don't fill silence with more pitch.

Should I ask my own questions at the end?

Yes. 2-3 specific ones. Ask about a portfolio company, a recent deal, or what surprised them about a recent investment. Generic "what's your process" wastes the moment.

What if they ask something I genuinely don't know?

"I don't have that number — let me follow up after this" is fine. "I think it's around X" with a wrong number burns credibility.

How do I know if I nailed it?

Asks for next steps unprompted. References specifics from your story when wrapping. "Let me think about it" = you didn't.

Related research

Open raise(fn) — get matched with investors who fund your space.

Open raise(fn) →