Writing your first product brief
What to put in your product's description before you generate your first topics and scripts.
A brief is just your product's name and description — that's the input every topic, script and render downstream is generated from, so it's worth getting right before you generate anything. There's no separate audience or tone field; everything lives in the description, so cover it there:
- What it does — in plain language, and the single most useful thing it changes for a user.
- Who it's for, if that shapes how it should be described. Being specific here produces sharper topics ("solo founders evaluating analytics tools" works better than "small businesses").
- How it should sound, if tone matters to you — a line or two is enough to carry through into generated copy.
Once the description is saved, every new topic you generate for that product reuses it automatically — you don't need to repeat any of this per topic.
Was this article helpful?
Your feedback helps us continuously improve our documentation.