At EOS, every AI tool we used started each conversation knowing nothing about our clients. The company brain fixes that. It's a git repo of plain markdown holding what the agency knows about its clients and itself, and the AI reads it before it answers.
- Company
- EOS Healthcare Marketing
- Role
- Lead developer
- Type
- Internal tool
- Stack
- Markdown, Git, Slack, LLMs
EOS Company Brain at a glance
- One source of business context for every AI tool and teammate
- Plain markdown in git, so every change is versioned and reviewable
- The team asks it questions from Slack
Starting from a blank page
Ask a general AI tool about one of our clients and it has no idea what the practice does, what we deliver for them, or what was already decided. That knowledge lived in people's heads and in scattered docs, so every useful prompt started with someone pasting in background by hand.
Store only what nothing else owns
One rule shaped the whole design: the brain stores only what no other system owns. That covers practice identity and positioning, what we deliver to each client, notes someone needs before touching an account, and what got decided and why.
Anything a live system already owns stays there. Tasks live in ClickUp and hosting details live with the host, so the brain links to them instead of copying them. Copies go stale, and two sources that disagree are worse than one.
Plain text on purpose
Everything is markdown in git. The AI can read it directly, changes go through the same review as code, and the history shows who changed what and when.
Slack is the front door for now, since the whole team already works there. Because the content is plain text, moving to a different front door later won't mean rewriting anything.
What it changed
Our AI tools now start each task with the context a new teammate would get on their first day.
1
source of business context
for every AI tool and teammate
Slack
where the team asks it
no new tool to learn
Git
versioned history
every change reviewable