Remember how OSF saved his company REKT ~$400k in payroll two days ago? Well, he just casually dropped the entire playbook for turning Claude into the most knowledgeable employee at your company.
No fluff. No "it depends." Just a raw, step-by-step breakdown of how he built an 80+ page AI knowledge base — what he calls "the Brain" — that now runs operations across his entire organization.
And honestly? This is the kind of alpha most people sleep on because it doesn't have a token ticker.
Let's break it down.
The Problem Everyone Has (But Nobody Talks About)
You open Claude. You type "write me a marketing email." You get back something that sounds like it was written by a LinkedIn ghost.
You try a better prompt. Still mid. You give up and write it yourself.
Here's the thing — that's not a prompting problem. It's a context problem. Claude knows nothing about your brand, your products, your customers, or your internal processes. It's working completely blind.
Fortune 500 companies solve this with internal knowledge systems that cost millions and take years to deploy. Entire departments manage them.
OSF built his version in one afternoon for about $20.
The Core Concept: Building "The Brain"
The Brain is a structured Notion database that Claude can search any time it needs context about your business. OSF's version has 80+ pages across 13 categories — and it grows automatically every single day.
Once Claude has access to this, it stops being a chatbot and starts being an operator.
Here's what you need before you start:
- A Notion account (free tier works)
- Claude Pro or Team ($20/month)
- One afternoon of focused time
- A folder of your existing company docs — pitch decks, brand guidelines, product info, team details, whatever you've got
That's it. That's the barrier to entry.
Step 1: Connect Notion to Claude FIRST
Most people start by manually building a Notion database, filling it out, then connecting it to Claude. That's backwards.
If you connect Notion first, Claude builds the brain for you.
Depending on your setup:
- Claude Pro/Team on the web: Go to settings, find integrations/MCP settings, and connect your Notion workspace.
- Claude Desktop (Cowork): Notion connects as an MCP integration with full read/write access.
- Claude Code (technical route): Set up the Notion MCP server for direct database access.
Test it with a simple prompt: "Can you access my Notion workspace? List some of my recent pages so I can confirm you're connected."
If Claude can see your pages, you're live. Move on.
Step 2: Let Claude Build the Brain
This is where it gets beautiful. You don't write 80 pages from scratch. You don't manually organize anything. You dump all your existing company documents into a folder, upload them to Claude, and let it do the work.
Pitch decks, brand guidelines, product specs, corporate filings, org charts, investor Q&A docs, process docs — all of it. Doesn't need to be clean. Doesn't need to be organized. Just dump and go.
Claude reads through everything, figures out the right categories for your specific business, creates a structured Notion database, and populates it with clean, organized pages.
For reference, here are the 13 categories Claude created for OSF's company:
1. Company Details — corporate structure, revenue targets, competitive positioning, funding history
2. Brand Guidelines — tone of voice, visual identity, colours, messaging
3. Product Catalog — products, ingredients, SKUs
4. Key Contacts — team, roles, key partners, advisors
5. Processes — internal workflows, onboarding, approvals, shipping
6. Standard Q&A — investor FAQs, customer support, pitch talking points
7. Compliance — filing deadlines, regulatory requirements, tax obligations
8. File Locations — where important docs live across Google Drive, Dropbox, etc.
9. Meeting Notes — auto-synced from transcription tools
10. Slack Digests — auto-generated nightly summaries
11. Email Summaries — auto-generated from Gmail triage
12. Tasks — auto-captured from Slack
13. And room to grow
Yours will look different. That's the entire point.
The prompt OSF used (adapt for your company name):
> "I've uploaded all my key company documents. I want you to read through everything, then create a structured company knowledge base in my connected Notion workspace. Call it '[YOUR COMPANY] Brain.' Create a single database with a 'Category' select property. Read through all the documents, decide on the best categories for my business, create those categories, then populate the database with clean, organized pages. Each page should belong to one category. Don't lose any important information. Use clear headers and structure within each page."
Go make a coffee. Come back to a populated brain.
Step 3: Put the Brain in Slack
A brain only you can query is useful. A brain that your entire team can query is a force multiplier.
OSF built a Slack bot called "Kitt" that anyone on the team can @ with a question. It searches the brain and responds with sourced answers. Before Kitt, every question landed on OSF's desk. Now the bot handles 90% of them.
Three ways to build this:
Option A — Always-on Mac Mini or similar: Run a Python script locally that monitors Slack for mentions, searches Notion for relevant pages, sends the question + context to Claude, and posts the answer back in Slack.
Option B — Cloud function: Same logic, but running on AWS Lambda, Google Cloud Functions, or Railway. Costs almost nothing for a small team.
Option C — No-code: Use Make.com or Zapier. Trigger on Slack message → search Notion → send to Claude API → post response. Less flexible, but gets you 70% of the way with zero code.
Ask Claude to walk you through whichever option fits your setup. It'll give you the exact Slack app configuration, Notion API setup, and code or automation flow.
Step 4: Make It Self-Sustaining
A static knowledge base goes stale. People stop trusting it. It becomes digital furniture.
The unlock is automation that feeds new information into the brain every day without anyone having to touch it.
What OSF automated:
- Nightly Slack Digests: Claude scans every channel and writes a summary of key decisions, action items, and discussions into the brain. Nothing gets lost in the scroll.
- Meeting Notes: Transcription tools (Fireflies, Otter, etc.) post summaries to Slack. Claude picks them up and adds them to the brain.
- Email Summaries: An email triage agent scans Gmail for important threads — filing deadlines, vendor negotiations, legal updates — and creates summary pages.
- Task Capture: When someone posts a task request in Slack, Claude picks it up and adds it to the brain's task board.
After two weeks of this running, Claude knows things about your company that half your team has already forgotten.
The Security Layer (Don't Skip This)
This part matters. A lot.
What's safe to include:
- Brand guidelines and tone of voice
- Product catalog and public pricing
- Team names, roles, work contact info
- Processes and workflows
- Standard Q&A and FAQ content
- Meeting summaries (decisions and action items — not sensitive verbatim transcripts)
- General company structure
What should NEVER go in the brain:
- Bank account numbers, card details, financial credentials
- Customer personal data (emails, addresses, payment info)
- Passwords, API keys, secret tokens
- Employee personal info (salaries, home addresses, SSNs, health info)
- Confidential legal communications
- Trade secrets or proprietary formulas
- Board meeting minutes with sensitive strategic decisions
- Investor term sheets or cap table details with specific numbers
For grey areas, use summaries instead of raw data. Don't put your full financial model in — put a summary like "Q1 revenue was above target, Q2 projection is X% growth." Claude gets the context without the raw numbers.
Create a "sensitivity" property in your Notion database. Tag pages as public, internal, or restricted. Only give Claude access to public and internal. Restricted stays out.
Keep credentials in a proper secrets manager. Never in Notion. Audit monthly — it takes 10 minutes.
The mental model: think of the brain as a company handbook you'd give a new hire on day one. You'd give them brand guidelines, product info, team structure, and processes. You would NOT give them the company bank login or everyone's salary. Same rules.
Why This Matters More Than You Think
Once the brain is running and compounding daily, Claude becomes the single most knowledgeable entity in your organization. Unlike a human employee, it never leaves, never forgets, and is available 24/7.
The gap between companies that build a brain and companies that don't is going to be massive. And the barrier to entry is one afternoon and $20.
This is the kind of infrastructure play that looks boring on the surface but changes everything underneath. If you're running a project — crypto or otherwise — and you're still prompting Claude from scratch every time, you're leaving an absurd amount of leverage on the table.
Go build the brain. Everything else gets easier after that.
This breakdown is based on OSF's original thread on X. Full credit to him for sharing the entire playbook publicly.
