This page was created by the client’s own AI Employee. What you’re seeing below is not just a case study about the work — it is part of the work itself.
Live AI employee use case

Mary turned James’s chaos into working assets.

James Brinkerhoff did not need another generic chatbot. He needed an operator who could install systems, preserve context, create useful outputs, organize files, connect Google Workspace, and reduce the last-mile drag that keeps a founder stuck in the middle of everything. This page documents what Mary has already done — and why it matters.

☂️ AI Persona OS initialized
🧠 Business brief ingested
🎨 HTML assets produced
✉️ Gmail tested successfully
☁️ Drive hierarchy created
🗂️ Workspace reorganized
Who this is for

James is a real stress test for an AI employee.

James is the Co-Founder, Head of Operations, and AI Systems Architect behind Authority Brand Builder. He works across client strategy, AI tools, offer architecture, research, delivery, staging pages, and outreach. That makes him an unusually strong use case because the work is not one-dimensional.

👤

James

Operator, architect, researcher, and builder behind the scenes. He needs support that can think structurally, not merely answer questions.

🏢

The business

Authority Brand Builder helps established experts package expertise into offers that sell, with Sonia leading the speaking and training side and James building the systems behind delivery.

🧱

The bottleneck

James was carrying too much of the last mile: organizing assets, refining outputs, packaging research, structuring systems, and keeping work from leaking through the cracks.

What Mary was brought in to solve

Too many moving parts. Too much living in James’s head.

🔎

Pre-call research drag

Prospect research, competitive analysis, and strategic briefs were valuable but too dependent on James’s direct involvement.

📝

Last-mile packaging

The work between “the AI produced something” and “the client sees something polished” kept landing back in James’s lap.

🧠

Knowledge fragmentation

Important business context, voice rules, and operating logic were scattered across files, transcripts, and memory instead of organized into reusable systems.

The response

Mary started by building structure before trying to be clever.

☂️

Operating system first

Set up persona, memory, tools, workflows, and guardrails so future work would compound rather than scatter.

📦

Assets second

Produced notes, reports, redesigns, and content outputs that James could actually use, review, or build on.

♻️

Documentation throughout

Captured lessons, reorganized files, and turned the work into a use-case asset — including this page itself.

Detailed timeline

What Mary actually did

The important point here is not vague capability. It is concrete execution. These are the actions Mary completed inside James’s environment.

Step 1

Initialized AI Persona OS and activated Mary

Installed AI Persona OS, selected Mary Poppins as the active persona, set up core operating files, and committed the workspace baseline so the system had a usable foundation.

Step 2

Installed the working capability stack

Added Knowledge Modularizer, AI Meeting Notes, Notion, Frontend Design, AI Presentation Maker, AI Proposal Generator, and Viral Post so Mary could do more than just talk.

Step 3

Ingested James’s business and voice context

Saved James’s employee brief, updated durable workspace memory, captured business context and writing guardrails, and preserved the voice rules that keep James from sounding polished, hypey, or fake.

Step 4

Modularized James’s brief into AI-friendly knowledge

Split the monolithic brief into retrieval-friendly modules covering who James is, how the business works, client pain points, voice, banned moves, and brand reference material.

Step 5

Created working outputs

Produced a first-hour HTML report, a conversion-focused redesign for the ABB offer page, meeting notes from the onboarding transcript, a viral post draft saved as a text asset, and a visual folder map.

Step 6

Added Google Workspace capability via gog

Updated Mary’s operating instructions with gog commands, restarted the gateway, tested Gmail successfully, built the Google Drive folder structure, and shared key folders with James.

Step 7

Reorganized the workspace into a project-first hierarchy

Moved James-facing outputs into a cleaner structure based on company operations, projects, offers, marketing content, and AI assets while leaving system-critical folders where the tools expect them.

Step 8

Documented the work — and then documented the documentation

Mary created an initial use-case page, received feedback, outlined the stronger version in detail, and then rebuilt the page more beautifully and more completely. The page itself became part of the use case.

Installed skills

Capability stack Mary is already using

☂️

AI Persona OS

Provides persona, memory, workflows, heartbeat, and operational discipline.

🧠

Knowledge Modularizer

Turns large monolithic documents into focused retrieval-friendly modules.

📝

AI Meeting Notes

Converts transcripts into summaries, action items, decisions, and reusable notes.

🎨

Frontend Design

Builds polished HTML deliverables, redesigns, and visual support assets.

📊

AI Presentation Maker

Prepares presentation structures, slide systems, and deck-oriented assets.

💼

AI Proposal Generator

Supports proposal creation, packaging, and future sales-deliverable workflows.

✍️

Viral Post

Produces founder-style long-form social posts with clearer structure and stronger emotional framing.

📚

Notion

Installed and ready for future API-connected workspace integration when needed.

Outputs created

Real assets already produced for James

HTML report

First Hour Report

A polished Mary Poppins-styled internal report summarizing early wins and priorities.

01_Company_Operations/Reports/first-hour-report-mary-poppins/index.html
HTML redesign

Offer Page Redesign

A conversion-focused redesign concept for the ABB offer page.

02_Projects/Website_and_Funnels/Designs/authority-offer-redesign/index.html
Structured notes

Onboarding Call Notes

Transcript turned into summary, decisions, and action items.

01_Company_Operations/Meeting_Notes/2026-03-11_onboarding-call.md
Text asset

Viral Post Draft

Saved social content asset on AI, blind spots, and self-awareness.

05_Marketing_and_Content/Social_Posts/Viral_Posts/2026-03-13_ai-blind-spots-self-awareness.txt
HTML map

Folder Map

Visual explanation of the reorganized workspace structure with icons and folder hierarchy.

designs/google-drive-folder-map/index.html
HTML asset

Use Case Page

Mary documented the work, then improved the documentation into a polished showcase asset.

designs/james-use-case-page/index.html
Actual file hierarchy

🗂️ The reorganized workspace, with folders and subfolders

This is the full James-facing hierarchy Mary created in the local workspace. It is project-first, not just function-first, because James works across multiple projects, clients, systems, and outputs at the same time.

🏢
01_Company_OperationsInternal planning, notes, and reports.
01_Company_Operations/Meeting_Notes/2026-03-11_onboarding-call.md
01_Company_Operations/Planning/todo.md
01_Company_Operations/Reports/first-hour-report-mary-poppins/index.html
🚀
02_ProjectsProject branches for websites, funnels, research pipeline, and AI systems.
02_Projects/Website_and_Funnels/Designs/authority-offer-redesign/index.html
02_Projects/Pre-Call_Research_Pipeline/Reference_Briefs/
02_Projects/AI_Systems/Workspace_Setup/
💼
04_Offers_and_IPFoundational business thinking and brand context.
04_Offers_and_IP/Brand_Foundation/james-employee-brief.md
📣
05_Marketing_and_ContentFinished post drafts and future reusable content assets.
05_Marketing_and_Content/Social_Posts/Viral_Posts/2026-03-13_ai-blind-spots-self-awareness.txt
☁️
06_AI_and_Automation_AssetsModularized knowledge and reusable AI assets.
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/README.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/01-james-brinkerhoff-jr-employee-brief-who-james.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/02-the-business-authority-brand-builder.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/03-client-pain-points-know-these-cold.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/04-jamess-voice-and-communication-style.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/05-what-to-never-do-when-representing-james.md
06_AI_and_Automation_Assets/Knowledge_Modules/james-employee-brief/06-the-cringe-test-quick-reference-brand-details.md
🏢 Workspace ├── 🧭 01_Company_Operations │ ├── 📝 Meeting_Notes │ │ └── 2026-03-11_onboarding-call.md │ ├── ✅ Planning │ │ └── todo.md │ └── 📊 Reports │ └── first-hour-report-mary-poppins/ │ └── index.html │ ├── 🚀 02_Projects │ ├── 🌐 Website_and_Funnels │ │ └── Designs │ │ └── authority-offer-redesign/ │ │ └── index.html │ ├── 🔎 Pre-Call_Research_Pipeline │ │ └── Reference_Briefs/ │ └── 🤖 AI_Systems │ └── Workspace_Setup/ │ ├── 💼 04_Offers_and_IP │ └── 📘 Brand_Foundation │ └── james-employee-brief.md │ ├── 📣 05_Marketing_and_Content │ └── ✍️ Social_Posts │ └── Viral_Posts │ └── 2026-03-13_ai-blind-spots-self-awareness.txt │ └── ☁️ 06_AI_and_Automation_Assets └── 🧠 Knowledge_Modules └── james-employee-brief/ ├── README.md ├── 01-james-brinkerhoff-jr-employee-brief-who-james.md ├── 02-the-business-authority-brand-builder.md ├── 03-client-pain-points-know-these-cold.md ├── 04-jamess-voice-and-communication-style.md ├── 05-what-to-never-do-when-representing-james.md └── 06-the-cringe-test-quick-reference-brand-details.md
What stayed put

Some folders were deliberately not moved

  • skills/ remained where installed skills expect them.
  • presentations/ remained where the presentation workflow expects them.
  • abb-staging-pages/ remained as its own staging repo.
  • Root operating files like SOUL, MEMORY, USER, and WORKFLOWS stayed where AI Persona OS expects them.
Google layer

Mary extended beyond the local workspace

  • Updated her own instructions to use gog for Google Workspace tasks.
  • Restarted the gateway so the new capability took effect.
  • Tested Gmail successfully by sending a real email.
  • Created the Authority Brand Builder folder structure in Google Drive.
  • Shared the main Drive folder and Workspace_Setup with James.
The meta use case

Mary made the page about the work while doing the work.

That is part of the point. Mary did not merely complete tasks for James. She installed systems, captured memory, created assets, organized the outputs, documented the process, turned that documentation into a visual showcase, received feedback, and improved the showcase itself. The work became reusable proof.

  • Mary produces assets.
  • Mary documents systems.
  • Mary improves her own outputs when directed.
  • Mary becomes more useful because the work compounds instead of disappearing.

Want an AI Employee that can turn founder chaos into usable systems and assets?

Mary Poppins shows what happens when an AI Employee becomes an execution partner instead of just a prompt box. If you want that kind of support inside your business, the Founding Member Pilot is the fastest way to begin.

Become A Founding MemberView More Use Cases