Back to Blog
GoScript Journal

Showing Real Numbers Honestly In A Case Study Video

·7 min read·GoScript Team /Research

Honest numbers beat impressive ones

The fastest way to lose trust in a case study is to present numbers that do not add up. Honest figures, even modest ones, hold up under inspection. Inflated ones fall apart the moment someone checks.

I treat every number in a script as something I might have to defend. If I cannot say where it came from in one sentence, it does not make the cut.

Round for clarity, not for effect

Rounding is fine when it serves the viewer. Turning 47.3 percent into about half is honest. Turning 12 percent into a big jump because the word big sounds better is not.

Say the real figure first, then offer the plain-language version. That way the precise number is on record and the round one is clearly a shorthand, not a substitute.

Show the window and the source

A number is meaningless without a time frame. Was that a thirty-day lift or a twelve-month one? State the window every time. Short windows flatter results and viewers know it.

Name the source when you can: analytics, a client report, a public dashboard. A figure with a visible origin carries more weight than one that appears from nowhere.

If a number needs three qualifications to sound good, it is not a strong number. Pick the honest one and let it stand.

Explain the exceptions out loud

Some results come with caveats: a seasonal spike, a paid push, a one-off event. Mention them. Audience members who spot an unspoken caveat will distrust the whole video.

Caveats do not weaken a case study. They prove you thought about the result instead of just pasting it on screen. Stating what you cannot claim makes what you can claim stronger.

Key takeaways

  • Use figures you could defend in a single clear sentence.
  • Round for clarity, never to make a result sound bigger.
  • State the measurement window and the source of every number.
  • Call out seasonal spikes and paid pushes that shaped the result.
  • Treat caveats as proof of care, not as weaknesses.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel