Stop Setting Up Grok Bot Until You Fix This

0:00it seems really every day I wake up there is a new AI tool out there, and every time I publish a video about my insights, I get the same comment I'm confused every week, new feature, where to begin. and the thing is, to be clear, it's not us putting you onto the ride. We are in the same boat.

0:16I may switch tools, but the system underneath stays. It's tool agnostic. and also just because we are on this ride, it doesn't mean that you need to follow along. That's the point. So in the next few minutes, I'll show you on one whiteboard how all this works. And I promise you, you will get a complete different perspectives on these things.

0:36You will see what changed for me and what never changed. For example, Google Calendar, Todoist, ClickUp, Gmail, these never changed yet. But you see what it would mean if I would change these things. You'll also see why Notion, ClickUp, and Obsidian are just front ends sitting on your data, And you'll see where GrokBot, but also Claude or chatGPT actually fits in.

0:56it doesn't replace my personal knowledge management system. it is just how the AI works and how it interacts with my data So let's dive into this. So to better explain to you this, we brought back the tool workflow creator inside the membership. So you guys can use this too if you want to lay out your w- uh, tool workflows, what I'm doing right now here, to better explain and get a better understanding

1:18what is going on in your technology. We have the ICOR framework where you lay out your tool stack, where you understand what tools do you use for what. You can even have a Venn diagram here. And there you see already on all the tools that I'm using, here is still my custom-made tool. For everybody who built your own tools, it doesn't mean we change something now

1:40and everything is now Grok, Grok bot. And this is something, the foundation behind everything is the ICOR methodology that never changes. It still applies, and you need to always compare it against these concepts and workflows in your life. How does this new tool change affect your life? And do I need to change anything at all? Just because we are being on this ride, it doesn't mean

2:05that you need to follow along. That, that's the point. Uh, you can look at it, we test the things for you, and it doesn't mean that you need to keep switching the moment we do something new, okay? But, um, here you see this is my self-built application, Anyck, and this replaced a lot of tools in the past, which was Heptabase and, uh, uh, e- essentially was just Heptabase in the end, and then Read- uh, Readwise, and

2:32then it was Obsidian after Heptabase when I had the local folder approach. And all this got reflected inside the ICOR framework. But we see here there's Google Calendar, there's Todoist, there's ClickUp, there's Gmail. This never changed. And once you get this understanding that there's a, just a part, a, um, a, a section or a part of your system changing, you will look at it differently and

2:55don't feel that everything changes now. And that's why it's important, uh, to realize this. And then we also talked in the past about backend and frontend Which means that we have the data that lives here, also in ClickUp or in Todoist. There's a database in the back end that holds all your data, and then on top of

3:17it, there is this interface that shows you and presents the data in a certain way. So if I'm going into Notion, it looks different than it looks in ClickUp, but it is very similar when it comes to the data structure in the behind the scenes. They just present it differently. It lets you interact differently with the data and so on. So using tools like GroqBot or, uh, even Claude Code or any other AI tools that

3:44you use, chatGPT, that lets you connect to other tools, this is what's happening. They are connecting to the back end of these tools. It's just reasing- reading the databases behind the scenes. It doesn't care about how ClickUp looks like, how Todoist looks like. It cares about the data behind the scenes to gather the things together for you to work with or what you ask for, or to up- uh, create a calendar event inside

4:15your Google calendar, things like that. That's why I wanted to bring back this g- workflow creator, because now it makes easier to explain this in more detail. So we have now GroqBot, and what did we have else before? It was Claude, Claude Code, and it is still there. That's the whole point. It's still there.

4:35But in the beginning, we only had Claude Code. And then we had folders created because there was the pivotal moment where it was suddenly possible to connect your AI to a local folder. And then we gave instructions in this local folder how this AI should behave, and rules and skills and all this. And now GroqBot replaced this combination when it comes down to how my AI works.

5:08It doesn't replace my knowledge base, my PKM, all this data. It is just how the AI works itself and how it interacts with my data. So this means for you, if you've been using folders and you used it, I don't know, ICOR for life, Scaffold, uh. And also we can bring in here Obsidian as the typical example

5:32when you want to look into an interface, because that's exactly it. Obsidian is just the interface to your back end, which is the folder here. Okay, so you can treat folders as your back end And Obsidian in this case would be the front end And now we used Claude Code and people say, "Well, Claude Code, it work," or Claude, "It works perfectly with Obsidian.

5:56I can interact with it. I can do whatever I want." No, you don't. You interact with the folders, and you just, you can hook into Obsidian to give it the right rules through Obsidian how the folder, which it's called a vault, is set up, and, uh, the specifics for this interface to show you

6:16this, what is inside a folder properly. But in the end, all you're manipulating is just files in a folder. So now if you keep this in mind, and I think now about my own tool, I have the same system, okay? I have my own tool. There is the front and back end, and I can bring this in twice. So we have a front end

6:38Back end. Okay? That's what I built to visualize my information that I have in here. So now what happens, I always were able to hook into the back end and manipulate my any, uh, information. But- I could now sit just in this terminal, and keep talking to AI and say, "Hey, I have this idea about something," or, "I want to create

7:03a new journal entry," and so on. And all AI does, it manipulates or updates or edits the database of any tool that you want. This is not happening at all in Claude Code. And even if you have memory switched on, you know, this is not your personal knowledge management. You have to have some sort of tools around this AI ecosystem. So many people start with GroqBot, or they start with even earlier, right, with chatGPT, and they start sharing their whole life in chatGPT,

7:37and they have several chats open. And then they consider that this is a PKM system, personal knowledge management system. But it's not, because even that you have a lot of things shared in there, there's no structure to it. It's just all over the place. And if you ask, um, your AI, it will find it, but it looks through all these things,

7:56and that's where it becomes inefficient. And eventually you want to access this data in a proper form too, maybe. And that's not possible if you keep everything inside these tools. That's why, again, you end up with a front end. So one last example, let's use Notion because it's a common tool. And here we have the same principle again. Whoever used Notion, they know it is based on databases, and you

8:20have cross-connected databases, but it is also a note-taking tool. You can very easily interact with it, and this is exactly what happens there again. We have the Notion, which is the front end that you open up to type and, uh, add informa- data into the database, and we have the back end of Notion,

8:40which are the tables that you don't see. You see it through this interface, okay? It's always served towards this. So now again, I can hook Claude Code into Notion. Many did this, but you hook it into the back end. You will never be in the front end. Even we could argue now, okay, computer use and you use your

8:59Chrome extension, whatever. That's not what I'm talking about. That's simulating you interacting with the interface. And as you know, it takes forever to do because it's the inefficient way. The efficient way to interact with this tool is go into the back end to talk to it. Okay, now we've been able to build all this in the past ourselves

9:21and say, "Hey, Claude, can you actually connect to Notion?" And it will build the connection for you. I- earlier times it was much more complex. You had to build the setting files yourself and so on. Now I just ask Claude, "Can you connect to Notion?" Or in Claude Desktop, I even have a connector. I click a button, I connect directly to Notion, and that's what's happening,

9:42and this happens through the MCP. or API, but most of the cases MCP. So now why GrokBot is, uh, shocked me over the weekend, to be honest, and I used it. I started using it last week, but then the more I used it was really, first of all, the ease of connection to other things.

10:01Yes, it's easy with Claude Code, but here I was just sitting in the car. I said, "Connect to the things," and it just connects directly via the MCPs and gives me a page where I need to confirm, and that's all it. So now I hope you better understand that there's a layer of this AI And

10:19this is now the thing that removes the friction of interacting with my tools. I need to open my tool. I need to go to the place where to find the information. I need to search it. And, uh, here I can now have this as my capture device and say, "Hey, keep this in mind. Update my, uh, AI tool. Create a task in Todoist, uh, because I need to work on this." Um, and/or, or, or ask about what are my tasks and all this,

10:49and this is all the same principles. So now I have a central hub and one single point of contact c- contact that I can go to, to talk to. And in my self-built version, or if I'm using AI inside Notion, or if I build something that works inside Obsidian, those are isolated AIs again that

11:09work in this ecosystem that I built. That's why I forced ANIC to be the all-in-one solution, but it will never be. And even if you're building it yourself, it will never be. And it ends usually when you realize, "Oh, I have a team actually I want to work with. How can I now get my team into my self-built tool?" And that's, again, where we see people misunderstand how it works, because I

11:32can actually connect to team tools, and then I can interact with it this way. Again, I have here backend of the team tool, whatever it may be. And once this clicks, then you understand what we are talking about and why it's so easy for us to say, "Okay, let's use GrokBot," or, "Now let's see, l- let's use chatGPT, connect it to all the tools and see if it is

11:54nat- more natural." Or Claude Code. Beware, the moment it becomes available in Europe, we might st- you know, we at least will test Claude Duet to see if this works. so that's the whole picture. Your data lives in the back end, the database, the folders. The tool is just a front end on top that presents it. once you get that, a new tool is just a part of your system

12:17changing, not everything, and it stops feeling like a threat. if you want to lay out your own tool stack like I did in this video, we brought back the tool workflow creator for our members inside myICOR. You can use it too. Link in the description. and to see how I moved my whole AI team into GroqBot, watch this one next. I catch you there