How to Write a Great Demosmith Prompt (With Examples)

Creating a demo in Demosmith starts with three fields: your app URL, the prompt describing what to show, and an optional Login Credentials section for apps that require a sign-in. The agent uses all three, but the prompt is where the quality of your demo is made or broken.

The prompt is the only instruction the agent gets for the actual flow. It will not visit your marketing site, read your docs, or guess what matters to your viewers. A well-written prompt produces a polished 60–90 second walkthrough that a real viewer would watch from beginning to end. A vague one produces a demo that wanders or stops at the wrong screen.

The difference is usually a few specific sentences. This guide shows you exactly what to write and gives you five real prompts you can copy and adapt.

What the agent reads

Once you submit, the agent reads your prompt before it navigates a single page. It does not visit your marketing site, read your documentation, or make assumptions about what your product does. It starts with what you wrote, and nothing else.

Your URL and login credentials are handled in their own fields. The prompt itself needs three things:

• Where to start within the app: which view, section, or page to land on first (e.g., "Open the Pipeline view" or "Start from the homepage")
• The flow: the steps in order, written as what the user is trying to accomplish
• Where to end and what to emphasize: the screen to close on and the one or two things the voiceover should make the viewer notice

If any of these are missing, the agent makes a reasonable guess. Sometimes the guess is fine. Often it is not the demo you had in mind. The prompts that produce the best videos are the ones that leave nothing to guesswork.

Anatomy of a great prompt

Every strong Demosmith prompt has four parts. You do not need headers or bullet points in the prompt itself. Plain prose works fine. But these four elements need to be present in whatever order feels natural.

Writing goals, not UI steps

The most common mistake new users make is describing the interface instead of the workflow. The agent navigates by goal, not by pixel position. UI language is brittle: a button might be in a different location depending on screen size, account state, or a recent release.

5 example prompts

Example 1

SaaS signup and first value moment

Best for: landing pages, Product Hunt listings, investor decks. Shows a new user going from your homepage to a real output before the viewer has time to lose interest.

Example 2

CRM deal pipeline update

Best for: sales tool demos, team training videos, feature announcements. Shows how fast it is to keep deal records clean and current without switching tabs or writing emails.

Example 3

E-commerce checkout

Best for: e-commerce demos, conversion optimization showcases, checkout flow walkthroughs. Shows the complete purchase experience to highlight speed and friction-free design.

Example 4

Analytics dashboard drill-down and export

Best for: data and analytics tools, business intelligence platforms, reporting features. Shows a complete question-to-answer workflow that ends in a tangible deliverable.

Example 5

Team invite and permission setup

Best for: enterprise SaaS, team collaboration tools, security-focused demos. Shows buyers how granular your access controls are without needing a live sales call.

Mistakes to avoid

Most demos that don't turn out right come down to one of four mistakes. All of them are easy to fix once you know what to look for.

• Not specifying where to start within the app

  The URL field handles the domain, but once the app loads, the agent needs to know where to go. If your demo should start in the Pipeline view, or the Analytics tab, or after navigating to a specific record, say so. Without it, the agent will start from whatever the app loads by default, which may not be where you want.

• Too many flows in one prompt

  If your prompt asks the agent to show signup, the dashboard, settings, team management, and the export feature, the output will be scattered and over 3 minutes long. Viewers stop watching at 90 seconds. One prompt, one workflow. Split everything else into separate demos.

• Describing the UI instead of the goal

  Prompts that say "click the gear icon in the top-right corner" are fragile. The agent navigates by intent. If the icon moves, the agent gets confused. Write what the user is trying to accomplish ("Open Settings") and let the agent find its way there.

• No endpoint

  If you don't say where the demo should end, the agent will pick a stopping point. It might cut off before the payoff moment: the thing viewers came to see. Name the frame you want to close on, even if it's just "end on the confirmation screen."

Not sure how to start? Use this AI helper prompt

If you have a clear sense of what you want to show but aren't sure how to phrase it, paste the template below into ChatGPT, Claude, Gemini, or any other AI with your product details filled in. It will write the Demosmith prompt for you.

I'm creating a product demo video with Demosmith, an AI agent that opens a real browser, navigates a live web app step by step, generates a professional voiceover, adds transitions and captions, and exports a finished MP4.

The Demosmith prompt only describes the flow to show. The app URL goes in a separate URL field, and login credentials go in a separate Login Credentials section; they don't belong in the prompt itself.

My product:
[One sentence: what it does and who it's for]

The workflow I want to demo:
[Describe the user goal, e.g. "a new user completing signup and seeing their first report" or "an admin inviting a teammate and setting their permissions"]

Target viewer:
[Who will watch this, e.g. potential customers on a landing page, investors in a pitch deck, new users during onboarding]

Where in the app the demo should start:
[Which view, section, or page the agent should navigate to first after the app loads, e.g. "the Pipeline view", "the Analytics tab", or "the homepage"]

Anything to skip or emphasize:
[What the voiceover should highlight, any UI elements to avoid, steps to keep short, or a key outcome to land on]

Using these details, write a Demosmith prompt that:
1. Names the starting view or section within the app (not the URL)
2. Lists each step of the workflow in plain English, in order, written as user goals rather than UI instructions
3. Names the screen or moment the demo should end on
4. Tells the agent what the voiceover should emphasize (speed, ease, outcome, number of clicks)
5. Keeps the total walkthrough focused on a single outcome, no more than 60 to 90 seconds

Write the prompt in plain instructional prose, as if you are briefing a colleague who will navigate the product on camera.

Key takeaways

1. The prompt is for the flow only. Your app URL goes in the URL field, and login credentials go in the Login Credentials section. Neither belongs in the prompt text.
2. Every strong prompt has four parts: where to start within the app, the steps in order, a clear endpoint, and what the voiceover should emphasize.
3. Write user goals, not UI steps. "Open the Pipeline view and log a call" is more reliable than "click the dropdown in the sidebar." The agent finds its own path.
4. Keep each prompt to one workflow. A 90-second demo of one thing done well outperforms a 4-minute tour of everything every time.
5. If your prompt feels rough, use the Enhance button. Demosmith's AI will rewrite it for you before the agent runs.
6. If you're not sure where to start at all, copy the AI helper prompt above, paste it into ChatGPT, Claude, Gemini, or any AI, fill in your product details, and use the output as your first draft.

Once your demo is ready, you can embed it directly on your website with a single line of code. The embed works on WordPress, React, Webflow, and any platform that supports HTML.