# How Sean C Davis is trying to cut a 3-4 hour video publishing job to an hour with Claude Cowork

Sean C Davis has produced videos for many years. He says going from nothing to a published, distributed video usually takes 3-4 hours, even when he keeps edits to a minimum. He built a pipeline in Claude Cowork that runs through six phases. Cowork picks up a recorded video and transcribes it locally with Whisper. It proposes titles and descriptions, drafts a blog post as a pull request and proposes a Figma thumbnail. It uploads to YouTube and drafts and schedules social posts for X, Bluesky and LinkedIn. He reviews and approves at each phase. His goal is to get the whole process down to about an hour. He says he has not reached it yet.

| | |
|---|---|
| **Who** | Sean C Davis, developer educator. His X and Bluesky bios read "Helping developers build better websites" and mention Netlify, former Stackbit and CFE.dev host. Writes at [seancdavis.com](https://www.seancdavis.com) |
| **Problem** | A published, distributed video "usually takes 3-4 hours," so one video a week "has felt like an accomplishment" |
| **Stack** | Claude Cowork (project with a dedicated directory and an inbox folder), Whisper (run locally), a repository with pull requests, Netlify deploy previews, Figma in the browser (thumbnail template), YouTube, a Markdown file of social drafts, X, Bluesky, LinkedIn, voice note transcriptions |
| **Confidence** | Medium (first-person on his own blog; no outcome metrics; the stated goal is not yet met) |
| **Last verified** | 2026-10-21 |

## The problem
He says, "With that level of commitment, it's hard to produce as much as I want to." The work tends to span several days. His hypothesis is this: "If Cowork could handle the repeatable tasks and I could keep my time focused on the recording and the things that require human judgment, I might just be able to record and publish daily." His goal is "to complete the recording, editing, distribution, and promotion process in about an hour."

He wants to keep his voice in the output. "Cowork handles the execution and proposes direction. I handle the judgment." He adds: "The point isn't to produce more content for its own sake."

## The blueprint (as he describes it)
1. **Record and drop it in the inbox.** He tries to keep each video to 10 to 20 minutes. If there were major goofs, he notes the timestamp and cuts them. Otherwise he treats the recording as live. He drops the exported video into an inbox folder inside his Cowork project directory.
2. **Set up a working directory.** Cowork picks up the video from the inbox and generates a slug for the project. It creates a dated working directory and moves the file in.
3. **Transcribe locally.** Cowork runs the video through Whisper locally. A 20-minute recording usually takes a few minutes, so he works on something else in the meantime.
4. **Propose direction.** Cowork proposes a YouTube title and description and a blog post title and description. It also writes a general summary of the direction for the blog post. He reviews the proposals, gives the go-ahead or pushes back and iterates, then approves.
5. **Draft the blog post as a pull request.** Cowork drafts a full post from the transcript. It follows the style guide and rules he has set up. It submits the draft as a pull request on his repository so he can see the Netlify deploy preview. He usually records a voice note and shares the transcription in the chat thread. They iterate until the post is ready. He describes this as being "an editor in a live meeting with the agent."
6. **Thumbnail and YouTube upload.** This runs in parallel with the blog post. Cowork opens Figma in the browser, finds his thumbnail template and proposes a thumbnail for the video. He usually makes a few tweaks, then exports the final version into the project directory. He tells Cowork it is ready. Cowork uploads the video with the title, description and thumbnail and sends him the YouTube URL.
7. **Draft social posts in two sets.** After the video and blog post are published, Cowork writes social drafts in a Markdown file. The first set promotes the video and goes out immediately. The second set promotes the blog post and is scheduled for the following business day. Each set has drafts for X, Bluesky and LinkedIn, with the tone adjusted for each platform.
8. **Approve, then post or schedule.** He edits the drafts and tells Cowork when they are approved. Cowork posts and schedules natively on the platforms where it can. Bluesky has no native scheduling, so Cowork creates a custom scheduled task that fires at the right time.

## Stated results
- He has been through the process "a few times now."
- "it's definitely still taking more than an hour for each body of work."
- "I'm still quite a ways from proving the hypothesis, but I don't think it's out of the question."
- He says "the foundation gets stronger each time."
- No daily publishing, views, traffic or time-per-phase results are stated.

## Caveats
- The one-hour goal has not been reached. He says "every time there's something small to tweak in the system."
- The post says the pipeline has six phases but does not number them. The steps above follow the order of his description and may not match his phase boundaries.
- The post does not say how Cowork posts to X and LinkedIn. It only says Cowork posts and schedules natively "for the platforms where it can."
- This is his own blog, not a vendor site, and the post does not sell a product, course or kit. His bios mention Netlify, and the pipeline uses Netlify deploy previews. The post does not state any relationship with Netlify.
- He frames the goal as getting more of his voice out, not more content.
- Handles (verified 2026-10-21):
  - X: @seancdavis29, linked from seancdavis.com. The X bio links back to seancdavis.com and his Bluesky.
  - Bluesky: @seancdavis.com, a domain handle linked from seancdavis.com.
  - LinkedIn: linkedin.com/in/seancdavis29, linked from the post.
  - GitHub: github.com/seancdavis, linked from seancdavis.com.
  - YouTube: channel UCskZ3MNbeGSVyOTL0L5ooww, linked from seancdavis.com.
  - Threads, Instagram, Mastodon, TikTok: not checked.

## Sources
- https://www.seancdavis.com/posts/how-i-built-a-video-to-published-pipeline-with-claude-cowork/ (primary: first-person build write-up on his own blog, dated Apr 11, 2026)

---
*Want agents like these working your distribution? [See the Agent Stack Teardown](/agent-stack-teardown). Get new teardowns weekly: [subscribe](/subscribe) (double opt-in).*