Hola, Bot fanatic.

Another week (aka year in AI news) has gone down… and that’s why your boy is here to enlighten your inbox with the latest and greatest sauce 😤

It would appear the SpaceXAI team doesn’t sleep.

How do we know this?

Because they shipped more Grok Bot upgrades in the past 7 days. Let’s talk about it.

There are many more updates to go through, but methinks it’s time to transition over to the Tips & Tricks…

I’ll leave a few more nuggets here (Grok Bot improvements from one of the lead engineers on the team, and here (Morning Brief Bot template from Grace Clarke, who helps translate AI into english for us normies).

Ok… onwards!

Grok Bot calls its sidebar folders Sections. On desktop, right-click a Bot and choose Move to → New Section. Name the Section for a workstream your team already recognizes.

For your agency or SaaS team, that might mean Prospecting, Sales, CRM Management, and Account Management. Put the recent-conversation Bot, the company-research Bot, and a brief compiler in Prospecting. Keep the Bots that work with signed customers in Account Management. The Section makes the roster easier to navigate; you still have to give the compiler access to the researchers’ notes.

For a prospect call, ask the recent-conversation Bot what people have said about the company and its category in the last 30 days. Ask the deeper-research Bot what the company sells, who it says it serves, and what its public material can actually support.

Have the compiler turn those notes into a one-page call brief: verified facts, recent signals, five questions tied to sources, and anything the Bots couldn’t establish. Check the links, then use the gaps as questions on the call. The brief cannot tell you what the prospect privately needs.

After onboarding, run the same research roles again with the question your team needs to answer. Say you just signed a skincare brand. You could ask which ingredient concerns appear in recent public discussion and which ones the brand’s own site addresses. Add only the onboarding material the account owner has approved for this use. Ask the compiler to separate company facts, public customer language, contradictions, and questions for the account owner.

Here’s the handoff I’d give that compiler:

The account owner can review that document and decide whether it belongs in a creative brief for copy or ads. If the specialist files aren’t in a place the compiler can access, paste or attach the approved results yourself.

These are installable marketplace Bots, with setup steps on their pages. Their output depends on the sources and access you configure. X or Reddit coverage isn’t automatic; ask each Bot what it could actually reach.

Add last30days to Grok Bot for the recent-conversation job. Give it the customer, category, question, and date window. Ask for links and dates rather than a pile of unsourced themes.

Add Researchy to Grok Bot for the company fact sheet. Its assignment is different: establish what the company says about itself, then note what still needs checking.

Use either Bot on its own, or bring their sourced notes together for the compiler to review.

The sidebar Section keeps your Bots together. The Company Brain gives them something reliable to work from: what you sell, who owns each account, current decisions, customer language, useful examples, and links to the original files. Without that shared context, you end up explaining the business again in every prompt. Worse, one Bot may use an old offer while another uses the current one.

If it’s just you, start with one folder for your offers, active projects, decisions, and examples of work you like. You own the updates. With 2 to 10 people, put reviewed company facts and approved customer context in a shared place. Name the person responsible for each area, so a teammate knows whom to ask when a note looks wrong. At 11 to 50 people, give sales, product, and account teams their own owners and access rules. Keep a decision log and a regular review habit. Otherwise, an old meeting note can quietly become the answer every Bot repeats.

The useful test is whether someone can check a claim. If a Bot says a customer asked for something, the account owner should be able to open the dated note and see what was actually said.

I like the shape of Corey Haines’ makerskills Company Brain: raw source material, a reviewed wiki, and outputs made from it. It’s a great setup if you feel comfortable starting with a GitHub repo (which may sound complicated, but it’s where the software nerds save their code… kinda like Dropbox for code).

HQ for Work is another way to organize company context without asking every teammate to learn GitHub. Give each Bot the approved files it needs through the file tools you’ve set up. Putting Bots in one sidebar section does not give them access to the same files.

I'm so curious to hear how this goes today.

Give me some feedback on the newsie.

What's been helpful? What are you trying? Reply back.

My bots and I await your response.

Toodles ✌️

Jesse