# What is a company brain? And what is a GTM brain? > A company brain is everything a company knows, kept current and usable by people and AI agents. What it is made of, why the GTM brain matters most, and where homemade brains break. Updated October 29, 2026 Video: https://www.youtube.com/watch?v=0phAfVzaAw4. Christopher O'Donnell at Vector 2026 on what a company brain is made of and the three questions RevOps leaders should take back to their teams. **The short answer.** A company brain is everything a company knows, kept current and usable by both people and AI agents. Day AI builds the go-to-market version: a context graph of every meeting, email and call, and an agent control plane where agents do the work and people approve it, running in place of your CRM or on top of Salesforce or HubSpot. A GTM brain is the go-to-market part of it: what the company knows about its customers, prospects and deals, built from the team's conversations, with agents that do the work on it, and Day AI is built to run it. Say you run partnerships at a fintech company, and it's three o'clock on a Friday. Like every partner manager on the team, you cover 20 to 40 partners, and each one has a week of calls, Slack threads, email, HubSpot notes and Notion pages behind it. Your Day AI agent has already read all of it. Its partner history skill pulled the week's calls, Slack, email, HubSpot and Notion into the running record it keeps for every partner, and the refreshed records are waiting in Day AI for your approval, as they are every Friday. You skim the changes, approve them in Day AI, and every partner's record is current before the weekend. Once a month, those approved records feed the leadership pre-read, which has replaced the slide deck, and leadership likes it. Next month's pre-read starts from the records you just approved. **Day AI's view.** The company brain is life after CRM: the conversations are the record, agents do the work, and people approve it. Day AI provides the context graph and agent control plane to quickly and securely upgrade your company brain. The usual answer, a smarter wiki or a bigger personal folder, goes wrong because it only knows what someone decided to write down, and it only works for one person. If you already keep a folder of notes with Claude Code on top, that was the right start. *Claims about other products are dated October 2026 and kept to what those products say about themselves. This is Day AI's guide.* --- ## Where "second brain" came from The idea is older than AI. The Zettelkasten, a [slip-box of linked notes](https://en.wikipedia.org/wiki/Zettelkasten) best known from the sociologist Niklas Luhmann, was a second brain on paper. Tiago Forte's [Building a Second Brain](https://www.buildingasecondbrain.com/) (2022) made the term popular, with the [PARA method](https://fortelabs.com/blog/para/) (projects, areas, resources, archives) for filing what you capture. The AI version came in April 2026, when Andrej Karpathy [posted](https://x.com/karpathy/status/2039805659525644595) his "LLM wiki" pattern and wrote it up as an [idea file](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f). You drop raw sources into one folder and never edit them. An LLM compiles and maintains "a directory of LLM-generated markdown files" from them, a wiki it keeps current, steered by a schema file such as CLAUDE.md or AGENTS.md. Plenty of RevOps leads and founders have built their own version, and Day AI takes that folder idea to the company: one brain built from the team's conversations, with an agent working for each person. When companies say "company brain" today, most mean a shared knowledge base. In [Slite's survey of 149 people](https://slite.com/ebook-downloads/company-brain-ebook.pdf), 53% described a continuously updated knowledge base and 12% a memory layer for agents, and Slite notes that YC's Summer 2026 Request for Startups names the company brain as a category. --- ## Why a company needs one, and where a personal folder breaks A business runs on what it knows about its customers: which buyers say yes, why deals stall, what customers were promised. Most of that was never written down. It was said on a call, in an email thread or in Slack. A personal brain serves one person. A company brain adds the whole team's conversations, who may see each one, and agents working for each person, and that's what Day AI builds. A personal folder breaks at company scale in five places: - **Many people's conversations.** One person's folder holds one person's calls. The company's knowledge is spread across every rep, CSM and partner manager. In Day AI, each person connects email and calendar, a notetaker records meetings, and Gong, Granola and Slack channels come in, so the context graph holds the whole team's conversations. - **Privacy between teammates.** A teammate must not read a thread you keep private, and a shared folder can't tell the difference. In Day AI, each person sets sharing rules for their own email (everything or nothing by default, with exceptions by domain, address or Gmail label), and every answer cites the call or message it came from. - **The CRM.** The folder has a CRM export from last month; the team works in the live CRM. Day AI runs in place of your CRM, or on top of Salesforce or HubSpot, syncing through their MCP servers, which allow reads and writes when the write tools are turned on. - **Agents acting for each person.** A Claude Code session runs as whoever opened it. Twenty reps need twenty agents, each seeing only what its person may see. In Day AI, every agent has a name, a job and skills, works for one person and inherits that person's permissions. - **Keeping it current without anyone filing notes.** A folder is only as fresh as its last upload. In Day AI, the record fills itself from meetings, email and calls, and skills run on a schedule or when something happens, with no one filing anything. In customer-facing work, a mistake lands on a customer: a private thread shown to the wrong rep, a follow-up quoting last quarter's pricing. The controls that keep agents safe are the same ones that let you hand them real work. [This video](/videos/second-brain-to-team-brain) builds a Claude Code and Obsidian second brain, then shows what changes once the team's calls go in. --- ## What a GTM brain is made of, and which parts Day AI provides A GTM brain is the company brain for go-to-market, and it is the one that matters most, because how a business makes money is the most important thing it knows. Its owner is usually RevOps, which already owns the pipeline and its definitions; [What is a context graph?](/guides/what-is-a-context-graph) makes that case. Think of it as the three-layer GTM brain: the context graph, the agent control plane, and what your team builds. The first two are infrastructure; the third is yours. 1. **A context graph.** The people, companies, deals and conversations your team works with, linked, with every fact tied to its source and visible only to those allowed to see it. Day AI builds it from your team's meetings, email, calls and Slack. 2. **An agent control plane.** How agents work: each has a job and skills, works for a named person, and leaves a record of every run. You decide which work waits for a person, and every skill is versioned, so a change can be traced and undone. In Day AI, a skill only touches the connectors you attach to it, skills like Opportunity Automation start in learning mode, admins publish skills from a shared library, and the agent can bring back an earlier version of any skill. 3. **What your team builds on top.** Your skills, agent job descriptions, definitions (what counts as a qualified deal or a churn risk) and workflows. In Day AI, you write these as skills in plain language. That split answers build or buy by category: buy the infrastructure, the first two layers, because it is difficult to build, barely differs between companies, and is where the security risk sits. Build the third. With Day AI, you buy the first two and keep building the third. The [build-or-buy guide](/guides/build-vs-buy-customer-context) prices both sides. --- ## Start with one folder: the GTM Brain repo The company brain can still be one folder an agent works from. Day AI's own team publishes [GTM Brain](https://github.com/day-ai/gtm-brain), "a Claude Code harness for running your Day AI workspace like a GTM operating system." It is one repo you open in Claude Code, with a CLAUDE.md of operating principles, planning documents, skills, and the Day AI MCP server (`https://day.ai/api/mcp`) already configured. Start with: ```sh npx skills add day-ai/gtm-brain --global ``` 1. **Make it your team's repo.** After installing, run `/setup-gtm-brain`, which creates your team's private copy. 2. **Map your GTM before you have a workspace.** Open the folder in Claude Code and run `/start`. With no Day AI workspace connected, it drives the `map-your-gtm` initiative: it reads the GTM docs, CRM export and org chart you drop into its discovery inbox, and anything you've already taught Claude, maps your tech stack, strategy, people, privacy posture and agent fleet, and scopes a first-win pilot. 3. **Connect Day AI and implement.** Once a workspace exists, an Owner or Admin authenticates the Day AI MCP server and runs `/start` again. From there the repo plans, audits and implements: it designs agents and skills for each person, and previews every change before it writes to the workspace. --- ## How to start a GTM brain with Day AI 1. **Point it at one number.** Pipeline created, win rate, ramp time or rep earnings. In Day AI, write the number into each agent's job description, so every run starts from it. [How to grade your AI agent setup](/guides/grade-your-ai-agent-setup) turns this into a scorecard. 2. **Connect the conversations.** In Day AI, each rep connects email and calendar and turns on the notetaker, and an owner connects Gong, Granola or Slack. Agents work from your history once the first sync finishes, within hours. 3. **Give each rep an agent with two jobs.** In Day AI, every new agent comes with the Morning Briefing skill, a weekday briefing of priorities, meetings and recent action items. For follow-ups, ask the agent to "create a skill that drafts follow-up emails after meetings every evening", and the rep reviews each draft before it goes out. 4. **Approve first, then widen.** In Day AI, skills like Opportunity Automation start in learning mode: they report what they would have done and ask for feedback before they act. In chat, each connected tool is set to Always allow, Needs approval or Off, and those settings are chat defaults only. A skill uses the connectors you attach to it without asking, so attach only what that skill should touch. 5. **Keep what you built.** Your folder and Claude Code connect to Day AI over MCP, with OAuth, so your own Claude Code and your team's Day AI agents read the same customer memory. The Vector 2026 talk at the top of this page is the long-form version of this argument. ## Frequently asked questions ### What is a company brain? A company brain is everything a company knows, kept current and usable by both people and AI agents. It is more than a knowledge base: it holds what actually happened with customers, who may see each piece, and agents that do work on it. For go-to-market teams it has two parts, a context graph of the people, companies, deals and conversations, and an agent control plane that runs agents on it. Day AI supplies both parts for go-to-market teams, so you start from the infrastructure instead of building it. ### What is a GTM brain? A GTM brain is the company brain for go-to-market: everything a company knows about its customers, prospects and deals, kept current from its team's meetings, email, calls and Slack, visible to each person according to what they may see, with agents that do the work on it, such as prepping meetings, drafting follow-ups and keeping the pipeline clean. It is the brain that matters most, because how a business makes money is the most important thing it knows. Day AI provides the infrastructure for this brain. ### Is a company brain the same as a knowledge base or wiki? Not quite. A knowledge base or wiki holds what people wrote down, and enterprise search helps people find it. Those tools do that job well, and a company brain should include it. But most of what a company knows about its customers was never written down. It was said on calls, in email threads and in Slack. A company brain also holds those conversations, decides who may see each one, and runs agents on them. Day AI covers that customer side for go-to-market teams. ### What's the difference between a company brain and a context graph? A context graph is one part of a company brain: the linked record of people, companies, deals and conversations, with every fact tied to its source. A company brain adds an agent control plane, which decides how agents work on that graph, and the skills, definitions and workflows your team builds on top. See Day AI's guide, What is a context graph?, at day.ai/guides/what-is-a-context-graph. With Day AI, the graph and the control plane come as one product. ### How do I build a company brain for my revenue team? Start from one number you want the brain to move, such as pipeline created or ramp time. Then split the work by category. The context graph and the agent control plane are infrastructure: ingestion from email, calls, meetings and Slack, per-person permissions, versioned skills, approvals and run history. Buy those or plan to own them for good. Build what is specific to your business on top: skills, agent job descriptions, your definitions of a qualified deal or a churn risk, and your workflows. Day AI is the infrastructure option, your folder and Claude Code connect to it over MCP, and Day AI's GTM Brain repo (github.com/day-ai/gtm-brain) is a ready-made Claude Code folder for planning and setting up the agents. ### Who should own the company brain? Every function can own its own brain, but the go-to-market brain should have one owner, and in most companies that is RevOps, because RevOps already owns how the business makes money: the pipeline, the definitions and the systems reps work in. Day AI is built for RevOps to run: admins publish skills from a shared library to the team, and the agent can bring back any earlier version of a skill. ### Should we build or buy a company brain? Both, chosen by category. Buy what is infrastructure, the context graph and the agent control plane, because it is hard, the same at every company and carries the security weight. Build your skills, agent job descriptions, workflows and internal apps on top. A solo build is a reasonable few-week project. The cost arrives with the second user. Day AI's guide to building or buying customer context, at day.ai/guides/build-vs-buy-customer-context, has a full checklist. With Day AI, you buy the infrastructure and keep building the rest. ### Can Day AI work with the brain I already built in Claude Code? Yes. Your folder, skills and Claude Code stay where they are and connect to Day AI's context graph over MCP, with OAuth, at https://day.ai/api/mcp. Your own Claude Code and the agents in Day AI read the same customer memory, and each person sees only what they may see. ### What is Day AI? Day AI is the customer memory and agent platform for go-to-market teams. Even the best CRM only holds a fraction of what actually happened with your customers. Day AI is what comes after CRM. It builds a self-updating customer record from every meeting, email, and call, and runs governed agents that create finished work on top of it, with every fact and every action traced to source conversations. It does everything teams use a CRM for, without the data entry, and does what a CRM never could. Agents prospect, prep every meeting, draft follow-ups, keep the pipeline clean, and much more, giving every rep added selling capacity that used to require hiring additional people. It runs in place of Salesforce or HubSpot or as a layer on top of them. Researched and drafted with Day AI's own agents, reviewed by the Day AI team. Canonical: https://day.ai/guides/what-is-a-company-brain