Example Week
A fully worked weekly grid for a growing solo build-in-public channel (around 3k subscribers, audience in US Eastern). The creator can make 1 long-form and 3 Shorts a week. This is an illustration, not a prescription.
Inputs
- Theme: building an AI side project in public
- Audience: indie devs and early founders, US Eastern
- Pillars: Build logs, Tool teardowns, Mistakes and lessons, Quick tips
- Capacity: 1 long-form + 3 Shorts per week
- Stage: growing (1k to 50k)
The grid
| Day | Slot | Format | Pillar | Title angle (formula) | Thumbnail angle | Hook (formula) | Goal | Window (ET) |
|---|---|---|---|---|---|---|---|---|
| Mon | Short | Quick tips | one setting that 2x'd a metric (Y4 Mistake) | the setting toggled, big arrow | 3-sec frame-one (Y10) | CTR / reach | 12:00 PM | |
| Tue | Long-form | Build logs | "How I shipped X in 5 days" (Y3 How-I) | exhausted face + the live product | cold-open payoff (Y8) | retention | 4:00 PM | |
| Wed | Community | - | poll: which feature next | - | - | engagement | 1:00 PM | |
| Thu | Short | Tool teardowns | "this free tool beats the $200 one" (Y6 Versus) | two logos, one crossed out | 3-sec frame-one (Y10) | CTR / reach | 12:00 PM | |
| Fri | Short | Mistakes | "I almost shipped this bug" (Y1 Curiosity) | the error on screen + face | 3-sec frame-one (Y10) | CTR / reach | 5:00 PM | |
| Sat | Community | - | question: worst deploy story | - | - | engagement | 10:00 AM | |
| Sun | (rest / batch) | - | - | - | - | - | - | - |
Why this balances
- Format mix: 1 long-form (the watch-time engine) + 3 Shorts (top of funnel), matched to the creator's real capacity.
- Through-line: all three Shorts excerpt or tease the build-log long-form, so the reach they earn points at the library.
- Goal spread: the long-form is retention-first; the Shorts are CTR-first; the community posts drive engagement that seeds the next video. Not all one note.
- Pillar variety: four different pillars across the week, so the channel does not feel like one repeated topic.
- Timing: the long-form publishes Tuesday afternoon ET, a few hours before the indie-dev evening viewing peak, so the browse feed has data when it tests.
How each slot gets built
The planner stops here. Each slot is then handed to the dedicated skill:
yt-title-optimizerwrites 3 to 5 title variants for the slot's angle.yt-thumbnail-briefwrites 2 to 3 thumbnail concepts for the slot.yt-hook-scripterscripts the first 30 seconds (or 3 for a Short).yt-description-writerwrites the description, chapters, and links.yt-community-post-writerwrites the Wednesday poll and the Saturday question.
Holding the cadence
- Batch on Sunday: record the Shorts in one session, plan the long-form.
- If a week slips, drop a Short, never the long-form. The long-form is the engine.
- Re-evaluate the mix every 4 weeks against long-form watch-time and returning viewers, measured separately from Shorts views.