All guides

Practical guide / 6 min read

Make a product film in your own voice.

Plan a product story, review the script, and make wide and phone versions with Claude Code or Codex. See the example, setup and costs before choosing a skill.

Start with the change your product makes.

A product film needs a reason to keep watching. Begin with a familiar problem, show what changes, then give the viewer one useful next step. A tour of every button rarely tells that story.

Our My Leads Engine example follows a missed enquiry and shows how the product can help with the next one. It uses a script, voice, rebuilt app screens, music, captions and sound effects. It is a story made around a product, rather than a recording of someone clicking through it.

Gather the inputs before asking AI to build.

Choose the audience, the problem and the one thing they should understand. Bring accurate product information, approved screens and a clear next action. Use demonstration data rather than customer information.

For the Product Story Film skill, we made and tested the process on a Mac with Apple silicon. You need Claude Code or Codex with a paid plan, about 15 GB of free space, and a 30 to 60 second recording of your own voice. Check the current product page before buying.

  • Write one sentence describing the problem and the product's actual contribution.
  • Choose the screens that prove that contribution. Leave out private information.
  • Record your own voice somewhere quiet. Use another person's voice only with their permission.
  • Decide whether the film leads to a product page, an enquiry or another useful action.

Approve the words before building the scenes.

Ask your assistant for a short script first. Read it aloud. Remove claims you cannot support and explanations the viewer does not need. A spoken sentence should be easy to follow the first time.

For example, a reporting tool could begin with the team gathering the same figures every week, then show the report it actually prepares. That is an illustrative story structure, not a claim about results from our products.

  • Does the opening describe a problem the viewer recognises?
  • Can the actual product do everything the script promises?
  • Does each scene help explain the next sentence?
  • Is the ending's next step clear?

Build once. Review for each screen.

With the skill, your assistant prepares the voice and scenes, then makes a wide film and a separate 9:16 phone version. Review both. A phone film needs readable text and a composition made for the narrow screen, rather than a crop of the wide one.

Check captions, pronunciation, scene timing, music level and the final link. Look for any screen that suggests a capability the product does not have. Keep the project files so the film can change when your product changes.

Understand the setup and the costs.

The skill's voice tools run locally through Voicebox. That avoids a separate per-film voice-generation charge in this setup. Your paid assistant plan, computer, storage and time still have a cost. Do not treat a zero per-film voice charge as free production.

The package includes the skill, a setup guide, the real project files behind the My Leads Engine films, and guides for story, voice, music, scenes and the phone layout. You can also build your own process if you prefer. Choose the package when those reusable materials are useful to you.

An example made for our My Leads Engine product. The story illustrates the product; it is not a customer-results claim.

About this guide

Based on the process and requirements in our Product Story Film. Product details can change; check the current listing before buying. See our work and the people behind it.