How to export a client mind as a deliverable when an engagement ends, and how to prepare it for the successor CMO or in-house team.
Why Handoff Matters
Most fractional CMO engagements end with a strategy deck and a goodbye. Armbrain changes that. When an engagement ends, the client gets a "client mind": a client-safe export of the brand, decisions, campaigns, stakeholders, and open commitments built during the engagement.
"We don't just leave a strategy deck. We leave an AI that knows your brand."
What Gets Exported
A client handoff includes the client-safe parts of the client's client mind:
| Section | Contents |
|---|---|
| Brand DNA | Voice, positioning, messaging, stakeholders, content themes |
| Decision log | Every decision captured from meetings and manual entries |
| Campaign history | Results, learnings, and performance outcomes |
| Stakeholder map | Key people with titles, roles, and communication preferences |
| Active commitments | Open action items and their status |
| Known preferences | How the client likes to work, communicate, and receive updates |
| General facts | Company details, industry context, organizational knowledge |
What is NOT included:
- Sensitive, private, and internal CMO memories -- these are your internal-only observations
- Hidden memories (marked with
memory) -- these were flagged as incorrect or outdated - Dismissed memories -- anything you dismissed is excluded automatically
- Memories from other clients -- isolation is enforced at every level
Sensitive Data Filtering
Client handoff packages are generated by the mind owner and filtered before the package is rendered. Armbrain excludes rows that are private, sensitive, cmo-only, hidden/dismissed, non-active, or missing a safe visibility classification.
The preflight shows memory counts for included items and each exclusion reason. The handoff package excludes raw source documents.
Preparing for Handoff
1. Review and clean up memories
Before exporting, review the client's memory landscape:
"Search for all memories about Acme"
"Show me open commitments for Acme"
"What are the campaign outcomes?"Hide anything that's outdated or incorrect:
"Hide the memory about the old office address"Store any missing context that should be in the handoff:
"Remember: Primary brand color is #2B5797, secondary is #E8912D"
"Remember: Annual marketing budget is approximately $1.2M"2. Verify Brand DNA completeness
"What's Acme's brand voice?"Review all five Brand DNA fields. Fill in gaps:
"Set Acme's content themes to developer education, API tutorials, case studies, and product launches"3. Close out open commitments
"What commitments are still open for Acme?"Mark completed items as done:
"Mark the media plan as done"For items that will carry over to the successor, leave them open -- they'll appear in the export as active action items.
4. Generate the handoff package
Armbrain produces a polished client-safe handoff package:
"Export a handoff for Acme"This returns the package in the response payload. Nothing is sent externally and no files are written by handoff.
| Format | What it is | Best for |
|---|---|---|
| JSON | Structured client-safe snapshot with brand DNA, memories, rocks, campaigns, and open items | Portable archive and future live-access setup |
| Markdown | Human-readable summary | Quick reference or pasting into other tools |
By default, JSON and Markdown are returned. You can request a specific format:
"Export a handoff for Acme in JSON format"
"Export a handoff for Acme as Markdown"Privacy in handoff exports:
The handoff package is filtered for a client-safe audience. It includes active, open, non-private memories only. Private, sensitive, internal CMO, hidden/dismissed, non-active, and unknown-sensitivity memories are excluded. Raw source documents are not included. Structured sections such as stakeholders, planning items, and inherited company context are also filtered server-side; unsafe sections are omitted rather than shown to the client.
Every handoff includes internal preflight metadata with included memory count, exclusion counts, omitted sections, raw-document status, and source receipts. Use it to QA the package before sharing. Give the client the Markdown or JSON handoff, not internal preflight metadata or your raw owner export.
5. Live recipient access
Live handoff means recipient access to a queryable client mind, not an import command. Until access grants ship, the handoff package is a portable snapshot. Share the Markdown with people and keep the JSON as the structured archive.
Do not promise that a successor can import the JSON handoff into Armbrain today. There is no supported import_handoff tool in the current gateway.
What the Successor Gets
The handoff gives the successor CMO or in-house marketing lead:
- Instant brand context -- voice, positioning, and messaging guidelines they can use immediately
- Decision trail -- why things are the way they are, not just what they are
- Campaign intelligence -- what's been tried, what worked, what didn't
- People knowledge -- who to talk to, how they prefer to communicate, and organizational dynamics
- Open threads -- active commitments and unresolved items that need attention
If the successor uses Armbrain, use the JSON as the setup snapshot while live recipient access is being completed.
When to Use Handoff
| Scenario | What to Do |
|---|---|
| End of a retainer engagement | Full handoff with all sections |
| Transitioning to in-house team | Handoff emphasizing brand DNA and stakeholder map |
| Temporary coverage by a colleague | Quick handoff with open commitments and upcoming meetings |
| Client requests their data | Export the client mind (GDPR-compliant data portability) |
| Annual renewal review | Generate handoff-style summary to demonstrate value delivered |
Key Details
- Sensitive/internal memories are excluded. Use sensitive or cmo-only notes for internal observations, compensation notes, legal/medical details, or strategic assessments you don't want in the deliverable.
- Handoff is read-only. Generating a handoff document doesn't modify any data. You can generate multiple versions as you refine the export.
- Brand DNA history is preserved. The audit trail of brand voice and positioning changes is recorded in the database. The handoff captures the current state, not the full change history.
- Deletion cascades. If you delete a client mind, all associated memories, briefs, documents, and history are permanently removed. Export before deleting.
- Data rights. Clients can request a full export or deletion of their data at any time. See the Data Privacy and Isolation guide for details.