The Company Brain

What This Guide Is

The Company Brain is a complete implementation manual for building an internal knowledge assistant on Claude Projects: the knowledge audit that finds the 20% of documents answering 80% of questions, the rewrite pass with required owner comparison and approval, an instruction "constitution" designed to request citations and missing-answer reporting, without guaranteeing correctness, an illustrative afternoon build-block walkthrough after preparation and approval, with testing and upkeep separately resourced, and the rollout, adoption, and maintenance systems that keep it trustworthy after the novelty fades.

Use an already approved Projects setup for the pilot; additional procurement or engineering may be needed for broader requirements. Assign an owner and audit before uploading. This guide covers existing chat-style Projects only where that interface and its knowledge, instructions, and access controls are available in your account. Before using this workflow, check your account, plan, organization settings, and current interface against the applicable documentation; do not assume the redesigned cloud-thread Projects beta has the same features or permissions.

Context-control check (October 17, 2026): project/account memory and chat search can add context. For docs-only testing, start a new chat with Memory off before the first message, check the controls available to your account, and verify citation/refusal behavior. This is not a tested isolation guarantee.

What's Inside

The Foundation

• What a company brain replaces (Slack archaeology, the human search engine) — and what it never should (judgment calls, sensitive cases)
• Context and retrieval modes, their documented limits, and a 10–20-document pilot target for testing and maintenance — not a product cutoff
• The knowledge audit: harvest two weeks of real questions, map them to documents, pick the right pilot domain

The Build

• Documents Claude can actually use: heading rules, self-contained sections, tables for numbers, and the AI-assisted rewrite prompt, clarification markers, and owner verification before upload
• Capturing tribal knowledge: authorized capture, approved methods and redaction → draft SOP → owner verification and approval before upload
• The instruction constitution: mandatory citations, the scripted "I don't know," conflict surfacing, and the sensitive-topic bright line
• The illustrative pilot build block: HR onboarding pilot: prepare and approve documents, use an illustrative build block, red-team, then test solo or with approved shared-plan access

Running It

• 7 prompt patterns for ops & HR: policy Q&A, onboarding plans, SOPs from meeting transcripts, policy-change candidates checked against an owner inventory, audit-prep drafts, monthly gap reports
• Security & privacy: exclusions for files and all chat/reporting inputs, commercial training-default exceptions, private visibility, and viewer/editor access settings
• Rollout & adoption: the redirect month, the onboarding scavenger hunt, the champion model, and measuring interruptions avoided
• A 30-minute monthly gap report, plus policy-change, quarterly, and annual maintenance — and a troubleshooting table of possible causes and proposed tests for five common bad-answer patterns

Scaling

• Department blueprints to adapt and test: AskIT, AskFinance, AskSales, AskSupport, AskFacilities — each with its upload set and domain-specific trap
• Multi-project architecture and the signs you've outgrown Projects
• A whole-build cheat sheet and practical next steps

Who This Is For

This guide is for the person who IS currently the company brain — and would like to delegate the job to something that doesn't take PTO.