Mindvalley Stories
Tracie Fujikane
AI Mastery

Built an AI organization of eight agents that runs the business while I sleep

Quick summary

This entrepreneur built an autonomous AI organization of eight specialist agents that handles everything from morning briefings to customer service—while he sleeps. By focusing on purpose over tools and packaging reusable solutions, he's created systems that run independently across two businesses and serve over 1,100 users.

My Entry can be found at: https://portfolio.businessreimagined.ai

ACHIEVEMENTS

Running without me

- A morning brief compiles at 7:45 and is delivered at 8:00 as text and audio, on a schedule, with nobody starting it

- Thirty to forty headless sessions rewrite and index my second brain while I sleep

- An organization of eight specialist agents, coordinated by one chief of staff

Personal, not only work

- My recipe library was hotlinked to other people's sites, so I had all 133 images pulled local with a reversible log back to each source

- Tax and other sensitive documents run on local models and never leave the house

- 71 video study documents in my vault, produced by a shortcut I built

- Songs written for a business that bought one, a friend's memorial, an engagement, and a company anniversary

Built and in use

- A study system: three Skills, four lessons live, two blocking quality gates

- A company-wide AI program at Purium, past eleven hundred conversations

- An application my team runs their day inside

- A second business: the platform delivering Hartman Color Code assessments for my facilitation practice

- A product video for Purium's ULT program, brand and compliance Skills, and a pomodoro timer because I wanted one that worked the way I work

At corporate level, beyond my own team

- Brought Claude to Purium's corporate office, taught the staff, installed Skills; their team publishes without me

- Classified real customer-service transcripts and built a cited knowledge base from the company's own asset library

TOOLS

- Models and environments: Claude Max and Claude Code, Claude Skills as the packaging format, ChatGPT for the GPTs my Brand Partners use, Gemini Notebook, Ollama for local inference

- Voice: Wispr Flow for dictation, edge-TTS and a self-hosted VoiceBox for speech

- Media: Suno for music, HeyGen and Higgsfield for video, yt-dlp for source material

- Knowledge: Obsidian in plain text with Copilot, Smart Connections, Text Generator and FileOrganizer running inside it

- Build and infrastructure: Supabase, Netlify, Vercel, Cloudflare, Infisical for credentials, self-hosted Langfuse for tracing, Docker, Neo4j and Tailscale across a Mac mini that never sleeps

- Sixty-seven items, inventoried and dated, because a tool I have forgotten I own is a tool I am not governing

METHODOLOGY

I look at the purpose and outcome before I look at the tools.

1. Decide the boundary before the task. Anything sensitive runs locally and never leaves the house. Everything else goes to whichever model fits.

2. Use voice on both ends where it earns its place. Dictation when speaking is faster than typing, and audio output for what I want to take in while doing something else: the morning brief arrives as text and audio, and every lesson in the library is narrated.

3. Keep the assistants separate, one job each. Pepper runs my day. Amira handles Purium discovery. Donna routes my agent organization. Echo tells me when my writing has stopped sounding like me. One assistant that does everything is one I cannot audit.

4. Package anything reusable as a Skill. A tool should be usable by someone who does not understand it. That is why my Brand Partners get finished tools rather than prompts.

5. Review harder than I ask. Across twelve build sessions there are roughly two correction turns for every build request.

6. Refuse the fix, demand the rule. A fix leaves the generator free to make the same mistake tomorrow, so every flaw I catch by eye becomes an automated check.

LEARNINGS

- The standard I hold now is whether I can hand something to someone else and have it keep working when I am not there. That changed what I build: fewer capabilities, more finished tools with the judgment already inside them.

- The more access I gave, the more carefully I had to think about what I had handed over. There was a point where I stopped and said I might have given more permission than was safe. That question is now part of how I set up everything I run.

- The work outgrew my memory of it. I keep a dated inventory because I can no longer hold the list in my head, and something I have forgotten I own is something I am not governing. Once a thing is too big to watch by attention, it needs a system instead.

- Watching my first AI Summit in 2024 opened up ways to be creative and bring ideas to life I would never have dreamed of. I know I have a great deal more to learn. The best is yet to come.

ENTRY URLs

Portfolio, start here: https://portfolio.businessreimagined.ai

These are separate entries that fall under this submission

Study notes library: https://portfolio.businessreimagined.ai/library-index

Bringing AI to Purium: https://portfolio.businessreimagined.ai/bringing-ai-to-purium

Success Planner, live: https://planner.nlgj.vip Test Account PW: welcome123

Color Code assessment, sample report: https://portfolio.businessreimagined.ai/samples/color-code-report-sample.pdf

The AI Organization: https://portfolio.businessreimagined.ai/agentic-organization

I even had Claude work on fill in the forms.


Tracie Fujikane

Written 11 August 2026 Submitted by the storyteller

Every story is written by a Mindvalley student or by someone our teachers have worked with. How we collect and check stories

Related Stories

Built an AI organization of eight agents that runs the business while I sleep | Mindvalley Stories