How to make a product demo video from your brand and your code
A step-by-step cookbook: set up your brand in Kitereach, connect GitHub so Claude reads your codebase and learns how your features really work, then turn one sentence into an on-brand product demo video.
A product demo has to get the product right: the real feature names, what each one does, and the colours and fonts your users know. A general AI video tool doesn't know any of that. Kitereach learns it once, from your website and, if you like, from your code, and writes it into a brand. Every demo you make for that brand starts from it.
This cookbook takes you from nothing to a finished, on-brand product demo in four parts: connect Claude, set up your brand, connect GitHub, then make the video.
What you need
- A Kitereach account (sign in with Google; your first reel is free).
- A Claude subscription. Kitereach runs Claude Code on it, so you don't buy credits.
- Your product's website.
- Optional: the product's GitHub repository, and permission to install a GitHub App on it.
Step 1. Connect Claude Code
Go to Settings → API Keys, run claude setup-token in a terminal and paste the token it prints. The video at the top of this page shows it in one minute. Every step below (researching your brand, writing the script, rendering the video) runs on that token.
Step 2. Create your brand
Open Brand Setup in the sidebar. Under Analyze Brand / Product:
- Type your Website URL.
- Leave Deep research · Claude Code selected. (Quick scan reads only your homepage, in one pass, and guesses colours from the HTML. Fine for a one-off, not for demos.)
- Optional: under Other pages to study, add your docs, pricing page, changelog or app store listing, one per line. Under Notes for Claude, add anything the site doesn't say, like “We're repositioning for agencies”.
Don't press start yet. First, connect your code.
Step 3. Connect GitHub so Claude reads your codebase
Your website says what the product promises. Your code says how it actually works. On the same form, under GitHub repository:
- Click Connect GitHub. GitHub asks you to install the Kitereach GitHub App and choose which repositories it may see. Pick only the ones you want Kitereach to read.
- You're sent back to Brand Setup. Choose your repository from the dropdown.
- Pick a Model (Opus reads the site and code most deeply; it's also the slowest) and click Start deep research.
Claude Code now works in a private sandbox for 10 to 20 minutes. It opens your site in a real browser, measures the actual colours and fonts, saves your logo and screenshots, and clones your repository to read it. From the code it takes the exact design tokens, the real feature list and what shipped recently. It writes all of that into a brand book.
- Kitereach reads your code during research, not every time it writes a video. To pick up a new release, open the brand and run deep research again.
- The repository must be one the GitHub App can see. If it belongs to an organization, an owner of that organization has to approve the app first.
- You can change which repositories the app sees, or remove it, at any time in your GitHub settings.
Step 4. Review and apply the brand book
When research is Ready for review, read what Claude found: colours, fonts, logo, voice, a summary and a full business profile. If it's right, click Apply to brand. If not, Discard it, add a note and run it again. Nothing is saved to your brand until you apply it.
Step 5. Link the brand to your demo
Open Reels. In What should the reel explain? write one sentence about the demo. Be specific about the feature and the outcome:
- “A 45-second tour of how our invoicing app turns a timesheet into a paid invoice”
- “What's new in version 3: the three features our customers asked for most”
- “How our scheduler plans a week of posts in 10 minutes”
Then open the brand dropdown beside it. It says No brand (one-off) until you change it. Pick your brand. That's the link: the script is now written in your brand's voice from its brand book, and Claude is told never to contradict it. The video uses your colours, fonts and logo. Click Next: choose a look →.
Step 6. Choose a look and write the script
Pick a style, a voice, a format and a length. For a demo you'll post on LinkedIn or your website, choose Portrait 4:5 or Landscape 16:9; for Reels, TikTok and Shorts, Vertical 9:16. Click Write script.
Claude researches and writes a scene-by-scene script. Check the Facts & sources list: this is where you catch a feature name that's out of date. Edit any line, or type what to change and click Rewrite. When it's right, click Approve & build video. Nothing is voiced or rendered before that.
Step 7. Approve, then download
Watch the video. If a scene is off, describe it (“Scene 3: show the invoice total before the Pay button”) and click Redo. When you're happy, click Approve video, then Download MP4. Under Other sizes · LinkedIn & more you can have the same demo re-laid out for another frame, and Post copy gives you a caption to paste.
Tips for better product demos
- One feature per video. A 30–45 second demo of one job done well beats a 2-minute tour.
- Lead with the outcome. “Get paid in 2 days” before “Click Export”.
- Make a series for launches. One brand, one video per new feature. See the reel farm cookbook.
Made with Kitereach, one sentence each
“How a project management app saves a team 5 hours a week”
“How a meal-kit delivery works, from farm to your door”
“How a habit-tracking app keeps your streak alive”