My Blog

Blog

  • Grok Bot: How To Easily Make $1,000/Month With Grok Bot (Step by Step)

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

    Channel: By Joel Blackman

    Building a $1,000/Month Dental Marketing Agency with Grok Bot AI Agents

    Joel Blackman presents a practical framework for launching a niche marketing agency targeting London dental clinics using Grok Bot AI agents. The model requires approximately six hours of initial setup and roughly $100 in first‑month tool costs, with a revenue goal of $1,000 per month secured by landing just two clients at $500 each. The approach leans on three specialized agents — Lead Scout, Outreach Team, and Ads Manager — to automate lead discovery, cold outreach, and ad fulfillment while the founder handles only the sales conversations.

    What the Video Covers

    • Designing three Grok Bot agents that each own a distinct stage of the client acquisition pipeline.
    • Sourcing affordable domains and email infrastructure via Inbox Kit instead of traditional G Suite or Microsoft 365.
    • Warming email inboxes with Instantly to protect deliverability before launching outreach.
    • Building a lightweight landing page on Lovable to display before‑and‑after case studies.
    • Running the entire system on a $19/month Grok Bot subscription plus ancillary tool costs totaling ~$100 for the first month.
    • Targeting roughly 2,500 private dental clinics in London, with a conversion assumption of two closed deals to hit the $1,000/month target.

    Step‑by‑Step Walkthrough

    The setup unfolds in three parallel tracks: agent creation, infrastructure provisioning, and outreach execution.

    1. Create the Lead Scout Agent

    In Grok Bot, configure a Lead Scout prompt that scans the Meta Ad Library for London dental clinics currently running ads, checks whether a Meta Pixel is installed on their site, and captures the clinic owner’s name and email. The agent outputs a structured lead list ready for the outreach stage.

    2. Create the Outreach Team Agent

    This agent handles domain acquisition (3‑5 domains such as dentalgrowth.com via Inbox Kit), sub‑email creation, and email warm‑up on Instantly. It then writes personalized cold email sequences that reference each clinic’s specific pain points — for example, a missing Meta Pixel — and schedules the send cadence.

    3. Create the Ads Manager Agent

    Once a prospect books a call and signs, the Ads Manager agent takes over fulfillment: setting up campaigns in Meta Business Suite, managing creative, and reporting performance. The founder’s only manual responsibility is the sales call itself.

    4. Provision Infrastructure

    • Sign up for Grok Bot ($19/month minimum plan).
    • Open an Instantly account for email warm‑up.
    • Purchase 3‑5 domains on Inbox Kit and configure sub‑emails.
    • Set up a Meta Business Suite account for running client ad accounts.
    • Build a simple landing page on Lovable ($15/month) showcasing dental marketing case studies.

    5. Launch and Iterate

    Activate the Lead Scout to populate the lead sheet, start the Outreach Team’s warm‑up and sending sequence, monitor replies, book calls, and personally close two clients at $500/month.

    Tools & Numbers at a Glance

    • Grok Bot subscription: ~$19/month
    • Lovable landing page: ~$15/month
    • Total first‑month startup cost: ~$100 (covers all tools)
    • Target revenue: $1,000/month ($12,000/year)
    • Client price point: $500/month each
    • Clients needed: 2
    • Addressable market: ~2,500 private dental clinics in London
    • Setup time estimate: 6 hours
    • Key software: Instantly (email warming), Inbox Kit (domains/emails), Meta Business Suite (ad accounts), Lovable (landing page)

    Caveats & Hype Check

    I’m literally going to give you the simplest and the easiest way, step by step, of how you can make a thousand dollars a month.

    You’ve got to be confident enough to take the call and sell on that call. That is the hardest part of all of this.

    The revenue math assumes a smooth conversion from cold email to signed contract, but the video does not disclose actual response rates, meeting‑booking rates, or close rates for a beginner. The “six‑hour setup” estimate excludes the learning curve for Grok Bot prompting, email deliverability nuances, and sales conversation skills. The free agent scripts serve as a lead magnet — likely funneling viewers toward a paid course or affiliate commissions for Instantly, Inbox Kit, and Lovable. Treat the $1,000/month figure as a best‑case scenario rather than a guaranteed outcome.

    Concrete Next Actions

    • Sign up for Grok Bot on the minimum $19/month plan.
    • Create an Instantly account for email warm‑up.
    • Buy 3‑5 domains on Inbox Kit (e.g., dentalgrowth.com) and set up sub‑emails.
    • Set up a Meta Business Suite account for client ad management.
    • Build a landing page on Lovable ($15/month) with dental marketing case studies.
    • In Grok Bot, create the Lead Scout agent with a detailed prompt for London dental clinics (Meta Ad Library scan, Meta Pixel check, owner contact capture).
    • Create the Outreach Team agent: configure domain/inbox setup, Instantly warm‑up, and personalized cold email sequences targeting pain points.
    • Create the Ads Manager agent to handle ad fulfillment for signed clients.
    • Launch outreach, monitor replies, and book sales calls.
    • Personally take sales calls and close two clients at $500/month.

  • Marketing & Lead Gen: I Tried the LAZIEST Way to Make Money with Claude AI at Night 🌙

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

    Channel: Patrick Dang

    AI-Powered Meta Ads Service: A Night-and-Weekend Business Model

    Patrick Dang’s latest video outlines a beginner-friendly service model that uses Claude and Higsfield to create Meta ads for direct-to-consumer brands, then sells the service through cold LinkedIn outreach backed by Loom videos. The pitch: you can run this nights and weekends while keeping a full-time job, land a first client within 30 days, and charge $2,000+ per month on retainer. Below is a breakdown of the workflow, the numbers, and the reality checks you should weigh before diving in.

    What the Video Covers

    • Four criteria for a starter AI business: non-technical, doable part-time, AI handles 70–80% of the work, realistic path to a first client in ~30 days.
    • Core workflow: Mine the Meta Ads Library for competitor winners → feed those signals into Claude for analysis → generate fresh ad creatives with Higsfield inside Claude → package samples + analysis into a clean deliverable.
    • Pricing benchmarks: Static ads $150–$1,000 each; monthly retainers $700–$50,000; suggested starter rate ~$2,000/month for multiple ads and variations.
    • Sales framework: Diagnose the prospect’s pain (can’t scale ads), dreams (revenue targets), and challenges (no team or AI know-how) → position your service as the simple, cost-effective bridge.
    • Outreach tactic: Target director/VP/CMO-level contacts on LinkedIn, send a personalized Loom video showing the competitor gap and your custom samples, ask for a call or DM reply.
    • Ideal clients: DTC physical-product brands already running ads but losing to competitors, and unaware of what AI can now produce.

    Step-by-Step Walkthrough

    1. Competitor research. Open the free Meta Ads Library, search a brand like Aura Ring (690 active ads, 4+ month longevity, multiple languages/placements). Note which creatives have run longest and in how many variations.
    2. Signal analysis with Claude. Paste the ad URLs or screenshots into Claude. Ask it to extract winning patterns: hooks, formats, copy angles, visual styles, CTA structures. Use the “One-Person Business Blueprint” Cloud skill (free in the video description) to structure this analysis.
    3. Creative generation via Higsfield. Inside Claude, invoke Higsfield (or Higsfield NPC) to produce new static ad images and copy that mirror the winning signals but tailored to your target brand’s product and voice.
    4. Package the deliverable. Assemble 5–10 sample ads plus the competitor analysis into a single HTML or PDF document. Keep it clean: brand logo, ad previews, rationale for each variation.
    5. Build a target list. On LinkedIn, identify 20–30 DTC brands running ads but not yet using AI heavily. Filter for director, VP, or CMO titles.
    6. Record Loom outreach. For each prospect, record a 2–3 minute Loom video walking through their competitor’s ad landscape, the gaps you spotted, and the custom samples you made for them. No hard sell — just “thought this might help.”
    7. Book and close. On the call, revisit pain/dreams/challenges, present the retainer scope (e.g., 15–20 ads/month + weekly reporting), and close at your starter rate.

    Tools & Numbers Referenced

    • Claude — analysis, strategy, and Higsfield integration
    • Higsfield / Higsfield NPC — image and ad generation inside Claude
    • Meta Ads Library — free competitor ad archive
    • Loom — personalized video outreach
    • LinkedIn — cold outreach to decision-makers
    • Pricing data: static ads $150–$1,000; retainers $700–$50K; starter ~$2K/month
    • Old agency cost baseline: ~$19K/month for designer + copywriter + strategist salaries
    • Aura Ring case: 690 active ads, 4+ month longevity, multi-language placements
    • Student results cited: Brandon $10K/month; Teresa “thousands” in real estate niche
    • Outlier claim: some agencies charge $50K/month from a single client

    Caveats & Hype Check

    The video heavily promotes a free lead magnet (“One-Person Business Blueprint” Cloud skill) and a free live training that likely funnels into a paid program. Student results (Brandon, Teresa) are unverified testimonials. The “30 days to first client” framing is presented as possible, not guaranteed. The $50K/month single-client figure is an outlier, not a benchmark. Success hinges on sales skill — cold outreach, discovery calls, closing — not just the AI tools.

    In short, the workflow is legitimate and demonstrable, but the funnel structure (free content → free skill → free training → paid offer) means you’re entering a marketing ecosystem. Treat the numbers as directional, not promised.

    Concrete Next Actions

    • Download the free “One-Person Business Blueprint” Cloud skill from the video description.
    • Register for the free live training (link in description) for deeper workflow demos and live sales role-plays.
    • Pick one AI-powered service to sell (Meta ads, LinkedIn ghostwriting, automations, etc.).
    • Research competitor ads in Meta Ads Library; use Claude to extract winning signals.
    • Create 5–10 sample ads for a target brand using Claude + Higsfield.
    • Package samples + competitor analysis into a clean HTML/PDF document.
    • Identify 20–30 target DTC brands (running ads, non-AI-savvy) on LinkedIn at director/VP/CMO level.
    • Send personalized Loom videos showing competitor gaps + your custom samples.
    • Book calls → diagnose pain/dreams/challenges → close on a monthly retainer.

  • Grok Bot: How I Grew My X Account to 10K Followers With Grok Bot (Copy Me)

    Watch on YouTube: https://www.youtube.com/watch?v=YiY-jis_Rww

    Channel: Jordan Rafealov

    How One Creator Built a 10-Automation Grok Bot to Scale X from 514 to 10,000 Followers

    Jordan Rafealov recently shared a system he built to grow his X (formerly Twitter) account from 514 followers to a year-end target of 10,000. The centerpiece is a custom Grok Bot that bundles 10 distinct automations — covering content creation, engagement, analytics, and lead generation — all operable through X direct messages. He’s distributing the bot for free via his pinned X post, conditional on following his account.

    What the Video Covers

    The walkthrough breaks down each automation, the research behind the posting cadence, the onboarding flow that tailors output to your voice, and the technical stack that connects the bot to X. Key sections include:

    • 10 automations: Morning Brief, Reply Hunter, Your Take, Promo Replies, Product Posts, YouTube→X, Clips, Accountability, Weekly Review, and Client Finder.
    • Benchmark research: Analysis of the top 25 X accounts revealed a consistent pattern — 3+ posts per day, 20 replies per day, 1 thread per day, 1–2 clips per day, and 1 X article per week.
    • Onboarding questionnaire: The bot asks detailed questions about your voice, audience, offers, goals, style preferences, and logistics before generating any content.
    • DM-based approval workflow: Each morning the bot sends draft posts, replies, threads, articles, and clip ideas for one-click approval or revision.
    • Xurneo integration: A free tool (affiliate link disclosed) that connects AI agents to X for posting and data retrieval.
    • Micro SaaS promotion: The bot automatically plugs Rafealov’s own products — Vibe Check ($9 security audit), Invoice Bot, and dailymeme.co.
    • Weekly analytics review: Tracks follower growth, post-type performance, optimal posting times, reply word counts, and top-performing content.
    • Client finder: Searches niche keywords daily to surface potential leads and draft outreach replies.
    • Skill library: Built from roughly 300 skills developed across Claude and Grok, combined with deep research on viral account patterns.

    Step-by-Step Walkthrough

    The implementation path Rafealov demonstrates follows a clear sequence:

    1. Access the bot: Click the link in the video description, follow Rafealov on X, navigate to his pinned post, and click the Grok Bot download link.
    2. Add to GrokBot: Click “Add to GrokBot” and complete the onboarding questionnaire covering voice, audience, offers, goals, style, and logistics.
    3. Connect Xurneo: Link your Xurneo account to enable the bot to post on your behalf and pull analytics data.
    4. Approve daily drafts: Each morning, review the Morning Brief delivered via X DM — approve, edit, or reject posts, replies, threads, and article outlines.
    5. Record voice notes for “Your Take”: When prompted, speak your opinion on a trending topic; the bot converts it into an opinionated post or thread in your voice.
    6. Review the weekly report: Every week, examine the analytics summary to adjust posting times, content mix, and reply strategy based on actual performance data.

    Tools and Numbers Cited

    • Follower goal: 514 → 10,000 by end of year (approximately 4 months).
    • Posting benchmarks from top 25 accounts: 3+ posts/day, 20 replies/day, 1 thread/day, 1–2 clips/day, 1 X article/week.
    • 300 skills sourced from Claude and Grok incorporated into the bot.
    • Xurneo (free tier available, affiliate link provided).
    • Vibe Check micro SaaS: $9 for security vulnerability prompts.
    • Nano Banana for AI image generation.
    • Grok Bot platform as the orchestration layer.
    • 10,000 YouTube subscribers milestone reached by the channel.

    Caveats and Hype Check

    Ambitious 20x follower goal (514→10K) in ~4 months with no proven results yet — bot was just built. “Free” download requires X follow (growth tactic). Affiliate link for Xurneo disclosed. Micro SaaS revenue claims ($9 Vibe Check) shown without sales data. Entire system untested at scale.

    The growth target is aggressive and unvalidated; the bot was completed shortly before the video’s release. The “free” distribution functions as a follow-gate, which is a legitimate growth tactic but worth noting. Xurneo’s affiliate link is disclosed, and the micro SaaS revenue figures are presented without supporting sales metrics. As with any new automation stack, real-world performance will vary by niche, consistency, and content quality.

    Concrete Next Actions

    • Click the description link → follow Jordan on X → go to pinned post → click Grok Bot download link.
    • Click “Add to GrokBot” and complete onboarding (voice, audience, offers, goals, style, logistics).
    • Connect Xurneo account to enable posting and analytics.
    • Approve daily Morning Brief drafts via X DMs (posts, replies, threads, articles).
    • Record voice notes for “Your Take” prompts to generate opinionated content.
    • Review weekly analytics report to adjust posting times and content types.

    If you’re testing AI-driven X growth, this bot offers a structured, low-cost way to experiment with high-frequency posting and engagement — provided you’re comfortable with the follow-gate and the early-stage nature of the system.

  • AI Tools: Unlimited Claude Code For Free (Runs On Your Computer)

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

    Channel: Sharbel A.

    Running Claude Code Without the Subscription: Three Free Paths

    Claude Code has become a popular AI-powered coding assistant, but its official pricing model ties usage to Anthropic’s hosted models. A recent walkthrough by Sharbel A. outlines three practical ways to use the Claude Code tooling for free by swapping the underlying model for local or free-tier alternatives. The core insight: Claude Code is an agent harness — a tool that orchestrates tasks — while the model is the “brain” doing the reasoning. You pay Anthropic for the brain, not the harness. By pointing the harness at free models, you keep the workflow without the recurring cost.

    What the Video Covers

    • Local execution via Ollama — run open-weight models on your own hardware, trading RAM and speed for privacy and zero API fees.
    • Free LLM API aggregation — a Docker-based gateway that pools free tiers from Google AI Studio, Grok, and Mistral behind a single local endpoint.
    • Open Code — a separate open-source coding agent (opencode.ai) that supports free models out of the box with minimal configuration.

    Each approach has distinct hardware requirements, privacy implications, and setup complexity. The video emphasizes matching the method to your machine’s capabilities and your tolerance for latency.

    Step-by-Step Walkthrough

    Option 1: Ollama + Local Models

    1. Assess your RAM. The model you can run depends on available memory:
      • 8–16 GB system RAM → Gemma 4 12b
      • 18–32 GB system RAM → Qwen 3 Coder
      • 64 GB+ system RAM → GPT OSS 120
    2. Mac unified memory adjustment. On Apple Silicon, the GPU shares system RAM. Pick a model sized for roughly half your total RAM (e.g., an 18 GB Mac → 9 GB model like Gemma 4 12b).
    3. Install Ollama. Download from ollama.com for your OS.
    4. Pull the model. Example: ollama run gemma2:12b (adjust tag per the creator’s model-selection guide).
    5. Connect to Claude Code. Open the Ollama app → Apps → “Claude Code in other apps” → copy the provided ollama launch claude command into your terminal.

    Option 2: Free LLM API (Docker Gateway)

    1. Install Docker. Get it from docker.com.
    2. Deploy the Free LLM API container. The GitHub repo (linked in the video description) provides the compose file.
    3. Add free-tier API keys. Via the dashboard (port 3000 or 3001), enter keys for:
      • Google AI Studio (free tier)
      • Grok free tier
      • Mistral free tier
    4. Point Claude Code to localhost:3000 (or 3001). The gateway routes requests to whichever provider has quota.

    Option 3: Open Code

    1. Visit opencode.ai and follow the installation instructions for your platform.
    2. Configure a free model (local via Ollama or remote free tier) in the settings.
    3. Start coding — no separate Claude Code harness needed.

    Tools, Models, and Numbers at a Glance

    • Ollama — local model runner (ollama.com)
    • Models referenced: Gemma 4 12b, Qwen 3 Coder, GPT OSS 120
    • RAM thresholds: 8–16 GB, 18–32 GB, 64 GB+
    • Mac rule of thumb: model size ≈ 50 % of total unified memory
    • Free LLM API — Docker-based aggregator (GitHub repo)
    • Free-tier providers: Google AI Studio, Grok, Mistral
    • Dashboard ports: 3000 / 3001
    • Open Code — alternative open-source agent (opencode.ai)

    Caveats and Hype Check

    Running a model locally is the private way to do this, but it’s not the only way to get Claude Code for free.

    The “unlimited” claim holds only if you ignore the hidden costs:

    • Hardware floor. Local models need 8 GB RAM minimum; usable performance starts around 16 GB. Many laptops won’t qualify.
    • Speed trade-off. On modest hardware, token generation can be seconds per step — acceptable for experimentation, painful for production workflows.
    • Privacy vs. convenience. Free LLM API sends code to third-party free tiers; local keeps everything on-device but consumes your compute and electricity.
    • Tool divergence. Open Code is a different agent with its own UX; it’s not a drop-in Claude Code clone.

    The creator is transparent about these limits and offers a free model-selection guide (newsletter signup) rather than promising magic results.

    Concrete Next Actions

    • Audit your machine. Check total RAM (and unified memory on Mac) against the thresholds above.
    • Pick a path.
      • If you have ≥16 GB RAM and value privacy → Ollama + local model.
      • If you have limited RAM but free API quotas → Free LLM API via Docker.
      • If you want zero-config and don’t mind a new tool → Open Code.
    • Execute the first two steps of your chosen path today. Install Ollama or Docker or Open Code, then pull a model or add an API key.
    • Benchmark. Run a realistic coding task (e.g., “refactor this React component”) and measure latency. Decide if the speed is acceptable for your daily loop.
    • Iterate. Swap models or providers as your hardware or quota changes; the harness stays the same.

  • Grok Bot: I Replaced My AI Team with Grok Bot and I’m Not Going Back

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

    Channel: ICOR with Tom | AI Productivity

    From 59 Local Agents to a Cloud-Native AI Team: Why Tom Switched to Grok Bot

    For months, Tom from ICOR ran a sprawling local AI team: 59 agents, 37,361 files, 149 SOPs, 57 work streams, 107 guideline files, 20 skills, 1,408 task files, and 2,260 session logs. The system worked — until it didn’t. The overhead of maintaining guardrails, resolving conflicting rules, and manually copying context between agents turned the setup into bureaucracy. When Opus 5.5 demonstrated that modern models can handle guardrails natively, and Grok Bot arrived with built-in orchestration, a persistent cloud computer, and cross-device voice handover, Tom migrated. He now runs roughly two dozen bots behind a single lead orchestrator, keeping his custom knowledge app (Any.do) as the source of truth while Grok Bot handles execution.

    What the Video Covers

    • The tipping point: Opus 5.5 removed the need for hand-crafted SOPs; Grok Bot added orchestration, skills, routines, and enforced rules out of the box.
    • Architecture shift: from a folder-based agent swarm to a lead bot + specialist bots + group chats model.
    • Key Grok Bot capabilities: one always-on cloud computer with per-bot screens, file sharing in chat, integrations (email, calendar, Dropbox, ClickUp, Todoist, custom APIs via MCP), per-bot memory/journals, shareable templates, and voice chat that hands over seamlessly across devices.
    • Ownership and transparency: files live on Grok Bot’s computer but can be zipped and exported anytime; bot setups export as templates; instructions, skills, journals, and generated files are all visible.
    • Hybrid workflow: Grok Bot as orchestration layer; Any.do (or Notion/Obsidian) as the primary knowledge store, connected via API/MCP.

    Step-by-Step Walkthrough: How the Migration Worked

    1. Audit the old system. Tom counted every artifact — agents, files, SOPs, work streams — and recognized the maintenance burden had exceeded the value.
    2. Define the new guardrails. Instead of 149 SOPs, he wrote negative constraints for each bot: explicit lists of what a bot should never do. Fewer rules, clearer boundaries.
    3. Build a minimal viable team. Start with one lead bot (orchestrator) plus two to three specialists, each with a single, well-defined job (e.g., research, drafting, code review).
    4. Replace work streams with group chats. Multi-bot workflows (video prep, course creation) now run in shared group chats where the lead delegates to specialists in real time.
    5. Connect tools once. Email, calendar, Dropbox, ClickUp, Todoist, and custom apps (via API/MCP) are linked to the Grok Bot computer, not to individual agents.
    6. Enable voice-first ideation. Use voice chat on mobile for on-the-go capture; continue the same conversation on desktop without losing context — “that is the last 20%.”
    7. Keep knowledge external. Primary storage stays in Any.do; Grok Bot reads/writes via API/MCP, ensuring Tom owns the canonical data.

    Tools & Numbers at a Glance

    • Old system: 59 agents (3 retired), 37,361 files, 149 SOPs, 57 work streams, 107 guidelines, 20 skills, 1,408 task files, 2,260 session logs.
    • New system: ~24 bots (lead + specialists), 21 shared skills, 3 routines.
    • Model: Opus 5.5 (guardrails handled natively).
    • Platform: Grok Bot (cloud computer, per-bot screens, cross-device sync, voice handover).
    • Integrations: Email, Calendar, Dropbox, Google Drive, ClickUp, Todoist, custom apps via API/MCP.
    • Knowledge store: Any.do (custom app), connected via MCP.
    • Upcoming comparison: Claude Code (waitlist, US only) — not yet accessible.

    Caveats & Hype Check

    Tom explicitly states no affiliation or sponsorship with SpaceX/Grok Bot. He promotes his own paid membership courses (‘Build your own agent harness’ and ‘Your AI team with Grok Bot’), which is a clear commercial interest.

    • Best-in-class claim is based on personal experience, not independent benchmarks.
    • “2,000 bots” figure appears to be a transcript error; the consistent number is ~24 bots.
    • Ownership/export relies on manual zip downloads and template shares — no one-click full export yet.
    • Vendor lock-in risk: While data can be exported, the orchestration logic (skills, routines, group chats) lives inside Grok Bot’s platform.
    • Claude Code remains untested; a future comparison may shift the calculus.

    Concrete Next Actions

    • Audit your current AI setup. Count agents, SOPs, and rule files. If maintenance feels like bureaucracy, it’s time to simplify.
    • Prototype a minimal Grok Bot team. Create one lead bot + 2–3 specialists. Give each a single job and a short “never do” list.
    • Connect your tool stack once. Link email, calendar, file storage, and task managers to the Grok Bot computer via native integrations or MCP.
    • Use group chats for multi-step workflows. Replace linear work streams with collaborative group chats where the lead delegates to specialists.
    • Adopt voice chat for capture. Start ideas on mobile voice; continue seamlessly on desktop.
    • Keep canonical knowledge in your own app. Use Notion, Obsidian, Any.do, or similar as the source of truth; treat Grok Bot as the execution layer.
    • Evaluate learning paths. If you want full control, take ‘Build your own agent harness’; if you prefer a managed orchestration layer, take ‘Your AI team with Grok Bot’ (both via My AI Co membership).

  • Marketing & Lead Gen: The $1,000/hour 1-person AI business

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

    Channel: Greg Isenberg

    The $1,000/Hour One-Person AI Business: Selling Outcomes, Not Technology

    Greg Isenberg sits down with James Dickerson of Mr. Boring Marketing to unpack a counterintuitive playbook: build a high-leverage solo business by selling AI-powered marketing funnels to Main Street service companies — plumbing, HVAC, commercial hood cleaning, dental implants, and similar trades — rather than chasing tech startups. The core insight? Local businesses doing $2M+ in revenue already spend heavily on ads but leak 20% or more of their leads through broken conversion paths. Fix the leak, charge for booked jobs and measurable ROI, and you create a recurring revenue stream that compounds.

    What the Video Covers

    The conversation walks through the entire lifecycle of the model: selecting a single trade and geographic radius, building a Dream 100 list of ideal prospects, using AI coding agents to research and score each company, crafting niche-specific funnels that match each ad campaign, and blending old-school direct-response tactics (lumpy mail, breakfast meetups) with new-school Meta ad automation. Dickerson emphasizes that the buyer never cares about “AI agents” — they care about phone calls, booked appointments, and revenue. The discussion also covers pricing architecture, the importance of a free case study to prove the model, and the foundational reading list that underpins the approach.

    Step-by-Step Walkthrough

    1. Pick One Trade, One City

    Start narrow. Choose a high-LTV, urgent-need trade (e.g., HVAC, plumbing, tree service) and a 25-mile radius. The U.S. has roughly 112,000 plumbing/HVAC companies averaging $2.5M annual revenue; about 14% report AI as fully embedded in operations, leaving a large addressable set that still runs on manual marketing.

    2. Build and Research the Dream 100

    Apply Chet Holmes’ Dream 100 framework: compile 100 ideal clients in that niche/geo. Deploy AI agents (Claude Code with MCP connectors) to scrape Google Maps, Yelp, ad libraries, and websites; extract owner names, review velocity, employee counts, and ad spend signals. Score each prospect so you know who spends $150–250k/year on marketing but converts poorly.

    3. Diagnose the Conversion Leaks

    Typical low-hanging fruit: ad-to-landing-page message mismatch, missing Google ratings on the page, three-plus scrolls before a booking button. A $5M company losing 20% of $129 leads wastes roughly $2,600/month. Quantify that gap in your outreach.

    4. Build Niche-Specific Funnels with AI Coding Agents

    Use tools like Boring Funnels (free library at boringfunnels.com) or Claude Code to spin up branded funnels in minutes. Template types include:

    • Tripwire offers (e.g., $79 HVAC tune-up to liquidate ad spend)
    • Repair-vs-replace quizzes that segment high-consideration buyers ($20–30k furnace installs)
    • Video sales letters and instant-pricing calculators

    Each ad campaign routes to a congruent funnel — no generic “contact us” pages.

    5. Combine New-School Ads with Old-School Outreach

    • Meta ads: Build campaigns via Meta MCP from code; creatives edited with Opus 5.5 for short-form UGC style. Lead with education, not “book a demo.”
    • Lumpy mail: Send a physical package (brass fitting, personalized letter, QR code to the prospect’s rebuilt landing page) to the top 20 prospects.
    • Breakfast meetups & handwritten notes: Relationship anchors that digital-only competitors skip.

    6. Brand for the ICP, Not Like a SaaS Company

    Example: “Leak-Proof Marketing — we fix leaks in your marketing, you handle the plumbing.” Good branding creates a feeling the ideal customer connects with instantly.

    7. Pricing Ladder

    • Free first funnel in exchange for a detailed case study/testimonial.
    • Introductory install fee + $2–5k/month retainer for optimization, testing, call tracking, and reporting.
    • Later add performance-based upside (percentage of incremental booked jobs).

    Tools & Numbers at a Glance

    • Market size: 112k plumbing/HVAC firms, avg $2.5M revenue
    • Ad spend benchmark: $5M company spends $150–250k/year
    • Lead cost example: $129/lead; 20% leak = $2,600/mo wasted
    • Tripwire price point: $79 tune-up
    • High-ticket install: $20–30k (financed, high consideration)
    • Agency funnel build cost: ~$20k (your AI-built version costs tokens + time)
    • Key tools: Boring Funnels (free), Claude Code, MCP connectors, Meta MCP, Opus 5.5, Brex (sponsor)

    Caveats & Hype Check

    Customers don’t care about AI automation. They care about revenue, they care about ROI.

    Never lead with ‘I’m implementing AI into your local company.’ Their eyes glaze over.

    Dickerson is transparent: this is a 6–18 month long game (Chet Holmes cites 6 months for Dream 100 results). Voice AI agents often fail with real customers (“Is this a dumb AI thing?”). Most owners don’t know what an AI agent is, and some actively dislike AI. He has a product (Boring Funnels) but gives away the library and says “do it however you want.” No specific agency revenue claims are made; the emphasis is on doing free work first to prove results.

    Concrete Next Actions

    1. Select one trade and one 25-mile radius city.
    2. Build a Dream 100 list of $2M+ revenue companies in that niche/geo.
    3. Deploy AI agents (Claude Code + MCP) to research each: scrape reviews, ads, websites, owners; score review velocity and employee count.
    4. Create a niche-specific funnel template library (tripwire, quiz, VSL, instant price) using a coding agent.
    5. Launch Meta ads targeting that niche with educational creatives; use Meta MCP to build campaigns from code.
    6. Send lumpy mail to top 20 prospects: physical package (brass fitting, custom letter, link to their rebuilt landing page).
    7. Offer a free “leak audit” or funnel build for 1–2 prospects in exchange for a detailed case study/testimonial.
    8. Set pricing: introductory funnel build fee + $2–5k/month retainer for optimization, reporting, call tracking.
    9. Report monthly on booked jobs, call volume, cost-per-lead improvements; automate reporting with AI (Looms, data prompts).
    10. Read The Ultimate Sales Machine (Chet Holmes), Jay Abraham’s Strategy of Preeminence, and Dan Kennedy’s direct response books; apply one concept per week.

    Final Thought

    The opportunity isn’t in selling AI — it’s in selling the outcome that AI enables you to deliver faster and cheaper than traditional agencies. By narrowing to one trade, one city, and one conversion problem, a solo operator can build a portfolio of case studies that commands retainer fees while the competition chases generic “AI automation” buzzwords. The playbook is old; the leverage is new.

  • AI Tools: I knew AI + Notion would be good, but this… wow.

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

    Channel: Jeff Su

    Teaching AI Your Notion Conventions: A Rulebook Approach That Works Across Platforms

    Most professionals who use Notion have developed personal systems — naming conventions, icon choices, database structures, property tags, and page layouts that reflect how they think and work. The challenge arises when bringing AI into the mix: connectors for Claude, ChatGPT, and Gemini understand Notion’s API, but they don’t know your conventions. Jeff Su’s demonstration shows how a single markdown rulebook solves this, letting any compatible AI operate your workspace exactly as you would.

    What the Video Covers

    The core problem is straightforward: external AI tools can read and write to Notion via API, but they lack the context of your personal workflow preferences. The solution is a Notion Conventions file — a markdown document that captures your rules for naming, icons, database selection, templates, properties, and page structure. Once this file is mounted in an AI project, the assistant reads it before every Notion action and applies your standards automatically.

    Key takeaways from the demonstration:

    • AI connectors know Notion’s API but not your personal conventions; a written rulebook bridges this gap.
    • The same conventions file works identically across Claude, ChatGPT, and Gemini as long as the folder is mounted.
    • The method scales to dozens of databases using a prompt template that has the AI analyze properties, templates, and recent entries, then ask clarifying questions.
    • Complex multi-database workflows — such as creating a live Q&A workshop project with a project page, North Star document, deliverables database, tasks database, and notes — can be executed in a single command.
    • The broader concept, called Jeff OS, positions a central AI context folder (holding conventions for Notion, Gmail, Calendar, and other tools) as the orchestrator, with Notion AI reserved for in-app tasks like copy review and bulk migrations.

    Step-by-Step Walkthrough

    The implementation follows a clear sequence that can be replicated in under an hour:

    1. Download the starter template. Jeff provides a Google Doc formatted as a Notion Conventions starter. Download it as a .md file.
    2. Create a local folder. On your desktop (or preferred location), create a folder named Notion Ops and place the conventions file inside.
    3. Connect Notion to your AI. In your chosen platform (ChatGPT, Claude, or Gemini), enable the Notion integration/connector.
    4. Create an AI project and mount the folder. Start a new project called “Notion Ops” and mount the Notion Ops folder so the AI can read and write the conventions file.
    5. Teach task and note preferences. Copy the link of an ideal task page and an ideal note page from your Notion workspace. Use the provided prompt template (linked in the video description) to have the AI analyze those pages and save your structural preferences to the conventions file.
    6. Verify with a fresh chat. Start a new conversation with the folder mounted and ask the AI to create a test task or note. Confirm the output matches your conventions.
    7. Scale to each database. For every database you want the AI to manage, use the database analysis prompt template. The AI will inspect properties, templates, and recent entries, then ask clarifying questions before writing the rules to the conventions file.
    8. Execute complex workflows. Once conventions are captured for the relevant databases, you can issue a single high-level prompt — e.g., “Create a live Q&A workshop project with North Star, deliverables, tasks, and notes” — and the AI will create and link all pages per your rules.

    Tools, Numbers, and Scale

    • Platforms: Notion, Claude, ChatGPT, Gemini, Notion AI
    • Starter asset: Google Doc template for Notion Conventions (download as .md)
    • Prompt templates: Provided for teaching task/note preferences and for database analysis (linked in video description)
    • Workspace scale: Demonstrated across 20+ databases in Jeff’s personal Notion workspace
    • Jeff OS: A folder system for multi-tool AI context (Notion, Gmail, Calendar, etc.), taught in the Co-work Academy course
    • Claim: “90% built second brain” upon downloading the Jeff OS system (course promotion)

    Caveats and Hype Check

    The video promotes Jeff’s paid Notion course and the Co-work Academy (which teaches the Jeff OS system). The “90% built the moment you download it” claim is a marketing hook for the course. However, the core methodology — creating a conventions markdown file, mounting it in an AI project, and using prompt templates to teach preferences — is demonstrated live and is fully reproducible for free using the provided templates. Notion AI remains useful for in-app tasks such as copy review and bulk migrations, but the external AI becomes the cross-tool orchestrator. No vendor lock-in: the same conventions file works across all three major AI platforms.

    Any AI with a connector to Notion already knows how to use Notion, but that’s not enough. It also needs a written rulebook with your preferences.

    We spend a little bit of time up front teaching AI our preferences, and it saves them in a rule book for that tool. So that the next time we ask it to use that tool, the AI can read the rule book and do the work the way we like.

    Concrete Next Actions

    • Download the Notion Conventions starter Google Doc as markdown (.md).
    • Create a Notion Ops folder on your desktop and place the conventions file inside.
    • Connect Notion to your preferred AI (ChatGPT, Claude, or Gemini).
    • Create a new project in the AI named “Notion Ops” and mount the folder.
    • Copy the link of an ideal task page and an ideal note page in Notion; use the provided prompt to teach the AI your structure.
    • Verify by starting a fresh chat with the folder mounted and requesting a test task or note.
    • Repeat the database analysis prompt for each database you want the AI to manage.
    • If you manage multiple tools beyond Notion, explore the Jeff OS folder system for a unified AI context.

    The upfront investment is modest — roughly 30 to 60 minutes to set up the folder, mount it, and teach the AI your core databases. After that, every Notion interaction via AI follows your conventions without further prompting. For teams or individuals running complex, multi-database workflows, this rulebook approach turns an otherwise generic AI connector into a reliable operator that works the way you do.

  • AI Tools: This Free Repo Lets Claude Code Build Any Mac App

    Watch on YouTube: https://www.youtube.com/watch?v=gN6wl-OX8-Q

    Channel: Dave Ebbelaar

    Building Native macOS Apps with Claude Code: An Introduction to the Bama Repository

    Dave Ebbelaar recently showcased Bama (Build Any Mac App), a free GitHub repository of skills and plugins for Claude Code that enables developers to build native macOS applications in Swift. The project extends the “reverse engineer anything” (REA) workflow by turning reverse-engineered specifications into polished, performant native applications. In the demonstration, Ebbelaar replaces more than ten paid Mac utilities with custom-built tools — including a window manager called Onyx, a todo application, and a video editor — all running locally, privately, and without subscriptions.

    What the Repository Provides

    Bama organizes its capabilities into five skill categories that map to the software development lifecycle:

    • Start: Project initialization and scaffolding for new macOS apps
    • Planning: Feature specification, architecture decisions, and task breakdown
    • Coding: Swift implementation with Apple Silicon optimization
    • Design: Design system extraction from screenshots of existing apps or websites
    • Shipping: Code signing, distribution preparation, and CLI agent integration

    The repository includes complete specifications for three demonstration applications — Onyx (window management and utilities), a todo list clone, and a video editor — which users can clone and modify as starting points.

    Step-by-Step Workflow

    The typical workflow begins with installation. Users add the Bama skills to Claude Code, after which the /bama slash command becomes available, or the skills auto-trigger when a conversation mentions macOS app building. From there:

    1. Reverse engineer a target: Using the base REA project, capture screenshots or recordings of an existing app or workflow you want to replicate.
    2. Extract a design system: The design skill uses computer-use capabilities to analyze captured pages and generate a consistent design system (colors, spacing, typography, components).
    3. Generate specifications: The planning skill produces detailed feature specs, data models, and UI component breakdowns.
    4. Implement in Swift: The coding skill writes native Swift code optimized for Apple Silicon, avoiding Electron or cross-platform frameworks.
    5. Optimize performance: A dedicated performance skill runs a measure-improve loop; the video claims a 10× faster export in the custom video editor compared to the reference application.
    6. Refactor automatically: As the codebase grows, an automatic refactoring skill applies software engineering best practices to maintain structure.
    7. Add a CLI layer: The agent CLI skill builds a command-line interface so other AI agents can drive the finished app programmatically.
    8. Ship locally: The result is a signed, distributable macOS binary that runs entirely on the user’s machine with no accounts, cloud sync, or recurring billing.

    Tools, Numbers, and Claims

    • Core tools: Claude Code, Swift, GitHub (Bama repository)
    • Base dependency: “Reverse Engineer Anything” (REA) repository
    • Performance claim: 10× faster video export in the custom editor versus the commercial alternative
    • Scope of replacement: 10+ paid Mac applications replaced in the demo
    • Privacy model: Local-first, no accounts, no telemetry, no subscription fees
    • Sponsor note: The video includes a sponsorship from Glydo (dictation tool) with an affiliate link for a free Pro month

    You own your own data so you don’t have to share it with people, no accounts, you don’t have to pay for it, no billing.

    Why would you pay a subscription and share your data with some company just to manage your to-do list?

    Caveats and Hype Check

    The 10× video export speedup and the claim of replacing ten-plus paid apps are impressive but have not been independently verified. The Glydo sponsorship uses promotional language (“world’s best”) and includes an affiliate link, which is worth noting for context.

    More substantively, building production-grade native macOS applications autonomously still encounters real-world hurdles that the video does not address:

    • Code signing and notarization: Distributing outside the Mac App Store requires Apple Developer Program membership and proper notarization workflows.
    • App Store distribution: Review guidelines, sandboxing, and entitlements add complexity not covered in a local-first demo.
    • Swift concurrency debugging: Data races, actor isolation, and structured concurrency issues can be difficult for AI-generated code to resolve without human intervention.
    • macOS version compatibility: Maintaining support across major OS releases (Ventura, Sonoma, Sequoia) requires ongoing testing and conditional compilation.
    • Accessibility and system permissions: Window managers, clipboard tools, and global hotkeys require specific entitlements and user approvals.

    These factors mean the “zero to shipped app” path will likely involve iterative human oversight, especially for anything beyond personal utilities.

    Concrete Next Actions

    If you want to explore the workflow yourself, start with these steps:

    • Visit the Bama GitHub repository (linked in the video description) and star it to track updates.
    • Install the Bama skills/plugin into your Claude Code environment.
    • Run the /bama command or start a new session mentioning macOS app building to trigger the skill set.
    • Review the /specs folder for example features: window snapper, clipboard history, color picker, launcher, and the three full demo apps.
    • Build a simple starter app — such as a todo list — to learn the end-to-end workflow.
    • Experiment with the design skills by screenshotting apps you like and extracting their design systems.
    • Apply the performance optimization skill for GPU-intensive workloads (video, audio, rendering).
    • Try the agent CLI skill to let other AI agents drive your custom applications programmatically.

    The Bama repository represents a practical step toward personalized, local-first software — trading subscription fatigue for upfront development effort. For developers comfortable with Swift and Claude Code, it offers a structured path to replace off-the-shelf utilities with tools that exactly match their workflow, data preferences, and performance requirements.

  • Grok Bot: NEW GrokBot Pages are Insane (7 Huge Updates)

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

    Channel: Jack Roberts

    GrokBot’s Seven Major Updates: From Chat Assistant to Persistent AI Agent

    GrokBot recently rolled out seven significant updates that collectively shift the platform from a conversational helper to an omnipresent, memory-enabled agent capable of building live dashboards, executing cross-app workflows, and retaining context across devices and sessions. The changes span voice interaction, email management, marketing automation, social and workplace integrations, and a universal connector layer via Zapier. Below is a breakdown of each update, the tools and numbers involved, a realistic assessment of the claims, and concrete steps to start using the new capabilities.

    What the Video Covers

    • Interactive Dashboard Pages — Auto-refreshing, shareable UI reports with charts, tables, and graphs that update daily without repeated prompting.
    • iPhone Action Button Voice Access — One-press voice chat with GrokBot from the lock screen or any screen, no app launch required.
    • Voice 3.0 with Persistent Cross-Session Memory — Remembers tasks, reminders, and context from prior voice conversations.
    • Unlimited Plus-Alias Email Addresses — Create aliases like financial7@ or newsletter@ to track signups, filter spam, and route mail per purpose.
    • Brevo Email Marketing Connector — AI-driven campaign analysis, drafting, scheduling, and pay-per-email pricing (not per contact).
    • X (Twitter) and Slack Integration — Tag @GrokBot in posts or DMs to capture ideas, manage messages, and sync context back to the main chat.
    • Zapier Connector — Universal authentication layer linking GrokBot to 6,000+ apps (Gmail, Outlook, School, etc.) with granular permission control.

    Step-by-Step Walkthrough of the Updates

    1. Interactive Dashboard Pages

    Instead of asking GrokBot for the same report repeatedly, you can now request a Dashboard Page — for example, “Build a revenue dashboard, update daily from my email connectors.” GrokBot generates an interactive page with charts, tables, and graphs that auto-refresh on a schedule you define. The page is shareable via a simple link, making it suitable for team reviews or client reporting without granting full account access.

    2. iPhone Action Button Shortcut

    On supported iPhone models, assign the Action Button to a Shortcut that launches GrokBot’s voice chat instantly. The setup path is Settings → Action Button → Shortcuts → Grok → Start Voice Chat. This removes the friction of unlocking the phone, finding the app, and tapping a microphone icon, enabling true hands-free capture of ideas, reminders, or queries while walking, driving, or working at a desk.

    3. Voice 3.0 — Persistent Memory Across Sessions

    Voice 3.0 introduces a memory layer that survives app restarts and device switches. You can set a reminder via voice, close the app, reopen it hours later (or on another device), and ask, “What did I ask you earlier?” GrokBot recalls the prior context. The model also claims reduced latency, making the conversation feel more natural.

    4. Unlimited Plus-Alias Emails

    Using the base+alias@domain pattern (e.g., financial7@, financial8@, newsletter@), you can generate unlimited aliases for different purposes: newsletter signups, receipt collection, financial tracking, or spam source identification. Each alias routes to your primary inbox but remains filterable and traceable. Note that this feature depends on your email provider’s support for plus-addressing.

    5. Brevo Email Marketing Connector (Sponsored)

    Brevo provides an MCP server API key that GrokBot uses to analyze past campaigns, draft new emails, schedule sends, and report performance. Pricing is pay-per-email-sent rather than per contact, and the free tier includes 300 emails/month. The video includes an affiliate code JRoberts50 for 50% off the first three months. Setup requires generating the API key in Brevo and pasting it into GrokBot’s connector settings.

    6. X (Twitter) and Slack Integration

    After connecting X and Slack in GrokBot’s Connect Apps section, you can tag @GrokBot in a tweet, reply, or DM, or mention it in a Slack channel or direct message. GrokBot captures the content, adds it to its working memory, and can later reference it in your main chat. This turns social and workplace conversations into actionable context without manual copy-pasting.

    7. Zapier Connector — Universal Auth Layer

    Zapier acts as a single authentication gateway. Once authorized, GrokBot can reach 6,000+ apps. Permissions are granular: you can grant read-only access to Gmail, send-only to Outlook, attachment access to Google Drive, etc. Tokens can be rotated or revoked at any time from the Zapier dashboard, reducing the risk of over-permissioned integrations.

    Tools, Numbers, and Key Details

    • 6,000+ connectors available via Zapier (free tier exists for testing).
    • 300 free emails/month on Brevo’s free plan.
    • 50% off first 3 months Brevo with code JRoberts50.
    • Voice 3.0 model — lower latency, persistent memory enabled.
    • Plus-alias format: base+alias@domain (e.g., financial7, financial8).
    • Brevo MCP server API key required for GrokBot connection.

    You don’t have to keep asking for the same data over and over again.

    Unlike calling everyone else… GrokBot will actually pick up on the first time.

    It retains memory — the next time we have a conversation, it can actually have that chat.

    The direction of travel here is that GrokBot is just going to be where you’re doing work.

    Zapier becomes the authentication layer — one key to rotate, granular permissions, revoke anytime.

    Caveats and Hype Check

    The video is sponsored by Brevo and includes an affiliate link (JRoberts50). The creator also promotes a paid “Agentic System Masterclass” and “Agentic Operating System.” Phrases like “light years ahead,” “unbelievably easy,” and “world’s number one voice model” are marketing hyperbole. The Zapier and Brevo integrations are real but require manual setup and configuration. “Unlimited aliases” only work if your email provider supports plus-addressing (most do, but not all). No verified revenue or productivity metrics are shown in the video.

    Concrete Next Actions

    • Enable the iPhone Action Button shortcut for GrokBot voice chat (Settings → Action Button → Shortcuts → Grok → Start Voice Chat).
    • Create plus-alias emails in GrokBot for newsletters, receipts, signups, and financial tracking.
    • Sign up for Brevo (use code JRoberts50), generate the MCP API key, and connect it to GrokBot for email marketing automation.
    • Connect X/Twitter and Slack in GrokBot’s Connect Apps section; start tagging @GrokBot in posts and DMs to capture context.
    • Set up the Zapier connector in GrokBot → allow access → configure permissions per app (read, send, attachments).
    • Build your first auto-updating dashboard: ask GrokBot “Build a revenue dashboard, update daily from my email connectors.”
    • Test voice memory: set a reminder via voice, close the app, reopen later and ask “What did I ask you earlier?”

  • AI Tools: The New Way To Use Claude For Regular People

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

    Channel: Paul J Lipsky

    Claude Code Opens Local App Building to Non‑Technical Users

    Anthropic’s Claude desktop app now includes a Claude Code tab that lets everyday users create, compile, and run native applications on their own machines — no cloud upload required. In a recent walkthrough, Paul Lipsky demonstrates how this feature moves beyond the developer‑focused Claude Co‑work workflow and puts custom app creation within reach of anyone comfortable writing a prompt.

    What the Video Covers

    • Menu‑bar timer — a lightweight macOS utility built and launched entirely by Claude Code.
    • Dayboard personal dashboard — integrates Apple Calendar, Reminders, and an Obsidian vault, plus a “creator mode” blur and the ability to assign tasks to Grok Bot, ChatGPT, or Claude itself.
    • iPhone stock checker — polls inventory every five minutes and sends a local notification.
    • Games and utilities — quick prototypes that showcase the breadth of local execution.

    Lipsky emphasizes that these apps are fully custom: “No waiting around for updates or new features. There’s no bloat because it only does what you want it to do and there are no paywalls, no annoying updates, and nobody asking you for money.”

    Step‑by‑Step Walkthrough

    1. Open the Claude desktop app and switch to the Claude Code tab.
    2. Create a project for a recurring task (e.g., invoice generation, research compilation). Projects mirror the regular Claude project system and sync across devices.
    3. Grant local folder access — pre‑approve a directory so Claude Code can read/write files on your machine.
    4. Enter a vibe‑coding prompt such as “Build a menu‑bar timer app” or “Check iPhone 15 Pro stock every 5 minutes and notify me.”
    5. Use the coordinator to spin off parallel threads — for example, a report, a slide deck, and a motion graphic — all within the same project.
    6. Toggle local execution for sensitive work; keep everything inside projects to retain mobile access.
    7. Try the dictation button for hands‑free prompting.

    Tools, Numbers, and Key Concepts

    • Claude desktop app — single install with two tabs: regular Claude and Claude Code.
    • Claude Co‑work (legacy) — cloud‑only, code‑output workflow that required manual execution.
    • Projects, coordinator, threads, artifacts — organizational primitives carried over from regular Claude, now with parallel task support.
    • Skills, connectors, plugins — existing integrations (Obsidian, Apple Calendar, Reminders) work unchanged.
    • Local execution vs. cloud toggle — keeps files on‑device; non‑project sessions do not sync to the mobile app.
    • Assignable agents — tasks can be routed to Grok Bot, ChatGPT, or Claude from within a custom app.

    Caveats and Hype Check

    Presenter is a heavy user who has built multiple personal apps (Dayboard, Tab Over) and claims Claude Code replaces all his Co‑work workflows. He calls it “hands down the best tool for editing videos” but doesn’t demo it — pushes to another video. No affiliate links or revenue claims shown, but strong advocacy may reflect personal workflow bias rather than universal fit.

    • Mobile sync limitation: Only project‑based sessions appear on the phone app; ad‑hoc local sessions stay desktop‑only.
    • Video editing claim: Teased as a separate deep‑dive; no evidence provided in this video.
    • Learning curve: While “easier than people think,” users still need to understand project structure, folder permissions, and thread management.
    • Platform focus: Demos are macOS‑centric (menu‑bar apps); Windows/Linux parity not addressed.

    Concrete Next Actions

    • Install or update the Claude desktop app and locate the Claude Code tab.
    • Create a project for a recurring personal or work task and designate a local folder for file access.
    • Run a first vibe‑coding prompt: “Build a menu‑bar timer app” or “Check iPhone 15 Pro stock every 5 minutes and notify me.”
    • Experiment with the coordinator to launch parallel threads (report, presentation, graphic) in one project.
    • Enable local execution for any sensitive data; keep all ongoing work inside projects for mobile visibility.
    • Test the dictation button for voice‑driven prompts.

    Claude Code represents a meaningful shift: local, private, and programmable AI assistance that doesn’t require a development environment. For knowledge workers who want bespoke utilities without vendor lock‑in, it’s worth a hands‑on trial.