The everyday 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 parrot the tone the original founder wrote three years ago. 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 in a Figma deck somewhere — but reading the brand-voice doc takes ten minutes and writing a release note takes five.
What you’d type into the New Agent form
The head of marketing clicks New Agent in the dashboard, picks the Content Writer template (or starts from scratch), and fills in:
Agent name · Brand voice editor
Description · Rewrites copy to match the company brand voice. Same rules every team writes against.
Persona · You are a senior brand editor at [Company]. You enforce three voice attributes — confident-not-arrogant, technically literate, never hype-y. You apply the do/don't word list and the audience-tier rules (developer-facing copy is denser; CXO copy frames in business outcomes).
Context to paste
- The brand voice guide (tone attributes, voice principles)
- The do/don’t word list (“revolutionary” out; “ships” in)
- The audience-tier rules
- 10–20 before/after examples drawn from real past edits
Skills to pick
brand-voicetone-auditsubject-line-audit
MCPs to wire
- Notion or Google Docs — to read the live brand guide as it changes
- Asana or Linear — where briefs originate
A few minutes of paste-and-pick. No code.
What your team sees when they use it
Same agent, every team that drafts outbound:
- Engineering pastes a draft release note and gets back a version that says “ships in v3.4” instead of “we refactored the deploy queue and now it’s faster.”
- Support drafts a macro for the “billing dispute” pattern; the agent rewrites it in the canonical empathetic-but-clear support tone. Every customer interaction sounds like the same company.
- Sales 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.
- Product proposes a feature name; the agent flags whether it lands in voice and suggests alternatives that do. Naming arguments shorten by half.
Marketing stops being the bottleneck on every launch week.
How it composes
This agent inherits the org defaults (company background, default audience persona, the brief workflow). On top, it overlays its role-specific skills: brand-voice, tone-audit, subject-line-audit. When marketing tightens the org-level audience defaults — a new segment, a tone shift — every team’s next invocation picks up the change.
How it evolves
A new product line launches and the head of marketing decides the tone shifts 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.