Grok BotUndisclosed

Solo SaaS founder uses Grok Bot for business ops, software engineering, and customer support; reports highest-ever shipping rate

Patrick GrenningX (Twitter) · 2026-11-06

Read original

Very impressed with Grok bot. I've been using autonomous agents since Openclaw came back in January and then Hermes a few months later. I switched from Hermes to Grok bot a couple weeks ago now and don't see myself going back. I use it for helping me run my business, software engineering, and customer support. I'm shipping at a highest rate than ever before and allows me to run my business efficiently as a solo operator. The integration with Cursor cloud agents for doing parallel development is incredible. I was hesitant to switch from Hermes because I prefer open source and the freedom to to pick models. These turned out to be non-issues really - I can have Grok bot run different models through OpenCode and Grokbot can backup all my skills and memories in github. The harness, connectors, and ease of use is so good compared to others I've tried. Hermes was excellent and helpful for me just not at the same level in terms of polish and ease of use as Grok bot.

Business model

Patrick Grenning, founder of optioncharts.io, switched from Hermes to Grok Bot and now uses it for business operations, software engineering, and customer support. He reports shipping at the highest rate ever and running the business efficiently as a solo operator, with strong integration to Cursor cloud agents for parallel development. Readers can reuse the pattern of one Agent covering ops + engineering + support plus IDE integration.

Workflow

  1. Turn a business to-do into a prioritized list (AgentFlow suggested minimal try)
  2. Grok Bot collaborates with Cursor cloud agents for parallel development
  3. Draft a support reply and flag uncertain details (AgentFlow suggested minimal try)

Adaptation plan

Results are as reported by the original post author. Workflow steps 1 and 3 are AgentFlow suggested minimal tries — the author did not detail them. FreePrompt and trial I/O are reconstructions and were not live-tested here. No income claimed. Specific plan fee, support volume, and time saved not disclosed. Bot-drafted support replies and code changes need human review before sending or merging.

Prompt

AgentFlow draft · Untested.

You are my Grok Bot helping a solo SaaS founder with business operations, software engineering, and customer support. Any external reply, code merge, or account change requires confirmation first.


- Current ops issue: {{ops_issue}}
- Development task: {{dev_task}}
- Support ticket summary: {{support_ticket}}
- Code or context (optional): {{code_context}}


1. Provide actionable advice or prepared materials for the ops issue.
2. Break down the development task and note how to collaborate with Cursor cloud agents.
3. Draft a reply for the support ticket.


- Three sections: Ops, Engineering, Support.
- Mark each item “pending confirmation”.
- List missing information instead of inventing.


Do not send support replies, merge code, or change production without explicit confirmation. This prompt is untested.

Running costs and pitfalls

Results are as reported by the original post author. Workflow steps 1 and 3 are AgentFlow suggested minimal tries — the author did not detail them. FreePrompt and trial I/O are reconstructions and were not live-tested here. No income claimed. Specific plan fee, support volume, and time saved not disclosed. Bot-drafted support replies and code changes need human review before sending or merging. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.