Content Studio Team Structure: Inside Our 25-Person Machine

Four channels. Four original documentary films a week, 20 to 37 minutes each, every single week. Twenty-five people, no office, no freelancer roulette. When people ask how that's possible, they expect a headcount answer. It isn't one — it's a content studio team structure answer, and the structure matters far more than the size.

We're Sentris Media Group. Our network — Blackfiles, Breakfiles, Outplayed, and Outlived — has crossed 500K subscribers, 60M+ views, and 200+ films, with Blackfiles alone going from launch in February 2025 to 436K subscribers and 53M views. This is the org chart behind those numbers: the pods, the roles, the handoffs, and the parts we got wrong before we got them right.

The Content Studio Team Structure at a Glance

Strip away the job titles and a documentary studio does five things: it researches, it writes, it builds images, it cuts and mixes, and it packages. Our entire content studio team structure is those five crafts, organized into channel pods and supported by a thin central layer. There are no producers managing producers, and no department heads whose output is meetings.

• Channel pods — small cross-functional crews that each own one channel's weekly slate end to end
• Research and writing — investigators and writers who turn 16–20 hours of source work per film into a locked script
• Visual production — 3D artists and motion designers; every frame original, zero stock footage
• Edit, sound, and voice — editors and sound designers, plus a directed AI voice performance
• Packaging and strategy — titles, thumbnails, scheduling, and the feedback loop from the data
• Ops and tooling — the small crew that builds and runs our internal pipeline: Vertex, Cortex, Scriptwriter, and Thumbnailer

The first five crafts live inside pods. The last one sits across all of them. Leadership stays deliberately thin: working leads who still touch films every week, not managers who only touch dashboards.

Pods Own Channels. Nobody Owns 'Video.'

The classic agency model groups people by function — a research department, an animation department, an edit bay. Work flows between departments through tickets and queues. At one film a month, that's tolerable. At one film per channel per week, it collapses, because every department starts optimizing its own queue instead of the film.

So we organize the other way. Each channel has a pod: research, writing, visual artists, and edit working the same channel every week. The Blackfiles pod knows that channel's tone in their bones — what a cybercrime cold open needs, how a spy story earns its third act. That accumulated taste is the real asset, and a departmental structure resets it on every new project.

Pods also kill the accountability fog. When an upload slips, there is no inter-departmental blame triangle to untangle. One pod, one channel, one weekly deadline. Ownership is the cheapest performance management system ever invented.

One Film, Five Handoffs

Here's how a single film moves through a pod. Research goes first: 16–20 hours per film spent in court records, declassified files, archives, and primary reporting, compressed into a verified fact base. Scriptwriter, our research-to-script tool, helps structure that mountain — but a human researcher decides what's true, and a human writer decides what's interesting.

The locked script triggers visual production. Because we use zero stock footage, every scene is designed and generated through Vertex, our in-house image and video pipeline, then refined by artists who own that channel's look. Edit and sound take it from there: pacing, mix, and a directed AI voice that gets performance notes the way any narrator would.

Packaging runs in parallel from the moment the script locks — not after the final render. Titles and thumbnails get iterated in Thumbnailer, our packaging lab, while the film is still moving through production. Films like 'The FBI Agent Who Warned Everyone About 9/11' (482K views) had their packaging pressure-tested while the edit was still open; the title shapes the film, not the other way around.

Handoffs Are Where Weekly Schedules Die

Every stage boundary is a chance to lose two days. A script that's '90% done.' An editor waiting on renders nobody flagged as late. A thumbnail brief that exists only in someone's head. Multiply that across four channels at weekly cadence, and sloppy handoffs will eat a studio alive long before quality ever gets the chance.

Our rule: a handoff is a contract, not a Slack message. Every stage has a definition of done — research doesn't hand off without sourcing on every claim, and a script doesn't hand off until it's locked, because rewrites mid-animation are how schedules die. When downstream finds a defect, it goes back upstream. The editor never quietly fixes the writer's problem, because quiet fixes hide broken stages.

Cortex, our production orchestration system, is the referee. Every film's stage, owner, and due date is visible to the entire studio, so 'where's my script' conversations simply don't exist. Remote teams don't fail because of distance. They fail because of ambiguity, and ambiguity is a tooling problem you can actually solve.

What Stays Central — and How the Structure Scales

Three things never moved into pods. Packaging strategy stays central, because thumbnail and title judgment compounds across channels — what a 422K-view heist film teaches us about framing transfers straight to a survival story. Tooling stays central, because Vertex, Cortex, Scriptwriter, and Thumbnailer serve all four channels at once. And final QC stays with leadership, because a network's reputation is only as strong as its worst upload.

Scaling is where the pod model paid for itself. Blackfiles proved the template; Breakfiles, Outplayed, and Outlived are the same pod design pointed at prison escapes, heists, and survival — now at 37.1K, 28.6K, and 7.8K subscribers respectively. We didn't reorganize the studio to launch them. We copied a structure that already worked and staffed it.

That's the honest test of any content studio team structure: can you clone it without cloning yourself? If a channel only functions because the founder touches everything, you own a job, not a studio. It's also the core of what we teach operators inside Sentris Academy — structure first, headcount second.

FAQ: Content Studio Team Structure

Do you need 25 people to run a documentary channel? No. You need the five crafts covered — research, writing, visuals, edit, packaging — and at a monthly cadence one person can hold several of them. Headcount follows cadence: weekly output per channel is the point where a dedicated pod stops being optional.

Doesn't AI tooling shrink the team structure? It compresses hours inside roles more than it deletes roles. Our tools strip the grunt work out of research structuring, image generation, and packaging iteration, but a human still owns truth, taste, and the final cut on every one of our 200+ films. As of 2026, we'd hire a great editor over another tool subscription every single time.

Why pods instead of one shared production team across all four channels? Shared teams optimize for utilization; pods optimize for the film. A crew that lives inside one channel compounds taste week over week, and taste is what retention curves are made of.

Fully remote — really? All ~25 of us, yes. Remote works when handoffs are contracts and status lives in a system instead of in someone's head. The structure does the managing, so the people can do the work.