My Blog

Tag: Sheets

  • Grok Bot: GrokBot Just KEEPS Getting Better (4 New Use Cases)

    Watch on YouTube: https://www.youtube.com/watch?v=q7lekwOXXqk

    Channel: Kacper Rutkiewicz | AI Made Simple

    Introduction

    The video from Kacper Rutkiewicz | AI Made Simple showcases four recently added capabilities of Grok Bot. Each feature is demonstrated in a short, hands‑free session that ties together search, file creation, messaging, and voice interaction. The presenter frames the bot as part of a Cursor‑based workflow and shares concrete usage numbers from his own account.

    What the video covers

    Kacper walks through:

    • Native X (Twitter) search that does not consume developer credits.
    • Creation of real Google Docs, Sheets and Slides in the user’s Drive.
    • A dedicated bot‑owned inbox at @mail.grokbot.com.
    • A hands‑free voice mode that returns a full transcript after the session.

    He ties the four functions together in a 33‑second voice command that searches X, builds a deck, a doc and a sheet, then emails the links, and he shows the impact on his weekly quota.

    Native X search

    Grok Bot can query X directly from the chat interface without drawing on the user’s X developer or API credits. The feature is limited to 1,000 searches per day per account. In the demo the bot’s X Developer balance stayed at $3.61, confirming that no credits were spent. This allows repeated research queries—such as “top posts about X in the last 48 hours”—to be run throughout the day without affecting any paid X API usage elsewhere.

    Google Docs, Sheets and Slides

    When Google Workspace is connected, Grok Bot creates actual files in the user’s Drive rather than markdown placeholders. Users can point the bot at personal master templates so generated decks, docs and sheets follow brand styling. Slide generation typically takes 5–10 minutes. The same 33‑second voice command that produced a deck, a doc and a sheet moved the weekly quota from 32% to 35% (about a 3% increase), indicating that file‑creation consumes a modest portion of the limit.

    Bot email inbox (@mail.grokbot.com)

    Each bot instance receives a unique address of the form name@mail.grokbot.com, separate from the user’s personal Gmail. The address is claimed by typing “Claim our email and create our inbox”; allocation follows a first‑come, first‑served basis as the feature rolls out. The bot can send formatted HTML messages to any recipient and can also receive mail—useful for verification codes, receipts or newsletter sign‑ups—and reply to incoming messages. An important caveat is that new mail does not automatically wake the bot; a polling routine must be set up otherwise messages remain unnoticed until the user explicitly asks the bot to check.

    Voice mode

    Activating the waveform or call button enables hands‑free speaking; Grok Bot returns a full transcript after the conversation ends. In the headline demo a 33‑second verbal command—search X, build a deck, a doc and a sheet, then email the links—was executed successfully. Longer sessions, such as 15‑ to 20‑minute verbal brainstorming calls, barely register against the weekly quota on the Cursor plan, showing that voice interaction can support extended workflows without significantly impacting usage limits while still providing a searchable transcript.

    Tools and usage numbers

    • Cursor subscription: $60 / month (the plan used for quota measurements).
    • Weekly quota before demo: 32%; after demo: 35% (≈3% increase for the full multi‑step voice command).
    • X Developer credit unchanged: $3.61.
    • Native X search cap: 1,000 searches per day per user.
    • Slide generation time: 5–10 minutes.
    • Voice demo length: 33 seconds; longer brainstorms 15–20 minutes barely affect limits.
    • Integrated tools: Grok Bot, Cursor, X (Twitter), Google Workspace (Drive, Docs, Sheets, Slides, Gmail, Calendar), mail.grokbot.com.

    Caveats and hype check

    The presenter notes that the demonstrated usage figures are based on a single creator’s session and have not been independently verified. Claims about Grok Bot being a “premier personal AI agent” should therefore be treated as directional rather than definitive. The email inbox feature is still rolling out, so name availability varies and users may need to try several variations of @mail.grokbot.com. Additionally, new mail does not auto‑trigger the bot; a polling routine is required to avoid missed messages.

    > “Even 15‑to‑20‑minute verbal brainstorming calls barely impact usage limits.”

    Concrete next actions

    • Claim a preferred @mail.grokbot.com address by typing “Claim our email and create our inbox.”
    • Connect Google Drive via Connect Apps; optionally set a master template for Docs, Sheets and Slides.
    • Add a routine that polls the bot inbox (since new mail does not auto‑wake the bot).
    • Try a native X search prompt, for example: “top posts about AI agents from the last 48 hours.”
    • Run one multi‑step voice command (search X, create a doc, sheet and slide, email the links) and review the transcript plus the quota delta.
    • Optional: join the Skool community at skool.com/ai-automation-network-2970 for templates and guides.

  • Grok Bot: Claude AI + Grok Bot = $61,000/month

    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.