Case study
The Assembly Line
12 carousels in one 4-hour afternoon, instead of 12 sessions that never actually happened.
The case study
The founder
A founder making one carousel a week, which meant re-entering content mode 52 times a year and, in practice, never shipping a full quarter.
The situation
Context-switching is the real cost. One-at-a-time means reopening the template, re-finding your voice and re-deciding what good looks like, every single week.
The ad-hoc route, 12 separate sessions at 2 to 3 hours each, costs 24 to 36 hours across a quarter and rarely ships all 12.
What they did
- 1Picked 12 ideas in 30 minutes from the blog, voice notes and mined sales calls. Selecting, not inventing.
- 2Outlined all 12 arcs first, hook to CTA, before designing anything. One hour.
- 3Batch-rendered all 12 through the locked template.
- 4Reviewed in one sitting, about 10 minutes each, then scheduled the whole quarter.
The result, per quarter
A full quarter of carousels in ~4 focused hours
20 to 30 hours saved versus the ad-hoc route, and a quarter that actually ships.
12
carousels in one sitting
~4 hrs
total vs 24 to 36 hours
6-8×
output per hour of input
1 quarter
scheduled in one go
Before / after
Before
After
Shipped / quarter
rarely 12
12
Time
24-36 hrs
~4 hrs
Context switches
12
1
Want your first batch mapped?
Reply "BATCH" and I will outline your 12. Free.
Reply BATCH →