Skip to content
For CMOs

Your First Week with Armbrain: Building the Habit

3 min read

The first week with Armbrain is about feeding it, not expecting perfection. By Friday, it knows enough to be useful. By month one, you rely on it.

Day 1: Set Up Your Personal Mind and First Client

Start by creating your personal mind. This is your CMO memory: preferences, voice, and cross-client patterns.

"Create my personal mind"
"Set my brand voice to direct, data-driven, no jargon"

Then onboard your neediest client, the one with a meeting this week:

"Create a client mind for Acme Corp"
"Switch to Acme"
"Set Acme's brand voice to approachable, technical, developer-first"

Store 5-10 things off the top of your head: stakeholders, brand positioning, and current work:

"Remember: Sarah Chen is VP Marketing, owns the rebrand, prefers Slack over email"
"Remember: Q2 budget is $85K, weighted toward paid social"
"Remember: We decided to pause LinkedIn ads until the new landing page is ready"

Don't overthink what to store. If you'd tell a colleague covering for you, it belongs in Armbrain.

Day 1: creating your first client mind and storing what you know
Day 1: creating your first client mind and storing what you know

Day 2: Feed It Real Conversations

Grab 2-3 recent meeting transcripts from Granola, Otter, or Zoom. Paste them in:

"Ingest this transcript from my March 15 call with Acme"

Armbrain extracts decisions, commitments, stakeholder details, and campaign outcomes automatically. Review what it extracted:

"Show me pending memories"

Promote the good ones, dismiss the noise. This teaches the system what matters to you.

Day 3: Run Your First Meeting Prep

You have a call with Acme this afternoon. Instead of scanning your notes:

"Prep my meeting with Acme"

The brief pulls together open action items, recent decisions, stakeholder concerns, and suggested talking points. It won't be perfect yet. The system only has a few days of data. But it's already faster than scrolling through email threads.

Day 3: your first meeting prep has context from what you stored
Day 3: your first meeting prep has context from what you stored

If something is missing from the brief, store it after the meeting. The next prep will include it.

Day 4: Capture Everything from Today's Meetings

After every call, spend 3 minutes:

"Quick note: Acme wants to move the launch from April 15 to May 1"
"Quick note: Sarah approved the new tagline - 'Build faster, ship smarter'"
"Remember as a commitment: I'll send the revised media plan by Thursday"

Quick notes are fast and unstructured. Use them for speed. Use store_memory when you want to be specific about type (decision, commitment, preference).

Day 5: See the Pattern

Run your first weekly summary:

"Give me a weekly summary for Acme"

Even with only a few days of data, you'll see the shape of what Armbrain is tracking. Open commitments, recent decisions, what changed this week.

Now do it across all clients:

"What's happening across all my clients?"
Day 5: cross-client view shows what you built in one week
Day 5: cross-client view shows what you built in one week

This is the moment it clicks. One command, full cross-client visibility.

The Habit Loop

The pattern that sticks:

WhenWhatWhy
Before a meetingprep meeting with [client]Walk in prepared
During a meetingQuick notes for key momentsCapture while it's fresh
After a meeting3-minute capture routineDecisions, commitments, action items
Monday morningMorning briefingSee the week ahead
Friday afternoonWeekly summaryClose the loop

Week one takes practice. You'll forget to capture things. You'll store notes that are too vague. That's fine. The system and your habit improve with use.

By week two, you'll start prepping meetings out of reflex. By month one, you'll have enough data that Armbrain genuinely surprises you with context you forgot you stored.