Product film / 01:48 / Published 2025-10-09
What Work Looks Like with ChatGPT | Write, Research, Code, Create
A white-stage capability reel repeats a short claim, a task-specific input, and an artifact or control detail across research, connected data, code, writing, and images.
Useful to borrow
Use one consistent chapter/input/result rhythm across different capabilities.
Do not infer
Speed claims are advertising copy, not measured latency; generated business plans and statistics are not independently validated here.
9 shot groups.
Read across from the observed content to its treatment and possible adaptation. Enlarge the frame for detail.
Approximate study intervals; horizontal scrolling reveals all columns on small screens.
| Moment / source | Reference frame | What is on screen | Framing / edit | Useful adaptation |
|---|---|---|---|---|
| Shot group 01 ≈ 00:00–00:08 App / browser screenWatch from here ↗ | Sample 00:04.000 | Opening request An isolated composer receives a broad work-related request. | Small control on a large white field. | Create a reusable entry motif. |
| Shot group 02 ≈ 00:08–00:24 App / browser screenWatch from here ↗ | Sample 00:20.000 | Research chapter A statement card leads to a research request, status, and a report with download/share controls. | Claim, input, then artifact detail. | Show a deliverable rather than ending on a spinner. |
| Shot group 03 ≈ 00:24–00:36 App / browser screenWatch from here ↗ | Sample 00:32.000 | Connected calendar setup A calendar request opens tool and connector choices. | Composer into native settings detail. | Keep connection setup visible. |
| Shot group 04 ≈ 00:36–00:48 App / browser screenWatch from here ↗ | Sample 00:44.000 | Agent task A chapter card precedes an agent-tagged research and spreadsheet request. | Repeated chapter grammar and enlarged input. | Expose the task's scope without implying instant completion. |
| Shot group 05 ≈ 00:48–01:00 App / browser screenWatch from here ↗ | Sample 00:56.000 | Code chapter A coding statement leads to a request and a dark code window. | White-stage setup with contrasting code artifact. | Distinguish code output from a verified running feature. |
| Shot group 06 ≈ 01:00–01:08 App / browser screenWatch from here ↗ | Sample 01:04.000 | Selected document edit A document passage is selected with a contextual rewrite request beneath it. | Native highlight and nearby instruction. | Keep the edit target readable. |
| Shot group 07 ≈ 01:08–01:20 App / browser screenWatch from here ↗ | Sample 01:12.000 | Document analysis An attached document leads to a response and chart before the next chapter. | Source-to-analysis pairing. | Show the input artifact alongside a representative result. |
| Shot group 08 ≈ 01:20–01:40 App / browser screenWatch from here ↗ | Sample 01:36.000 | App and campaign requests Chapter cards alternate with prototype and campaign requests, ending on a generated shoe advertisement. | Repeated input/result rhythm with a colorful final artifact. | Label generated demo artifacts rather than implying shipped host-app features. |
| Shot group 09 ≈ 01:40–01:48 App / browser screenWatch from here ↗ | Sample 01:44.000 | Closing conversation A final short question and reply precede the end mark. | Return to the opening composer motif. | Close the loop without another feature list. |