Grok Bot + Whop, Vercel and Notion: a one-person business stack with costs
One founder runs his digital-product business on Grok Bot with Whop for payments, Vercel and GitHub for the site, and Notion for CRM and numbers. He claims the core costs "$165/mo + whop's cut per sale" (unverified).
What does a solo founder AI stack with Whop, Vercel and Notion look like?
This solo founder AI stack runs a digital-product business on Grok Bot with Whop for payments, Vercel and GitHub for the site, and Notion for CRM and numbers. Inbox and writer Bots draft but never send, and a chief-of-staff morning report plus an audit Bot oversee the rest. The founder's claimed core cost is unverified.
Setup
- Money: Whop plugin. Site: Vercel and GitHub plugins.
- Inbox: Gmail plus an inbox Bot that drafts and never sends.
- CRM and numbers: Notion, with inboxes built by Grok Bot.
- Content: the X plugin plus draft-only writer Bots. Video and design: Opus 5.5 with Cursor cloud agents.
- Oversight: a chief-of-staff morning report, plus an audit Bot (he calls it DOGE) that reviews every other Bot.
- Optional, added when needed: Intercom or Plain with a support inbox Bot, Klaviyo with Grok Bot routines, lead-finding Bots, and builder and reviewer Bots for code.
Starter prompt
- Context / Role
Grok Bot with Whop and Vercel + GitHub and Notion (documented setup). Do the setup steps above first.
- The copy-paste prompt
Starter promptWritten by our editors from the source Every morning at [time], send me a one-page report: 1. Sales and refunds from [Whop] since yesterday, with totals. 2. New leads and replies waiting in [Notion CRM]. 3. Drafts waiting for my approval from each Bot (inbox, content, support), with links. 4. Anything a Bot got stuck on or did differently from its instructions. Don't send, post or publish anything yourself.- Variables to customize
- [time]
- [Whop]
- [Notion CRM]
- Expected output / next step
A one-page morning report: Whop sales and refunds since yesterday with totals, new leads and replies in the Notion CRM, drafts waiting from each Bot with links, and anything a Bot got stuck on or did differently. Nothing is sent, posted or published.
Stack next step: Grok Bot + Notion or Google Drive: one source of truth for every Bot.
Business fit
How this stack helps specific businesses:
Solo founders selling digital products: run payments, site, inbox and content from one set of Bots that draft and wait for approval.
Solo founders- Creatorskeep posts and emails as drafts you approve, with a morning report on sales.
Watch-outs
- No business results are shared; this is a list of what he uses, not proof it works better.
- The monthly cost is his own figure and wasn't checked; Whop's cut per sale comes on top.
- He says Grok Bot replaced two other assistants for him; his bio also lists his own agent tools, so read it as one builder's preferences.
Workflows on this page at a glance
The starter prompt, then the use cases and prompts linked below. Input data is what each prompt asks you to fill in; the last column is what it produces, or the time or money result the source states.
| Workflow / use case | Primary AI role / tool slot | Input data | Expected business output / time saved |
|---|---|---|---|
| Starter prompt for this stack | Grok Bot + Whop + Vercel + GitHub + Notion | [time]; [Whop]; [Notion CRM] | Expected outputA one-page morning report: Whop sales and refunds since yesterday with totals, new leads and replies in the Notion CRM, drafts waiting from each Bot with links, and anything a Bot got stuck on or did differently. Nothing is sent, posted or published. |
| Morning readout: what's new, what matters, what to do | Grok Bot, Chief of Staff Bot (Autopilot) | [priority 1]; [priority 2]; [priority 3]; [name] | Expected outputA weekday 7am readout of up to 8 items ranked against your priorities, each with a source link, the priority it affects and what to do (reply, decide, hand off or ignore), then today's meetings and what to prepare. |
Related
- Morning readout: what's new, what matters, what to doChief of Staff prompt
- A Chief of Staff with specialist BotsBot structure
- Approval gates: Bots do the work, you keep the irreversible clicksBot structure
- Routines: daily and weekly runs that keep work movingBot structure
- Grok Bot + Notion or Google Drive: one source of truth for every BotStack
- AI for operationsDepartment hub, 57 examples
Related stacks and workflows
- AI operations workflow examples with promptsThe Operations workflow pack: all 57 prompts on one page
- Start with one AI agent for one jobBot structure: One Bot, one job
- AI assistant in Slack for teamBot structure: A Team Bot your whole team uses in Slack
- Multi-model AI agent setupStack: Grok Bot + Claude Code and Codex CLIs: route each task to a model
- Shopify AI agent daily exceptionsStack: Grok Bot + Shopify: store operations through Shopify's connector
- Track every follow-up promptChief of Staff prompt: Track every follow-up you promised, and draft the overdue ones
- Weekly bot team review promptChief of Staff prompt: Weekly review of your Bot team: what shipped, what's stuck, what to change
- AI agent prompt for weekly vendor portal tasksOperations prompt: Weekly run through supplier and vendor portals that have no API
- AI agent team newsletterPlaybook: Autonomous agentic business: named Bots, a weekly newsletter, posts twice a day
- AI for beginners business owners freePlaybook: First 48 hours with AI: four free tasks that use your own business
- How to turn missed calls into booked jobsPlaybook: Missed call to booked job: four AI steps for local service pros
- AI CFO promptsAll 18 Grok Bot prompts, by role
- AI automation stack small businessAll 8 Grok Bot stacks
Know what you want to show here?Book this slot on Shopify
