Brand profile
Structured who we are sheet every downstream agent reads. Overview tab covers mission and audience. ICPs tab names the buyer segments.
Executive summary
Three short paragraphs explaining the feature and value.
The Brand profile generates the structured who we are sheet that every downstream agent reads from. Twelve LLM written fields define the brand: short identity, mission, value proposition, USPs, positioning, vibe, tone, voice, ICPs, common buyer questions, and more. The contract every blog writer and audit agent uses.
Each field has a regenerate button so the user can iterate without typing again. The agent reads the Brand sitemap Core pages, extracts the source signals, and writes the field in the brand's voice. Generated content can be edited inline; manual edits take precedence and are remembered across regenerations of other fields automatically.
The ICPs tab is the most consequential view. Each ICP carries its own pains, goals, language preferences, and triggers. Downstream content agents pick the right ICP per blog topic, write in that ICP's preferred register, and weave the right pain points into the narrative. Without ICPs, every blog reads like generic broadcast.
Key highlights
Five capability points teams should know about quickly.
- Twelve LLM written brand fields ready upfront
- Per field regenerate without typing again
- ICPs tab names buyers with pains and triggers
- Manual edits take precedence over future regenerations
- Source of truth for every downstream agent
Top FAQs
Five common questions answered for fast practical clarity.
What fields does the Brand profile cover?
Twelve fields total: short identity, mission, value proposition, USPs, positioning, vibe, tone, voice, ICPs, common buyer questions, top products, and supporting evidence. Together they form the brand contract that every downstream blog writer, audit insight, and visibility analyst reads from. New fields can be added through the support channel.
How are fields generated initially?
An agent reads the Core URLs from the Brand sitemap, extracts brand signals from copy, structure, and metadata, then writes each field in the brand's existing voice. Output is a draft, not final. Users review every field, edit anything that misses the mark, and regenerate individual fields until each one captures the brand correctly without compromise.
What happens when I regenerate a field?
The agent reads the source signals plus any related fields the user has already approved, then writes a new version of the chosen field. Manual edits to OTHER fields are preserved. The new version replaces the old one; previous versions stay in the version history so users can roll back to a prior draft if needed safely.
Who reads the Brand profile downstream?
Every content agent reads it before writing anything. Blog writers use the voice and tone fields to match register. Audit insight agents use the value proposition and ICPs to judge whether existing pages match positioning. Visibility scan analysts use the common questions field to interpret which AI model responses are on brand or off.
Can two workspaces share a Brand profile?
No. The Brand profile is workspace scoped, just like the sitemap, keywords, and every other setup artefact. Even brands with shared parent organisations get separate profiles per workspace so positioning, ICP definition, and voice can vary across regions or product lines without one bleeding into another by accident in production.