HUBVERSE
Skip to content

Build Stack 001 of 111

My Bots Read Notion Before They Read Me

Build Stack 001 of 111. Why Notion stopped being a wiki for us and became the context layer our bots read before they build, write or ship.

By Azaan Feroz Sait (AFS)

On 3 November I asked my bots for one thing: connect Notion to every tool and subscription we use, so Notion becomes the hub of the whole stack. ๐Ÿš€

The same day, one of them ran a single search from inside Notion. It came back with results from Slack, Google Drive, Gmail and my calendar, all in one answer. It also dug up a renewal receipt in Gmail for a subscription that wasn't in our subscriptions database at all. Nobody opened four apps, and nobody had to remember anything. That was the moment Notion stopped feeling like the place I write things down and started feeling like the place my bots go to understand how we work.

So when Josh's X Article "Why I wouldn't count Notion out in the AI era" landed on my feed this week, I read it twice! His core idea is that Notion's real opportunity isn't building a better AI assistant, it's becoming the context layer that other agents depend on. I've been living a small version of that for months, so here's what it looks like from inside a build that runs on bots.

The brain is allowed to be a pile

I keep what we call a Mother Brain in Notion. It isn't one giant document. It's an index of eleven purpose databases, and honestly only three of them are live today: Daily Notes for the near field of a day, Living Intelligence for the people and ideas that keep coming back, and a 2nd Brain Master that we also call My Wiki.

Capture stays messy. Voice notes, links, half-baked ideas, a reel that made me think at midnight. Later, things get processed and flushed into the 2nd Brain. The bet is simple: a pile, if you keep looping it, can still compound.

Here's what I didn't expect. The pile matters more to my bots than it does to me. When I drop a link and say "make this a post", the bot that drafts it doesn't just read the link. Before it writes a single line, it reads my worldview and stance notes synced from the 2nd Brain, and the drafts I've already turned down. The draft is only ever as good as what it can find.

Agents don't care how pretty your dashboard is

Josh makes this point and it's the one I'd underline twice. A human opens Notion and enjoys a clean page. An agent opens Notion and asks three things: can I find the right information, do I understand how it connects to the task, and am I allowed to act on it?

That changed how we build pages. We have a Notion Master that describes itself in one line: the rules, registries and logs that make the rest of the workspace behave. Not a wiki, not a dump. Every master in our build stack carries an owner, a status and a usage protocol, because a bot can't tap someone on the shoulder and ask what a column means.

Our content runs the same way. Every post lives as a row in a content calendar. Bots strategise, draft, mock up and critique inside that row, and there's a Human Approved checkbox that stays unticked until I say yes. Nothing goes out without it. The row holds the context, the checkbox holds the judgment, and both live in the same place. Even the Hubverse website's intake form writes straight into a Notion database, so the first conversation with someone new lands exactly where the bots can already read it.

Context > Capability

The models get better every month. What makes them useful for us is whether they know how we actually work.

Where I'd push back a little

Josh is careful to say Notion doesn't win just because companies store their knowledge there, and I agree with him from experience. Documents drift. That receipt my bot found on day one is the proof: the subscriptions database said one thing and Gmail said another. The document was neat, and the truth was sitting in the inbox.

So for us Notion isn't the source of truth on its own. It's the place where truth from Slack, Gmail, Drive and the calendar gets pulled in, checked and written back. The loop is the product, not the page.

We also keep a way out. Earlier this month a new notes app started getting pitched as a Notion replacement, so one of my bots looked into it properly. Our verdict was Watch, not switch. Notion's MCP already lets every one of my bots read and write with no extra login, while the newcomer needed an install and a sign-in on every machine. But the real lesson was about portability. If your company's brain lives somewhere, you should be able to carry it out the door, and Notion's own export gives us that.

Why this is a Hubverse story

Before 2025, Hubverse was an agency, and its operations already lived in Notion. Back then Notion was a shared space for people to find things. Today most of its readers are bots, and I'm the one saying yes or no to what they make. Same tool, a completely different job.

That's what this series is about. Hubverse is where we write down how we build and how we go to market, out loud, one tool at a time. This is post one of 111 across the 11 tools in our build stack, and it had to be Notion, because every other tool in the stack ends up writing into it.

A huge shout out to Josh for putting words to something I've felt for a while. Read his full piece on X: https://x.com/joshcons0/status/2123100973069398243

So here's my question, and I'd love for you to pick a side ๐Ÿ‘‡

Who ends up owning the context layer for companies that run on agents: Notion, or the giants that already sit on your email and documents, like Google and Microsoft?

Tell me where you'd place your bet. Here's to building out loud ๐Ÿš€


Sparked by Josh (@joshcons0), "Why I wouldn't count Notion out in the AI era", X Article, 18 Nov 2026: https://x.com/joshcons0/status/2123100973069398243