# Founder Deck Feedback Framework

Accessed: 2026-06-18

Purpose: define how the deck review product should give useful feedback to a founder after they upload a fundraising deck.

This is not a generic "perfect pitch deck" checklist. The product should behave like a thoughtful investor/operator reviewing the deck for a specific round, category, and founder context. Good feedback should help the founder get more meetings, answer investor objections faster, and preserve the company's strongest authentic story.

## Two Deck Types

The product has two separate deck objects and should never blur them:

| Deck type | Uploader | Visibility | Primary score | Product rule |
|---|---|---|---|---|
| Founder pitch deck | Founder or reviewer | Private | Investor Readiness Score | Used for feedback on the founder's own pitch deck. It should not become part of the public reference library by default. |
| Public reference deck | Admin only | Public | Reference Value Score | Used as a benchmark library asset. It requires admin curation, source review, company research, and publication approval. |

Founder pitch decks are scored on how well they earn the next investor conversation and what feedback will improve them. Public reference decks are scored on how useful they are as comparables: later fundraising, current company status, headcount trend, source quality, reusable slide patterns, and which claims aged well or poorly.

## Reference Deck Qualification Gate

The public reference library and the feedback retrieval dataset are not the same thing. A company can have a public profile for research while still being blocked from positive comparable-slide recommendations.

Before a reference deck can influence founder feedback, it needs to clear two outcome gates:

1. Successful round or venture outcome after the deck.
   - Strong pass: verified follow-on seed, Series A, Series B, acquisition with clear positive signal, or multiple later rounds.
   - Weak pass: some credible financing or outcome evidence, but details are incomplete.
   - Fail: only the deck ask or pre-existing financing is verified.

2. Sustainable company signal after the deck.
   - Strong pass: active company with growing/stable headcount, hiring, expanding customers, retail footprint, revenue, or product activity.
   - Weak pass: active company, but headcount or operating momentum is mixed.
   - Fail: shut down, inactive, materially lowering headcount, or no active operating footprint.

### Dataset Statuses

| Status | Meaning | Product behavior |
|---|---|---|
| qualified_core | Strong post-deck funding/outcome and strong current operating signal. | Use by default for comparable-slide recommendations. |
| qualified_with_caution | Good outcome evidence, but one signal is mixed or needs explanation. | Use only when the caution is visible and the pattern is directly relevant. |
| case_study_only | Useful for research or lessons learned, but not a clean positive benchmark. | Do not use as a positive comparable; use only for cautionary analysis. |
| hold_until_verified | The company may qualify, but funding/headcount/status research is incomplete. | Do not use until verified. |
| excluded | Failed the funding or sustainability gate. | Do not use for positive comparable slides. |
| research_pending | Profile exists, but qualification research is incomplete. | Do not use for feedback retrieval. |

### Hard Bar For Feedback Retrieval

Do not use a company as a positive slide comparable if:

- It did not raise more money after the deck and has no other strong venture outcome.
- It is shut down, inactive, or cannot be verified as operating.
- It is lowering headcount or shows material contraction without a credible recovery signal.
- Its strongest deck claims aged poorly or were contradicted by later public evidence.
- The source confidence is too low to connect the deck to the later outcome.

This means a company can raise a major round and still be excluded from positive retrieval if the durability signal is poor. Conversely, a company with a modest financing history can be held back until the operating evidence proves it is a sustainable benchmark.

## Core Research Synthesis

The strongest external guidance converges on five ideas:

1. Investors scan quickly, so the deck must be understandable almost immediately.
   - DocSend says investors spend less than 3.5 minutes on average with each pre-seed deck, and that the deck's job is to get the meeting, not close the investment.
   - Silicon Valley Bank quotes investors emphasizing that the first slide should quickly tell them what the company is about.

2. Every slide should answer an investor question.
   - Sequoia's framework is organized around company purpose, problem, solution, why now, market, competition, product, business model, team, financials, and vision.
   - NFX frames pitch quality as understanding the investor's state of mind.

3. Feedback has to be stage-aware.
   - Pre-seed feedback should tolerate uncertainty but punish confusion.
   - Seed feedback should press on proof, velocity, GTM, business model, and founder-market fit.
   - Series A feedback should press on repeatability, metrics quality, retention, sales efficiency, and the next stage of scale.

4. The most valuable feedback identifies the objection behind the slide.
   - First Round's partner-meeting guidance emphasizes that founders should prepare for deeper questions, know their numbers, and practice being interrupted.
   - The product should surface those likely investor questions explicitly.

5. Feedback should improve the next pitch, not merely judge the current deck.
   - NFX recommends treating investor questions and feedback as a learning loop, even suggesting founders change at least one thing after every meeting.
   - Roy Bahat / Bloomberg Beta warns that pitch advice can backfire when given without understanding the company, so feedback should be transparent about assumptions and uncertainty.

## Feedback Principles

### 1. Start With The Fundraise Job To Be Done

The product should infer and state the deck's likely job:

- Cold outbound teaser deck
- Warm intro meeting deck
- Live presentation deck
- Follow-up/data-room deck
- Partner meeting deck
- Internal memo support deck

Feedback should change based on job:

| Deck job | Good feedback optimizes for |
|---|---|
| Cold outbound | Immediate comprehension, sharp one-liner, strongest proof early, low slide count, visual scanability. |
| First investor meeting | Story arc, problem urgency, differentiated product, founder credibility, investor curiosity. |
| Follow-up deck | Objection handling, metrics quality, GTM details, cohort data, competitive detail, use of funds. |
| Partner meeting | Narrative control, hard-question readiness, numbers fluency, "why this can be huge" clarity. |

### 2. Give A Diagnosis Before Prescribing Edits

The founder should first understand what the deck currently makes an investor believe.

Recommended opening structure:

1. What is already working
2. What an investor likely understands after 60 seconds
3. What is still unclear or unproven
4. The top 3 fixes that would most improve meeting conversion
5. Slide-level notes
6. Comparable slide recommendations

### 3. Separate Four Feedback Types

The product should label feedback so founders can act without confusion.

| Feedback type | Meaning | Example |
|---|---|---|
| Clarity | The investor cannot quickly understand it. | "Slide 1 does not say who the customer is or what the product replaces." |
| Evidence | The claim may be right, but the deck does not prove it. | "You say CAC is efficient, but there is no payback period, channel mix, or timeframe." |
| Narrative | The order or emphasis weakens the story. | "The deck explains features before the pain is urgent." |
| Fundraising risk | The slide creates a diligence concern. | "The forecast triples revenue without showing the growth driver or hiring plan." |

### 4. Use Founder-Safe, Direct Language

The tone should be candid but non-destructive. Avoid vague praise and vague criticism.

Bad:
- "This slide is weak."
- "Make this more compelling."
- "Investors will not like this."

Better:
- "The slide has the right ingredients, but it does not yet answer the investor question: why does this problem need a venture-scale company now?"
- "Keep the metric, but add the timeframe and denominator so the traction reads as momentum rather than a vanity number."
- "This claim may be true, but without a source or customer proof it will trigger diligence instead of confidence."

### 5. Preserve Founder Voice

The feedback should not flatten every company into a template. It should identify the company's strongest "reason to believe" and help the founder make that unavoidable.

Common reasons to believe:

- Founder-market fit
- Non-obvious customer insight
- Speed of execution
- Unusual distribution advantage
- Technical breakthrough
- Regulatory or platform shift
- Strong early retention
- Category-defining brand
- Compounding marketplace/network effects
- Proprietary data or workflow lock-in

## Investor Questions The Feedback Must Answer

The best feedback maps each deck issue to an investor question:

| Investor question | Deck evidence that answers it |
|---|---|
| What does this company do? | Plain-English one-liner, customer, product, use case, screenshot/demo. |
| Why does this matter? | Urgent problem, customer pain, current workaround, budget or behavior evidence. |
| Why now? | Market, platform, regulation, consumer behavior, cost, or technology shift. |
| Why this solution? | Product workflow, differentiated wedge, customer proof, demo, before/after. |
| Is this big enough? | Market logic, wedge market, expansion path, bottom-up math, comparable outcomes. |
| Is there proof of demand? | Revenue, users, pilots, LOIs, retention, usage, waitlist conversion, reviews, sales cycle. |
| Can growth scale? | GTM channels, CAC/payback, sales motion, retail or partner pipeline, referrals, loops. |
| Can the business make money? | Pricing, margins, unit economics, contribution margin, gross margin, take rate, payback. |
| Why will this company win? | Competition, defensibility, distribution, product advantage, team edge. |
| Why this team? | Specific accomplishments tied to this problem, domain access, execution velocity. |
| What happens after the round? | Raise amount, use of funds, milestones, runway, next proof points. |
| What could kill this? | Honest risks, mitigations, missing proof, regulatory or operational exposure. |

## Stage-Aware Feedback

### Pre-Seed

Primary goal: make the idea impossible to misunderstand and credible enough for a meeting.

What to reward:

- Clear customer and pain
- Founder-market fit
- Specific early customer discovery
- Prototype, demo, waitlist, pilots, LOIs, or early usage
- Non-obvious insight
- Transparent market math
- Clear next milestones

What to flag:

- Jargon in the first two slides
- No concrete customer
- Product before problem
- Market-size theater without wedge logic
- Fake precision in forecasts
- Weak team slide made only of titles
- Too many possible business models

### Seed

Primary goal: prove momentum and a plausible path to repeatable growth.

What to reward:

- Traction with timeframe
- Early retention or repeat behavior
- Revenue quality or usage quality
- GTM learning by channel
- Pricing and business model clarity
- Team accomplishments tied to category
- Use of funds tied to milestones

What to flag:

- Cumulative metrics without velocity
- Vanity users without activation or retention
- CAC claims without payback or channel context
- Competitive slide that ignores direct alternatives
- Forecasts that do not connect to GTM plan
- Raise slide that only says "hiring and marketing"

### Series A

Primary goal: prove repeatability, efficiency, and readiness to scale.

What to reward:

- Cohorts and retention
- Sales efficiency or payback
- Expansion revenue / NRR where relevant
- Repeatable GTM motion
- Pipeline quality and conversion
- Strong operating plan
- Evidence that the seed wedge can become a large company

What to flag:

- Growth without quality
- No segmentation by customer type or channel
- Big ARR/revenue number with unclear gross margin
- No churn or retention view
- No explanation of why the next capital unlocks step-change scale

## Category-Specific Feedback Checks

### Consumer Products / DTC

Check:
- Gross margin, contribution margin, payback, repeat purchase, cohort behavior.
- Channel mix: paid social, wholesale, retail, affiliate, marketplace, community.
- Inventory, payment terms, cash conversion cycle, supply chain resilience.
- Brand proof: reviews, organic reach, press, creator/community, waitlist conversion.
- Retail status: signed, launched, LOI, discussion, pipeline.

Good feedback example:
"The retail pipeline slide is promising, but it mixes live partners, discussions, and aspirational targets. Split it into launched, signed/not launched, LOI, and target pipeline so investors know what proof exists today."

### SaaS / B2B

Check:
- ICP clarity, buyer vs user, sales cycle, ACV, pipeline, churn, NRR, activation.
- Product proof: screenshots, workflows, before/after, integrations.
- GTM motion: founder-led sales, PLG, outbound, channel, enterprise.
- Security/compliance requirements if enterprise.

Good feedback example:
"The traction slide says 20 customers, but it does not show whether those are pilots, paid contracts, or annualized ARR. Add ACV, conversion from pilot to paid, sales cycle, and expansion signal."

### Marketplace

Check:
- Supply and demand density, liquidity, repeat usage, take rate, geographic focus.
- Which side is harder and why.
- Trust/safety, payments, quality control.
- Chicken-and-egg wedge.

Good feedback example:
"The GMV number is useful, but marketplace investors will ask whether liquidity is improving. Add searches-to-bookings, time-to-match, repeat rate, and supply utilization."

### Consumer App / Social

Check:
- Retention, frequency, DAU/MAU, creator/user loops, acquisition source, community dynamics.
- Evidence that usage is habitual, not novelty.
- Why a platform cannot copy it.

Good feedback example:
"The user count is less important than whether people come back. Add D1/D7/D30 retention, sessions per active user, and the behavior that creates a loop."

### Deep Tech / AI

Check:
- What works today, what is demo-only, what remains R&D.
- Benchmark quality, evaluation method, customer workflow, deployment constraints.
- Data advantage, technical moat, integration path.
- Why now: model cost, capability shift, regulation, infrastructure.

Good feedback example:
"The product slide says 'agentic automation,' but the investor cannot see the workflow. Show the input, the autonomous steps, the human review point, and the measurable output improvement."

## Slide-Level Feedback Schema

Each slide should receive structured feedback:

| Field | Description |
|---|---|
| slide_number | Slide number from deck. |
| slide_title | Detected or inferred title. |
| slide_type | Problem, product, traction, GTM, competition, team, financials, ask, etc. |
| investor_question | The question this slide should answer. |
| current_strength | What works now. |
| issue | The highest-priority problem. |
| severity | Must fix, should fix, nice to have. |
| evidence_needed | Data, proof, source, screenshot, customer quote, cohort, etc. |
| suggested_edit | Specific edit or rewrite. |
| comparable_pattern | Comparable slide pattern from training library. |
| founder_action | Concrete next step. |

## Overall Feedback Output Format

The MVP should produce:

1. Executive diagnosis
   - One paragraph on the deck's current fundraise readiness.
   - Mention inferred stage, deck job, and category.

2. What is working
   - 3 to 5 strengths grounded in slide numbers.

3. Top fixes
   - 3 to 5 ordered fixes with expected investor impact.

4. Investor questions still unanswered
   - The likely questions a VC will ask after reading.

5. Slide-level feedback table
   - One row per slide.

6. Suggested rewrite examples
   - Rewrite the one-liner, one problem slide title, one traction slide title, and one ask/use-of-funds slide if present.

7. Comparable slide recommendations
   - Recommend specific slide patterns from similar companies.
   - Explain why each comparable is relevant and what not to copy blindly.

8. Data room / appendix suggestions
   - Metrics, customer proof, financials, contracts, technical docs, regulatory docs, or cohort charts.

9. Next revision plan
   - A short action plan: fix now, test in calls, add later.

## Severity Framework

| Severity | Meaning | Product behavior |
|---|---|---|
| Must fix | Likely prevents investor from understanding or believing the company. | Put in top fixes and slide feedback. |
| Should fix | Creates a meaningful objection but may not block the meeting. | Include in slide-level notes and next revision plan. |
| Nice to have | Would improve polish or persuasion but is not core. | Keep concise; avoid overwhelming founder. |

## Scoring Rubric

Use a 1 to 5 score for each dimension, but do not overemphasize the numeric score. The explanation matters more.

| Dimension | What 5 Looks Like |
|---|---|
| Clarity | Investor understands company, customer, product, and value prop in the first 30 to 60 seconds. |
| Problem urgency | The pain is specific, costly, frequent, or strategically important. |
| Solution/product | The deck shows what the product does and why the approach is better. |
| Market and timing | The market is large or expandable, and why-now is credible. |
| Traction/momentum | Metrics include timeframes, quality, and proof of acceleration. |
| GTM/distribution | The company has a believable path to reach customers efficiently. |
| Business model | Pricing, margins, payback, or monetization path are understandable. |
| Competition/defensibility | The company knows true alternatives and explains why it can win. |
| Team | The team has specific advantages for this problem. |
| Fundraise plan | Ask, use of funds, runway, and milestones are tied together. |
| Narrative flow | Slides build conviction in the right order. |
| Design/readability | Slides are scanable, consistent, and not overburdened. |

## Feedback Language Templates

### Clarity

"Right now, the slide makes the reader work too hard to understand [X]. Rewrite it so the investor can answer this in five seconds: [investor question]."

### Evidence

"The claim is directionally useful, but it needs proof. Add [metric/source/customer/example] so this reads as evidence rather than assertion."

### Narrative

"This is the right point, but it appears too early/late. Move it after [slide] because the investor first needs to believe [prior premise]."

### Metrics

"Keep the metric, but add timeframe and denominator. '[metric]' is much stronger as '[metric] over [timeframe] from [base], among [customer segment].'"

### Competition

"The slide should not imply there are no competitors. It should show that you understand the real alternatives and have a specific wedge against them."

### Team

"Replace title-based credibility with founder-market-fit proof. The question is not 'where did you work?' but 'why are you unusually likely to win this market?'"

### Ask

"The ask should connect capital to milestones. Instead of only saying how the money is spent, say what will be true about the business before the next raise."

## Product Behavior Rules

1. Do not rewrite the entire deck by default. Prioritize the highest-leverage changes.
2. Do not punish missing data that is unrealistic for the stage. Instead, ask for the next credible proof point.
3. Do not call a deck "bad." Describe the investor comprehension or belief gap.
4. Do not treat templates as law. Explain when a missing slide is actually a problem.
5. Do not invent performance benchmarks. If benchmarking is uncertain, say what data is needed.
6. Do not recommend copying another company's slide wholesale. Recommend the pattern, not the exact claim.
7. Always separate deck-time claims from external validation.
8. Always flag claims that require substantiation: medical, legal, regulatory, financial, health/safety, scientific, environmental, or investment-return claims.
9. For consumer brands, separate brand heat from repeat purchase and product quality.
10. For AI companies, separate demo capability from production deployment and measurable customer value.

## How The Product Should Use Comparable Slides

Comparable slide recommendations should include:

| Field | Description |
|---|---|
| Comparable company | Company name. |
| Benchmark status | qualified_core or qualified_with_caution only. |
| Slide number/title | Specific slide from reference deck. |
| Pattern | The transferable lesson. |
| Why relevant | Similar stage, category, GTM, metric, or investor objection. |
| Outcome basis | Why this company is allowed to be used as a benchmark. |
| Caution if any | Any mixed signal that should not be copied blindly. |
| What to copy | Structure, evidence type, chart logic, or story move. |
| What not to copy | Company-specific claims, outdated market data, inflated tone, or irrelevant metrics. |
| Suggested founder adaptation | How to apply the pattern to the uploaded deck. |

Example:

"Caraway slide 18 is a useful comparable if the uploaded company is a physical consumer brand claiming omnichannel distribution. Copy the pattern of grouping channels with named partners and revenue logic. Do not copy the specific partner names or revenue assumptions. Adapt it by separating live, signed, LOI, and target partnerships."

Retrieval rule:

1. First filter to `qualified_core` companies.
2. Match on stage, category, business model, slide type, and investor objection.
3. Use `qualified_with_caution` only when the caution is visible in the recommendation.
4. Never use `excluded`, `case_study_only`, `hold_until_verified`, or `research_pending` as positive examples.

## Source Notes

- Sequoia Capital, "Writing a Business Plan": company purpose, problem, solution, why now, market potential, competition, business model, team, financials, and vision. https://sequoiacap.com/article/writing-a-business-plan/
- DocSend, "Here's how to create a pre-seed pitch deck that gets you funded": investors spend less than 3.5 minutes on average on pre-seed decks; deck should get the meeting; problem and narrative matter. https://www.docsend.com/blog/pre-seed-pitch-deck-guide/
- DocSend, "How to Nail the 3 Most Scrutinized Sections in Your Pre-Seed Pitch Deck": product readiness, business model, and competition received more investor scrutiny in the 2020 dataset. https://www.docsend.com/blog/how-to-nail-the-3-most-scrutinized-sections-in-your-pre-seed-pitch-deck/
- DocSend, "As VC focus shifts...": competitive landscape, product readiness, and business model became more scrutinized. https://www.docsend.com/blog/how-your-pitch-deck-can-shine-as-vc-focus-shifts/
- Silicon Valley Bank, "How to create a pitch deck": concise, precise, and intriguing; first slide should quickly establish what the company is about; narrative and simplicity matter. https://www.svb.com/startup-insights/startup-strategy/how-to-create-investor-pitch-deck-vc-angels/
- First Round Review, Liz Wessel, "Here's What You Can Really Expect When Pitching Your Seed-Stage Startup at a VC Partner Meeting": prepare for specific questions, know numbers, manage interruptions, ask point partners for feedback, and practice both short and long versions. https://review.firstround.com/heres-what-you-can-really-expect-when-pitching-your-seed-stage-startup-at-a-vc-partner-meeting/
- NFX, "The Non-Obvious Guide to Fundraising": rehearse, collect feedback, learn from investor questions, and change at least one thing after each meeting. https://www.nfx.com/post/the-non-obvious-guide-to-fundraising
- NFX Pitch Deck Library: evaluate decks from the investor's mind and focus on best-in-class patterns. https://www.nfx.com/post/the-nfx-pitch-deck-library
- Roy Bahat / Bloomberg Beta, "Our most frequent comments on pitch decks": avoid giving advice without context; focus on the specific reason to believe, team slide message, metric quality, and burn/milestones. https://also.roybahat.com/our-most-frequent-comments-on-pitch-decks-27281bb8f9f6