A Coffee Timer Races a Feature Request
A live-action product launch turns a slow feature request into a timed race, then proves the result with a readable UI demo.
Field notes / why it works
The first 11 seconds compare a familiar 40-second coffee brew with a feature request pending for 14 months, making the launch a race. A 17.7-second interface walkthrough (0:12.6–0:30.3) shows the request and resulting feature before the 36-second payoff at about 0:38. Sparse overlays and a returning physical timer sustain the comparison through a cut rate of only 5.4–6.3 per minute.
Plate 01 / The format in one breath
A presenter opens beside a coffee maker, says it brews in about 40 seconds, then contrasts that with a feature request open for 14 months. Two presenters introduce a product, show the request becoming a working feature through a filmed interface, and return to the still-running coffee timer to make the speed difference tangible. The launch claim is carried by a miniature experiment, not just an announcement.
Why it works
- The promise becomes concrete by 0:10: a 40-second everyday process is set against a 14-month backlog, creating a race the viewer can track.
- At 0:12.6–0:30.3, the video shows the embedded interface, a plain-language request, generated screens, and an approval flow while the speakers describe those steps.
- The counter appears again at 0:33.6–0:37.5, then the result lands at 0:38: the customer built the requested feature in 36 seconds. The physical timer makes that number feel earned.
Plate 02 / Format card
| Platform · aspect · length | X · 16:9, 1280×720 · 66.2 s at 30 fps |
| Pace | 7 measured shots; 5.4–6.3 cuts/min including one uncertain change; 13.6 picture changes/min including overlays; mean shot 9.46 s, median 10.73 s |
| Script | 170 spoken words; 163 wpm over full runtime, about 210 wpm while speaking; 21 short sentences averaging 8.1 words; no spoken questions; “you” 4.7 times per 100 words |
| Voice | Two young adult male presenter archetypes: conversational, low-to-mid registers, quick and assured; primary voice measured at median 127 Hz with animated movement |
| On screen | Approx. 55% kitchen presenters/prop, 27% screen demo, 18% seated presenters; live action remains the frame around the interface proof |
| Captions | Sparse white keyword chunks near the speaker or demo; occasional lavender italic keyword; separate small dark subtitle strip over screen content |
| Sound | Continuous quiet tonal/music-like bed about 13.7 dB under voice (music character inferred); no clear cut-synced effects; −22.4 LUFS integrated, −6.9 dBFS true peak in source |
| Structure | Timer setup → product reveal → demo → speed payoff → technical reassurance → CTA → future-state sign-off |
Pro / 13 plates + recipe
The first plates are open. The full dissection is Pro.
Get the timed shots, type and sound specs, and the runnable recipe.
Open the full blueprint- Plate 03 / The hook, frame by frame (first 3 seconds)Pro
- Plate 04 / Structure (beat sheet)Pro
- Plate 05 / Shot grammarPro
- Plate 06 / Visual style guidePro
- Plate 07 / Voice and deliveryPro
- Plate 08 / Sound designPro
- Plate 09 / PackagingPro
- Plate 10 / Script templatePro
- Plate 11 / Production planPro
- Plate 12 / PromptsPro
- Plate 13 / Edit recipePro
- Plate 14 / QA checklistPro
- Plate 15 / Make it yoursPro
- Recipe / runnable promptPro