How should I set up an AI second brain for my business?

I've had so many stops and starts with a second brain. I built a private one five times. Then I looked at what was in it and realized 98% was just company stuff.

"I'm simplifying everything to say everything is either business or it's personal. My personal stuff is completely separate, a hundred percent. Everything else... is one thing and everyone has access to all of it."

Should I have a personal brain and a team brain?

Yes, but draw the line at business versus personal, not at "mine" versus "the team's." Everything about the business goes in one shared brain that every teammate and agent can read. Personal material stays fully separate. Don't make the two writable to each other.

The rule underneath it: you can't have two sources of truth. The moment the same fact lives in two places, one of them goes stale.

Why did my earlier second brains fail?

An earlier version had plumbing that worked fine, but the knowledge itself was about 2 out of 10 useful. It was mostly navigation and technical receipts, not substance. A brain full of logs about the brain isn't knowledge.

My rebuild keeps raw evidence (transcripts, notes, source files) separate from curated knowledge (the actual answers and decisions). They live in separate repositories.

What tools have I used?

• Obsidian. In January 2026 I built an intelligence dashboard in 20 or 30 minutes with Claude Code. It pulled YouTube channels I like, synthesized what mattered for local media and newsletters, drafted LinkedIn and Twitter posts, and pulled in my meeting transcripts. Obsidian is like Notion for markdown files, which is what AI reads.
• Notion. As of October 2026, every podcast episode gets a page with takeaways and social posts. Each client portal pulls metrics from greetform and Meta ads. My email and Fathom call transcripts flow in automatically, so I don't even need to make a note in my CRM. I drop interesting links and they get analyzed with next steps. A checkbox can trigger an agent to act.

One design note from the Notion rebuild: tell the model to avoid walls of text and use visuals. I tried the Notion build with Codex first and it was bad at it. Claude's top model did it well, far better than the smaller Sonnet model.

Should the second brain be my production database?

No. For my local directories, Notion is fine as an editing layer, but the production database stays the source of truth. Notion shouldn't become the live database for thousands of listings. Production publishes an editable view, people propose changes, and one controlled writer applies the approved edits.

What do I do when the AI system isn't ready?

Don't let team memory wait on automation. When my agents failed one day in September 2026, I created a plain shared channel called reference and told the team: if you're doing any real work, document it. Shared references, client history in the CRM and agent work stay separate, so nothing depends on the agents being up.

Start small: have the AI interview you and save the result as the first page of your brain.