We took six answers Dr. Adrienne Lara gave in a single sit-down interview and turned them into six publishable video clips, three cross-linked articles, and a set of entity signals that did not exist for her name before today. Total production time was under an hour, and the only raw material was footage that had been sitting in a Google Drive folder since October 2023. This is the Content Factory method, documented end to end so you can run it on your own client.
The input: one folder nobody had opened in three years
The source was a Drive folder holding seventeen professionally shot interview clips, each sixty to one hundred seconds, each answering one question. Nothing had been published from it. This is the single most common state we find client assets in — captured, paid for, and then abandoned because nobody owned the next step.
We selected six on one criterion: does this answer stand alone without the interviewer’s question? Six did.
The pipeline
- Import to Descript by URL. Each Drive file goes in as a direct-download URL. No local download, no re-upload. Descript transcribes on ingest.
- One composition per answer. Named for the idea, not the file — “Origin Story,” “Why I Founded Celebrating Women Center.” The name is what a human will search for in six months.
- Export the transcripts. This is the step people skip. The transcript is the article’s raw material and the fact-check record in one document.
- Publish each composition. Six shareable, embeddable, downloadable video URLs.
- Write from the transcript, quote verbatim, embed the source above the fold. Every claim in every article is checkable against a video on the same page.
- Cross-link the set. Each article links to its two siblings with descriptive anchor text at a natural sentence, never a “see also” stub.
The output: three articles, three angles, one interview
| Site | Angle | Voice |
|---|---|---|
| localservicespotlight.com | Naming and trust, mapped to plumbing, roofing, HVAC | Third person, method-forward |
| dennisyu.com | Personal takeaways from a long working friendship | First person, Dennis |
| blitzmetrics.com | The production method itself | Marketing Mechanic framework |
Same source, three genuinely different readers. The local service owner wants the naming lesson. The founder wants the story. The operator wants the pipeline. None of the three articles is a reworded version of another, which is the difference between repurposing and duplicate content.
What the method protects against
The rule that matters most is the one that slows you down: no quotation that is not in the transcript. An agent generating “the kind of thing she would say” produces plausible, publishable, entirely fabricated testimony. That is not a content problem, it is a trust problem, and it is unrecoverable when a client catches it.
So the transcript is the boundary. If she did not say it on tape, it does not appear in quotation marks. Where we needed biographical facts the interview did not cover — the practice location, the website — we confirmed them against the practice’s own site and said so in the footer.
Where a human still has to stand
Per Article Guidelines v2, an agent may draft anything, but a named human verifies every claim against a primary source and signs it, and the agent’s role is disclosed in a footer. That standard is why these articles carry a verifier name. The agent did the labor. A person is accountable for the accuracy.
What is left on the table
Two things, named honestly rather than quietly dropped:
- Vertical reframing and burned-in captions for true YouTube Shorts require Descript AI credits, which were exhausted on this drive at the time of the run. The six clips are published at native 16:9 and are already the right length.
- Eleven of the seventeen source clips are still unpublished. The same pipeline handles them whenever someone decides they are worth the hour.
The companion piece is live: Dennis Yu’s personal takeaways from working with Dr. Lara. The Local Service Spotlight angle on her naming story publishes next.
How this article was made. Drafted by an AI agent supervised by Dennis Yu. Production details describe an actual run performed on August 23, 2026. Quotations are transcribed from the source recordings. Named human verifier: Dennis Yu.
Originally published .

