Playbook: the content studio (how this Academy is made)

This Academy isn’t written by hand — it’s produced by a Content Studio company inside askTheodor, and this lesson shows you the exact setup.

What you’ll do

• See a real production company, role by role.
• Understand how Theodor orchestrates a pipeline.
• Copy the pattern for your own content engine.

1. The studio, role by role

The Academy’s Content Studio is one Company staffed with a small crew:

• A scriptwriter drafts each video’s script.
• A blogger turns scripts into the written walkthroughs you’re reading.
• A designer (🎨) produces thumbnails and diagrams.
• A community manager drafts the posts that announce each lesson.

Each is a worker with its own soul, profession, and brain — the right model for the job.

2. Theodor orchestrates the pipeline

You don’t brief four workers separately. You ask Theodor for an outcome —

“We need the lesson on kiosks: a script, a written walkthrough, a thumbnail, and an announcement post.”

— and he routes each piece to the right crew member, in order. The studio’s brand voice and house style live in a Company-scope SOP, so every worker stays on-tone without being told twice.

3. Review, approve, ship

Every artifact passes a human. Drafts land for ✓ Approve / ✕ Reject, and outbound announcement posts are drafted and held — never auto-posted. Agents prepare, humans approve is exactly how a studio keeps its quality bar.

Run it while you sleep

Put the scriptwriter, blogger, and designer on a Team-Hub so they draft 24/7; keep the announcement send on your Command Center. You wake up to a stack of drafts to approve.

This is the dogfood

The studio that built this lesson is itself an askTheodor company. Run a company of one, staffed like a hundred — the Academy is the proof.

A publishing pipeline that survives contact with reality

Content work fails at the same three points for everyone. Here’s what to put in place at each:

The blank page. Keep a running “ideas” document in the Library and let the researcher add to it — anything a customer asked twice, anything you had to explain in a call. A brief that starts from a real question is always better than one invented at a keyboard, and it means the pipeline never begins from nothing.

The draft that sounds like nobody. This is where most AI content dies. The fix isn’t a better model, it’s the Company SOP: your banned words, a real sample of your writing, and the rule that every piece must contain at least one specific thing only you could know — a number from your own work, a mistake you made, a customer’s actual objection. Generic writing is a briefing failure, not a model failure.

The review that becomes rubber-stamping. Put a separate reviewer worker between drafting and you, with an explicit rubric: does it make a claim we can’t support, does it repeat itself, does it end with something to do? Two different workers catch more than one worker asked twice — and it keeps your review focused on judgement rather than proofreading.

Say the honest thing about volume

This pipeline makes it possible to publish far more than you used to. That isn’t automatically good. Ten pieces nobody reads is worse than two that get shared, and search engines have opinions about bulk-generated content. Use the throughput to raise the floor of what you publish, not the count.

Recap

A Content Studio is one Company, a four-role crew, and Theodor orchestrating a draft-review-ship pipeline — the same machinery that produced this Academy. You’ve now seen askTheodor end to end, from your first hour to a full content engine. Go build yours, and tell us about it.

📖 Reference in the docs: Plans · Library

➡️ Next: Join the community