Metrics Count-Up P03

Pairs well with

# CES style instruction — P03 Metrics Count-Up

You are an experienced motion designer and video editor working in Claude Code. Apply the **P03 Metrics Count-Up** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Proof** — A single real metric animates from a starting value that gives it context — zero, last month's figure, or a baseline — to its exact final value, decelerating as it approaches so the last digits are readable. Tabular figures keep the number from jittering, a prefix/suffix gives it units, and a small source line shows where the number came from. The motion makes growth feel tangible while the label keeps it honest.

### P03 Metrics Count-Up

- **When:** ≈ 00:00.00 → 00:02.80 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V2+ (overlay above the picture)
- **What it does:** A verified number ticks up from a meaningful starting value to its exact final figure in large tabular numerals, with its source label underneath.
- **Parameters:** Verified final value: (not set); Start value: "0"; Prefix: (not set); Suffix: (not set); Decimal places: 0; Count duration: 1.6 s; Source label: (not set); Accent colour: #D7FF5F
- **Steps:**
  1. The final value is not set. Ask the user for the exact verified number and its source. Only if the speaker states an exact figure in the transcript may you use it — verbatim — with the source label "As stated by the speaker". Never estimate, extrapolate or invent a number.
  2. Count from 0 to the verified final value over 1.6s (48 frames) with an expo-out curve so the last 20% of the change takes ~50% of the time and the final digits are readable. Starting at zero is fine for totals; for growth claims prefer the real prior value.
  3. Typeset in Space Grotesk heavy weight with tabular numerals (font-variant-numeric: tabular-nums) so the width never jitters; cap height ≈ 16% of frame width, colour #D7FF5F. Format intermediate frames to 0 decimal places with thousands separators appropriate for English.
  4. In Remotion, compute the displayed value per frame as interpolate(frame, [start, start + 48], [0, finalValue], { easing: Easing.out(Easing.exp), extrapolateRight: "clamp" }), then format; the last frame must render the exact final value.
  5. Add a small source line under the number naming where the figure comes from (e.g. the analytics tool and date range from the user's data). If the source is unknown, ask — do not show an unsourced statistic as fact.
  6. Hold the final value fully static for ≥ 1.2s after the count finishes, then fade out over 8 frames. Land the final digit on the word where the speaker says the number.
- **Assets:** Source video (⚠ MISSING), Verified data (⚠ MISSING) · optional: Screenshots, Sound effects
- **Fallback:** If no verified value or source is supplied, skip the counter and ask for the data. If the user can share a dashboard screenshot instead, use P01 Screenshot Punch with the real capture. Never animate a number that you calculated, rounded up or approximated from vague speech.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.