| # | Beat | Timecode | Motion | Logo | Audio | VO / on-screen |
|---|---|---|---|---|---|---|
| 1 | open | 0–8s | spatial-parallax | icon·liquid-chrome | ♪ bed in | Most content strategy is a calendar full of guesses, so Temerarii starts somewhere stranger: the number you actually need to move. on-screen: Content that moves a number |
| 2 | hook | 8.0–16.0s | kinetic-build | icon·wireframe | ♪ — | Name the single outcome — sign-ups, demos, replies — and let every post earn its place against it. on-screen: Pick the one metric first |
| 3 | quote | 16.0–24.0s | kinetic-build | icon·wireframe | ♪ — | Our rule is blunt: if a post cannot trace back to that one number, it does not get made. on-screen: "If it can't move the number, cut |
| 4 | proof | 24.0–31.0s | receipts-count | icon·wireframe | ♪ — | We tag every post with UTM links and read them straight in GA4, so the strategy edits itself off on-screen: Tag posts, read the data |
| 5 | hook | 31.0–38.0s | kinetic-build | icon·wireframe | ♪ — | Then the move is simple: find the few posts that moved the needle and make more of those, on purpose. on-screen: Double down on what worked |
| 6 | resolve | 38.0–45.0s | coalescence | stacked·liquid-chrome | ♪ bed out | We wrote the whole method down so you can run it without us — that is the point. on-screen: Full method at temerarii.xyz |