Ask anythingThe answer comes from the company wiki.ReadingThe wiki page and the calls it came fromWritingCiting as it goesAnsweredFrom 3 of 4 sources. 1 is hidden because you do not have access.
A question is answered once, with its source, and never asked of the same person again.
What changes
Without it
With it
Asking
Ask the one person who remembers.
Ask the brain and get the cited answer.
Agents
Each agent starts with a pile of files.
Every agent reads the same company pages.
Decisions
The reason lives in a call nobody wrote up.
Each decision has a page with its source.
How it works
What we build
What changes for your teams. We pick the tools to fit the systems you already run.
Sources checked against your access
1Billing: how and whyWiki, compiled 3 NovPage
2Pricing call, 12 MayCalls, 41 minCall
3Seat limit for monthly plansChat, #revenue-opsThread
4Board pack, Q2 pricingYou do not have access
Drive
Ask anythingThe answer comes from the company wiki.ReadingThe wiki page and the calls it came fromWritingCiting as it goesAnsweredFrom 3 of 4 sources. 1 is hidden because you do not have access.
Ask nextWho approves a monthly exception?Did churn at renewal drop after May?
Sources checked against your access
1Billing: how and whyWiki, compiled 3 NovPage
2Pricing call, 12 MayCalls, 41 minCall
3Seat limit for monthly plansChat, #revenue-opsThread
4Board pack, Q2 pricingYou do not have access
Drive
Ask anythingThe answer comes from the company wiki.ReadingThe wiki page and the calls it came fromWritingCiting as it goesAnsweredFrom 3 of 4 sources. 1 is hidden because you do not have access.
An assistant that answers internal questions from company docs takes the repeat questions off the people who used to answer them.
Over 70,000 questions answered, and about 13,000 engineering hours saved by Uber’s own estimate.
What you keep
Everything runs in your cloud, and stays yours
You own the config, the tests and the runbooks, so you can swap any part later.
The company brain running in your cloud, with each source’s access kept.
Ask anythingThe answer comes from the company wiki.ReadingThe wiki page and the calls it came fromWritingCiting as it goesAnsweredFrom 3 of 4 sources. 1 is hidden because you do not have access.
Ask nextWho approves a monthly exception?Did churn at renewal drop after May?
The first sources connected and the first wiki pages compiled.
Sources checked against your access
1Billing: how and whyWiki, compiled 3 NovPage
2Pricing call, 12 MayCalls, 41 minCall
3Seat limit for monthly plansChat, #revenue-opsThread
4Board pack, Q2 pricingYou do not have access
Drive
One connection your agents use to ask it.
An answer quality report and a runbook your team owns.
Typical building blocks: Raw sources kept per team as plain files, a wiki compiled from them by a model with a citation on every claim and kept in git, Postgres with pgvector for search, and one Model Context Protocol server so agents and people ask the same source.
Alternatives: Glean when buying beats building and your sources are all supported; Guru or Notion AI when the knowledge already lives in one tool. We build when answers must cite calls and decisions, and agents must ask it too.
How the weeks run
Live in about 6 weeks
The work happens in your cloud, with the people who will own it.
Weeks 1 to 2Connect the first sources and list the questions people ask most.
Weeks 3 to 4Compile the first wiki pages and tune answers against those questions.
Weeks 5 to 6Open it to the first teams and their agents, and hand over the runbook.
After thatRunning on real traffic
One place people and agents ask what the company knows.
Before we start
Admin access to each source and to one cloud account.
A named owner for the brain, and one for each source.
About 3 hours a week from the brain owner, and an hour from each source owner.
Fit
Is this the right first build?
It fits when
The same questions reach the same people.
Agents start every task knowing nothing.
A team on your side will own it after we leave.
It does not fit when
You want a hosted tool picked and resold to you.
You want a strategy deck in place of working software.
Nobody on your side can own it after we leave.
What’s included and what isn’t
Included
Up to 4 sources connected, such as docs, tickets, call notes and chat.
The access rules of every connected source kept.
Up to 2 teams and their agents using it at handover.
A test set of up to 100 real questions.
Not included
Sources with no API or export.
Cleaning up or rewriting your documents.
More sources, which your team adds after the handover with the runbook.
Fixed quoteOne price, agreed before work starts
About 6 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.
If the work takes longer than we planned, we absorb the cost.
You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
We start three new projects a quarter, so your start date depends on when you book.
We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often Postgres with pgvector for search and a wiki kept in git; Glean when buying beats building.
How is this different from enterprise search?
Search finds documents. The brain also writes short cited pages about your decisions, people and products, so one answer carries what ten documents would, and agents can ask it.
Can someone see what they should not?
No. Each source keeps its access rules, and an answer uses only what the person or agent asking may open.
Where does our data go?
It stays in your cloud. The sources, the wiki and the index run in your account.
How long does it take?
About 6 weeks for the first sources and the first teams. More sources are added after the handover, using the runbook.
Company brain, running in your cloud in about 6 weeks.
One place people and agents ask what the company knows. You own the config, the tests and the runbooks.
Ask anythingThe answer comes from the company wiki.ReadingThe wiki page and the calls it came fromWritingCiting as it goesAnsweredFrom 3 of 4 sources. 1 is hidden because you do not have access.