--- title: Use cases — what each team's AI answers from the brain description: What each team writes into its brain and what its AI then answers: sales, support, engineering, operations, legal, a new hire, and your systems. url: https://instibrain.ai/use-cases updated: 2026-11-03 site: https://instibrain.ai/llms.txt --- # What each team's AI answers from its pages. Your AI answers generically about your own company, because nobody wrote the company down. Here is what each team writes once, who reads it, and what its AI then answers. Request access → Connect Claude Code sales ## Your AI quotes the real floor. Today the floor and its one exception live in two founders' heads. As a page, the draft is right before the call. - `sales/pricing/floors.md` sealed space - `sales/deals/declined.md` sealed space - `team/playbook/objections.md` open space `sales/pricing/floors.md` sealed space asked · an example Can we go to $32k a year for Northwind? the AI, from the page Not without approval. The floor is $40k a year, and anything below it needs both founders to sign off. Who can read itClaude Code on the computers that hold the Sales key. No web AI opens it. support ## Your AI finds last time's fix. The same question comes back every week, and one person remembers the answer. As a page, every AI on the team has it. - `support/known-issues.md` open space - `support/runbooks/billing-sync.md` open space `support/known-issues.md` open space asked · an example A customer says invoices doubled after the sync ran. Seen it? the AI, from the page Yes. It is the retry storm in known issues: drain the queue, then run the billing sync once by hand. Who can read itEvery AI of the people the Support space is shared with, Claude on the phone included. engineering ## Your AI knows why the schema looks wrong. The reason sits on the data model's page, so nobody's AI suggests the same cleanup again. - `engineering/architecture/data-model.md` open space - `engineering/architecture/constraints.md` open space `engineering/architecture/data-model.md` open space asked · an example Can I drop the deleted_at column? Nothing reads it. the AI, from the page Keep it. The data model says why: deletes must reach every computer, so a row is marked, never removed. Who can read itClaude Code and Codex in the repo, and every AI its people give the Engineering space. operations ## Your AI gives the restore order at 3 a.m. The person on call and their AI read the same steps, in the same order, with nobody else awake. - `operations/runbooks/restore.md` open space - `operations/oncall/escalation.md` open space `operations/runbooks/restore.md` open space asked · an example The database is down. What first, and who do I wake? the AI, from the page Bring back the database, then api, then web. Still down after twenty minutes? Page the second name on the escalation list. Who can read itThe on-call person's AIs, Claude on the phone included. legal ## Your AI checks what you already promised. A clause signed two years ago decides today's answer. The contract sits in a sealed space that only Legal's computers open. - `legal/contracts/acme-msa.md` sealed space - `legal/contracts/obligations.md` sealed space `legal/contracts/acme-msa.md` sealed space asked · an example Acme asks to move their data to a US region. Can we? the AI, from the page Not under the current terms. Section 7 of the Acme agreement keeps their data in the EU. Who can read itClaude Code on the computers that hold the Legal key. Our server holds ciphertext. new hires ## A new hire's AI knows the company on day one. A first month goes on asking where things are. One installer links their computer, and their AI reads the team's pages from the first question. Their first day. - `new-hires/start-here.md` open space - `new-hires/style/naming.md` open space `new-hires/start-here.md` open space asked · an example First day here. How do we ship a change? the AI, from the page Open a branch, get one review, then merge. Start here says releases go out on Tuesdays, and names who approves them. Who can read itEvery AI of the people the New-hires space is shared with, the new hire's own included. your systems ## Your AI rotates a password without printing it. A page names each system, its owner, and where its key lives. Your vault holds the key, and a team script runs only at the version a manager approved. The systems it works with. - `platform/access/map.md` sealed space - `platform/access/never.md` sealed space `platform/access/map.md` sealed space asked · an example Rotate the staging database password and update whatever uses it. the AI, from the page Done. The credential at ops/staging-db is new, and api and worker restarted. Production is on the never list, untouched. Who can read itClaude Code on the computers that hold the Platform key. Our server holds ciphertext. every team ## See how much each person's AI works from the brain. Activity counts the sessions, prompts, and pages written this week, against the week before. the fit ## Where instibrain fits your team, and where it does not. It keeps the pages your team writes and corrects. It does not run your AI or search your file store. it fits when Your team uses AI every day, and it should know the company. - Claude Code or Codex already in use - Facts you would not paste into a vendor's chat - What people know could be written as pages - A model you expect to change look elsewhere when You want one vendor to search, answer, and run the AI. - Search across thousands of raw files - A vendor that runs your AI for you - A model bundled in ## Start with one team's space. Each person links a computer, and their AI reads the team's pages. Request access → Connect Claude Code --- instibrain is made by WebWork AI, Inc. Everyone uses the same models · the difference is what yours knows.