# Fintech SaaS Demo Shot-Study Template

Use this reference when analyzing a fintech SaaS demo video frame by frame, extracting its motion language, or applying that language to a new AI SaaS product demo.

## Study Goal

Do not copy the product, brand, UI, or exact claims from the reference. Extract reusable film grammar:

- How the camera moves through UI.
- How user actions trigger scene changes.
- How dense finance/product data becomes readable.
- How foreground objects carry continuity.
- How text enters, holds, and leaves.
- How trust is built through review, approval, and status proof.

## Frame-by-Frame Logging Table

Use this table while studying a reference:

| Timecode | What appears | Camera move | UI/action | Text behavior | Transition | Purpose |
|---|---|---|---|---|---|---|
| 0.0-1.5s | Brand/pain/context | Fade or slow push | None or abstract UI | Short hook appears | Text-to-UI | Establish the problem. |
| 1.5-4.0s | Product surface | UI enters from depth/side | Cursor or card appears | Text reduces | Push/pan | Move from claim to product proof. |
| 4.0-8.0s | First operation | Camera follows target | Click, type, upload, select | Minimal label | Cursor-led cut | Make the workflow real. |
| 8.0-14.0s | AI/process moment | Calm push or local focus | Fields extract, rows highlight | Optional status text | Processing scan only if useful | Show transformation. |
| 14.0-22.0s | Result artifact | Foreground card/document lifts | Generated output appears | Caption names result | Foreground carry/match cut | Make AI output tangible. |
| 22.0-34.0s | Data/result view | Pan or zoom to KPI | Numbers/charts animate | One insight at a time | Data reveal | Prove value with change. |
| 34.0-45.0s | Human control | Slower push, stable framing | Review/approve/send | CTA/status text | Cursor-led or status cut | Build trust. |
| 45.0-60.0s | Success/outro | Pull back or fade | Final status visible | 2-3 benefits max | Hold/fade | Let the value land. |

## What To Extract

For each useful shot, write three things:

```text
Reference behavior:
Reusable rule:
Applied to this product:
```

Example:

```text
Reference behavior: A table row floats forward while the dashboard blurs.
Reusable rule: Lift out a real workflow object to simplify a dense UI.
Applied to this product: Selected client row becomes a foreground client card before analysis starts.
```

## Camera Rules Learned From Fintech References

- Start wider than the final focus so the viewer understands the product environment.
- Push only toward an active target: selected row, input, primary button, KPI, document, approval state, or success badge.
- Use slow camera motion during reading moments; use faster motion only for navigation or scene transition.
- Avoid static angled product screens. Perspective is meaningful only when the camera is moving through space toward a UI action.
- Keep UI text readable: no rotation on dense tables, forms, documents, or dashboards.
- Use pull-back only after the result is visible, to connect the detail back to the whole workflow.

## Transition Patterns To Reuse

| Reference pattern | Reusable transition | Use in new product demo |
|---|---|---|
| Text fades while UI slides in | Text-to-UI reveal | Turn a claim into immediate product proof. |
| Row/card lifts from dashboard | Foreground carry | Move from selection to detail without losing continuity. |
| Button click triggers new state | Cursor-led cut | Make the next scene feel caused by the user. |
| Generated document/card appears | Card morph or foreground lift | Show AI output as a tangible artifact. |
| Fields highlight in sequence | Processing proof | Show AI extraction/generation without decorative effects. |
| KPI or status changes | Status-change cut/data reveal | Prove the result, not just the interface. |
| Approval rows check off | Human-control payoff | Show B2B trust and governance. |

## Text Animation Rules

- Use short text, usually 2-7 words per beat.
- Let text appear just before or as the product action begins; do not let text explain something the UI never shows.
- Prefer word-stagger or phrase fade for editorial polish.
- Keep text still during dense UI reading.
- Remove supporting copy if it competes with the product operation.
- Use final benefit copy only after the workflow has produced a visible result.

## Data And Finance UI Rules

- Animate numbers from prior state to new state; do not pop all data at once.
- Reveal one insight at a time: KPI, trend, comparison, then conclusion.
- Use foreground labels for the changed value, not for every metric.
- Keep finance trust cues visible: status, date, owner, approval, compliance, risk, or audit trail.
- Do not over-style serious finance workflows with playful motion.

## Common Mistakes To Remove

- Decorative sweep that does not reveal extraction, generation, verification, or status.
- Focus rectangle that is offset from the real UI element.
- Overlay card covering the next important line of product text.
- Camera push with no destination.
- Static perspective used as a substitute for actual motion.
- Caption describes value while the screen only shows a static screenshot.
- Too many animated metrics competing at once.

## Translation Workflow

When applying a reference video to a new product:

1. Identify the product's real workflow object: client, invoice, task, ticket, report, document, account, or recommendation.
2. Choose one continuity object that can travel across scenes.
3. Map each reference shot to a product state change, not to a visual style.
4. Rebuild important UI as layers if focus, cursor, or data animation must be precise.
5. Render key frames and check alignment, overlap, readability, and whether camera motion has a target.
6. Remove any effect that still works only as decoration.

## Final Shot-Study Output Format

Return:

1. **Reference grammar**: 5-8 reusable rules from the video.
2. **Shot map**: timecode table with visual, camera, text, transition, and purpose.
3. **Product translation**: how each useful pattern maps to the target product workflow.
4. **Do-not-copy list**: brand/UI/product-specific details to avoid.
5. **Implementation notes**: layered UI, Remotion timing, camera paths, and key-frame checks.