An animated invoice summary video (the per-customer billing recap)

The standard monthly billing email is the lowest-engagement piece of communication in SaaS. It lands in the inbox, gets glanced at, and is deleted before the customer reads any of the numbers inside it. The numbers are the part that actually matters.

A short animated recap — the same numbers, in a 20-second video — is a meaningfully more engaging way to deliver the same information. It's also one of those "obviously possible" pieces of automation that almost nobody ships because the per-customer production cost looks intimidating. With a template + a renderer, it isn't.

What goes in

For most SaaS bills, three to five metrics carry the story:

• The total. Big number, count-up.
• The biggest line item. "Compute: $1,247.32".
• The delta vs last month. ±%, colored.
• A "you saved" or "you used more of" callout. Specific to the product.
• The next charge date. Quiet, at the bottom.

Plus the customer's name. That's it. Five fields per customer drive the entire video.

The template

A four-scene flow:

1. Opener (3s). "Hey NAME, here's your May invoice."
2. The total (4s). Big number, ease-out count-up, tabular numerals.
3. The breakdown (5s). A small bar chart of the top three line items.
4. The delta + next charge (4s). "Up 8.4% vs April. Next charge: June 14."

Total: 16 seconds. The right length for an embedded email video.

The data

One row per customer, joined from your billing system:

customer_id,name,total,top_item_label,top_item_value,delta_pct,next_charge_date
c-001,"Acme Co.",2847.32,"Compute",1247.32,8.4,"2026-06-14"
c-002,"Beta LLC",1118.00,"Bandwidth",640.00,-3.2,"2026-06-15"
...

The renderer reads the row, fills the template, renders the 16-second MP4. The CSV is the contract; if a field is missing, the corresponding scene is hidden.

The delivery

Two reasonable paths:

1. Email with a poster + link. The email body has the customer's name, the total, and a poster image of the video. Click → opens the video on a one-off page.
2. In-app modal. Next time the customer signs in, an "Your May recap is ready" modal plays the video.

Don't try to inline an MP4 in the email; most email clients block autoplay. The poster + link pattern works in every client.

The compliance

Billing communications have legal copy — line-item breakdowns, terms, contact info. Don't try to put all of that in the video. The video is the summary; the full invoice (PDF or web page) is linked from the email and contains everything legal requires.

The privacy question

Per-customer video means per-customer data on a render server. Treat it the same as any other PII flow: server-side render, no logging of the input data, short-lived output URLs with signed access. The MP4s themselves should expire after the customer has seen them (or after 90 days, whichever is sooner).

The scale math

For 10,000 customers × 16-second videos at 1080p:

• ~24 render-seconds per customer.
• 10,000 × 24 = 240,000 render-seconds = ~67 hours on one box.
• 30 parallel workers: ~2.2 hours overnight.

The end-to-end "10k variants overnight" path is in render 10k variants overnight. The CSV-driven render pattern is in batch personalized videos from CSV. The KPI scene that drives the recap is detailed in animated KPI cards that look like money.

A close

A billing email is a transactional message. A 16-second recap video is the same information delivered with editorial care. The cost difference between the two, once you've built the template, is rounding error. The engagement difference is not. The companies that figure this out treat the monthly recap as a touchpoint, not a notification — and the customers remember.