Skip to content
For VAs

Building Templates and Systems from Your CMO's Patterns

5 min read

Building Templates and Systems from Your CMO's Patterns

Your CMO repeats tasks without noticing patterns. Every Monday they write similar client updates. Every quarter they pull the same data. Every onboarding follows the same rough steps. Your job is to watch, document, and turn those patterns into templates and systems that save everyone time.

The goal: turn your observations into leverage. The CMO's time is the bottleneck - you reduce the cost of their repeating work.

Spotting the Pattern

Before you can build a template, you have to see the repetition. Here's what to watch for:

SignalWhat It Means
The CMO asks you for the same thing every weekThat's a recurring report template
You copy-paste from last time and change the detailsThat's a template waiting to happen
The CMO says "do what we did for ClientX" for a new clientThat's a process you can standardize
You find yourself explaining the same steps to a new team memberThat's an SOP that should be written down
The CMO does 5 steps every Monday in the same orderThat's a workflow you can shortcut

Build templates before being asked. Present the draft: "I made a template based on your last 4 Friday updates. Want to try it next week?"

Using Armbrain to spot a repeating pattern and build a template
Using Armbrain to spot a repeating pattern and build a template

Common Templates Worth Building

These are the templates that save the most time for fractional CMOs managing multiple clients:

Client Update Email

Pull the structure from emails the CMO has already sent. Most follow a pattern: what we did this week, results so far, what's next, anything we need from you. Build a template with placeholders and fill it in from Armbrain data.

Meeting Agenda Structure

If the CMO runs structured meetings (especially L10s), the agenda format is the same every time. Build a template so you're not recreating it from scratch.

Onboarding Checklist

Document the 15-20 onboarding steps so nothing gets missed.

Sprint Report / Monthly Report

Build a report template with sections for KPIs, updates, wins, risks, and next steps. Fill it from Armbrain:

"Switch to ClientX"
"What are the key metrics and campaign updates from the last 30 days?"

Quarterly Review Deck Outline

Use the same outline each quarter: goals versus actuals, rocks, scorecards, and next priorities. The CMO only fills in current data.

Turning a Process into an SOP

When you spot a multi-step process that repeats, document it as a standard operating procedure. Keep it simple: bullet points, not essays.

A good SOP answers:

  1. When does this happen? (trigger)
  2. What are the steps? (actions, in order)
  3. Where does the output go? (who sees it, where it's stored)
  4. What could go wrong? (common mistakes to avoid)

Example: "Friday Client Update Process":

  1. Switch to each active client in Armbrain
  2. Pull the week's activity and action item status
  3. Draft the update email using the client update template
  4. Send the draft to the CMO for review (or send directly if approved to do so)
  5. Store a memory that the update was sent: "Quick note: sent weekly update email to ClientX, April 4"

An imperfect SOP beats no SOP. Refine it with each use.

Building Automations They Didn't Ask For

This is the advanced move. When you see the CMO repeat a 5-step sequence, handle steps 1-4 and hand them step 5.

Examples:

  • Monday morning: You pull all client summaries and compile them into a single briefing before the CMO even starts their day.
  • Before quarterly reviews: You pre-populate the review template with scorecard data, rock status, and key memories from Armbrain.
  • After meetings: You create the follow-up email draft based on the meeting notes pattern you've observed.

The key is to frame it as a draft, not a decision. "I pulled this together based on what I saw in Armbrain. Want me to send it, or do you want to edit first?"

Templates for Armbrain Itself

Build templates for Armbrain too: standard queries, memory formats, and prep sequences.

Standard meeting prep sequence:

"Switch to ClientX"
"Prep meeting with Bob - include rocks, open issues, and recent campaign results"
"Show me the agenda"
"Any action items from the last meeting that are still open?"

Run the same sequence for every client meeting. It becomes muscle memory.

Standard memory format for decisions:

When storing a decision, use a consistent format so they're easy to search later:

"Store a memory: DECISION - ClientX is pausing LinkedIn ads for Q3 and shifting budget to events. Discussed in April 4 meeting. Bob approved."

The "DECISION" prefix makes it easy to search for all decisions later.

The Template-Building Rhythm

WhenWhat You Do
First 2 weeks with a new CMOWatch and take notes. Do not build yet: observe the patterns
Week 3-4Build your first 2-3 templates based on what repeats most
MonthlyReview your templates. Are they saving time? Do they need updating?
When something feels tediousAsk yourself: is this the third time I've done this? If yes, templatize it

Tips

  • Start small. One good template is better than 10 unused ones.
  • Get feedback. Show the CMO your first template and ask what's missing. Their edits tell you what matters to them.
  • Don't over-engineer. A Google Doc with placeholder text is a perfectly good template. It doesn't need to be a fancy system.
  • Name things clearly. "ClientX Weekly Update Template" beats "Template v3 final FINAL."
  • Share what you build. If another VA joins the team, your templates and SOPs are the training manual.
  • Morning Routine: a process that is already templatized
  • End of Week Summary: another repeating process to templatize
  • Tracking Action Items: templates for consistent action item tracking
  • Feeding Armbrain - building a system for ongoing knowledge capture