Skip to main content

The Company Brain

A persistent store of how a specific company works, which agents read on every run and write back to as they learn.

Hand-drawn ink-line illustration on terracotta: a large open head profile drawn in one continuous line, with a loopy hand placing small cream blocks inside it.

What it is​

A company brain is organizational knowledge made machine-usable: the procedures, standards, vocabulary, and accumulated judgment of one specific company, held somewhere agents can read it at the start of every run and improve it at the end. It is what turns a generic model into something that works here, at this firm, the way this firm works.

The term is not this wiki's coinage. YC's Summer 2026 Requests for Startups names "Company Brain" as a category, framed as "a living map of how a company works," and three companies in that batch (Rational, Kebra, and Levocred) use the exact phrase in their own launch descriptions. Rational, for one, describes agents that "onboard themselves to the firm, build a company brain." The demand side of this pattern is explicit.

The supply side, in the published corpus​

The customer stories show what the pattern looks like shipped, usually as skills plus persistent memory:

  • Brainlabs turned its agency's know-how into "A library of roughly 400 skills authored by employees in four weeks," including an SEO audit skill its CTO describes as "one skill, refined across thousands of iterations from our SEO team, that captures the full universe of what to look for and what good looks like." (source)
  • YMCA South Australia built "20+ custom skills" that its story says were "built to encode organizational knowledge, brand standards, and operational procedures" across 65 locations. (source)
  • Notion closes the write-back loop with a "Self-improving skills database" that is "maintained by Claude after every completed task," so each run's lessons are available to the next. (source)
  • Rakuten's specialist Managed Agents run with "persistent compute and memory" beside employees across engineering, product, sales, marketing, and finance. (source)

The mechanics underneath​

On the Claude platform the pattern decomposes into pieces that already exist: Agent Skills carry the procedures (Anthropic's Agent Skills post, October 2025, is the canonical description), Memory Stores carry the accumulating state, and a stable versioned agent carries the configuration. The distinctive engineering problem is curation: a brain that only ever appends becomes noise, so the write-back path needs the same review discipline as code. Notion's thumbs-up-and-down feedback loop on its skills database is one published answer.

Why it compounds​

A company brain is the rare agent asset that appreciates. Models improve and harnesses depreciate, but a well-curated store of how-we-work transfers to every better model that arrives, and every run that writes back makes the next run start further ahead. That is also the moat argument: two competitors can buy the same model, but not the same brain.

Further Reading​