Quick answer: The solution slide follows the problem slide and answers it with the product. It contains the one-line description of the product, the product visual, and the single workflow that resolves the pain from the previous slide.

The investor's test is direct: does the solution actually solve the problem the previous slide described?

The slide contains

  1. The one-line solution. The product name and the job it does, mapped to the previous problem.
  2. The product visual. A screenshot, an annotated workflow, or a short demo clip.
  3. The before/after. The old workflow and the new one, in one row.
  4. The key workflow. The core path, shown, not described.

The one-line formula

[Product] lets [the customer] do [the job]
without [the old friction].

The line should match the problem slide one-for-one. If the problem slide was about resizing launch images, the solution slide names the same job, not a broader platform.

The visual is the slide

The screenshot is the proof. A solution slide with no visual is a claim; the screenshot makes it real.

  • Show the product in the moment of the workflow.
  • Annotate the steps if the workflow needs them, using the annotation approach.
  • A 10-second demo clip can replace the screenshot if the product is the moment.

Before and after

The most convincing version is a two-panel comparison:

Before: [the old workaround, with the steps].
After: [the product, with the one step].

This frame also shows the founder's understanding of the customer's actual process.

What the slide is not

  • A feature list. The solution is one job, not a menu.
  • A category label. "An AI-powered platform" is not a solution; the workflow is.
  • A duplicate of the product slide. The solution slide is the promise; the later product slide shows the product in detail.

The relationship to the product slide

The solution and product slides split the argument:

  • Solution slide: the one-line answer and the core workflow.
  • Product slide (later): the interface, the depth, the capabilities.

A founder can combine them in a short pre-seed deck, but the one-line answer still has to come first.

Common errors

  • The solution is bigger than the problem. The problem described one pain; the solution claims to fix everything.
  • The screenshot is the homepage. The homepage doesn't show the job; show the workflow.
  • The slide is text-only. The investor needs the visual.
  • The product name appears before the job. State the job first.

Frequently asked questions

Should the solution slide show the product? Yes, with the core workflow or an annotated screenshot. The visual is the proof.

Can the slide be a one-liner? A one-liner with a visual is the cleanest version; the spoken pitch carries the rest.

What if the product is a platform? State the first job it solves; the platform story unfolds later.

How does the slide differ from the product slide? Solution is the promise; the product slide shows the depth and the interface.

Can I generate the slide? The layout and the screenshot composition can be generated; the actual product screenshot must be the real product.

Map the solution sentence to the problem sentence. If the two don't match, the deck is arguing two different companies.

Related guide: the pitch deck guide.