Pitching
How to Build a Useful Pitch Deck Appendix
Turn recurring investor questions into readable backup slides with evidence, limits and a clear boundary between appendix and data room.
What you will learn
- Map follow-up questions to backup evidence
- Separate appendix, main narrative and sensitive records
- Maintain source-linked backup slides that are easy to use
Build a pitch deck appendix by mapping likely investor questions to the smallest useful supporting slide. Each backup slide should answer one question with definitions, evidence and limits. An appendix is not a dumping ground for every document or a substitute for permissioned diligence materials.
Bring your core deck, source records and actual investor questions where available. When questions are anticipated rather than observed, label them that way. Keep the main narrative readable and share sensitive evidence only through an approved process.
Give each backup slide a decision
Write the question first: how was the market estimate built, what changed in the cohort, how does the product handle a particular case, or what assumptions drive the plan? A slide titled “Additional information” has no clear job.
Reid Hoffman’s annotated LinkedIn pitch is a primary example of explaining the reasoning and audience behind a deck. Study the communication choices, not the company’s historical facts as proof for your business.
The existing investor FAQ lesson owns the broader answer register. This lesson converts selected questions into usable presentation evidence.
Decide what belongs where
Route information by its purpose
| Material | Best working location | Reason |
|---|---|---|
| Essential claim qualification | Main slide | Removing it would make the headline misleading. |
| Concise analysis answering a follow-up | Appendix | Supports discussion without interrupting the core story. |
| Detailed confidential records | Approved controlled diligence process | Access and sensitivity require separate review. |
| Unverified idea | Internal research queue | Not ready to present as evidence. |
| Outdated or duplicated chart | Archive outside the active deck | Avoids inconsistent versions. |
Do not put a necessary denominator in the appendix while showing a stronger unqualified claim in the main deck. Supporting detail can move; the meaning of the main claim must remain accurate.
Work an appendix map
Fictional example: SolaceCart is testing a purchasing workflow for specialist retailers. Its founder wants to answer three anticipated questions. The table is an original teaching artifact, not observed investor behavior.
Completed question-to-slide map
| Question | Backup slide | Evidence and limit | Owner |
|---|---|---|---|
| How many reachable buyers exist? | Bottom-up segment calculation | Source-backed customer count, filters and unverified assumptions. | Commercial lead |
| What happened during the trial? | Defined cohort funnel | Invited, attempted and completed events; small sample and dates. | Product lead |
| What changes with the next hire? | Capacity and cash scenario | Approved role timing and dependency assumptions, not guaranteed revenue. | Finance owner |
For the cohort backup, write a headline such as “The trial reveals onboarding friction before the first completed order.” Show the eligible cohort and step counts, then explain what the team is testing. Do not use a polished funnel to conceal missing data.
Give each slide a short identifier so the presenter can reach it quickly. An appendix that is impossible to navigate under questioning is not ready, even if its contents are accurate.
Build and maintain one slide at a time
- Choose an actual or clearly anticipated question.
- Define the answer and the evidence needed.
- Check source, period, units and permissions.
- Build one legible table, chart or explanation.
- Label assumptions and limitations.
- Link back to the core claim it supports.
- Assign an owner and update trigger.
Question / observed or anticipated: [ ]
Core slide supported: [ ]
Backup slide ID and headline: [ ]
One answer: [ ]
Evidence / definition / period / source: [ ]
Limit or unresolved assumption: [ ]
Sharing sensitivity and approval: [ ]
Presenter navigation cue: [ ]
Owner / version / update trigger: [ ]Test the appendix in a rehearsal
Have a teammate interrupt the pitch with the mapped questions. Can you find the right slide without searching through a long deck? Can you give a short answer before opening it? If the question needs legal interpretation, do not improvise from a backup table; route it to the appropriate adviser.
- Every appendix slide answers a distinct question.
- The evidence matches the current main deck.
- Definitions and limits remain readable.
- No unnecessary sensitive records are embedded.
- The presenter can navigate to the right proof.
Use the market-sizing worksheet or pre-revenue evidence pack when building those specific backups. Keep detailed diligence files in their established process.