Draft emails in the CMO's voice using Armbrain voice profiles and approval workflows.
The Goal
Draft emails clients believe the CMO wrote. Match their voice: sentence length, greetings, sign-offs, formality, and client-specific phrasing.
A good draft saves 10 minutes. A bad one wastes 15 on rewrites. Voice makes the difference.
Pull the CMO's Voice Profile
The CMO's personal mind has a voice profile. Switch to it and pull their brand voice:
switch to [CMO's personal mind]get brand voiceThis returns the CMO's style: email openings, first name usage, sign-off formality, and repeated patterns. Some CMOs start every email with "Hey [first name]," and end with "- Ben". Others open with "Hi [full name]," and sign "Best regards."
Then switch back to the client mind to get client-specific context:
switch to AcmeGet Meeting Context for Follow-ups
Most emails you draft are follow-ups after meetings. Pull the context:
prep meeting with AcmeOr search for specific topics:
search memories about what was discussed with Sarah last meetingThis gives you the specific commitments, decisions, and next steps that need to go in the email. Never guess what was discussed. Look it up.
Draft Structure
A typical post-meeting follow-up from a CMO follows this pattern:
- Personal greeting matching their style
- Reference the meeting - "Great talking with you today" or "Following up on our call"
- Key decisions - what was agreed
- Action items - who's doing what, with deadlines
- Next steps - when you'll connect next
- Sign-off matching their style
Example:
Hey Sarah,
Great call today. Here's where we landed:
- Q2 campaign launches May 1 with the "Growth Series" theme
- Your team handles product copy by April 15
- We'll have landing page mockups ready for review by April 20
Next steps: I'll send the mockups as soon as they're ready. Let me know if anything shifts on your end.
Talk soon,
BenThe Approval Gate
Armbrain has an email approval gate. No email sends without the CMO seeing it first (unless they've explicitly enabled auto-send in their preferences).
The workflow:
- You draft the email
- Present it with To, Subject, and Body
- The CMO approves, edits, or rewrites
- Only then does it send
This protects against voice mismatches, factual errors, and political missteps you wouldn't know about. The CMO might see your draft and say, "Don't mention the budget - Sarah's board hasn't approved it yet." That's context you didn't have.
Client-Specific Tone
Different clients get different communication styles from the same CMO. Search for past communication notes:
search memories about communication preferences for AcmeYou might find:
- "Sarah prefers bullet points over paragraphs"
- "Always CC Mike on emails about the website project"
- "Acme team is sensitive about timelines. Frame delays as 'adjusted schedules,' not 'delays'"
Stakeholder preferences in the Brand DNA also inform how to write to specific people.
When to Draft vs. When to Let the CMO Write
| Situation | Who Writes |
|---|---|
| Post-meeting follow-up with action items | You draft, CMO approves |
| Status update on deliverables | You draft, CMO approves |
| Response to a simple client question | You draft, CMO approves |
| Sensitive topic (budget, timeline slip, personnel) | CMO writes |
| First email to a new contact | CMO writes |
| Bad news or scope change | CMO writes |
| Renewal or upsell conversation | CMO writes |
If unsure, draft it anyway. The CMO can discard it. Never send sensitive emails without explicit direction.
Common Voice Mistakes
Too formal for a casual CMO. If the CMO writes "Hey" and you draft "Dear Ms. Chen," you've missed the mark.
Too long. Most CMO emails are short. If your draft is 5 paragraphs for a 2-sentence reply, cut it down.
Wrong sign-off. Match exactly. "Best" vs. "Thanks" vs. "- Ben" vs. "Cheers": clients recognize these distinct habits.
Adding context the CMO wouldn't include. The CMO knows what Sarah knows. You might over-explain because you're less familiar with the relationship. Keep it concise.