Your operational knowledge, in one place at last.
A rep walks out of a meeting. The contact change goes to the CRM, but the growth plans, the open questions, the support issue the customer is stewing on, that goes nowhere, and the next person to touch the account flies blind. The brain holds that operational knowledge in one place. Your workflows write to it as they run, and soon it keeps itself current automatically from your communications, so everyone who talks to a customer, person or agent, has the same picture. It draws on everything your team writes, across every channel, plus the meeting notes that reach your inbox. It's the second job this+that does, alongside automating the work.
Acme Corp
The operational picture of this account, built from email, Slack, and Teams. Structured fields stay in the CRM. This page holds the context that runs the relationship, current for whoever talks to them next.
What is going on
Evaluating the Scale plan, blocked on a security review. @Priya Raman owns the proposal. Open support issue on SSO from last week, still stewing.
Who knows what
The knowledge that runs your day lives nowhere
Your systems of record hold the structured stuff: customers in your CRM, finance in your books, clicks in your analytics. The brain holds the rest of what your company knows: the canonical knowledge like pricing, positioning, and the company vision, and the operational knowledge in between, what is going on with a customer, who knows what, the context buried in last week's threads. A wiki can hold the canonical half. The operational half lives nowhere today: it sits in people's heads and Slack history, and walks out the door when they go to lunch.
It is not a CRM, your systems of record stay exactly where they are. And it is more than a wiki: it holds the canonical knowledge a wiki would, your workflows write to it as they run, and soon it keeps the operational layer current automatically from your communications, so the next person or agent to touch an account starts with the full picture instead of flying blind.
More on the thesis in our essay on the missing middle of company knowledge, or see how the brain compares to a meeting knowledge engine like Otter.ai.
Company knowledge comes in three layers:
Workflows read the brain. Workflows write the brain.
Humans reading and writing a wiki is the baseline. What's different about the brain is that agents are equal-class participants in both directions. Read and write are the two structural moves, and on each, the agent half is the novel half.
Workflows that read the brain
An agent or workflow reads existing team knowledge to act. The agent's reply is grounded in what your team actually decided, not in what a base model guesses.
A sales agent backed by a price sheet
Pricing questions arrive over email. The agent answers using the canonical price sheet maintained in the team brain, schedules a follow-up call if the prospect is interested, and logs the interaction as a task that links back to the source thread. When pricing changes, you edit the brain page once. Every downstream answer updates.
Workflows that write the brain
An agent or workflow produces durable knowledge over time. Output that used to be a one-shot report becomes a compounding history you can search.
A competitive analysis agent that compounds
Each run produces a page in the brain. What the agent found, what was new since last time, what changed. The next run reads the previous one as context. Over weeks the brain accumulates a history of how competitors have moved, which positioning they've tried, what's worked.
Humans get a normal wiki too
Markdown editor with @-mentions for people, tasks, and other pages. Hierarchical page nesting. Page-level versioning and conflict detection when two people or two agents edit at once. Attachments. Search. The familiar wiki experience is the baseline, not the differentiator.
Private by default. Publishable in slices.
Every page in the brain is private by default at the team or personal level. Permissions aren't a separate layer bolted on top. They're the same layer that decides what's visible inside the company and what's visible outside.
Personal
Pages only you can read. Your notes, your drafts, your ongoing reasoning.
Team
Pages everyone on your this+that account can read and contribute to. Pricing, positioning, vision, playbooks, the durable thinking the team does.
Public
Pages you choose to make public: landing pages, FAQs, customer-facing microsites. The rest of the brain stays private.
Public pages, powered by your brain
Publishing isn't a separate feature. It's just choosing which pages to make public. Pick a set of pages and turn them into a customer-facing page: a landing page, a public FAQ, a microsite, or any combination. The published page reads from your live brain, so when a customer asks a question, the answer comes from what your team has actually written down. The rest of your brain stays private.
Public pages aren't just for reading. The same page can show your live calendar and let a visitor book a demo, so a launch page can answer a prospect's question and close a meeting without sending them anywhere else.
We can write into yours instead
Some teams have already settled on a different home for knowledge: a Notion workspace, a Confluence, a shared Git repo. Our agents can read from and write into those through MCP, the same way they read from and write into the brain.
The brain inside this+that is the default, with the lowest friction and the tightest integration with the rest of the product. But if your team has already settled on another home for knowledge, our agents can keep that home up to date instead.
NotionYour brain is not training data for anyone
Brain content is encrypted at rest with AWS-owned keys. No this+that employee can decrypt it. We never use Customer Data (including content from the brain) to train, fine-tune, or improve any machine learning model, ours or any third party's. The contractual commitment lives in our DPA and our no-training clause. Sub-processors that touch brain content are bound by the same restriction.
Build a brain your team and your agents both contribute to
Sign up and start writing pages today. Your first read-and-write workflows can land this week.
Get startedFree during beta · No credit card required