0% Completion: We Never Tested the Hook
September 2, 2026 · 6 min read · Scout7
A candid B2B video case study: six videos, 0.00% completion, 5.2-9.4 second watch times, and the testing mistake behind them.

In short-form video strategy for B2B, optimize the opening before you optimize the story. Our six-video batch failed not because the ideas were empty, but because we built 34-84 second videos, measured the ending, and skipped the only comparison that could tell us which first three seconds deserved to survive the scroll.
A hand lands on publish six times in eight days, and six times the ending never gets seen. That is the whole reason this piece exists.
We are not using industry averages here. We are looking at our own batch from August 21-28, where every video ended at 0.00% completion and average watch time sat between 5.2 and 9.4 seconds.¹ ²
The mistake was specific. We had already written the right rule for B2B video marketing optimization, and then ignored it.
That rule matters because the ugly number alone does not tell you what to fix next.
The 0% Completion Reality

And that is where the embarrassment starts: all six videos finished at the same number. Not low completion. Zero.
Across six videos published from August 21-28, completion rate was 0.00% on every one.¹
Average watch time also stayed under ten seconds, landing between 5.2 and 9.4 seconds, while the videos themselves ran 34-84 seconds.²
- Six videos, one result: every post ended at 0.00% completion ¹
- Average watch time: only 5.2-9.4 seconds across the batch²
- Runtime planned: between 34 and 84 seconds for each video²
- What this forced us to admit: we built for endings no one reached
The first useful step in any B2B video marketing optimization effort is to stop softening your own data. Ours said the same thing six times.
And once we stopped staring at the outcome, the real production mistake became obvious.
The Test We Wrote Down and Never Ran

And then the more painful truth showed up: the creative was not the first thing that failed. The process did.
We had a standing rule that every video should ship with three hook variants so the opening could be compared instead of guessed. Then we shipped all six videos with one hook each and never ran the test once.
That means we do not know which hook was weakest. We only know that all six videos ended at 0.00% completion.¹
Based on what we saw when our own six-video batch went out with one hook each instead of the three-hook comparison we had already defined, the first failure was missing measurement, not missing effort.
- Our rule existed: three hooks per video, same core facts
- Our actual output: one hook per video, six times
- What we lost: the ability to compare openings under the same conditions
- What we cannot claim: that any single hook caused the result
- What the confession is: you cannot fix a hook you never tested
That is the core lesson in this case study on B2B video hook testing. If no alternatives exist, failure teaches less than people think.
Which brings us to the arithmetic that made the problem impossible to ignore.
We Scripted a Minute. They Watched the Trailer.

And once we looked past completion, the gap between what we made and what people consumed was brutal. We scripted a minute. They watched the trailer.
Our videos ran from 34 to 84 seconds, while average watch time sat between 5.2 and 9.4 seconds.² That does not prove the exact second viewers dropped, because we do not have a retention curve.
It does prove something simpler and more useful: most of the script likely never had a chance to matter.
- Planned length: as much as 84 seconds ²
- Consumed length: as little as 5.2 seconds on average ²
- What 0.00% completion proves: nobody reached the end¹
- What it does not prove: the exact drop-off point without per-second retention data
- Practical answer: in this dataset, “ideal length” was whatever fit inside roughly 5-9 seconds
So what is the ideal length for a B2B marketing video in 2026? In our case, it was not a fixed runtime. It was the amount of value a stranger could understand before leaving.
That changes the build order completely.
Rebuilding Our Hooks: From Narrative to Impact

So the next change is not “write tighter.” It is stricter than that: seconds 0 to 3 must show a specific number.
Our rule now is simple. Clip 1 is never the presenter. The presenter can appear in clip 2, but the first frame has to carry proof by itself.
The opening should show a receipt, not ask for patience.
What belongs in those first three seconds is a number made physical: a price tag, a dot grid, a ledger page, a visible count. Not a greeting. Not a logo. Not “in this video.” Not context spoken from camera.
- Clip 1 is never the presenter on camera
- The first frame shows proof without needing narration
- The proof is numeric: price tag, dot grid, ledger page
- No greeting or brand setup in seconds 0-3
- The test: would a stranger stop for this without knowing us?
That is our practical short-form video strategy shift. Numbers shown beat context spoken because they arrive faster than explanation.
But a better hook philosophy is still not enough unless we finally run the test correctly.
The Test We Can Finally Run

And that is the part still ahead of us: the fix is copyable, but the result is still unknown. We have not earned a victory story yet.
Here is the test. Take one piece. Keep the facts identical. Build three different opening three-second hooks. Post them in the same daypart. Then compare which version holds attention best.
This is B2B video hook testing in its cleanest form because the opening is the main variable, not the whole narrative.
- Use one core asset with the same facts in every variant
- Change only the first three seconds in each version
- Post in the same daypart to reduce timing noise
- Read results on Instagram and Threads where per-post views are clear enough to compare
- Avoid X for this test if every variant returns zero visible engagement
- State the limits plainly: one brand, six videos, eight days, no retention curve, no per-second cost data
How do you optimize B2B videos for short attention spans? In this case, by testing multiple openings against the same facts instead of scripting one full narrative and hoping it survives the scroll.