Pitching
How to Build a Send-Ahead Pitch Deck
Edit a live presentation into a readable investor deck with enough context, accurate evidence and a tested independent reading path.
What you will learn
- Identify narration that must become visible context
- Create a concise self-contained reading deck
- Test the exported deck without explaining it
Build a send-ahead pitch deck by replacing the context you normally say aloud with concise explanations the reader can understand independently. Keep the argument clear, evidence labeled and next step easy to find. Do not solve missing context by pasting a speech onto every slide.
Start with the current approved deck, its source notes, the intended recipient and permission to share. This lesson edits a deck for independent reading. It does not repeat the teaser-versus-deck sharing decision or the full slide outline.
Decide what a reader needs without you
YC’s seed-fundraising guide describes a coherent leave-behind. Use that communication principle, not its historical market numbers. An independent reader needs the customer, mechanism, evidence status, business logic and reason to continue without a live explanation.
List the clarifications you usually provide aloud: metric definitions, development status, time periods, diagram meaning, customer segment and what the ask funds. Those are candidates for concise visible context. Confidential supporting detail is not automatically appropriate just because the reader is absent.
Edit in a deliberate sequence
- Write the intended reader and next decision.
- Check the headline-only sequence for a coherent story.
- Add only missing interpretive context beside the relevant evidence.
- Label current product, prototype and roadmap.
- Replace unexplained charts with titles, axes, units, dates and source notes.
- Move useful but nonessential detail into a reviewed appendix.
- Export and test the actual file on a laptop and phone.
Use plain language and avoid unexplained acronyms. A person forwarding the deck should not have to invent the explanation that connects your slides.
Work a live-to-reading revision
Fictional teaching case: ParcelLane’s live slide has a screenshot and “Pilot:18.” The founder normally explains that 18 invited coordinators were offered access,10 tried the prototype and 6 completed the defined dispatch task in September. No one has paid.
Completed send-ahead edit
| Element | Live draft | Independent-reading version |
|---|---|---|
| Headline | Pilot:18 | Six coordinators completed the dispatch task in September. |
| Definitions | Spoken only | 18 invited;10 tried;6 completed. Prototype trial, no revenue. |
| Screenshot | Unlabeled view | One annotated synthetic example showing the task’s input and outcome. |
| Interpretation | Founder’s narration | “We are investigating why four trial users did not finish.” |
| Next step | Verbal close | Current contact and requested follow-up conversation. |
The reading version does not call 18 people customers or imply 6 retained users. It explains the observed step. All figures are fictional teaching inputs, not a Finta result.
The slide can remain concise because each added sentence resolves a specific ambiguity. Put full methodology in the appendix if needed, but keep the qualification that prevents a misleading headline visible.
Run a no-narration test
Give the exported deck to a reviewer unfamiliar with the company. Do not provide a tour. Ask them to explain the customer, product, current evidence, unknowns and next step. Then ask which slide made them guess.
Completed cold-read issue log
| Observed confusion | Revision | Check |
|---|---|---|
| “18 paying users?” | Add invited/tried/completed definitions and no-revenue label. | Reader distinguishes the funnel. |
| “The screenshot is live customer data?” | Label synthetic demonstration. | Reader understands evidence type. |
| “What should I do next?” | Add the relevant contact and conversation request. | Reader can find the next action. |
Do not claim a tiny reader test predicts investor conversion. It identifies communication failures in the file you actually intend to send.
Copy the release checklist
Audience / context / next decision: [ ]
Approved deck version and owner: [ ]
Headline sequence reads independently: [ ]
Spoken context added where necessary: [ ]
Metrics / dates / units / sources: [ ]
Current / prototype / roadmap labels: [ ]
Sharing permissions / sensitive details removed: [ ]
Appendix and source links checked: [ ]
Export / phone / laptop readability: [ ]
Cold-reader confusion and fixes: [ ]
Contact / next conversation: [ ]Check that links work for the intended recipient rather than only in your logged-in session. Keep one approved version and record what was shared. If you track views, use the deck analytics guide: a recorded open is not proof that the person understood the story or intends to invest.