17 Grok Bots for a web studio, university and life admin

• He runs a web design and development studio and is a university student. He built around 17 Grok Bots for business, university and everyday life; some started as ideas from a Grok Bot meetup in Bucharest.
• Rule 1: one job per bot, so it's easier to see what broke.
• Rule 2: one shared context file (his background, how he writes, preferences, things bots shouldn't do) that every bot is told to read.
• Rule 3: clear instructions per bot, instead of expecting it to remember rules from a random chat.
• Rule 4: important actions need approval. Bots research, organize files and update him; messaging other people, publishing content or deleting accounts needs his yes.
• Rule 5: keep notifications to a minimum. If nothing important happened, no message.
• Rule 6: a hub plus a bot maker. He explains an idea to the maker, it works out instructions and setup, then the hub creates the bot and keeps track of the others.
• Pulse checks his inbox and calendar a few times a day and only messages when something needs attention; it caught a parcel locker about to expire while he could still extend it.
• Accountant checks email daily for company expenses, invoices he sent and documents from his accountant, files them in a shared Google Drive folder she checks monthly, and watches for changes in Romanian taxes and regulations.
• Account Cleaner went through services to change his login email where possible and close accounts he no longer needed, so he could retire an old address.
• Car Finder checks listing and auction sites weekly with his saved logins and adds auction fees and other costs to the price.
• Attendance Checker asks each weeknight which classes he attended and updates a Google Sheet of absences. Homework Guy tracks exams and deadlines in his calendar and drafts assignments he reviews before submitting.
• Product Finder compares products, prices, specs and reviews before he buys.
• Rival Watch checks other design studios' sites every Monday for pricing, services, new pages or offers.
• SEO Specialist checks his site's search performance; SEO & AEO Desk researches searches and content ideas for Google and AI search; Website Improver turns their findings into Linear tasks and never changes the live site.
• Fleet Ops checks the other bots weekly and reports which work, which need fixing and which aren't useful; nothing is removed without his approval.
• What didn't work: Copy Humanizer went unused (he prefers ChatGPT for copy), Podcast Maker is untested, and Reply Scout (daily X posts worth replying to) still finds posts he wouldn't reply to, so it's paused.
• In the comments: the first week burned his full weekly usage in 4 days while a bot used the computer to change emails and delete accounts; now he doesn't hit the weekly limit, since bots mostly organize mail and files and research.

“Creating bots is easy. Making them actually useful without constantly having to fix or babysit them is the hard part.”— u/mihaipostelnicu (r/GrokBot), Reddit

Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes