📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the clearest breakdown of the two-decks-from-one-file idea, and it teaches with real artifacts, not theory: it puts Uber's 25-slide reader deck next to DoorDash's 10-slide YC demo-day presenter deck so you can literally see how the same story compresses. Read it to calibrate how much text belongs on a slide that gets forwarded versus one you narrate live.
From
VIP Graphics
by VIP Graphics
9 min read
- A reader deck is the story (it stands alone when forwarded); a presenter deck is your sidekick (you are the story in the room)
- Reader decks carry more longform text, detailed charts, and data because there is no narrator and no time limit; presenter decks strip to shortform text and big visuals
- Build the standalone version around detail and self-explanation, then cut it down for the room, not the other way around
Open
vip.graphics →
📄 Article
✓ Link checked
India
Free
Intermediate
Why we picked it
This is a working Indian seed VC (Blume backed Unacademy, Purplle, Slice) writing down what it actually looks for, slide by slide, from the people who read hundreds of Indian founder decks a year. It is blunt about the mistakes that kill decks here: a vague problem statement, a team slide buried too deep, and no customer validation when Blume wants to see the product already live with signups. Use it as the reviewer sitting across the table before you send.
From
Blume Ventures
by Blume Ventures
20 min read
- Nail the specific customer problem and who has it; a fuzzy problem line sinks the deck no matter how good the product
- At seed the team slide is the bet, so lead with founder background and your reason for doing this, do not bury it
- Indian seed investors want customer validation now: product launched, signups coming in, not just a plan
Open
blume.vc →