Company Brain With Claude: Give Every Session the Right Brief

To build a company brain with Claude, give it a maintained team brief, links to approved sources, working rules, and the current state of each project. Keep that material in a shared record with a named owner, then ask Claude to read the relevant parts before starting work.

Tools like fenbs keep decisions and task progress outside a private conversation, so another teammate or assistant can pick up the same work. The useful result is a reliable starting point: what the company agreed, what remains uncertain, and who can authorize the next step.

How do you set up the first useful company brief?

1. Choose one active project. Write its goal, intended audience, current owner, and next deliverable in plain language.
2. List the sources that support the work. Identify the current document, who maintains it, and when it was checked.
3. Write approved instructions separately from ideas. Include who agreed to each rule and where it applies.
4. Record the current state: completed work, outstanding checks, open questions, and the next action.
5. Ask Claude to summarize the team brief before doing a small task. Correct any misunderstanding in the record, then try a fresh session.

For example, a small design studio might start with its website redesign. Its brief needs the approved audience, the chosen contact form, the design source, and the unresolved delivery test. It does not need every discussion the studio has ever had about websites.

Set a practical success test. A teammate who missed yesterday’s meeting should be able to explain the next action after reading the team brief. If they cannot, adding more documents usually makes the problem larger. Fix the missing decision or unclear status first.

Where should the material live in Claude?

Claude projects can hold uploaded knowledge and project instructions. Put stable reference material in knowledge and working directions in instructions; Anthropic’s project management guide↗ (opens in a new tab) explains both. Do not rely on the project name or description alone to communicate the team brief to Claude.

Choose one current home for each fact. A service description can remain in your approved handbook, while the task record explains which version the team used. If you copy a passage into Claude, include its source and review date so someone knows how to check it later.

If you are new to the product, start with what Claude is; the broader AI brain guide explains the record you are building around it. The aim is enough context for the task, with a clear route back to the evidence.

Which parts should teammates actually share?

A shared Claude project and a private chat have different boundaries. Where project sharing is available and enabled, members can receive view or edit access inside the organization; individual project chats remain private unless shared. Check Anthropic’s project visibility guide↗ (opens in a new tab) before inviting people.

Make the shared brief useful without requiring access to a colleague’s transcript. Save the approved outcome, its reason, the responsible person, and the next step. A private brainstorming session can stay private while its reviewed conclusion becomes part of the team’s record.

• Share the minimum source material needed for the project’s work.
• Give editing responsibility to people who maintain the team brief, rather than everybody who reads it.
• Keep confidential client work in an appropriately restricted location.
• Test access with a teammate’s own account before treating setup as complete.

For the wider structure of sources and access, see company brain architecture.

How do you keep suggestions from becoming company rules?

Label the difference explicitly. “Consider a shorter proposal” is an idea. “The owner approved a two-page proposal for this client” is a project decision. “A person must approve proposals before sending” is a continuing rule. Each leads to a different next action.

Ask Claude to identify the decision it is relying on and to leave unanswered questions open. If two sources disagree, the useful response is to name the conflict and ask the responsible person. A confident answer does not settle which source should govern the work.

In fenbs, people decide and assistants record their decisions; Decisions and rules are part of the shared team workflow. This gives the next session a reviewed answer instead of an instruction inferred from an old exchange.

How does Claude reach a current work record?

A connector gives Claude a supported route to an outside service. Anthropic’s connector guide↗ (opens in a new tab) explains how these connections retrieve information and take actions. Choose the connection for the actual source rather than assuming an uploaded copy will update itself.

For fenbs, use MCP, a standard way for an AI app to use an outside tool. Follow the Claude setup in Integrations, sign in through the browser, and approve the intended access. An account in Claude and an account in fenbs do not connect simply because both use the same email address.

Before a substantial task, ask Claude to state the current rule, the last saved progress, and what it plans to do. Afterward, check that the saved record distinguishes work completed from work tested. That small review is easier than discovering a mistaken handoff during the next client meeting.

How to do this with fenbs

1. Create a free account and try the setup on a personal kanban board; use a team kanban board when colleagues need shared access.
2. Add the active project and its real tasks. Write a short project description and link to the approved source material.
3. Record the decisions people have made and the continuing rules they approved. Leave unresolved choices open for a person.
4. Connect Claude using the integration guide, then ask it to read the project’s AI context before working and save progress before stopping.
5. Have a teammate start a new session, read the same record, and explain the next action. Correct the record wherever the handoff is unclear.

fenbs is free for one person, no credit card. It is not the right fit if you only need a document editor or storage for all company files; keep those materials in their proper tools and link the work to them.

What keeps the company brain useful after setup?

Make upkeep part of completing work. Replace an outdated next step, record a superseding decision, and say what was checked. Assign someone to review source links when the underlying policy or deliverable changes. A short current record is easier to trust than an impressive archive nobody owns.

Review the setup whenever the team changes assistants or a new member joins. Ask whether they can find the goal, the governing rule, and the next action without asking the previous person. The team brain hub covers related ways to keep shared AI work understandable as the team grows.