01 / The short answer
The practical answer.
Use Adobe Express to arrange a problem-to-solution story, combine product visuals with clear text, and add optional voiceover or music. Make the explanation understandable before polishing the effects.
An explainer answers “Why would I use this?” A demo answers “How does this workflow work?” For a 45-second explainer, try problem, cost of the current approach, product mechanism, visible outcome, and next step. Use everyday language; a new viewer may not understand your category jargon yet.
- A specific customer, their current workaround, a supported mechanism that helps, one product screenshot, and a next step.
02 / The walkthrough
The Adobe Express walkthrough.
Make one clear first version, review it, then refine the details.
Name the audience and the current workaround.
Write the problem in one everyday sentence. List what the customer does today and the specific way the software changes that work. Choose a screenshot that makes the mechanism visible.
Build five short video scenes.
Create a video project with a problem, friction, mechanism, outcome, and CTA. Use your own visuals where the product is being explained. A stock clip can establish context, but it should not replace evidence of the software.
Pair each sentence with a visual.
Use a short headline and a cropped interface or simple diagram. Rearrange and trim scenes to follow the explanation. Keep the mechanism scene long enough for a viewer to understand what changed.
Add voiceover and selective movement.
Record narration if it helps explain the story, then use text or image animation to guide attention. Keep music below the spoken message. Review a muted version too, since viewers may encounter the film without sound.
Review the explanation and save a video.
Ask someone unfamiliar with the product to describe what it does after watching. Fix confusing language before downloading. Check the exported file’s sound, duration, and final CTA.
03 / A useful prompt
Start with a usable brief.
Use this planning prompt in ChatGPT, Claude, or Gemini. Replace the bracketed details with verified product information.
Product: [name] Audience: [specific user] Current problem: [what is difficult today] Verified product facts: [supported features and evidence] Available visuals: [logo, screenshots, clips] Brand: [colors, font, tone] CTA and destination: [real action and URL] Write a 45-second SaaS explainer in five scenes: problem, current friction, product mechanism, outcome, and CTA. Give concise on-screen copy, optional narration, a real visual, and a suggested duration for each scene. Do not invent features, metrics, testimonials, prices, or availability. Flag missing facts and assets. Separate on-screen copy, narration, and production notes.
This prompt produces a brief or checklist. The walkthrough explains the separate production and delivery work.
04 / Worked examples
Three ways to apply it.
These are illustrative production briefs. They are not customer case studies or claims that the featured tool produced the LaunchVideoAI film above.
An invoicing app: less chasing, clearer follow-up
Start with a freelancer searching through messages to find an unpaid invoice. Introduce the invoice list and a supported reminder workflow, then show a clear outstanding status. End with “Keep your invoices in view.” Explain the organizational benefit without promising that clients will pay faster. The viewer needs to understand the mechanism, not a fictional revenue uplift. In Adobe Express, arrange the visual beats as separate scenes and time the callouts around them. Review the downloaded video for the still reading intervals.
A team knowledge base: stop asking the same question
Use a repeated onboarding question as the opening. Reveal a searchable team guide, show the relevant answer, then close on an invitation to create the first workspace. If permissions are an important feature, show the actual access rule rather than a generic padlock. Keep screenshots uncluttered so the answer is visibly connected to the original question. In Adobe Express, arrange the visual beats as separate scenes and time the callouts around them. Review the downloaded video for the still reading intervals.
A monitoring tool: understand the alert
Begin with an ambiguous notification, introduce a dashboard that explains the affected service, then show the supported investigation view. End with “Know where to look next.” Avoid promising zero downtime or instant resolution. A useful explainer makes the alert-to-context connection clear, even when the viewer has no specialist infrastructure knowledge. In Adobe Express, arrange the visual beats as separate scenes and time the callouts around them. Review the downloaded video for the still reading intervals.
05 / Checks and limits
Before you publish.
A template or stock clip can support the story, but it cannot establish what your software actually does. Review the source assets, account options, and downloaded video before publishing.
- Describe the audience’s situation in words they would use themselves.
- Explain the mechanism: what does the software actually change?
- Treat time-saving figures, revenue numbers, and testimonials as claims that need evidence.
- Test the script with someone who has never used your product.
06 / A website-first option
Choose the production path.
Use Adobe Express when its workflow fits your project. For an original product film based on a public website, LaunchVideoAI offers another starting point.
01 / THE WORKFLOW
Work with Adobe Express
- Use the Adobe Express walkthrough for this specific task
- Supply accurate product facts and publishable assets
- Review the scene plan and produce or export the film
- Keep the editable source and verify the delivery file
02 / THE WORKFLOW
Start with LaunchVideoAI
- Enter a public website URL
- Choose the theme, length, and anything to highlight
- Generate original animation and music for the product
- Review versions, request an edit, and download the MP4
YOUR WEBSITE IS ALREADY THE BRIEF
Let’s put it in motion.
Original animation and music, made for your brand.
07 / Common questions
Questions before you start.
How is a SaaS explainer different from a demo?
An explainer introduces the problem, the way the software helps, and the outcome. A demo focuses on a particular sequence inside the product. Combining them can work, but keep the main purpose clear.
Can stock footage replace my product visuals?
A template or stock clip can support the story, but it cannot establish what your software actually does. Review the source assets, account options, and downloaded video before publishing.
Was the audixa example made with Adobe Express?
No. The featured audixa film was made with LaunchVideoAI. It is product-video inspiration, not a result from this Adobe Express walkthrough. The worked examples are proposed briefs, not demonstrations of measured customer results.
Can I start from my public product website?
Yes. LaunchVideoAI starts from a public website URL. Choose your theme, video length, and focus, then review the generated film and request changes if needed. Check the current Essential and Explore packages before purchasing.
You can use LaunchVideoAI to make an awesome launch video in a few minutes.
Sources & further reading