Channel: Ritesh Verma
Introduction
Ritesh Verma’s video explains how he combines Claude AI as the strategic “brain” with Grok Bot as an operational “computer‑using” employee to run an AI‑driven consulting business. He claims the setup generated roughly $61,000 in revenue over the last 30 days while he traveled to four countries.
What the video covers
The presentation walks through the architecture of the AI employee team, the specific roles Claude and Grok Bot play, how the team is built and trained, and the concrete workflows used for lead generation, advertising, and content creation. It also shares the tools involved, example numbers, and a set of action items for viewers who want to replicate the model.
Step‑by‑step walkthrough
- Claude as the brain – Claude designs the overall strategy, creates system prompts, and defines the organizational structure. In the video Claude writes a COO‑builder prompt for Verma’s consulting company, Agent Rise.
- Grok Bot as the operator – Grok Bot runs a personal computer and executes tasks inside the business (WhatsApp messaging, Meta Ads management, content repurposing, etc.) rather than relying solely on API‑only chat.
- Building the org chart – Using Claude’s COO prompt, Grok Bot proposes a structure with managers and individual contributors (ICs) across sales, client acquisition, content, and scaling. Verma mentions an example org chart of roughly 4 managers and 11 ICs (about 16 seats). He removes an AI “closer” role and adds a short‑form script writer.
- Training Grok Bot employees – Skills are sourced from a Claude Skills zip file (script writing, repurposing, director, id8). Additionally, a Google Drive voice profile built from the highest‑converting YouTube scripts is used to align the bots’ tone with proven messaging.
- Speedy SDR on WhatsApp – Grok Bot monitors a raw lead sheet. If a lead appears only in the raw data and has not yet been booked (i.e., not on the lead tracker), Grok Bot sends a WhatsApp message. Leads that already have a booked call are skipped to avoid duplicate outreach.
- Ads manager workflow – A Meta Ads MCP/developer app with a system‑user token (ads_read, ads_management) lets Grok Bot audit campaigns daily. Under‑performing ads are paused or killed. Verma cites an example where the cost per acquisition (CPA) hovered around $30.
- Scaling rule – Before adding any new hire, Verma asks whether the task could be performed by a Grok Bot employee. If yes, the role is filled by a bot; if not, a human is required. He notes that creative/design work still relies on humans for now, while growth is driven by more content, higher ad spend, and fresh creatives.
Tools and numbers mentioned
- Revenue claim: $61,000 in the last 30 days (as stated by Verma).
- Travel: Business operated while Verma visited 4 countries.
- Claude usage: Since February (approx. timeline).
- Grok Bot usage: Roughly 45 days at the time of the video.
- Claude model referenced: Claude Fable 5.1 medium (as spoken).
- Org chart example: 4 managers, 11 ICs (~16 seats).
- Ads performance: Example ~$30 CPA on Meta ads.
- Free offers: 15 free roadmap strategy calls; claims clients can grow from $1k to $20k+/mo.
- Tools list: Claude, Grok Bot, Google Drive/Sheets, WhatsApp, Meta Ads (developers.facebook.com apps), Agent Rise, Slyte, Skool WiFi Life.
Notable prompts and quotes
Claude becomes the brain that designs the system, and Grokbot becomes an operator that runs it entirely.
If a raw lead appears on lead tracker and they have booked a call, do not WhatsApp them. If they’re only in raw lead data and not on lead tracker… those are the only people to message.
Can this hire be a Grockbot employee? If so… If not, you need a human employee.
Caveats / hype check
The video presents a large revenue figure without showing a profit‑and‑loss statement or detailed financials on screen. The claim of a seven‑figure business relies on the stated $61k/month extrapolated over a year. The presentation includes a strong call‑to‑action for a free community, 15 strategy calls, and a done‑for‑you offering (Slyte). While the WhatsApp and Meta Ads automations appear to be real workflows demonstrated in the video, the results shown may be cherry‑picked. Viewers should treat the income claim as aspirational rather than guaranteed.
Concrete next actions
- Draft a COO‑style organizational prompt for Grok Bot that outlines workstreams such as content, lead handling, and operations before launching any bots.
- Export reusable Claude Skills (script writing, repurposing, etc.) as Markdown files and use them to train matching Grok Bot employees in the same way Verma describes.
- If testing a WhatsApp‑based SDR, replicate the “raw lead vs booked lead” gate in Google Sheets: only message leads that exist in the raw sheet but are absent from the lead tracker.
- Set up a Meta Ads developer app with the required system‑user token (ads_read, ads_management) and create a daily audit routine that pauses campaigns exceeding a target CPA threshold.
- Apply the scaling heuristic: for any new role or task, ask whether a Grok Bot employee could perform it; if the answer is no, plan to hire a human for that function.