Build · Create · Writing & Content
YouTube channel content calendar
The buyer gets a ready-to-execute YouTube upload calendar where every slot has a working title of at least three words, a content format, a marketing goal, a target keyword, a planned length within the cap, and a valid publish date, with the committed number of posts landing in every week of the horizon.
You receive: A JSON object with an entries[] array, one entry per slot, where each entry = {slotId, publishDate (ISO YYYY-MM-DD), workingTitle, format (one of the allowed formats), primaryGoal (one of the goals), targetKeyword, plannedLengthMinutes}. The entry count equals horizonWeeks x postsPerWeek.
Part of Get First Users, Distribution
What's verified: STUD verifies the structure and internal consistency of the submitted calendar: it parses as a JSON object under 200,000 characters; the entries array has exactly horizonWeeks x postsPerWeek entries; every publishDate is a real ISO date (YYYY-MM-DD), dates never step backwards, and every week of the horizon contains exactly postsPerWeek entries; slotIds are non-blank and unique; every workingTitle is non-blank, unique, and at least three words; every format is one of your allowed formats; every primaryGoal is one of your goals and every goal appears at least once; every plannedLengthMinutes is a positive number no greater than your maximum (default 20 minutes); every targetKeyword is non-blank. STUD does NOT verify that titles are compelling, that target keywords have real search demand, that topics fit your channel, description, or target audience, or that the schedule is achievable for your team. Channel name, channel description, and target audience are operator context only, they never affect acceptance. If goals or allowed formats are left empty, disclosed default lists apply (goals: awareness, leads, community; formats: tutorial, talking-head, shorts, interview, review), and out-of-range numbers are clamped to sane bounds (horizon 1 to 52 weeks, 1 to 14 posts per week, length cap 1 to 600 minutes).
Opens soon
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
Entries
| Slot Id | Publish Date | Working Title | Format | Primary Goal | Target Keyword | Planned Length Minutes |
|---|---|---|---|---|---|---|
| yt-w1-1 | 2026-08-11 | Pick a Play and Watch STUD Run It | tutorial | awareness | run a play on stud | 12 |
| yt-w1-2 | 2026-08-14 | Why Every AI Chat Starts From Zero, and How a Workspace Fixes It | talking-head | awareness | ai workspace for founders | 10 |
| yt-w2-1 | 2026-08-18 | Inside The STUD Workspace: State a Fact Once, Use It Everywhere | tutorial | leads | workspace facts pre-fill | 14 |
| yt-w2-2 | 2026-08-21 | STUD Pricing Explained: Credits, Plans, and Play Costs | talking-head | leads | stud credits pricing | 9 |
| yt-w3-1 | 2026-08-25 | Founder Interview: A Venture That Compounds Every Week | interview | community | compounding business workspace | 15 |
| yt-w3-2 | 2026-08-28 | 60 Seconds To Commission Your First Play | shorts | awareness | commission a play | 1 |
| yt-w4-1 | 2026-09-01 | How Playbooks Become Automations On STUD | tutorial | leads | business playbook automation | 13 |
| yt-w4-2 | 2026-09-04 | Community Q&A: Building On The STUD Waitlist | talking-head | community | stud waitlist questions | 15 |
Get early access to STUD the day it goes live.