Pitch deck basics
How to write the solution slide
Short answer
The solution slide says what the product does in one plain sentence and shows the result for the buyer, with a number where you have one. Use one screenshot or diagram. Lead with the outcome, not the features, and make sure it answers the exact problem on the slide before.
One sentence first
Write the solution as: "We help [buyer] do [job] so that [result]." For example: "We give independent pharmacies a stock system that warns them 60 days before medicines expire, cutting write-offs by more than half."
If the sentence needs the word "platform", "ecosystem" or "AI-powered" to make sense, it is not finished.
Then the result
Investors buy outcomes. Show what changed for a customer:
| Before | After |
|---|---|
| Stock checked by hand once a month | Expiry alerts every morning |
| 9% of revenue written off | 4% of revenue written off |
Use real results from a pilot if you have them, and say how many customers they come from.
One picture
Pick the screen that shows the product doing its job. Crop it. Label the one thing the reader should notice. A grid of six small screenshots communicates nothing.
Match the problem exactly
Read your problem and solution slides back to back. If the problem is expired stock, the solution must be about expired stock. Founders often state a narrow problem and then present a broad product; the investor is left wondering which one is the business.
Say why it is hard to copy, briefly
One line: data you accumulate, an integration that takes months, a cost advantage. The full argument goes on the competition slide.
Mistakes to avoid
- A feature list with no outcome
- Adjectives in place of facts: "seamless", "revolutionary", "end-to-end"
- Three products on one slide. Lead with the one that sells today.
Quick answers
Should I list features?
No more than three, and only those that produce the result. Features belong on the product slide or in a demo.
Do I need a demo in the deck?
A single screenshot is enough. Offer a live demo in the meeting.
How technical should it be?
As technical as a smart outsider can follow. Put architecture in the appendix.