Content Hub OSby Audra Carpenter
Home/Hubs/Setup
Foundation hub

Setup

The source context layer. This is where you teach the OS who your business is, who it serves, and what voice to use. Every content workflow pulls from what you build here.

Complete these three before running any content workflow.

Brand, Personas, and Verticals are the minimum context the OS needs to produce useful, specific content. Without all three, output will be generic. Order does not technically matter but this sequence makes the most sense.

1 Brand
2 Personas
3 Verticals
Required Step 01

Brand

The anchor record for everything else. Defines who the business is, who it serves, what voice to use, what words to never use, and how AI should write for this brand. Style guides and content examples live here too.

Brand name About Voice guidelines Excluded words Brand colors Social URLs Style guides Content examples
Playbook coming next
Required Step 02

Personas

The audience profiles passed to the AI when generating content. A persona is a real description of a real reader, their role, their pain points, their goals, and what motivates them to act. One persona per distinct audience segment.

Name and role Verticals Bio Pain points Primary goal Buying motivation Content formats Full profile
Playbook coming next
Required Step 03

Verticals

The industry or niche records that give your personas context. A persona tells the AI who the reader is. A vertical tells it what world they operate in. Both travel into every content workflow together.

Name Description
Build your Verticals →
Optional Podcasts and YouTube only

Guests and Sponsors

Contact and context records for the people who appear on your podcast or YouTube channel, and the brands that sponsor your content. When a guest record exists, the AI uses their bio, expertise, and speaking topics when generating episode assets.

Name and type Bio Area of expertise Speaking topics Social URLs Consent status
Playbook coming later
Optional When you have custom prompts

Prompt Library

A library of saved prompts that can be selected and used across content workflows. Build one prompt per use case. Store the prompt text, a good output example, and the content format it applies to so you can reuse it without rewriting it every time.

Name Prompt type Content format Prompt text Good output example Brand
Playbook coming later