# How Chris Alarcon turns one recording into 14 shorts a week

Chris Alarcon records one talking-head session and lets a Claude Code system handle the rest: cutting, QA, polish, scheduling and native rewrites for his newsletter and LinkedIn. He keeps two jobs for himself, recording and approving. Each stage has a check, so mistakes get caught instead of shipped.

| | |
|---|---|
| **Who** | Chris Alarcon ([christopheralarcon.com](https://christopheralarcon.com), X [@chrisralarcon](https://x.com/chrisralarcon), YouTube @chrisbuildssystems) |
| **Problem** | One person can't hand-produce daily shorts, long-form, a newsletter, LinkedIn and a blog |
| **Stack** | Claude Code, Blotato (scheduler), phone camera, handheld mic |
| **Confidence** | High. First-person, with public output he invites readers to check |
| **Last verified** | 2026-10-14 |

## The problem
He writes that "a single person working full time cannot manually produce daily shorts, weekly long-form, a newsletter, LinkedIn, and a blog."

## The blueprint
1. **Record:** one batched talking-head session on his phone, retakes included. He calls this "the only unautomatable part."
2. **Cut:** the system transcribes, removes retakes and dead air, and renders clean cuts. It keeps his words instead of "improving" them.
3. **QA:** each cut is re-transcribed and compared with the original to answer "did the edit clip a word or break a sentence?" The result is ship or fix, with timestamps.
4. **Polish:** title overlay in the safe zone, captions checked against the transcript, real screenshots for any claim needing proof, and audio mastered to broadcast loudness. He reviews it.
5. **Schedule:** batch upload to TikTok, YouTube Shorts and Instagram through a scheduler.
6. **Repurpose:** the newsletter and LinkedIn get native rewrites of the week's ideas, "never a copy-paste." The system drafts and he edits.
7. **Learn:** a weekly analytics pull. He decides next week's topics.

**His minimum version:**
- Write the process as numbered steps.
- Automate the transcript.
- Build one rewrite lane.
- Add one QA question per stage.
- Only then add platforms.

## Stated results
- One recording session becomes 14 shorts a week. The rest of the week's thinking becomes blog posts, a Tuesday newsletter and LinkedIn posts.
- He describes the time as "a few focused hours a week." His video title says "5 Hours."

## What broke (per the author)
- **Wrong captions:** a captioning step spliced in another video's captions because two jobs shared a folder. QA caught it.
- **Pacing pass rejected:** an automated pacing pass was rejected three times in one week.
- **Broken newsletter links:** these went unnoticed for a while, which is why analytics review is now a scheduled stage.

## Caveats
- X: @chrisralarcon (verified 2026-10-14: profile links christopheralarcon.com).
- He runs a top-tier Claude plan plus two $100 plans. He says a leaner version works on one $20 plan.

## Sources
- https://christopheralarcon.com/blog/claude-code-content-system