Claude Makes
Videos Now?
Published about 1 months ago • 3 min read
Varick Agents - Volume 2
Claude went from video concept to product demo visuals, with no designers or external tools needed. At the end of the day everything you see on a screen is code. These LLMs can create far more than you give them credit for.
The Problem
You need a demo that explains your product without hand-holding. You’re likely facing one of these:
Investors who need to grasp it in 30 seconds
Site visitors who bounce if it’s unclear
Prospects who don’t see the value
Social audiences with 3-second attention spans
Traditional demo creation is slow and costly. The creators don’t know your product like you do. Did I mention they're costly?
The Approach
I needed a demo for COLD.AI, our automated email pipeline. Instead of using After Effects or hiring anyone, I prompted Claude with a detailed request. Two iterations later, I had everything I needed.
It resulted in a clean, clear 30-second walkthrough of the entire product that you can watch here. No seriously click it, it's insane.
Why This Works
Clear Messaging
You write the prompt, so the message is accurate. No back-and-forth with outsiders.Fast Iteration
Change anything with a small prompt tweak.Multi-Use
Same demo works across your site, sales, onboarding, investor decks, and social.Low Cost
Typical demo: $500–2500. This cost me 30 cents in Claude credits.
How to Do It: The Two-Prompt Method
Prompt 1: Strategic Brief
#####
I need you to generate a different kind of visual. These aren't going to be for a video, but instead are going to be recorded and turned into GIFs for my website (built in Framer).
Does that make sense?
So optimize for whatever would need to be shown to the end user.
This is for Varick Agents, where I want to display STUNNING visuals cleanly and sized properly for a widget on a webpage - the visuals are meant to display the AI Agents that we are building, and be seen by potential customers.
So make a new directory in VIDEO VISUALS called VARICK AGENTS VISUALS, then create the first visual for this product:
It's a fully automated, agentic email pipeline, called COLD.AI. You can put that name, and what it is in the subject line. And a tag line would be handle cold email and book meetings on auto-pilot.
So the idea is that the user starts out by entering the type of person/role they're looking for, in plain english.
i.e. "product managers at fintech companies in San Francisco"
then, the tool scrapes their info off Linkedin/the internet, specifically their first name, last name, role, and company.
This is all saved in a spreadsheet style format.
Then, the tool auto calculates their most likely email address format from an online API call, and then double checks it with the MillionVerifier API.
Then, it generates custom emails for each one, based on their role at the company, and the email is hyper tailored to their needs.
For example, you can imagine a company that builds AI SDR's is using our platform to find people and send cold emails to them, to book meetings.
They will send emails to each contact that comes through like: "Hi , We can help with sales, etc etc"
And then it auto-sends these emails out as well, tracking replies, follow ups, etc.
And the end result shows a calendar being populated with meetings.
That is the FULL DEMO.
I want you to do the following:
make a markdown file documenting this:
1. First, plan out WHAT needs to be shown, as in step by step so no step is forgotten. Are you going to use titles and subtitles so the eventual video seen by the user is easy to understand?
2. Next plan out HOW its going to be shown (i.e. how are you going to make it transition from one to the other, in the same place on the screen, timed properly, so that it can be recorded, and that recording can be understood by the end user)
3. Next plan out the technical stack you're going to use. Detail that in the doc as well.
DO JUST THAT. Then I'll ask you to start implementing it.
#####
Prompt 2: Context Additions
#####
Fantastic. Does this document also contain all of the context on what exactly is being asked / why we're doing this? aka the info I provided you in the very first message:
Add that at the top so that a fresh pair of eyes just needs this doc to understand and execute.
#####
Claude returned a complete document with:
Visual flow
Tech implementation
Transitions and timing
Metrics and success criteria
Production notes
The markdown file is a little long, so grab that (and the other prompts) here.
Bonus Value: Clarity of Thought
Writing a good prompt forces you to get clear:
What’s your product really doing?
What steps matter?
Who’s this for?
What does success look like?
Build Your Own Demo: The Template
Start with:
What’s the product?
Who’s it for?
What’s the goal?
Then outline:
What problem does it solve?
What’s the process?
What’s the outcome?
And define format:
Where will it live?
What are the constraints?
How long should it be?
Then prompt Claude.
Other Use Cases
This method also works for:
Feature explainers
Onboarding guides
Training flows
Process docs
Campaign planning
This entire workflow: text to product demos is a $1M ARR business when implemented properly. Go ahead and build this - I'll take my 10% royalties in perpetuity.
—
Vasuman Moza
P.S. If this helps, tag me on X. I want to see what you build. And if you want to hire me and my team to build you AI Agents instead, just reach out with the bottom right link - at Varick Agents.