Skip to content
Other

Auto-Generated Case Studies

How to turn successful campaigns into polished case studies using data Armbrain already has -- no manual data entry required.

Overview

After a campaign succeeds, Armbrain can draft a case study from the memories it already holds: the original objectives, the approach you took, the results you achieved, and even client quotes pulled from meeting notes. Your portfolio builds itself.

The case study is written in your voice (the CMO's brand voice), not the client's. It is your work product, showcasing your expertise.

When to Use This

Generating a Case Study

"Generate a case study for Acme's Q1 email campaign"

or use the command directly:

/cmo-case-study Acme Q1 Email Campaign

Armbrain gathers data from the active client mind:

  1. Campaign objectives from your planning memories
  2. Approach and tactics from execution memories
  3. Results and metrics from recorded campaign outcomes
  4. Client quotes extracted from meeting transcripts where the client commented on results
  5. Timeline from memory timestamps

The output follows a standard case study structure:

Important: Client Quotes Need Approval

Any quotes pulled from meeting notes are clearly marked with a warning:

"Extracted from meeting notes -- verify before publication"

You must get explicit client approval before publishing any quotes attributed to them. Armbrain flags these automatically so nothing slips through.

Regenerating with Different Focus

Not happy with the emphasis? Ask for a different angle:

"Regenerate the case study but focus more on ROI"
"Make it shorter -- just the highlights"

Armbrain uses the same underlying data but reshapes the narrative based on your direction.

Saving and Exporting

The case study is saved as a document memory in the client's client mind, so you can find it later:

"Find the case study I generated for Acme"

The output is standard markdown, which you can copy into your website, a proposal, or a PDF.

Quality Safeguards

Armbrain applies several safeguards to ensure case studies are accurate and trustworthy. These run automatically -- you do not need to configure anything.

Minimum Data Requirements

Armbrain checks how much campaign outcome data exists before generating:

Outcome CountWhat Happens
0 outcomesRefuses to generate. Tells you to record campaign outcomes first.
1 outcomeGenerates with a warning: "Based on limited campaign data. This case study will improve as more outcomes are recorded."
2-4 outcomesGenerates normally.
5+ outcomesGenerates a comprehensive case study.

This prevents thin data from producing a case study that looks more complete than it actually is.

No Fabricated Numbers

Every metric in the case study must come from a recorded campaign outcome. If a metric is missing, Armbrain uses a placeholder instead of making something up:

Results: [Specific metrics not yet recorded]

A case study with honest gaps is far better than one with invented numbers. Record the missing outcomes when they become available and regenerate.

Contradiction Detection

If Armbrain finds conflicting data for the same campaign -- for example, one outcome says "revenue up 30%" and another says "revenue up 15%" -- it pauses and asks you which is correct before generating. It will not silently pick one or average them.

Attribution Sourcing

In the version you see as the CMO, every metric includes a source reference showing which memory it came from and when it was recorded. This lets you verify claims quickly. The exportable version strips these references for a cleaner read, but keeps the claims intact.

Quote Verification

Client quotes pulled from meeting transcripts are:

If no direct quote exists in the data, Armbrain says so rather than fabricating one: "No direct client quotes available. Consider asking [stakeholder name] for a testimonial."

Tips