Prototype for team review. Sign-in, forms and the workspace are mock: nothing is sent. New headlines, and text with a dotted orange underline, are proposals waiting on the founders. What’s real
Splice Log · LG-122 · Testing 04.11.2026Entry 1 of 9 · Field test

Creator videos to weekly email

Our field-test workflow pointed at a creator brand's weekly subscriber email, with two independent reviewers checking every line.

NewRead length · 4 min
Stage
Testing
Type
Email workflow
Logged
04.11.2026
Controls
Spend cap / kill switch / full record
Read the full spec

Field test by Angelo Pullen, checked 4 November 2026. The brand, its founder and the channel are not named.

Spec sheet · Creator videos to weekly emailLG-122
Part / LG-122Stage / TestingChecked / 2026-11-04Rev / 1.0

Creator videos to weekly emailtechnical specification

CREATOR VIDEOS TO WEEKLY EMAIL is a test of our field-test workflow on a weekly subscriber email for a creator-founded toothpaste brand: pick three of the founder's recent videos, quote him word for word, add cited tips from the ADA and NIH, and have two independent reviewers check every claim before anything could be sent. Nothing was sent.

01

Overview

Why it's in the log

Creator brands want to turn the founder's videos into email without spreading claims they cannot support. We tested whether our research workflow can do it on a real week, and where a person still has to step in.

What we found

The workflow found its own sources and drafted a cited issue. Reviewers raised 10 problems in the first draft; by round 4 the subscriber copy passed 57 of 57 claim checks. The blocker was outside the copy: two of the three videos ended with product pitches in disease-type wording, and the brand's site made gum and enamel claims, so every link was held.

How it fits

The workflow researches, drafts and runs the first review. An editor listens to every quote, a separate compliance checker clears or blocks, and the brand's approver gives a written go. Counsel clears the approach once.

What it means for your team

You keep your email platform and your creator's channel. The research and checks run beside them, and a person on your team still approves every send.

02

Specifications

Category
Process: research workflow, two independent reviewers, a person's approval
Input
3 recent videos from the founder's YouTube channel, picked by recency, views, topic and length
Transcripts
YouTube's automatic captions; 248 of 248 extracted quotes matched by script
Sources found
ADA, NIH, FTC, FDA and the Gmail and Yahoo sender rules, all found by the workflow
Output
One sample issue: 3 video sections, 5 verbatim quotes, 4 cited habits, 8 sources
Review
2 independent reviewers over 5 rounds: a claim check, and a dentist and compliance read
Sent
Nothing. No email platform, account or site was touched
03

What we measured

Review roundClaims checkedClaims passedBlockers in the copyBlockers outside the copy
1453830
2514820
3535213
4666404
5, changed lines only191804

The fluoride line

The toothpaste is fluoride-free, and the ADA and NIH pages the workflow cited recommend fluoride toothpaste. The first draft left fluoride out. The dentist reviewer blocked that, so the final issue's first habit is to brush with a fluoride toothpaste, and the product block says the toothpaste has none.

The videos

All three videos end with the founder pitching his own toothpaste. Two pitches use disease-type wording, and none says aloud that the segment is an ad. Linking them would make those claims the email's, so the sample quotes the videos and holds the links.

The website

The landing page made gum and enamel claims, so the product link is held until counsel clears one page with cosmetic-only wording.

Where it needed help

A plain fetch could not read the channel's video list; the built-in browser on the operator's computer could. The captions spelled the brand's name at least nine ways, so every quote needs one listen before sending.

04

What it costs

ItemCost
Model usageNot measured in this run
Transcripts and video factsA transcript API on our existing plan; per-call cost not recorded
Email platformNone used; nothing was sent
05

Limits and caveats

  1. One week, one issue, one run. It is not a measure of how the workflow does over many weeks.
  2. Nothing was sent, so there is no open, click or unsubscribe data.
  3. Quotes were checked against automatic captions, not audio.
  4. The reviewers are AI. A person and counsel still have to clear the email before any send.
  5. The rules research is not legal advice.
06

How we tested it

01

Ground and pick

Read the team's earlier research, then the channel's latest uploads in a real browser, and picked three videos by a stated rule.

02

Pull and research

Pulled the captions and kept the founder's words exactly. Found the brand facts, the FTC, FDA and email rules, and ADA and NIH pages for the tips.

03

Draft and review

Wrote the sample issue with a source for every claim. Two reviewers who did not write it checked every line over five rounds until the copy was clean.

07

Questions people ask

Can it turn a creator's videos into an email on its own?

It drafted a cited issue on its own. It needed a real browser to read the video list, and a person must listen to the quotes and approve every send.

Does it find its own sources?

Yes. It was given only the channel and the brand's site, and found the ADA, NIH, FTC, FDA and email-rules pages itself.

Why were the video links held?

Two of the three videos ended with product pitches in disease-type wording. Linking them would make those claims part of the email.

Does a person still check the email?

Yes. An editor, a separate compliance checker and the brand's approver sign off on every issue, and counsel clears the approach once.

08

Sources

spliceops.lrgfrmt.com/log/creator-weekly-emailTesting / 04.11.2026
Next in the logImage consistency audits LG-121
Copy the promptBook a session