> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/channels/product-demo/opening-visual.md).

# Opening Visual

How to create the opening visual for a Product Demo: gather source screenshots, prompt an image tool, and set the result on your demo.

The opening visual is the first thing a prospect sees when a demo starts, before the agent says a word. It holds the screen during the few seconds where a visitor decides whether to stay, so it is worth treating as a title slide for the demo rather than as decoration.

A good opening visual answers one question immediately: what is this company, and what am I about to be shown? This page covers how to produce one with an AI image tool and how to put it live on your demo. For everything else about the channel, see [Product Demo](https://docs.spara.com/build/channels/product-demo.md).

## What makes a good opening visual

The best results come from treating the slide as a piece of brand collateral, not a copy of your website:

* **One logo, shown exactly as it appears in your brand assets.** No redrawing, no recoloring.
* **One headline**, usually the positioning line already on your homepage.
* **One product visual** that shows what the product actually does.
* **A restrained amount of customer proof**, such as three or four logos or a single rating.
* **No website chrome.** No navigation bars, buttons, forms, cookie banners, or calls to action. A prospect cannot click them, and they make the slide look like a screenshot instead of a slide.

Design for 16:9. The demo scales the image to fit the stage without cropping it, and the stage is wide, so a 1920 x 1080 image fills the space. A square or portrait image is shown with empty space on either side.

## Gather your source screenshots

Image tools blend their reference images together by default. If you attach four screenshots and say "use these as source material," the model averages them and you get a generic slide with an approximated logo. The fix is to tell the model which screenshot owns which part of the output.

Collect at least four screenshots, each one the authoritative source for a different element:

1. **Logo or brand mark.** Crop tight on the logo, from your site header or brand page.
2. **Hero messaging.** The top of your homepage, with the headline and supporting copy readable.
3. **Product or visual system.** The clearest shot of the real product UI, an architecture diagram, or a key workflow.
4. **Customer proof.** The customer logo strip, a testimonial, or a ratings badge.

Add more screenshots if you want the model to pick up secondary brand colors, iconography, textures, photography treatment, or spacing patterns. To capture clean screenshots of your own product, use the [Spara Scanner](https://docs.spara.com/build/channels/product-demo/spara-scanner.md) Chrome extension.

## Write the prompt

Use an image generation tool that accepts several reference images in one prompt. The prompt itself has two parts: the run block changes for every company and goes first, and the standard instructions stay the same every time and go underneath. Attach the screenshots to the same message, in the order the run block names.

### The run block

Edit this for the company you are building the demo for:

```
COMPANY: [company name]

HEADLINE SOURCE: Screenshot 2
PRODUCT VISUAL SOURCE: Screenshot 3
LOGO SOURCE: Screenshot 1
CUSTOMER LOGOS SOURCE: Screenshot 4

PRIMARY VISUAL IDEA:
[one sentence naming the steps the product moves a user through, in order]

BRAND CHARACTER:
[background tone, typography color and weight, accent color, overall design feel]

DO NOT INCLUDE:
Buttons, navigation, forms, website chrome, CTAs.
```

Two fields do most of the work. **PRIMARY VISUAL IDEA** is what keeps the slide from being a logo on a gradient: it tells the model what story the product visual should tell. **BRAND CHARACTER** is what keeps the result from defaulting to generic SaaS blue.

The source lines are the attachment order you actually used, so you do not have to reorder your screenshots to match the standard instructions. If the run block and the standard mapping disagree, the run block wins.

### The standard instructions

Paste this underneath the run block, unchanged:

```
Create a single title slide for a product demo.

OUTPUT
- One 16:9 image, 1920 x 1080.
- A title slide, not a web page.
- Legible at a glance: one headline, one product visual, minimal supporting copy.

## Source Screenshot Mapping

Use every attached screenshot intentionally. Treat the screenshots as separate
sources for different parts of the final slide rather than as layouts to reproduce.

[Screenshot 1 - Logo / Brand Mark]
Use this as the authoritative source for:
- company logo
- logo proportions
- primary brand colors

[Screenshot 2 - Hero Messaging]
Use this as the authoritative source for:
- headline
- supporting copy
- primary positioning
- typography character

[Screenshot 3 - Product / Visual System]
Use this as the authoritative source for:
- product UI
- product architecture
- key workflows
- illustrations or photography
- visual motifs

[Screenshot 4 - Customer Proof]
Use this as the authoritative source for:
- customer logos
- trust statement
- ratings or proof points, if useful

[Additional Screenshots]
Use these to understand:
- secondary brand colors
- UI styling
- textures
- photography treatment
- gradients
- iconography
- spacing and composition patterns

PRIORITY RULES
1. Preserve the logo and brand identity exactly from the supplied screenshots.
2. Preserve the core headline and message unless explicitly instructed to rewrite it.
3. Use product visuals to explain what the company actually does.
4. Use only a restrained subset of customer proof.
5. Do not copy the website layout itself.
6. Resolve conflicts by favoring the screenshot that most directly represents that element.
7. If the run block above names a different screenshot for an element than this
   mapping does, follow the run block.
```

### Example: a PandaDoc run block

```
COMPANY: PandaDoc

HEADLINE SOURCE: Screenshot 2
PRODUCT VISUAL SOURCE: Screenshot 4
LOGO SOURCE: Screenshot 1
CUSTOMER LOGOS SOURCE: Screenshot 3

PRIMARY VISUAL IDEA:
Agreement creation, then fillable fields, then signature, then completed deal.

BRAND CHARACTER:
Warm off-white, dark charcoal typography, restrained PandaDoc green, clean
editorial B2B design.

DO NOT INCLUDE:
Buttons, navigation, forms, website chrome, CTAs.
```

## Check the result before you use it

Most first attempts are close but need one correction. Look for these:

* **The logo is redrawn, recolored, or slightly wrong.** Re-attach the logo screenshot on its own and repeat that it must be preserved exactly.
* **Navigation, buttons, or a browser frame appeared.** Repeat the DO NOT INCLUDE line.
* **The slide is a copy of your homepage.** Repeat priority rule 5 and describe the composition you want instead.
* **The headline was rewritten into marketing filler.** Quote the exact headline in the run block and say to use it verbatim.
* **Ten customer logos crowd the slide.** Name the specific number you want.
* **Invented text or fake product UI.** Point at the product screenshot again and say every screen element must come from it.

Read every word in the generated image before you publish it. Image models misspell product names and invent plausible-looking copy, and this slide is the first thing a prospect sees.

## Add the visual to your demo

{% stepper %}
{% step %}

### Upload the image

Go to [**Settings > Product Demo > Visuals**](https://app.spara.co/settings/product-demo/visuals) and click **Upload visual**. Accepted formats are PNG, JPG, GIF, SVG, and MP4, up to 25 MB. Give it a name you will recognize in the picker, such as "Opening visual".
{% endstep %}

{% step %}

### Select it on the demo

Open your Product Demo channel from [**Agents**](https://app.spara.co/agents), go to the **Settings** tab, and use the **Opening Visual** picker to search for the visual you just uploaded.
{% endstep %}

{% step %}

### Save and publish

Click **Save draft**, click **Open demo** to see it in place, then click **Publish**. The opening visual is part of the versioned configuration, so prospects keep seeing the old one until you publish. See [Saving & Publishing](https://docs.spara.com/build/channels/configuring/saving-and-publishing.md).
{% endstep %}
{% endstepper %}

## FAQ

### Can I use a video instead of an image?

Yes. The opening visual can be an MP4 as well as an image, up to 25 MB and 30 seconds. It plays once, automatically and without sound. Make sure the last frame stands on its own, because that is what the prospect looks at for the rest of the introduction.

### Does every demo need its own opening visual?

Each Product Demo channel has its own opening visual setting, so demos aimed at different segments or industries can open differently. If you run an A/B test, each variant carries its own setting too, which makes the opening visual something you can test.

### What happens if I do not set one?

Prospects see a blank canvas until the agent shows its first visual during the demo. The Settings tab flags this with a warning.

### Can Spara create the opening visual for me?

Yes. The Spara team can help with initial setup for a Product Demo channel, including the opening visual. After onboarding you can replace it at any time by following the steps above.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/build/channels/product-demo/opening-visual.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
