Build · Create · Writing & Content
Video production creative brief
A structured creative brief a production team can pitch from: a written-out objective and audience, one single-minded proposition, named video deliverables with durations and aspect ratios, at least one success measure, and, unless you switch those checks off, a disclosed budget and an ordered timeline.
You receive: A JSON object: {business_objective, target_audience, single_minded_proposition, tone, mandatories:[string], deliverables:[{name, duration_seconds, aspect_ratio}], budget_disclosed:{amount, currency}, timeline:{first_draft_date, review_date, delivery_date}, success_measures:[string]}. tone and mandatories are context fields and are not machine-checked.
Part of Get First Users, Distribution
What's verified: STUD verifies the brief is a single JSON object within a 60,000 character size bound; that the five core fields (business objective, target audience, single-minded proposition, deliverables, success measures) are present and non-empty; that the objective and audience are written out in at least 8 words each, with no placeholder text (TBD, TODO, xxx, lorem ipsum, [insert, <placeholder>) in the objective, audience, proposition, or success measures; that propositions stay within your maximum (default 1); that at least your minimum number of deliverables (default 2) each carry a name, a positive duration in seconds, and an aspect ratio (restricted to your allowed list when you set one, any ratio when you leave it empty); that a budget with a positive amount and a 3-letter currency code is disclosed, and that first draft, review, and delivery dates are valid calendar dates in strict order (these two checks are on by default and each can be switched off in the intake); that every success measure is a non-empty string; and that your settings are in range (minimum deliverables 1-20, maximum propositions 1-5; an unrecognized yes/no value falls back to yes). STUD does NOT verify that the strategy is sound, that the audience, budget, or dates are realistic or achievable, that the proposition is persuasive, that success measures are actually measurable, or that tone and mandatories are honored (tone and mandatories are context fields, not machine-checked). Your product summary, campaign goal, audience notes, and mandatories intake fields are operator context only: they guide the work but do not change the machine verdict.
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.
Business objective
Drive qualified signups for STUD's soft launch before paid fulfillment opens, introducing the living system that runs a venture's work
Target audience
Solo and early-stage founders and small product teams who need real work done while staying small; secondarily ops and engineering leads adopting AI agents
Single minded proposition
Pick a play and STUD runs it with your venture's facts already in hand
Tone
Plain, factual, confidence-building
Mandatories
- Use the STUD wordmark exactly as written, uppercase, no trailing period
- No em dashes in any onscreen text or narration
- Frame every play with the commit verb Run, never as employment or staffing
Deliverables
| Name | Duration seconds | Aspect ratio |
|---|---|---|
| Explainer: a living system that knows your business, does the work, and learns | 60 | 16:9 |
| Product demo: run a play end to end | 45 | 16:9 |
| Social cutdown: join the soft-launch waitlist | 15 | 9:16 |
Budget disclosed
Timeline
Success measures
- 800 waitlist signups from paid and organic social within 30 days of launch
- 15% click-through rate from the social cutdown to the waitlist page
- 40 activated buyers in month 1 (illustrative launch scenario target)
Get early access to STUD the day it goes live.