15-Second Showreel for Our Website
Claude Opus 5.5 video example. The 15-second sample mixes people and architecture footage, a website screen, numbers and a logo. It reads as a rapid portfolio assembled from existing work rather than a feature tutorial. Includes an asset-replacement and staged production guide.
Overview
What you get
- Turn two or three website case studies into a roughly 15-second reel.
- A product-specific asset list, replacement table and staged AI requests.
Case study
Make a similar video
The 15-second sample mixes people and architecture footage, a website screen, numbers and a logo. It reads as a rapid portfolio assembled from existing work rather than a feature tutorial.
Your goal: Turn two or three website case studies into a roughly 15-second reel. 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 says the model edited supplied footage, coded animation and composed music, without publishing a stack. Provide a local asset list and ask AI to choose an available editing/export workflow.
Prepare your assets
- One original clip or clear image per case.
- Website screenshot, logo, positioning and URL.
- Case names, your contribution and supported results.
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 |
|---|---|
| Architecture and people footage | Your own case footage |
| Website homepage | Your current website |
| Numbers such as 30M+ | Verified outcomes, or case names instead |
| Brand mark | Your logo and contact action |
A photographer can use two shoots; a development team can use two shipped projects and real screens. Explain your contribution rather than claiming every client outcome.
A few cases communicate better than a full homepage montage; leave readable time for the final brand and URL.
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.
- 0–2s: brand or strong case visual.
- 2–8s: two cases, one point each.
- 8–12s: site plus capability or outcome.
- 12–15s: logo and contact action.
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.
- Check assets and plan shots.
I am using Claude Opus 5.5 to make a video for [my product].
Goal: Turn two or three website case studies into a roughly 15-second reel.
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.
A few cases communicate better than a full homepage montage; leave readable time for the final brand and URL.
Provide the shot list before producing the full film.
- Make one sample. After approving the plan and file paths, send:
The shot list is approved. Preview a transition between two case clips and check that neither is stretched.
Production approach: The creator says the model edited supplied footage, coded animation and composed music, without publishing a stack. Provide a local asset list and ask AI to choose an available editing/export workflow.
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.
- Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:
Complete the other shots using the approved sample's visual rules.
A few cases communicate better than a full homepage montage; leave readable time for the final brand and URL.
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.
- 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.
Revise the film and fix problems
Name the shot and change instead of requesting vague improvements that reset approved pacing:
Replace the second case with [video file], using [start] to [end] seconds and [case title]. Preserve the final three seconds.
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.
- The reel is overloaded: remove a case before speeding up every shot.
- Clips use different orientations: recompose them for the output rather than stretching to fill.
Creator source and reproduction limits
The post names Claude Opus 5.5 and a 15-second website-showreel request. Editing and original-music details are creator claims without a complete project to verify. 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.