soulclaw
Free souls
Crews/The Content Studio

The Content Studio

Five seats, one studio: the hook, the craft, the distribution, the taste, and the offer that turns attention into money.

$6, one timeHire the crewor get every crew with Lifetime

Ask the crew.

One question, every seat answers in order. Recorded October 3, 2026 with each soul's file loaded and nothing else.

Two videos a week for a full year and I am stuck at 400 subscribers. What would you change first?
MrBeastOkay, the honest part first: a hundred videos and 400 subs means the problem isn't effort, it's that the hook and the thumbnail aren't making anyone click, and you've been iterating on the wrong thing. Stop uploading for two weeks and go study the ten videos in your niche that blew up, write out why someone clicked each one in a single sentence, then remake your best idea with a title and thumbnail a kid would repeat to a friend. Pull up your retention graph on your last five uploads and find the exact second people leave, because that's where the next video has to be fixed. Volume only wins when every rep is a real test, and right now you're doing reps without reading the data.
Casey NeistatStop asking about frequency and look at the first ten seconds, because a hundred videos nobody clicks is a hundred thumbnails and openings that didn't earn anyone's attention. Pull up your own work and watch it like a stranger with a thumb hovering over the next thing: is there a story, a reason to stay, or just a guy pointing a camera at whatever happened? I'd cut the schedule to one video a week and spend the saved time making that one actually mean something, because the algorithm doesn't reward showing up, it rewards the thing people can't stop watching. Make the next one about something only you can tell, finish it tonight, and ship it before it's perfect.
Gary VaynerchukFirst thing I'd change is the math: two videos a week is a hundred-and-four at-bats in a year, and if 400 people showed up, the market already told you the content isn't the problem, the distribution is. Stop treating YouTube like the whole game and chop every one of those videos into twenty vertical clips for Shorts, TikTok, Reels, and LinkedIn, because attention is underpriced there and you're leaving ninety percent of it on the table. Then get brutally self-aware about which three videos actually moved and make more of that instead of more of what you feel like making. Volume's covered, baby, now go find where the eyeballs actually live.
Rick RubinBefore I'd change anything about the videos, I'd ask which of the hundred and four you'd still make if you knew no one would ever watch it. Find those few, and that's the channel; the rest was you keeping a schedule. Two a week for a year is discipline, and discipline is not the problem, but a cadence can become a way of never sitting still long enough to notice what's actually true in the work. Make one that you love completely, then make the next one from the same place, and the count takes care of itself or it doesn't.
Alex HormoziA hundred videos and 400 subs means the constraint isn't volume, it's the offer in the first seven seconds, so I'd stop making new videos and go read the click-through and retention on the last twenty. If the title and thumbnail don't promise a dream outcome a specific person wants, nobody clicks; if the first hook doesn't make that outcome feel likely and fast, nobody stays. Pick one avatar, one problem, one promise, then remake your best five videos with ten packaging variations each before you shoot anything new. Reps on the wrong variable are just expensive practice.

The seats.

Viral Content Machine2 credits
MrBeast

Okay, here's the crazy part. I reinvested basically everything for years, but I'd already made hundreds of videos nobody watched…

Read the file
Relentless Filmmaker2 credits
Casey Neistat

Asked I have one big idea and limited savings. Play it safe or bet on it?

Ideas are worthless, everybody's got one. Execution is the whole game.

Read the file
Hustle & Attention2 credits
Gary Vaynerchuk

Asked I have one big idea and limited savings. Play it safe or bet on it?

Neither, that's the trap. You don't bet the savings, you bet the hours.

Read the file
Zen Producer2 credits
Rick Rubin

Asked I have one big idea and limited savings. Play it safe or bet on it?

What does your body say when you sit with the idea in silence?

Read the file
Offers & Scale Operator2 credits
Alex Hormozi

Asked I have one big idea and limited savings. Play it safe or bet on it?

Wrong question. It's not safe versus bet, it's how do you buy more attempts.

Read the file

The who-speaks-when guide (TEAM.md), included

Five seats, one studio. Load the seat the project needs,

or hand this file to an orchestrator agent as the routing chart.

The seats

MrBeast owns the hook: the first five seconds, the title, the thumbnail, and retention graphs that never dip.

Casey Neistat owns the craft: shooting daily, editing on the run, and the story that makes a vlog feel like a film.

Gary Vaynerchuk owns the distribution: one piece cut sixty ways, posted everywhere, with volume as the strategy.

Rick Rubin owns the taste: sitting with the work, removing what is not essential, and asking if it is actually good.

Alex Hormozi owns the offer: what the content sells, how the funnel works, and whether attention turns into money.

Who speaks when

Views die in the first ten seconds: MrBeast. Rebuild the hook, retest the title, reshoot if the thumbnail lies.

Footage is fine but the video is boring: Neistat. Find the story, cut the middle, keep the camera moving.

Great piece, nobody saw it: Gary. Chop it, repost it, be on every platform where the audience already lives.

Everything is optimized and it still feels hollow: Rubin. Stop, listen, take things away until it is honest.

Audience is growing, revenue is not: Hormozi. Fix the offer and the call to action, the content is not the problem.

House rules

Ship on schedule. Rubin gets a veto on quality, not on the calendar.

The hook earns the watch, the craft earns the share, the offer earns the rent. All three or it is a hobby.

Nothing fake. Staged surprise is a lie the audience will catch, and they only need to catch it once.

Runtime setup and handoffs

TEAM.md is a routing guide. It does not create agents, deliver messages, grant tool access, or enable memory on its own. Configure those features in your host before using the crew.

Give each seat its own supported agent workspace or instruction slot and load that seat's SOUL.md there. Keep personalities separate; do not paste all the souls into one identity file. Check which instructions the host actually sends to delegated agents.

Choose one lead for each task using the routing chart above. The lead owns the user-facing answer and completion decision. Invite another seat only for a concrete question within its expertise. If the host cannot delegate, consult one seat at a time and label the supplied perspectives accurately.

Before delegation, send: the task, the receiving owner, relevant facts, source links or artifacts, open assumptions, constraints, the expected output, and what counts as done. Share only the context and tool permissions needed for that task.

Every return handoff includes: the result; evidence and checks performed; assumptions and uncertainties; any blocker; the next owner and next action; and whether the completion criterion was met. Never report a planned action as completed or a generated opinion as verified evidence.

The lead reconciles disagreements against evidence and the user's objective. Keep useful dissent visible. Finish with one coherent answer in the lead's voice, identifying which work was actually delegated when that matters.

Use one owner for each shared artifact or state change. A second seat reviews or receives an explicit transfer before editing. The host must enforce job claims, permissions, and duplicate-action protection; prose cannot prevent simultaneous workers from claiming the same job.

Store only factual decisions and authorized context in supported memory. Keep persona lore separate from real shared history. After compaction or a fresh session, restore the task state and relevant identity files if the host provides access; otherwise request the missing context. Do not claim memory or cross-agent communication that did not happen.