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

Grok · X (Twitter) · Amount undisclosed (operations workflow case, not a revenue case; author reports highest-ever shipping rate, no income claimed)

## Business summary

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.

## Business value

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

Turn a business to-do into a prioritized list (AgentFlow suggested minimal try)

Grok Bot collaborates with Cursor cloud agents for parallel development

Draft a support reply and flag uncertain details (AgentFlow suggested minimal try)

## Preparation and limitations

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.

## Starter prompt

````text
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.
````

## 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.

## Source and attribution

Patrick Grenning (@pgrenn)
https://x.com/pgrenn/status/2118727460950872404
2026-11-06
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
