Thanksgiving week release notes video for SaaS: three avatar clips

Release notes shipped the week of Thanksgiving (Thursday, November 26, 2026, per OPM, read 2026-10-03) get read by fewer people, because many are away. Three short avatar clips, one per change, give the ones who are watching a way to catch up in a minute. Each clip is a script of 4 to 60 seconds on the avatar route, with captions burned in, and each gets a written version under it so no one depends on video alone.

The date is the only outside fact. All product claims in the clips are yours, and the avatar reads whatever you write.

One clip per change

Resist the urge to cover every item. Pick the three that a customer will notice.

Keep the presenter consistent

Create one avatar for the product team, from a prompt or a consenting person's photo, and reuse its handle for every release. A familiar presenter turns a changelog into a series.

• Write the script from the written release notes, not the reverse.
• Use inline captions so the clip works on mute.
• Link the full changelog from the post, not from inside the video.

Render one

Each change is one talking-video job, so a loop in your release script can render all three.

curl -X POST https://api.sume.com/v1/avatar-1.0/talking-video \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: release-notes-1" \
  -d '{
    "avatar_handle": "my_presenter",
    "aspect_ratio": "9:16",
    "quality": "plus",
    "script": "This week we shipped a faster export. Large projects now finish sooner, and you can leave the page while it runs.",
    "captions": {
      "enabled": true,
      "style": "slam",
      "language": "auto"
    }
  }'

Limits

A clip says what you tell it, so the risk is overclaiming. A line such as faster export needs a measured basis in your own data, or should be phrased without a number. Do not promise dates you do not control. The sample script is a placeholder for your own product.