Matt Zimak Case studies A company brain
A company brain, updated by every meeting.
Everything a company knows, in one GitHub repo that people and AI agents read alike: strategy, decisions, customers, suppliers, people. After every meeting the new facts go in with their source, and a change to strategy, decisions or finance waits for a person to approve it in Slack. Fed by every meeting of a family business group since July 2026; four more companies run on the same structure.
- Company knowledge
- AI agents
- Meeting notes
- Approvals
Built for
Built with
Fireflies
n8n
Claude
GitHub
Slack
What travels where.
- TRANSCRIPT after every meeting
- FACTS each with its quote
- SAFE EDIT timelines, notes, new contacts, with the source
- CORE CHANGE strategy, decisions, finance, as a pull request
- APPROVED a click in Slack merges it
- CONTEXT the repo, for any agent
Who is this for?
Companies whose knowledge lives in people's heads.
What was agreed, with whom and why, written down once and kept current.
Groups of several companies.
One folder per company, with shared people and decisions in one place.
Teams that work with AI agents.
Every agent starts from the company's facts instead of a blank page.
What problem does it solve?
What a company knows lives in meetings, chats and a few people's heads. A new hire, an adviser or an AI agent starts from zero, and a decision made in March gets argued again in June. A wiki helps until nobody updates it.
What it does.
- One repo per company
- Strategy, products, brand, goals, customers, suppliers, people and decisions, one file per thing, in plain text that people and agents read alike.
- Fed by every meeting
- Fireflies records the meeting. n8n files the transcript in the repo and pulls out the facts, each with the sentence it came from.
- A curator every night
- A Claude agent folds the new facts into the right files: dated timeline entries, meeting notes, new contacts and suppliers as drafts, each citing its meeting. Once a week it writes a short brief per company.
- A person for what matters
- A change to strategy, a decision, the goals or finance becomes a pull request and a card in Slack, in the team's language, with Approve and Reject. Approve merges it; nothing core changes without it.
- Any agent
- Ask it in a Claude chat, edit it with Claude Code, or point Cursor, Codex or any other agent at the repo. It is plain files in Git, so no tool owns it.
How it was built.
May to June 2026
The first brains, one GitHub repo per company on one structure: a design studio group, my own three companies, then a family business group.
7 July
Meetings start feeding it: the n8n fact tap, the nightly curator and the approval card in Slack.
August
A weekly check for broken links, duplicates and contradictions.
September
The meeting loop published as an open-source template, next to the repo template.
By October
149 meetings folded in, a weekly brief per company, and the transcripts searchable in the CEO's terminal.
The rules it runs by.
- Every fact cites its meeting
- No source, no write.
- Timelines only grow
- An entry is never edited or deleted. A correction is a new dated entry.
- Decisions stay as decided
- A merged decision record is never rewritten, not even through a pull request.
- Nothing invented
- A missing number, date or name stays missing. An uncertain fact is flagged and goes to a person.
- Private stays private
- Pay, health and family topics from a meeting are noted as a sensitive topic, never quoted.
- Checked every week
- A separate pass looks for broken links, duplicates and contradictions.
What the owners have now.
- One place for what is true
- Timelines, contacts, suppliers and meeting notes per company, current to last night's meetings.
- Context for every agent
- A Claude chat, Claude Code or any other agent starts from the company's real facts.
- A weekly brief
- Each company gets a short summary of its week, written from its meetings.
- Control
- Core files change only on Approve. Everything else carries its source and can be undone in Git.
The same brain, five times.
The same structure runs for a design studio group and for my own three companies: Agentmatik, Deep Noise and Museverse. The repo template and the meeting loop are open source on GitHub, as template-intelligence and brain-curation-loop. The meeting transcripts also feed the CEO's terminal.
Start with a call.
Fifteen minutes on what your company knows, where it lives today, and which meetings should feed it first.




