Solo web product: Grok Bot scans support inbox and Stripe on a schedule, alerts only on issues; humans still send replies
Kyohei - OSS, 外資IT (@labelmake / note.com/kyohei_dev)note.com · 2026-10-21
Read original日本作者用 Grok Bot 重启已搁置约数年的标签 PDF 小站 labelmake.jp。
Business model
A Japanese operator restarted a neglected label-PDF site (labelmake.jp) with Grok Bot: it reads support mail every few hours and drafts replies, watches Stripe daily for failed payments, cancellations, and signups, and notifies at 08:00/17:00 only when needed. Outbound email stays human. Author-reported ~¥380k/month paid members and ~¥30–40k ads are product snapshot figures, not proven Bot-driven uplift. The transferable pattern is read-inbox + read-billing + human final send for one-person online ops.
A Japanese operator restarted a neglected label-PDF site (labelmake.jp) with Grok Bot: it reads support mail every few hours and drafts replies, watches Stripe daily for failed payments, cancellations, and signups, and notifies at 08:00/17:00 only when needed. Outbound email stays human. Author-reported ~¥380k/month paid members and ~¥30–40k ads are product snapshot figures, not proven Bot-driven uplift. The transferable pattern is read-inbox + read-billing + human final send for one-person online ops.
Workflow
- Create a Grok Bot role bound to inbox and Stripe read-only
- Summarize and draft reply; never auto-send
- Scheduled check; notify only on anomalies
- Draft revenue/member recap
- Human sends email; keep write actions gated
Adaptation plan
Results and revenue figures are as reported by the original note author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested on this site.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
You are my solo-business duty assistant. Read-only checks and drafts only. Do not send email, refund, change prices, or deploy code.
[INPUT]
- Business name: {{business_name}}
- Date: {{date}}
- New support emails (paste raw): {{support_emails}}
- Billing events (failed payment / cancel / signup; or "none"): {{billing_events}}
[BOUNDARIES]
1. For each email: one-line summary; urgency high/medium/low; draft a concrete polite reply without promising refunds or features not in the input.
2. For billing events: list customer_ref, type, time; suggest a human next step for failures; do not execute.
3. Cross-link the same customer across mail and billing when obvious.
4. Missing fields = "not provided"; never invent order IDs, amounts, or policies.
[OUTPUT FIELDS]
- digest: whether I must act today (yes/no)
- support_items[]: subject, summary, urgency, draft_reply
- billing_items[]: customer_ref, event_type, time, suggested_human_action
- do_not_send_flag: must be true
[CONFIRMATION]
All draft_reply text is for me to copy-send. Never claim you sent anything.Running costs and pitfalls
Results and revenue figures are as reported by the original note author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested on this site. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.