Managing multiple Grok Bot teams

To understand how teams should be using Grok Bot, I gave myself a challenge: build and launch a game as the sole full-stack PM managing five teams of Grok Bots.

The result is Rank’em: a mobile game live on iOS and Android where different teams of Grok Bots own parts of the product, tech stack, and operations.

So I replicated that. Each project gets a Grok Bot channel and an entry in a Notion database. Note that this is an experimental pattern I'm still trying out.

The setup

I set up five distinct teams of bots:

• Growth: Writes scripts to pull data from platforms and provide insights to the team.
• Engineering: Maintains code and handles app store submissions.
• Creative: Generates concepts and produces video ad assets.
• Ad Ops: Sets up campaigns and manages budgets on Google and TikTok.
• Game Design: Develops questions and tunes gameplay based on retention data.

Before setting them loose, I gave them three core operating rules:

全屏预览

全屏预览

Give each team its own machine

To make this work, each team gets its own machine configured with the tools it needs.

Engineering has a full dev environment with Node, Xcode, and Android Studio, plus access to app store credentials. Creative has video tools and file storage. Ad Ops has access to the ad APIs.

全屏预览

How I use it

The bots talk to each other

Here's an example of what now runs more autonomously as routines, but started as me asking my bots to do a little work as I went to bed.

You may notice that I asked it to do something, and on this particular night the bot realized that my request should be a routine and went ahead and added that to its own remit so I never had to ask again.

全屏预览

What was the ROI?

ROI is really the name of the game, and I plan to talk about this in more detail as I do the same work on revenue generation in the app. But two wins trace directly to the bots, resulting in a 15x improvement in cost per install and a 4x improvement in D7 retention.