VANDAMCompany Brain
Ask a question.Get your company’s answer.
A company knowledge assistant that answers everyday questions using the documents, emails and decisions you choose. Your team asks in plain language and can check the original sources.
$19,200 three weeks
Who can approve a customer discount?
- Pricing policy
- Account handbook
- Returns policy
- Operations guide
- Pricing approval
- Delivery cost review
- Onboarding checklist
- Supplier terms
- Board notes
Your account manager can approve a discount within the agreed account terms. Anything outside those terms goes to Finance before a quote is sent. Include the customer, proposed terms and reason in the approval request.
Account managers may approve terms within the current agreement. Exceptions require Finance approval before a quote is issued.
A quarter of the week goes to finding answers.
- 25%
- of their time, teams say, goes to searching for answers.
Atlassian survey of 12,000 knowledge workers, 2025. - 62%
- struggle with too much time spent searching for information in their workday.
Microsoft survey of 31,000 workers, 2023. - 95%
- of business analytics questions at
Anthropic are now handled by 
Claude, its data team reports, June 2026.
memory is half the equation. a company brain needs reliable enforcement of the decisions it has made.
So no, just dumping all your documents in Claude isn’t a scalable long-term solution.
The answer exists.
Finding it takes the time.
A new colleague asks who owns an account. A manager needs to know why a price changed. Someone searches for the current returns policy. The answer may be spread across documents, inboxes and the person who remembers.
Company Brain gives your team one place to ask. It brings together the material you choose, answers in everyday language and points to the records behind the answer. That helps people check the detail and understand the context.
The brain is also where the next systems start. Agent Onboarding, Account Brains, Judgment Vault and Invoice to ERP all build on it.
What a company brain looks like.
A company brain is a set of linked pages, one for every person, department, customer, product, site, decision and policy, each citing the email, document or record it came from. Our three public examples run to about a thousand pages each, and every page says whether it came from you, from public sources or from our own inference.
Your team reads it in a home page with the company at a glance, an explore view with the graph, a people view and a content view. It adds to it from a writing desk: type a decision in plain words and every person, policy and customer you name links to its page. An ask button answers with the pages behind the answer.
Three example brains, built from public sources onlyDecisionRuleWhat happenedHow I thinkBrain dump
Ask
The parts every brain has.
The content is yours. The structure is the same in every company we build for, which is why the build takes weeks and not months.
The org chart as spine
Departments, roles and people come first; every other page hangs off them.
Linked pages
People, customers, products, sites and decisions, each linked to the others and to its sources.
How you work
Your offer, customers, tone of voice and playbooks, written from your own material.
Rulings
Every correction becomes a written ruling with an owner, so the brain is wrong only once.
Authority pages
Contracts and policies quoted word for word, never summarized.
A numbers boundary
Live figures stay in the ERP or CRM that owns them; the brain links to them with a date.
Access by role
Roles and lanes compiled from the org chart, so each person and agent loads its own slice.
Labels and dates
Every page shows its source and a review date, and the build fails when a page goes stale.
How we build it, with a check at every step.
Six steps. Each one ends with something you approve before the next starts.
Scope and your questions
We agree what goes in, what stays out and the budget, and collect 20 to 30 real questions from at least three roles. Those questions are the test at the end.
Test questions - Who can approve a customer discount?Sales lead
- How do we handle a damaged return?Support
- Why did we change Northwind’s pricing?Finance
- Which supplier covers the Ghent site?Operations
- 24 more questions from 5 roles
Gather and sort
Documents, mailboxes, wikis and tickets are stored as they are and sorted before anything is compiled, so nobody pays to process the wrong material.
Sources sorted Build the org spine
We draft departments, roles and people. You check the org chart before anything is built on top of it.
Org spine, draft 2 Atlas & Co.
- SalesAccount teamPricing desk
- OperationsGhent siteLogistics
- FinancePayablesControlling
Waiting for your check
Compile the pages
Pages and links are written from your material, and every gap comes back to you as a question. Automated checks must pass before we move on.
Compile checks - Every page cites a source1,042 pages
- No broken links0 found
- Pages without an owner3 sent to you
- Stale review dates0 found
Wire systems and access
Numbers stay in the systems that own them, each department gets its slice, and anything that sends or spends starts switched off.
Access by department - Sales reads Sales + Productsread
- Finance figures stay in the ERPlinked
- Send emailoff until approved
- Spend moneyoff until approved
Pass your questions, then hand over
Every question from step one is answered with a citation or recorded as not covered. Your team is trained to add material and keep it current.
Ask Atlas Who can approve a customer discount above 10%?
The pricing desk lead, up to 15%. Above that, the head of sales signs off in writing.
- Pricing policy, v4
- Sales handbook, p. 12
Handed over.
Still looked after.
You own the code and every page from day one. Most teams still want someone to run it, so after handover we can stay on for a monthly fee.
Hosting
We run the brain, its connections to your AI tools and the access rules, on your infrastructure or ours.
Cleanup
A monthly check flags stale pages and broken links, and every correction is swept into a ruling.
Co-building
New sources, departments and questions are added with your team, a few each month.
Check-ins
A monthly session on what people asked and what it missed. When someone leaves, their knowledge is captured while they can still explain it.
$1,600/moafter handover · monthly
Ask about monthly careWhat you
receive.
Cited knowledge base
Every page links back to its source documents.
Connected tools
Answers through your selected AI tools, subject to your access rules.
Update system
The code, documentation and training to maintain it.
Where the brain leads.
The next systems build on it.
Source Cleanup
Comes before, when the sources disagree: one clean version for the brain to read.
$12,800
Agent Onboarding
Every new agent loads its own slice of the brain, by role, on day one.
$9,600 + $1,600/mo
Judgment Vault
Your experts’ decisions become rulings in the brain, next to the policies they apply.
$16,000
Account Brains
Account pages that link to your own people, offer and past decisions.
$11,200 + $1,600/mo
Invoice to ERP
Checks every invoice against the agreements and price lists kept in the brain.
$24,000
Before you ask.
Does every company need a graph?
No. If the real question is what you decided and how you do things, a handful of well-kept documents can be enough, and we check that before we scope anything.
Can everyone see every document?
Not by design. In a shared folder, roles tell people and agents what is theirs but do not lock anything, so sensitive material stays out; when it has to be in, we deploy with individual logins.
Can it be wrong?
Yes. Every answer cites its pages so a person can check, automated checks catch stale and contradictory pages, and every error we find becomes a ruling so it happens only once.
Does this replace our existing tools?
No. The brain connects to the AI tools you choose. We prefer Claude and also work with other models; your source systems stay where they are.