Your company's second brain
Every company already has a brain — it's just scattered across calls, inboxes, and the memories of whoever happened to be in the room. Here's the case for giving it one place to live, and hands to act with.
A company's most valuable knowledge is not in its docs. It's in the forty minutes where three people argued about pricing and finally agreed on something — and then the call ended, and that agreement went home in three different heads.
Within a week, nobody can reconstruct it. Within a month, someone re-litigates the same decision from scratch. This is the tax every growing team pays and almost nobody measures: the cost of forgetting.
Recording was never the hard part
Transcription is a solved problem. You can get a near-perfect transcript of any meeting today for a few cents. And yet the transcript is where most tools stop — they hand you a wall of text, a bulleted summary, and the same follow-up work you had before, just better documented.
A record you have to read is not memory. Memory is what answers a question without you going looking for it.
What a second brain actually has to do
We think there are exactly three jobs, and skipping any one of them collapses the whole idea.
- Capture
- Join the meeting, get the words right, and know who said them. Table stakes — but the foundation everything else stands on.
- Understand
- Separate a decision from a suggestion, an owner from a participant, a commitment from a maybe. Connect today's call to the one three weeks ago that set it up.
- Act
- Turn the commitment into the ticket, the message, the doc, the CRM note. In the tool where the work already lives, without a human retyping it.
Most products do the first, gesture at the second, and leave the third to you. That third job is the whole point. It's also where the compounding starts: once an agent is the one filing the work, it knows what was filed, what shipped, and what quietly died — and that becomes memory too.
Recall and execution are the same product
Recall without execution is a search box. Execution without memory is a macro. The interesting thing only happens when you have both.
An agent that files a Jira ticket but can't tell you why is an automation. An agent that can find the moment the decision was made but can't do anything about it is a nicer search bar. Squirrel is being built as one system: the same understanding that answers "what did we decide about the pricing tiers?" is what creates the ticket the moment the decision lands.
Why now
Two things changed at once. Models got good enough to reason across long, messy, multi-speaker conversations instead of just summarizing them. And every tool your team uses — Slack, Jira, Trello, Asana, Monday, GitLab, HubSpot, Salesforce, Docs, Sheets — grew an API that an agent can drive.
The pieces are on the table. What's missing is the thing that sits in the middle, remembers everything, and is trusted enough to press the buttons.
Where we are
Squirrel is in active development. Capture, understanding, and the first connectors are working end to end; the rest of the ecosystem is landing connector by connector. We'd rather write about what we're building while we build it than after.
That's the company we're building: your company's second brain. It remembers everything your team decides — and then it goes and does something about it.
The short version
- Company knowledge isn't missing — it's unindexed and unowned.
- A second brain has to do three things: capture, understand, and act.
- Recall without execution is a search box. Execution without memory is a macro.
Give your company a second brain.
Squirrel captures every meeting, remembers every decision, and files the follow-up work for you.