# The 30-Day Grok Bot Roadmap Four weeks, first bot to full team. Each week is one evening of setup and then the system runs. **The rule that keeps you out of trouble:** start with two or three bots. Spinning up twelve on day one is how you burn a week's usage allowance in an afternoon. --- ## Week 1 — Builds one and two **Goal:** something useful runs every morning without you. | Day | Do this | You're done when | |---|---|---| | 1 | Install the desktop app + the iPhone app. Sign in. Decline the data-retention checkbox. | Both apps open to the same sidebar | | 2 | Build the **chief of staff** (`5-bot-role-prompts.md` #1). Connect Gmail and Calendar. | It renamed itself and wrote its own description | | 3 | Give it the 7am morning brief routine. | The routine shows in its details panel with a schedule | | 4 | Let it run. Read the brief. Tell it what was wrong with it. | The next morning's brief is visibly better | | 5 | Build the **inbox-to-board bot** (#2). Connect your existing board. | Real tasks appear on your board before you open your laptop | | 6–7 | Leave it alone. Note what it gets wrong. | You have a short list of corrections | **Checkpoint:** you wake up to a plan and a populated board. Morning planning and inbox triage are off your plate. --- ## Week 2 — Builds three and four **Goal:** two bots that talk to each other. | Day | Do this | You're done when | |---|---|---| | 8 | Add the **Firecrawl** plugin. | It appears under Yours in Plugins | | 9 | Build the **research bot** (#3) with the daily 8am competitor scan. | Five ideas land on your board overnight | | 10 | Build the **content bot**. Point it at your channel or site. | Its pitches reference things that actually worked for you | | 11 | Open a **group chat** with research + content. Give them one task that needs both. | You can read them @-mentioning each other in the thread | | 12 | Upload one example invoice. Build the **invoice bot** (#4). | It matches your invoice style | | 13 | Put the invoice bot and the inbox bot in a group chat. | The invoice bot asks the inbox bot for invoice-related mail *on its own* | | 14 | Review the week. Delete anything that didn't earn its place. | Fewer bots than you started the day with, or the same | **Checkpoint:** bots are handing work to each other and billing runs itself up to the send button. --- ## Week 3 — Build five, plus your own skills **Goal:** teach it the things only you know how to do. | Day | Do this | You're done when | |---|---|---| | 15 | Connect your meeting notes tool. Build the **meeting-to-action bot** (#5). | Today's meeting produced assigned tasks by dinner | | 16 | Ask a bot: *"turn the process we just used into a skill."* | It appears when you type `/` | | 17 | Install the three starter skills from `skills-pack/`. | All three run from `/` on any bot | | 18 | Pick a tool your business runs on that has **no API**. Open the bot's computer, hit **teach a task**, and drive the process once. | It replays the process on its own | | 19 | Teach a second one — the fiddly weekly thing you always do manually. | Two taught skills, both repeatable | | 20–21 | Let everything run. Read the run histories. | You can name which routine produced which output | **Checkpoint:** the system now does at least one thing no off-the-shelf automation could, because you showed it your screen. --- ## Week 4 — Triggers, group chats, and the wider system **Goal:** stop checking things. Get told things. | Day | Do this | You're done when | |---|---|---| | 22 | Add the **Zapier MCP** — type `/`, pick Zapier setup, send. | It configures itself and you can name apps to link | | 23 | Set up your first **trigger** (Slack, Git, Teams, Linear). Invite the bot's app to the channel. | Posting a test message wakes the bot unprompted | | 24 | Add a second trigger for the thing you most hate missing. | It fires without you | | 25 | Try the **chief-of-staff-only** workflow: ask it for something outside every bot's lane. | It creates a new bot on its own | | 26 | Message a bot from your phone while away from your desk. | The answer arrives before you're back | | 27 | Wire the outputs into your wider stack — see `agent-os-integration.md`. | Grok Bot outputs land in your shared vault | | 28 | Write up two builds using `case-study-template.md`. | You know your real hours-saved number | | 29 | Run the security audit in `security-settings-guide.md`. | Nothing can send, post or pay without your click | | 30 | Prune. Turn off every routine that hasn't produced something you used. | Every remaining routine earns its usage | **Checkpoint:** five recurring drains gone — morning planning, inbox sorting, content research, billing, meeting follow-up. --- ## If you only have one evening Do days 1, 2 and 3. The morning brief alone changes how the week feels, and it only reads — it never sends, so there's nothing to be nervous about. --- *Part of the Grok Bot AI Full Course — *