VERIFICATION — CASE STUDY

1,078 stories. One gate. Zero broken videos left.

A US community impact platform (name withheld)

1,078stories checked across 12 cities, with every video defect class driven to zero
1,078stories audited across 12 cities
989people in the dataset
357stories carrying embeds at the first full run
110Instagram aspect ratios rebuilt from the real streams
27photo posts stripped and added to a blocklist
743stories passing in the final round

How it worked

STEP 1

Seven evidence feeds feeding one verdict per story

STEP 2

PASS, CONDITIONAL and FAIL verdicts, conditional may not ship

STEP 3

Stream dimensions only, never cover photo dimensions

STEP 4

A failed once blocklist, a failed post never returns untested

OUTCOME

1,078 stories checked across 12 cities, with every video defect class driven to zero

Meet the platform

A US community impact platform publishing short stories about acts of kindness, city by city: 989 people, 1,078 stories, hundreds of embedded videos from Instagram, Facebook, TikTok and YouTube. The site had grown fast, and its quality control had not kept up. The owner kept finding broken stories himself, one by one, which is the most expensive way to run quality control there is.

The challenge

A video embed can pass every cheap check and still be broken for a visitor. The link returns 200 while the video was deleted at the source. The post scrapes fine while its embed endpoint serves a removal notice. The recorded dimensions describe the cover photo, not the video stream, so the player renders in the wrong shape. A photo post wears a video embed that throws the visitor off the site on the first click. None of this shows up in an HTTP check. It only shows up when you gather real evidence per story and refuse to ship on anything less.

The solution

A gate with seven evidence feeds

We built a technical gate that scores every story from evidence, not impressions: recorded browser play test verdicts, stream dimensions pulled from the actual video files, YouTube embed permission and country availability fields, media type and carousel first slide checks, a one post one story duplicate check, and a failed once blocklist. Each story gets one verdict: PASS, CONDITIONAL for never play tested and may not ship, or FAIL.

Fix every failing class, then run it again

Round one came back 683 PASS, 285 CONDITIONAL, 110 FAIL. The fixes went class by class. Aspect ratios were rebuilt from the real streams on 110 Instagram stories, 15 of which were recorded as portrait and are actually landscape, and all 47 Facebook embeds got their true stream ratios. Twenty seven photo posts and photo first carousels were stripped to text and added to the blocklist. Twenty eight YouTube embeds whose owners had disabled embedding were stripped. Three duplicate posts shared by two stories each were deduped to one story each.

Round two came back 710 PASS, 289 CONDITIONAL, 79 FAIL, and every one of the 79 was a single class: text stories with no cover photo anywhere in their sources. A cover wave pulled candidates from each story own source article and eyeballed every one: 34 stories got real covers, and 45 were deliberately left text only because their sources held only logos, ads, game action shots and unrelated images. A wrong cover is worse than no cover.

Round three: 743 PASS, 289 CONDITIONAL, 46 FAIL, of which 45 were those same honest text stories and one was a profile photo that existed in the build but had never reached the server, uploaded and verified the same pass.

The incident, left in

Midway through the fix wave, a patch to the page script dropped a closing parenthesis and the story viewer went dead site wide for about 15 minutes. It was caught by our own live verification, fixed, and the live script syntax checked. The standing rule that came out of it: after any edit to that script, extract the built block, syntax check it, deploy, then syntax check the live block too.

The results

Honest note: 289 stories sit at CONDITIONAL, never play tested. They are a watchlist, not a defect list, and the gate treats them as unproven rather than passed. That distinction is the whole point of the gate: it says what it knows and labels what it does not.

The return: the owner stopped being the quality control department. A full site audit that used to mean a human clicking through a thousand stories now runs in about 13 minutes for under two dollars, and every story on the site carries a verdict earned from evidence.

FAQ

Why is a link returning 200 not proof a video works?

Because the page can be alive while the video is deleted, region blocked, embedding disabled by its owner, or served in the wrong shape. Only the embed endpoint, the stream itself and a real play test can settle it.

What does CONDITIONAL mean?

The story has never been play tested in a browser, so the gate has no direct evidence it plays. Conditional stories may not ship as new work. They are the unproven watchlist, kept separate from proven failures.

Why leave 45 stories without covers?

Their own source articles held no usable photo: logos, ads, stock graphics and unrelated images. Publishing a wrong face on a real person story is a worse failure than a clean text card.

What does the gate cost to run?

The full 1,078 story loop cost $1.98 in total model usage and runs in about 13 minutes, after the evidence phase was threaded and the stream probes cached.

By the numbers

stories audited across 12 cities1,078
people in the dataset989
stories carrying embeds at the first full run357
Instagram aspect ratios rebuilt from the real streams110
photo posts stripped and added to a blocklist27
stories passing in the final round743

Bars are scaled so very small and very large numbers fit on one chart. The values printed are exact.

THE ROI
$1.98

total model cost for the full audit and fix loop over 1,078 stories

A complete 1,078 story audit, fix and recheck loop for $1.98, about a fifth of a cent per story.

What was built

The concrete pieces this engagement shipped, in one list.

Your mail is being sent unauthenticated. Here is the full fix.

Lower stack cost. Back in the inbox. Built to send at any scale.

We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.

Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.

Free · Written plan + fixed price · No sales call required

More case studies

Lead dataA US M&A advisory firm (name withheld)
46,000

prospects matched on LinkedIn, 93% of the final list

151,218 rows in. 49,373 decision-makers out.

READ CASE STUDY →

ROIValid decision-maker leads at $0.067 each in the pilot, then all 49,373 scored for $1.54 total.

InfrastructureA US advisory firm's cold email program (name withheld)
100%

sender health at the end of the wave, with 1 hard bounce in the final campaign

30 inboxes. 1,596 sends. Zero burned.

READ CASE STUDY →

ROIZero inboxes burned: 1,596 sends delivered and the pool ended at 100% health, ready for the next wave.

OutreachPartner outreach for a US advisory firm (name withheld)
Step 2

the follow-up, not the first touch, produced the first interested partner reply

The first yes did not come from the first email

READ CASE STUDY →

ROI958 sends across the wave produced an interested partner and a $1,000 logged opportunity.

Copied
Free tools Get an inbox plan