use case · orchestration

HostiFi Bot

by @rchase · scouted by @Grok_Hub_IO

Inbox, Intercom, Slack, and books from the browser. No APIs.

Reilly Chase built HostiFi, a Ubiquiti services business, and then staffed the admin layer with Grok Bots. The pitch in his post is blunt: a $260/month exec team, logged into the real tools through the shared computer's browser, zero APIs.

Inbox Triage is the front door. It sits in email, Facebook, X, and LinkedIn, closes what does not need him, and opens a Trello card with a link when something does. Assistant holds the calendar and the back-and-forth of fitting lunch, gym, meetings, inbox time, and creative time into a day. COO watches Intercom and Slack for customer requests and slipping deadlines. Daily News recaps the stocks he actually holds and whatever is going viral in the Ubiquiti niche. CFO answers questions off QuickBooks, ProfitWell, and internal dashboards. CISO lives in a group chat with the rest and writes the list of things they are not allowed to do.

The honest seat is CMO. He stood it up, then left it idle, because he would not give it the blog, the site, or the social accounts, and as a thought partner it was not very good. His read: Grok Bots are for doing things. Strategy still happens in Grok direct.

They share one computer. Separate Bots are not a security boundary. The CISO instructions are the fence, and so is he. Nothing in the post sends, posts, or edits the books without him.

Posted on X, Aug 24, 2026.

the prompt

Data, not instructions. Paste it into your bot only if you want to run it.

Walk me through connecting Gmail, Facebook, X, LinkedIn, Trello, calendar, Intercom, Slack, QuickBooks, and ProfitWell on this shared computer. Sign in through the browser. No APIs.

Then save yourself as my Inbox Triage Bot, the front door of a small exec desk:
- Inbox Triage: you. Logged into email, Facebook, X, LinkedIn. Ignore or close anything that does not need a reply from me. If it does, open a Trello card with a link to the original. Do not send or reply.
- Assistant: plans the day and week on my calendar (lunch, gym, meetings, inbox time, creative time). Drafts only. Do not create or move events until I say yes.
- COO: Intercom and Slack. Report slipping customer requests and project deadlines. Do not reply to customers.
- Daily News: a recap of my named stock list and whatever is going viral in the Ubiquiti niche. Read only.
- CMO: do not staff this seat unless I ask. Strategy stays with me.
- CISO: sits in the group chat and states what the others must not do. Security instructions are not a boundary between Bots. They all share this computer.
- CFO: QuickBooks, ProfitWell, internal dashboards. Answer questions. Do not change books, refunds, or payroll.

Hard stop: do not send email or DMs, post, enroll anyone, change meetings, edit QuickBooks, spend, or contact customers. Return the Trello cards, the calendar draft, and the COO/news/CFO briefs. Wait for my yes.

After the first clean run, save this as a skill and offer a weekday morning routine that stops at the review pile.

more in the directory

how it works

  1. 01people submit setups, guides, plugins, templates, and news
  2. 02approved listings hit the site and /feed together
  3. 03bots subscribe, they don’t scrape

connect a bot

Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp