Your Second Brain Remembers Everything and Knows Nothing
You spent months building a second brain. Notion pages for every project. An Obsidian vault with hundreds of linked notes. Tags, backlinks, folders, a system.
Then you ask it a question. “Which of my clients haven’t ordered since January?” Silence. “Which customers are also newsletter subscribers?” Nothing. Your second brain has all the pieces of the answer scattered across pages, and no way to put them together.
That’s not a criticism of Notion or Obsidian. They were never built to answer questions. They were built to store notes. The problem is that “second brain” now describes two completely different things, and most people only know one of them.
What note tools actually are
Notion, Obsidian, Evernote, Logseq. These are filing systems. You write, you link, you tag, you organize. When you need something back, you search for it and read it yourself.
They’re genuinely good at this. If you’re drafting, journaling, building a team wiki, or connecting ideas while you think, a note tool is the right choice. I’m not going to pretend otherwise.
But look at what they store: documents. A note about a customer is a page of prose. The customer’s payment history is a bullet list someone typed three months ago, if anyone typed it at all. There are no records. No fields. No relationships the software understands. A backlink between two notes says “these are related” and nothing more. Related how? Since when? The link doesn’t know.
So when AI plugins arrived for these tools, they inherited the problem. The plugin embeds your notes, finds the chunks that look similar to your question, and summarizes them. Ask “how much did this client pay me last year” and it finds notes that mention the client and money. It doesn’t count anything. It can’t. There’s nothing to count. There’s only text about numbers.
The “just upload it to Claude” path
The other approach people try: skip the note tool, dump your files straight into Claude or ChatGPT. Upload the spreadsheets, upload the documents, ask questions.
For small inputs, this works. A page of text, a few hundred rows. I’ve written about where it breaks in one of my previous articles, so here’s the short version.
Every model has a context window, a hard limit on how much it holds at once. When your files exceed it, the tool doesn’t tell you. It chunks your material, guesses which chunks matter for your question, pulls in the top few, and skips the rest. You never see the selection. When the skipped part was the part that mattered, you get a confident answer built on half your data.
I hit this twice in ways that cost me real time.
First, contacts. Customers in one spreadsheet, leads in another, investors in a third, plus an old CRM export. Different columns, inconsistent formats, duplicates everywhere. Thousands of rows total. I asked AI to merge them. It truncated data, invented entries, and delivered a partial result while acting finished.
Second, my book. 211 pages that needed proofreading. Claude did solid work on the first 20 or 30 pages, then lost track of tone decisions from earlier chapters, hit its output limit, and every “continue” made it worse. Maybe 15% of the book got reviewed, inconsistently.
The AI had the skills for both jobs. The input was in a shape it couldn’t work with. That’s the pattern: uploading files gives AI your data as a pile of text, and a system you can’t see decides which parts to read.
What changes with Second Brain by Hexact
This is the gap we built our product around. It takes a different route: your data lives in a SQL database on your machine. Contacts, payments, subscribers, meetings, notes, scraped pages. Each one a row in a table, each field a column. Claude (or Codex) connects to it through MCP and does something neither a note tool nor a file upload allows: it writes a query and gets back every record that matches.
Ask which customers are two payments behind, and you get every customer who’s two payments behind. Not a summary of the ones the retrieval step decided were worth mentioning. All of them. No hidden ranking, no silent truncation. One approach skims and hopes. The other looks it up.
Both of my failed cases became routine. The contact mess got normalized into one schema, and deduplication became a matching rule on email and phone instead of a guess. The book became 211 rows of clean text, and I could run checks like “list every sentence longer than 35 words” across the whole thing with the same quality on page 211 as on page 1.
The same pattern covers technical documentation, and this one hits engineers and support teams daily. A 400-page equipment manual, an API reference, a compliance handbook, a folder of product spec PDFs. Upload one to a chat and ask "what are the torque specs for this model," and you're trusting the retrieval step to have picked the right chunk out of hundreds of pages. Sometimes it does. Sometimes it answers from the wrong model's section and sounds equally confident. Import the PDFs into Second Brain instead, up to 200+ documents at once through a single ZIP, and every page becomes a searchable record. Now "find every section that mentions this error code," "which procedures require certified personnel," or "compare the safety requirements across these three manuals" run against the full text, not a sample of it. And the answer cites records you can open and verify, instead of a paragraph you have to take on faith.
But exact retrieval is only half of it. The bigger half is joins.
Your data isn’t a pile of separate facts. It’s connected. The person who pays you on Stripe is the same person who reads your Substack newsletter and sat in that Google Calendar meeting last Tuesday. In Notion, those are three unrelated pages, if they exist at all. In a chat upload, they’re three files the model may or may not cross-reference. In a database, they’re linked records, and the questions that cross them are just SQL.
Three examples from my own use:
The newsletter question. For years I couldn’t answer whether people subscribe to my newsletter first and become customers later, or the other way around, and how long the gap is. No single tool has this. Substack knows opens. Stripe knows charges. Once both datasets sat in the same database, I asked the question and had the answer in about five seconds.
The calendar question. Google Calendar knows who I met with. Stripe knows who paid. Neither knows both. With calendar events imported and linked to contacts, I can ask “who did I meet with in the last six months who never became a customer” and get a follow-up list, or “how many meetings did it take before this deal closed” and see the actual count. Your calendar quietly holds your entire sales effort. Alone it’s a schedule. Joined with payments, it’s a conversion report.
The pre-call briefing. Before an important call, I ask Claude “what do I know about this person?” It pulls payment history, subscription status, newsletter engagement, past meetings, and my saved notes into one answer. The CRM alone would have shown me a name and a deal stage. The database shows me that their payment failed twice last month and they unsubscribed from the newsletter. I walk into the call prepared instead of guessing.
No note tool answers these. No file upload answers these reliably. They’re join questions, and joins need a database.
The part nobody else has: data that updates itself
Here’s the limitation shared by every option above, including a static database. The data is only as fresh as your last manual effort. Your Notion notes describe last quarter. Your uploaded CSV was accurate the day you exported it. A lead list is dead the day you download it.
This is where Hexomatic changes the equation. So Hexact (Second Brain) connects to Hexomatic directly, and scraping workflows feed the database automatically while the app runs. No exports, no file management, no pasting into chat.
Set the Google Maps Scraper on a monthly schedule per territory, and every run lands timestamped in your database. “Who’s new in this zip code since last month” becomes a query. So does “who crossed 100 reviews this quarter.” Chain the Page Content Extractor and Emails Scraper off the filtered list, and the unstructured parts, what businesses say about themselves on their own sites, become queryable too.
Same with competitor pricing. A scheduled workflow scrapes competitor pricing pages, the results flow in, and “which competitors raised prices this quarter” gets answered from actual timestamped pages, not from the model’s training data.
One scrape is a snapshot. Months of scheduled scrapes are a dataset that shows movement. That’s the compound effect: your internal records and live market data in one place, and Claude reasoning across both. Which customers in a region haven’t been contacted since a competitor changed pricing there. That question touches your CRM and the outside world at once, and it only works when both live in the same database.
No note tool does this. No chat upload does this. This is the combination.
Honest boundaries
Where the other tools win, they win clearly.
Use Obsidian or Notion when the work is writing and thinking. Drafts, wikis, freeform idea capture. Second Brain is not a writing environment and doesn’t try to be.
Upload files directly to Claude when the job is small and one-off. A single document to summarize, a few hundred rows to clean. Setting up a database for that is overkill.
Use Hexact (Second Brain) when your questions sound like database queries. Counting, filtering, comparing across time, joining sources. The moment your question has a “which,” a “how many,” or a “since when” in it, text storage stops being enough.
The second signal is repetition. Customers, leads, a knowledge base, a market you track. That data grows and changes every week. Uploading it to a chat means starting from zero each time. In a database, nothing resets. Every question runs against everything you accumulated before it.
And it works in both directions. Claude doesn’t just read your database, it writes to it. After a call, say “save this note about the client” and it lands on the contact’s record. Paste a meeting summary, it’s saved. Tell it “this person is now CEO of Acme Corp” and the record updates. No forms, no dropdowns. And writes happen only when you ask. Nothing changes on its own.
You don’t have to abandon your notes to get there. Second Brain imports from Notion, Obsidian, Evernote, Logseq, and OneNote, alongside Stripe, PayPal, Google Contacts, Google Calendar, Substack, email archives, and CSV exports from any CRM. 21 sources total. Your note tool becomes one input among many.
Where to start
Self-serve. Download Hexact Second Brain at brain.hexact.io, 7-day free trial, no card. Import one thing you already paste into AI by hand, a contacts export, your Stripe transactions, your Notion workspace. Connect Claude and ask a join question you’ve never been able to answer. That’s usually the moment the difference stops being theory.
Concierge. Already scraping with Hexomatic, or want to? Send us your brief and our team wires the full pipeline, workflows to database to first queries, through the Concierge Service.
Enterprise. Multiple businesses, multiple territories, a shared knowledge base your whole team queries? Book a call and we’ll architect it end to end.
