Answer from Damion Hänkejh, Chief Strategy Officer, BOHH Labs and Founder of InstantService, acquired by Oracle
As little as possible in no more than 10-13 slides, including cover/title and contact/disclaimer. I won't read larger decks and often ask entrepreneurs to try harder when they hand me a 20+ page deck.
- Convention/Disruption (20 or fewer words on each)
- Expand on prior slide, use schematics/workflow diagrams
- User experience illustrated
- Team (if you have prior exits, otherwise push this slide to the end of deck)
- Market size, growth rate (use a chart)
- Addressable market opportunity (use another chart)
- Pilots, big customers, or sales pipeline
- Competitor matrix: Grid of four squares with Leader/Follower (or other metric) across the middle and another metric from top to bottom. Where do you and your competitors fall into this space?
- Roadmap: Some past milestones, the present (e.g. we are here), and future milestones (dev, sales, funding)
- Funding: Prior, seeking, form (20% convertible, etc.), and contact (one person)
Most decks are designed for presentations only. This leaves them dead or barely useful when the presenter isn't in the room. Build your deck to live on its own. Every slide should have a title and two very short sentences about the slide content. Taken together, these sentences should stand on their own without slide content and form a narrative across the slides. Pull them out into a bullet list. If you can't read them on their own as a clean, understandable narrative, then you have more work to do.
When presenting, speak about the slide -- do not read the slide to your audience. Slides should have as few words as possible. If you can't articulate your message in short sentences, then you don't understand the topic well enough. It takes time to whittle a message down to its essential parts. Use more graphics than words. View your deck daily and tighten up the prose; pull a word out on every reading. Don't hesitate to pull entire slides out or combine one or more into a single slide using schematics/charts.