How to Run a Pitch Feedback Session That Actually Helps Founders

Pitch feedback sessions are one of the most common formats in accelerator programs — and one of the most frequently wasted.

The typical session looks like this: a founder pitches for five minutes, a panel of mentors and judges responds for twenty, and the founder leaves with a mix of conflicting opinions, some genuine insights, and a vague sense that they need to "tighten things up."

The feedback isn't wrong, exactly. But it's rarely organized in a way that translates into specific deck improvements. And because different judges have different frames of reference, the advice is often contradictory — leaving founders to reconcile irreconcilable opinions on their own.

Here's how to run pitch feedback sessions that actually work.

Step 1: Send the Deck 48 Hours Before the Session

One of the biggest sources of waste in pitch feedback sessions is that judges are seeing the deck for the first time when the founder presents it.

Without pre-reading, judges spend their cognitive bandwidth understanding the business model while the founder is trying to get feedback on narrative structure. Observations end up being reactive — what the judge noticed on first exposure — rather than analytical.

When judges read the deck ahead of time:

• They come with specific questions, not general impressions
• Feedback is more targeted (slide-level, not just overall)
• The pitch session itself can move faster, because judges already understand the fundamentals
• Q&A is more realistic — judges can simulate investor questions they'd genuinely ask

Practical note: Use a structured assessment tool to score the deck before the session. Share the scores with judges, not just the deck. This gives the panel a common reference point and helps them prioritize which dimensions to probe.

Step 2: Assign Roles to Judges Before the Session Starts

Generic panels produce generic feedback. When everyone is responsible for everything, responsibility is distributed so broadly that no one goes deep on anything.

Assign specific roles to each judge:

• Problem/Solution judge: Is the problem specific and painful? Does the solution address the stated problem? Is the differentiation real?
• Market judge: Is the market sizing defensible? Is the segment clearly defined? Is the growth thesis believable?
• Business model judge: Does the revenue model hold up? Are unit economics implied by the deck internally consistent?
• Team/execution judge: Does the team have the background to execute? What are the execution risks?
• Investor skeptic: Play the role of a skeptical investor — probe the weaknesses, push back on assumptions, ask the questions investors will ask

This role assignment should match the judge's actual background. A former operator makes a better execution judge than a VC with no operating experience. Play to your panel's strengths.

Step 3: Structure the Pitch Session Itself

The most effective pitch feedback sessions I've seen follow a tight structure:

5 minutes: Founder pitches (no interruptions) 2 minutes: Judges write down their top observation per assigned role (no verbal feedback yet) 10 minutes: Judges share observations in role order, structured as: "Here's what I saw, here's the question I'd have as an investor" 5 minutes: Founder responds and asks clarifying questions 3 minutes: Judges identify the single most important thing to fix (forced prioritization)

The "judges write first" step is critical. It prevents the common dynamic where the first judge to speak anchors the entire conversation and everyone else responds to their framing.

The "forced prioritization" at the end is equally important. Every founder knows their deck has problems. What they need is to know which problem to fix first — not an unranked list of everything that could be better.

Step 4: Use Objective Data to Anchor Subjective Feedback

One of the most common failure modes in pitch feedback is the opinion spiral. One judge says the market slide is too thin. Another says the traction metrics are the real problem. A third thinks the problem framing is confusing. The founder doesn't know which observation to weight.

Objective deck scores short-circuit this. When you enter the session with a structured assessment showing that a founder's Market score is 48 and their Problem score is 71, you have a shared reference point. The market analysis is the priority — not because one judge said so, but because a consistent rubric said so.

This doesn't eliminate subjective judgment — it focuses it. Judges who agree that market sizing is the priority can spend their time being specific about what "better market sizing" actually looks like, rather than debating which problem is most important.

In practice: Start every session by sharing the founder's scores by dimension. Tell judges: "This founder's two lowest scores are X and Y. Let's make sure those get addressed today."

Step 5: End with Three Actionable Changes, Not General Impressions

Most pitch feedback sessions end with the equivalent of "great work, here are some things to think about." Founders leave without a clear picture of what to do Monday morning.

End every session with a documented list of exactly three things:

1. The single most important structural change — usually about story architecture, market framing, or problem clarity
2. The single most important content addition — a metric, a slide, a reference point that's currently missing
3. The single most important thing to cut or simplify — pitch decks are almost always too complex; something needs to go

Three is the right number. More than three and founders prioritize inconsistently. Fewer than three and the session feels incomplete.

Assign someone (not the founder) to write these down and send them within 24 hours of the session. Founders are processing a lot in the room — having a written record removes ambiguity about what was decided.

Common Mistakes to Avoid

Running feedback sessions before decks are structurally ready. If the deck has a fundamental narrative problem — the solution doesn't match the problem, or the market framing is wrong — no amount of delivery coaching will fix it. Use a structured deck score to verify the deck is at a minimum viable level before running a feedback session. A score of 60+ on core dimensions is a reasonable bar.

Letting one judge dominate. Senior advisors with strong opinions can anchor the entire panel's feedback. Role assignment and a structured format prevent this. So does the "write first" rule.

Conflating delivery feedback with deck feedback. "You seemed uncertain about your market size" is delivery feedback. "Your market size calculation doesn't account for the addressable segment you actually target" is deck feedback. Both matter — but they require different fixes and should be separated.

Giving feedback on every slide. This is the most common mistake. If judges comment on every slide, founders treat every slide as equally important. They improve everything by 5% instead of improving the two critical things by 50%. Force prioritization every time.

Running feedback sessions without a follow-up mechanism. Feedback that isn't acted on is feedback that was wasted. Build in a check-in two weeks after every session: did the founder make the three changes? If not, why not?

A Note on Written vs. Verbal Feedback

Many founders find written feedback more useful than verbal feedback — but most programs default to verbal-only sessions.

Written feedback is more specific (you have to commit to a sentence), more reviewable (you can re-read it when you're actually making changes), and less susceptible to the in-room dynamics that distort verbal sessions.

Consider adding a written component to every feedback session: judges submit a brief written summary of their top two observations before or after the verbal session. This creates a record that founders can reference while revising, and it forces judges to be more precise than verbal feedback typically demands.

Building a Feedback Culture

The programs that get the most out of pitch feedback sessions are the ones that treat feedback as a skill — both for the judges and the founders.

Judges improve at giving specific, prioritized, actionable feedback when they run many sessions with a consistent structure. Founders improve at receiving feedback when they understand that the goal is to identify the two or three things that matter most, not to validate what they've already built.

That culture takes time to build. But once it exists, the quality of every session — and the quality of every deck — improves in kind.