A realistic rollout for the 50-minute Relay Talk recording — scoped for one person editing in their spare time. Six deliverables, three weeks, no overkill. Operators can ship their own extra clips later if they want; this is the floor, not the ceiling.
← Back to Gooism CollectiveThe story campaign was seven daily story drops and that was already heavy. This plan keeps the same person editing on the same kind of evening-after-work cadence — nothing here assumes a team.
One editor (Jack). Limited evenings. Need to gather more raw material first — photos from the event, additional phone-footage angles from anyone who recorded, rig stills. The 50-min program-out is the only thing fully captured today.
Caption-perfect quality is aspirational, not a blocker. We'll lean on YouTube auto-captions for the long upload and burned auto-captions for the verticals. Manual review only on the headline pieces.
Don't start cutting clips until the photo + extra-angle gather is done. We'll re-cut everything otherwise. Give it a week of asking around before the editor sits down.
60-90s vertical for each. The best minute of their Relay segment. Caption ends with their handle + GPortal slug so the clip is a one-tap path to "book this person."
gportal.wallspace.studioOne upload. Chapters per operator. Description links each operator's GPortal profile. This is the canonical home of the recording — everything else points back here.
AnalogToAI — Gooism Relay Talk · 4 operators, 1 rig, 50 minutes
00:00 — Cold open00:?? — operator_01 · Fetz · analog systems00:?? — operator_02 · Kevin · found media00:?? — operator_03 · Andrew · floral geometry00:?? — operator_04 · Jack · AI + projection49:?? — All operators online · closingUse YouTube's auto-caption track. If it's clearly broken in spots, fix those spots. Don't aim for a perfect SRT — the long-tail YouTube viewer will turn captions on themselves and most won't notice the difference between auto + reviewed for a 50-minute upload.
One frame from the closing wash — high-contrast, recognizable from a phone-sized YouTube grid. Single attempt, don't A/B.
60-90s. Cuts between all four operators with name supers. The most shareable single piece — goes everywhere (Reels primary, Shorts cross-post, IG Story).
gportal.wallspace.studioDesigned around evenings, not workdays. Drops cluster on Tuesday + Thursday so weekends stay free.
Don't compress. If Week 1 Tuesday misses, push everything one week. The cadence matters less than not burning out mid-rollout. The Story Campaign hit because it stayed on rhythm; the worst outcome here is starting strong and trailing off.
The point isn't view counts. It's whether someone watches a 60s clip and lands on an operator's GPortal profile. Keep the path one-tap.
Track new booking-request submissions on GPortal during the 3-week window vs. the 3 weeks before. Reach is a leading signal; bookings are the actual outcome. Pull from the booking_requests table by created_at.
| Workstream | Owner |
|---|---|
| All editing + uploads | Jack (default) |
| Photo / angle gathering | Each operator forwards anything they have to Jack |
| Rig stills | Each operator's call — can be retroactive or "next time we're together" |
| Bio / handle confirm | Each operator |
| Boost on operator channel | Each operator on their own clip day |
| Captions on YouTube full + trailer | Jack — manual review pass |
| Captions on operator clips | Whisper auto, no review unless visibly wrong |
If anything in this list lands on someone other than Jack and they don't deliver, the rollout still works — it just means that operator's day uses a less-polished clip. No single dependency blocks the campaign.
None of this is committed. If the 6-drop rollout converts to bookings, we expand. If it doesn't, we don't waste effort on the next layer.
Each is its own small commit when there's appetite. Not now.