Quarterly business review recap as an avatar video, three scenes
A QBR recap fits one 45-second Sume avatar video: result, one risk, next steps. A Plus render is $11.03; keep exact figures in the email, not the clip.
A QBR recap works as one Sume avatar video of about 45 seconds in three scenes: what moved, the one risk to watch, and the next steps. At the Plus tier and no product image that is 45 x $0.245 = $11.03 per account, so reserve it for accounts where a recap changes behavior, and keep exact figures in the script and the follow-up email.
Why a clip and not the deck
A deck is for the meeting. A recap clip is for the person who missed it, the executive sponsor who will watch 45 seconds and forward it, and the champion who has to explain the quarter upstairs. It works when it is short, specific to the account, and ends in one ask. It fails when it reads out a table of numbers aloud.
| Quality | Rate per second | 45 seconds |
|---|---|---|
| standard | $0.184 | $8.28 |
| plus (default) | $0.245 | $11.03 |
| max | $0.55 | $24.75 |
Three scenes
Use ordered video_inputs. Scene 1 (about 15 seconds): the headline result in one sentence, with at most two numbers. Scene 2 (about 15 seconds): one risk or open item, stated plainly. Scene 3 (about 15 seconds): the next step, an owner, and a date. Scenes share one avatar and one background, and the total planned duration must stay in the 4-60 second window.
Give each scene a stable id such as result, risk, next; Sume returns it in the scene previews. Keep the spoken text under the per-scene limit of 2,000 characters, though a 15-second scene is about 40 words.
{
"avatar_handle": "cs_lead",
"quality": "plus",
"aspect_ratio": "16:9",
"video_inputs": [
{"id": "result", "voice": {"type": "text", "script": "This quarter your team cut average setup time by a third.", "duration": 15}},
{"id": "risk", "voice": {"type": "text", "script": "One thing to watch: two integrations still run manually.", "duration": 15}},
{"id": "next", "voice": {"type": "text", "script": "Next step: we will automate both by the end of next month.", "duration": 15}}
]
}Workflow for many accounts
- Generate scripts from your CRM data, but have the account owner read each one; an avatar says whatever the script says.
- Submit each as a preview first and review the first frame for a sample of accounts, then render in waves. Queue capacity on your plan limits how many jobs wait at once.
- Use an
Idempotency-Keythat includes the account id and quarter so a retry never bills twice. - Burn captions in for forwarded clips; they often play muted.
When not to
Skip the video for accounts in a dispute, for bad news that needs a human voice, and for anything with sensitive figures. The avatar is not the account owner, so say that in the email that carries it. A recap also goes out of date as soon as numbers change. See the previews docs for the approve-then-render flow.
Sources
Related posts
More in Use cases
- Qwen-Image 2.1 circle-and-edit prompts, 10 references: a test plan
Qwen-Image 2.1 lists circle annotations, mask edits, 10 references. A test plan, plus the Sume route: mask_url and 16 references on ChatGPT Image 2.5.
- Real-estate listing video: 30-second Wan 3.0 clip from ten photos
Turn ten listing photos into a 30 second video on Sume: one reference-to-video clip or ten 3 second photo clips, both $3.75 at 720p. Which is more faithful.
- Realistic AI b-roll in a Short: is the Altered content flag needed?
A realistic generated scene that did not occur needs YouTube's disclosure; a fantasy scene does not. Sort Sume clips before upload using the page's own list.
- Recipe blog post to video: scrape text, send step photos to Wan 3.0
Wan 3.0 can take a webpage as a reference at Alibaba, but Sume does not expose web_url. Scrape the recipe, then send step photos as references. Steps and curl.
Written by Sume