Second brain
The store every department reads from and writes back to. It starts empty, fills from the onboarding interview, and then grows on its own every time a department finishes a job.
Preview
Knowledge graphA demo business's second brain, not a client's.
Recent writes
Example- finance/invoicesNorthline pays on the 20th, not the 7th. Terms corrected.
- marketing/brandNever say “leverage”. Added to the vocabulary.
- finance/reconciliationStripe fees post a day late. Match on the day after.
- marketing/cold-outreachWorkplace fleet leads reply most on Tuesdays.
Nothing here was typed by hand. Each line is a department recording what it learned while doing something else.
How it behaves
- Pages, not rows
Everything it holds is a page with a title, a type and links to other pages: a client, a decision, a price, a process. Links are how a department gets from the job in front of it to the thing it needs to know.
- Written by the work
No one sits down to fill it in. A department writes back at the end of a run, in the words that were actually used, and the page is there the next time anything looks.
- Read before acting
A department reads the second brain before it drafts, prices or sends. That is the whole difference between AI on a generic prompt and AI running on your business.
- Corrections win
When something in it turns out to be wrong, the fix replaces it rather than sitting underneath it. A page that contradicts itself is worse than no page.
Why it starts empty
Most tools arrive full of somebody else's assumptions about how a business runs, and the first month is spent arguing with them. Yours arrives with none. The cost is that it knows nothing on day one. The return is that by the end of the first month it knows things about your business that no other tool can be told.
Set up
We seed it with you in the onboarding interview, connected to the Claude or ChatGPT your team already uses. After that, every department you add starts contributing on its first run.
Book a Claude training day