Build: company brains
Company brains
One place that knows what your business knows: email, files, the CRM, the chat history, the SOPs, the notes from the meeting. Ask it anything and get the answer with its source.
- Gmailthe email thread
- Google Drivethe proposal, v2
- HubSpotthe deal record
- Slackthe channel where it was agreed
- The install SOPthe steps, in a doc nobody opens
- Meeting noteswhere the promise was made
You asked
What did we promise on the March proposal?
Answer
A two-week install starting on the 14th, at the quoted price. Nothing about weekend work was promised.
Source: your email to the client, 3 March; the proposal PDF, v2; the install SOP, step four
This site runs on one
The AI in the bar is our own company brain.
Built from the same files as these pages, and from what we believe: who we are, how we work, the voice, the rules. The bar at the end is the real one. Type into it.
- recipes.tsthe eight automations
- agentTypes.tsthe thirteen agent roles
- prices.tsthe three prices
- catalog.tsevery file on the marketplace
- Who we aretwo builders, not brokers
- The thesisthe answer already exists, scattered
- How we workfour beats, demo day every Friday
- The workevery system we can show
- The voicecandid, direct, no hype
- The rulesnever guess, never fabricate
The brain in the bar, live
One document, generated from all of it. The pages come from the same files.
Watch it work
One ask, start to finish.
Pick a scenario. Watch the tools connect, the sources get read, and the result come back in the shape it really takes.
You, in the bar: What did we promise the Millers?
It reads
- Sales call, the Millers
- The thread that followed
- The Millers' record
Reads all three, keeps what they agree on, and points back.
What came back
A replacement, not a repair, by Thursday. The quote was sent the same afternoon.
- from the sales call
- from the email after it
- from the record
How a brain works
Everything a company knows, behind one bar.
On the left, what a whole brain holds. On the right, what it runs when all of it is connected. Every ask in plain words; every answer with its source.
Everything it holds
- Gmail
- Slack
- HubSpot
- QuickBooks
- Google Drive
- Google Calendar
- Notion
- Calendly
- Sales call, the Millersexternal
- Monday planninginternal
- Support call, the water heaterexternal
- Site walk, voice memointernal
- Vendor call, the supplierexternal
- Onboarding SOP
- Quote checklist
- Crew training, week one
- Safety procedures
- The pricing sheet
- Every email thread
- Every invoice, and its status
- Every job on the schedule
- Every contact, and its history
- Meeting notes, every week
- How Sam quotes a jobasked, filed
- Which crew takes whatasked, filed
- The customer who always pays lateasked, filed
- Why the Thursday route is Thursdayasked, filed
The input layer
One brain. Every tool, every document, every call, and what only people knew.
What it runs, from one line
- Answers, with the source
YouWhat did we promise the Millers?
A replacement, not a repair, by Thursday.
the sales call, and the email after it
- Briefs before every call
YouBrief me for the ten o'clock
The Hendersons. Last time: the boiler, under warranty.
Open: the quote they never answered.
- Writes the documentation
YouWrite the onboarding SOP for a new crew lead
Crew lead onboarding: day one, the quote checklist, safety in our words.
drafted from six calls and the safety procedures
- Keeps the tools in order
YouLog this call and book the follow-up
- HubSpotrecord updated
- Google Calendarfollow-up booked
- Slackthe crew told
- Handles the communication
YouChase every unpaid invoice, in my voice
Three reminders drafted, in your words.
Waiting for your yes.
- Files and organises
YouFile last week's photos and notes to their jobs
- Jobs
- The Millers
- photos, notes, the quote
- Catches the contradictions
YouDoes the quote checklist match how Sam quotes?
Two steps differ.
The checklist says measure first; the calls say photograph first.
- Watches, and flags
YouTell me when a job slips
A job with no crew by Wednesday.
An invoice past its due date.
A quote with no reply in a week.
- Plans the week
YouPlan Thursday's crews
Crew A: the Millers, morning. Crew B: the Hendersons.
Parts ordered for both.
- Trains the new hire
YouOnboard the new hire on how we work
A course from the SOPs and the calls: how we quote, how we schedule, how we talk to customers.
Want one of your own?
This is what we build.
Yours would know your tools, your files, your SOPs and what lives in people's heads, and answer with the source.
What a brain is made of
Four parts. Not a tool connector: the tools, the files, the SOPs, and what lives in people's heads. The last part is what nobody else builds.
01
The sources
Email, files, the CRM, the chat history, and the documents: the SOPs, the process nobody wrote down until now, the notes from the meeting where it was agreed. Connected read-only; nothing is copied out of where it lives.
02
The index
Every document, message and record, chunked and indexed with where it came from, so an answer can always point back.
03
The answer, with its source
Plain words, then the email, the file, the record or the SOP it came from. If it cannot cite, it says it does not know.
04
The contradictions
When two of your own documents disagree, it says so, with both. The case study's first catch was the system misstating its own size.
Every engagement leaves more of your company written down than it found. Small fixes become connected ones. What lived in a few people's heads becomes something the whole business can ask questions of, built from your own work and owned by you.
Everything else we build lives inside it.
Automations run inside it. Agents read from it. Software writes to it. The brain is the end state the other three build toward, and the reason we package them the way we do: not four products, one system, restructured around how your business actually runs.
A day of work, moving through it.
One question in plain language. Four systems read. One answer, one action taken, one record updated. This is what a brain does with what it knows, all day.
You ask
A question
Your systems
- HubSpot
- QuickBooks
- Gmail
- That spreadsheet
AI
Reads · Reasons
What comes back
- An answer
- An action taken
- A record updated
A question arrives, in plain language.
The flagship build
One shipped for a sales team; the bigger version is in build now.
AI Systems
Sales & Growth
The first file of a brain is free: the company brain starter, the CLAUDE.md and AGENTS.md pair every one of ours begins with.
Try it yourself
Now run it on your tools.
Pick the apps your business runs on, watch them connect, then ask the questions you ask every day. It runs on a fictional company's last two weeks, so nothing here is your data and every answer is safe to poke at.