Voiceover Notes

CONTENT ANALYSIS

This is a faceless long-form explainer script about a company reducing its cloud infrastructure costs. The audience is likely individuals with some knowledge of cloud computing and logistics, and they are moderately patient as they are looking to learn about cost savings. The emotional journey of this script can be described as: Sceptical → Informed → Convinced, as it presents a real-life scenario where significant cost savings were achieved through careful analysis and optimization.

ARCHETYPE

The chosen archetype is The Quiet Authority, as selected by the creator. The reason for this choice is that the script deals with finance and business, which are typical topics for this archetype. The two runners-up that were rejected are The Expert and The Storyteller. The Expert was rejected because while the script does contain some technical details, its primary focus is on the financial and business aspects of the story. The Storyteller was rejected because although the script tells a story, its tone is more informative and authoritative than narrative-driven.

WORD BUDGET

The word budget is calculated based on the target runtime and words per minute (WPM). For a faceless long-form video, the WPM is 140. Given the target runtime of 3 minutes, the word budget is: 3 minutes × 140 WPM = 420 words.

NARRATION SCRIPT

So you're probably aware that cloud infrastructure can be expensive. Honestly, it's one of those things that can creep up on you if you're not careful. I want to be honest about it: a mid-size logistics company was spending forty-eight thousand pounds a month on cloud infrastructure back in 2023. That's a big number.

The person who managed to cut that figure down to nineteen thousand pounds nine months later now says she'd put some of it back. Specifically, the savings didn't come from one big decision, but from thirty-one separate line items. And the largest saving was only eleven percent of the total. Right, that's a lot of small changes adding up.

She called the first four months "free money". They found six managed database instances, three of which were staging environments that were sized like production. Someone had cloned a configuration file two years earlier, and nobody had looked at it since. It was costing them four and a half thousand pounds a month for machines that sat idle nineteen hours a day. So, that was an easy win.

Then the free money ran out. What came next was harder: cutting things that were genuinely doing a job, just expensively. For instance, hosted continuous integration went from seven thousand pounds a month to eleven hundred. That's a real saving of nearly six thousand pounds every month, verifiable on the invoice.

MARKED SCRIPT

So you're probably aware that cloud infrastructure can be expensive [pause 1]. Honestly, it's one of those things that can creep up on you if you're not careful [emphasis]. I want to be honest about it: a mid-size logistics company was spending forty-eight thousand pounds a month on cloud infrastructure back in 2023 [pause 1]. That's a big number [emphasis].

The person who managed to cut that figure down to nineteen thousand pounds nine months later now says she'd put some of it back [up]. Specifically, the savings didn't come from one big decision, but from thirty-one separate line items [breathe]. And the largest saving was only eleven percent of the total [down]. Right, that's a lot of small changes adding up [emphasis].

She called the first four months "free money" [pause 1]. They found six managed database instances, three of which were staging environments that were sized like production [slow]. Someone had cloned a configuration file two years earlier, and nobody had looked at it since [pause 1]. It was costing them four and a half thousand pounds a month for machines that sat idle nineteen hours a day [emphasis]. So, that was an easy win [down].

VOICE PROFILE

Tone: conversational, honest, dry sense of humor
Accent: no preference
Pace: 140 words per minute
Emotion baseline: calm, with a touch of enthusiasm when discussing personal experiences

VOICE DESCRIPTION

The ideal voice is a direct and honest one, with a dry sense of humor. It should sound conversational, like speaking to someone who is already competent in the subject matter. The voice should have a moderate baseline energy, with occasional spikes for emphasis, and a professional warmth with a touch of personality. A style reference for this voice would be a calm, measured narrator, similar to something between Wendover Productions and the BBC's More or Less.

DELIVERY NOTES

• Emotional arc: The voice should start with a sceptical tone, then become more informative and enthusiastic as the story unfolds, finally settling into a thoughtful and encouraging conclusion.
• Emphasis style: Light stress on key terms, such as numbers and savings, to draw attention to important information.
• Numbers: Delivered quickly and clearly, with a slight pause after each to allow the listener to process the information.
• Avoid: Do not oversell the opening, as the claim is strong enough said plainly. Avoid flattening out the statistics, and do not rush the explanation of the engineer's story. Do not use a rising inflection on statements, and avoid a breathless or urgent tone.