Taxtello Bookkeeping App Product Film

Make a similar video

Taxtello uses navy backgrounds and gold accents, linking finance dashboards, records and status screens through restrained camera moves before a brand ending. Interfaces and order take precedence over explanatory copy.

Your goal: Make a product film of no more than 15 seconds from three or four strong actual-interface moments. This work belongs to the Claude Opus 5.5 video collection. Select Claude Opus 5.5 in an AI coding tool that supports it and submit the assets and requests below in stages. The model plans, writes and edits code; the actual project handles preview/export. Voice and music need suitable tools or supplied audio.

The creator describes Opus 5.5 in Claude Code, React + Remotion and Python-synthesized music. The long request specifies a separate composition, frame-driven motion and finished-film inspection.

Prepare your assets

• Current screens, design tokens, fonts and actual logo files.
• Three or four related states, such as dashboard, record processing and overview.
• Demo financial values, target language and audio plan.

Put files in a directory AI can read, such as assets/, and explain each filename and purpose. Specify ratio, duration and publishing destination. If you supply only a URL, ask what content is accessible before assuming any functionality.

Replace elements for your product

Element in the sample or creator brief	Your replacement
Navy/gold system	Your actual design tokens
Finance dashboard and receipts	Your main interface and business object
Short German headings	Your audience language and short copy
Taxtello composition	A separate new composition in your project

An inventory system can show stock overview, intake record and status summary; a task product can show overview, card movement and progress. Carry one object between shots.

Do not copy private creator paths; keep existing compositions, use demo financial values and avoid invented tax-correctness guarantees.

Start with this shot plan

This is an editorial draft, not a frame-by-frame reconstruction. Approve assets and copy for each scene, adjusting durations to the information load.

1. 0–2s: enter the product moment quickly.
2. 2–6s: main dashboard.
3. 6–10s: one business object changes state.
4. 10–12s: result or clearer overview.
5. 12–15s: logo and short line.

Make it with AI in four steps

Editorial suggestion; not reproduction-tested. Fill in brackets and approve each preview before continuing. The creator’s film is not a downloadable project template.

1. Check assets and plan shots.

I am using Claude Opus 5.5 to make a video for [my product].
Goal: Make a product film of no more than 15 seconds from three or four strong actual-interface moments.
Audience: [people]. Ratio and duration: [requirements]. Assets: [directory].
Read my product brief, identity and assets. List confirmed features and missing files.
Use the draft above to plan visuals, short headings, asset files, durations and transitions.
Do not copy private creator paths; keep existing compositions, use demo financial values and avoid invented tax-correctness guarantees.
Provide the shot list before producing the full film.

2. Make one sample. After approving the plan and file paths, send:

The shot list is approved. Preview one dashboard value and chart appearing, checking actual UI structure and brand tokens.
Production approach: The creator describes Opus 5.5 in Claude Code, React + Remotion and Python-synthesized music. The long request specifies a separate composition, frame-driven motion and finished-film inspection.
Check dependencies and assets in this environment and provide the actual preview method.
Identify missing tools, models or audio rather than presenting placeholders as finished work.
Deliver this sample preview first, then list the files needed for the full film.

3. Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:

Complete the other shots using the approved sample's visual rules.
Do not copy private creator paths; keep existing compositions, use demo financial values and avoid invented tax-correctness guarantees.
Match headings, actions and audio cues. If audio is unavailable, provide a silent preview first.
Keep product name, logo, screen assets, colors and final action in easily editable configuration.
Provide full playback and key transition stills, identifying unfinished parts.

4. Review and export. Check copy and assets on a phone, then send:

Apply the approved changes and export, retaining editable source and asset references.
Provide this project's actual export command, prerequisites and output file location.
Check final MP4 duration, ratio, text clipping and audio instead of relying only on browser preview.
Deliver a contact sheet and list remaining limitations.

Remotion uses frame-driven animation; export needs your actual entry point, composition ID and output path. See animation fundamentals and the render CLI.

Revise the film and fix problems

Name the shot and change instead of requesting vague improvements that reset approved pacing:

Replace navy/gold with my design tokens and use [logo file]. Change only the new composition, preserving existing animation. Inspect mid-transition frames and provide a contact sheet.

For a 9:16 version, recompose headings, the main subject and final action. Preview the new layout rather than cropping the sides. To shorten the film, remove secondary shots or sentences before retiming.

• Creator paths fail locally: ask AI for commands using your actual entry point and composition ID.
• Effects hide the interface: reduce glow/blur and preserve actual structure and copy.

Creator source and reproduction limits

The post describes production and two feedback rounds after the initial request; the long brief is retained. React, Remotion and Python music are attributed claims without the original project. View the original post.

Visual descriptions come from the collected video; production details come from the stored request and post. They do not constitute testing of the current product. Shot plans, adaptations and expanded requests are editorial suggestions and have not been generated or tested. Supply your own assets and production environment when the original project is unavailable.