The problem
Every department writes outbound copy and almost none of it sounds like the same company. Engineering’s release notes read like a git log. Support’s macros are still parroting the tone the original founder wrote in 2021. Sales emails range from “hello, friend” to “per my last email” depending on who clicked send. Product names new features whatever sounded good in the design review. Marketing then spends Friday afternoons rewriting all of it. The brand voice exists — it’s documented in a Figma deck somewhere — but no one outside marketing actually reads it before hitting publish, because reading a brand-voice doc takes ten minutes and writing a release note takes five.
Author
The head of marketing and a brand designer co-author the brand voice agent in the AgentBundle dashboard wizard. They paste in the brand voice guide (tone attributes: confident-not-arrogant, technically literate, never hype-y), the do/don’t word list (“revolutionary” is out; “ships” is in), the audience-tier rules (developer-facing copy is denser; CXO-facing copy frames in business outcomes), and a library of “before / after” examples drawn from real edits marketing has made over the last year. The wizard generates the bundle — no code, and no per-team config to maintain. The reviewer-workflow controls referenced below ship on Business tier and above; see /pricing for what’s gated.
Review
The CMO approves changes to the canonical voice rules. The brand designer is a required co-reviewer on any change that touches the do/don’t list (it’s load-bearing across every department’s outbound). Both signoffs are captured in the N-required-reviewer audit log on Business tier. Voice updates are versioned the same as any other agent: every team can see what changed, when, and why.
Distribute
APM (Microsoft’s open packaging spec for AI agents) ships the agent. It’s installed across every runtime the org uses — Claude Code and Cursor for engineers, the ChatGPT-equivalent web client for sales and support, the design tool plugin for product. Same canonical agent, different surfaces.
Use
The same canonical agent runs through every team’s writing flow:
- Engineering uses it on release notes and changelog drafts. An engineer drops a v0 release note in their IDE, invokes the brand voice agent, and gets back a version that says “ships in v3.4” instead of “we refactored the deploy queue and now it’s faster.” Marketing stops being the bottleneck on every launch week.
- Support uses it on canned-reply templates and macros. A support engineer drafts a new macro for the “billing dispute” pattern, the agent rewrites it in the canonical empathetic-but-clear support tone, and the macro is added to the team’s library. Every customer interaction sounds like it came from the same company.
- Sales uses it on proposal language and email outreach. A sales rep pastes a draft cold email; the agent returns a version aligned to the audience tier (CXO vs IC) with the do/don’t list applied. Sales reps stop sounding like five different companies.
- Product uses it on feature naming and in-product copy. A PM proposes a feature name; the agent flags whether it lands in voice and proposes alternatives that do. Naming arguments shorten by half.
Composition
The brand voice agent gets used directly by every team that drafts outbound copy — engineers in their IDE, marketing in their drafting flow, support in macros, sales in cold emails. It’s the same canonical agent every time. When the head of marketing tightens the voice rules, the next agent invocation across every team picks up the new version on next sync. One canonical definition, every team aligned, no per-team retraining when the rules move.
Iterate
A new product line launches and the head of marketing decides the tone needs to shift to “founder-mode” for the launch quarter — slightly more direct, slightly less corporate. They update the canonical voice rules, ship v4, and the change propagates on next sync. Engineering’s release notes, support’s macros, sales’ emails, and product’s feature names all start landing in the new tone — no per-team retraining, no re-circulating a Figma doc, no Friday rewriting marathon. When the launch quarter ends and the tone reverts, that’s another canonical update, another sync, every team back in step.