Build · AI Profiles
One brand voice, set once, inherited everywhere.
An AI Profile is where an agent's persona, tone and audience actually live: structured fields a person can review, not a single long prompt nobody quite remembers the reasoning behind.
Why not just a prompt
A prompt nobody can review isn't a policy.
A voice buried in a paragraph of prompt text can't be reviewed, versioned, or inherited cleanly. Every new agent either copies it by hand or drifts from it slightly. Structuring it into its own object fixes both problems at once.
What's in a profile
Fields you can actually look at, not a wall of text.
- Persona and tone
- A name, a description, and the voice an agent actually answers in. Set once, not per conversation.
- Structured, not one blob
- Specialisation, context and company identity are separate sections that stack, not one long prompt.
- Versioned
- Changes are tracked: what changed, and when. A correction about tone or style becomes an instruction here.
- Inherited
- Set at the Company, and every Team and Agent below it starts from the same voice.
FAQ
Companies setting a brand voice are asking
What's actually in an AI Profile?
Persona and a short description, plus structured sections for specialisation, context, and company identity traits. Together they shape how an agent sounds and what it knows to prioritise.
Can a Team override the Company's AI Profile?
Only where the Company has explicitly granted that permission. Profiles stack in order: company identity, then context, then specialisation. A child adds detail; it does not erase what is above it.
Can we see how a change to the profile will actually sound before publishing it?
Yes, via the Effective Profile Preview. It shows the resolved, final voice an agent will actually use, not just the raw fields you edited.
Set the voice once. Let it inherit down every agent you add.
Twenty minutes with the founder. No slides. The real product.
