Aakash Gupta

The OpenClaw Guide no PM is Talking About (Masterclass for AI PMs)

Naman Pandey has spent weeks deep inside OpenClaw, the open-source AI agent with 245,000 GitHub stars and 2 million weekly visitors. In this episode, he walks through the complete installation process, connects it to Slack live on camera, and builds five PM automations from scratch, including morning stand-ups, competitive intelligence, customer feedback pipelines, and smart bug routing. Full Writeup: https://www.news.aakashg.com/p/naman-pandey2-podcast Transcript: https://www.aakashg.com/naman-pandey-podcast/ --- Timestamps: 0:00 - Intro 1:55 - Why PMs should care about OpenClaw 3:40 - Two ways to set up OpenClaw 5:02 - Three terminal commands to install 8:55 - Ads 10:41 - How to get your LLM API key 14:27 - Full Slack integration walkthrough 20:24 - Skills vs tools explained 23:40 - Local vs VPS vs Mac Mini 32:26 - Ads 35:14 - Slack vs TUI vs gateway dashboard 38:06 - Slack knowledge base (use case 1) 47:47 - Automated stand-up summaries (use case 2) 54:46 - Competitive intelligence on autopilot (use case 3) 1:13:26 - Voice of customer reports (use case 4) 1:24:30 - Smart bug routing by customer tier (use case 5) 1:37:40 - OpenClaw vs Claude Cowork vs Claude 1:40:21 - Outro --- 🏆 Thanks to our sponsors: 1. Jira Product Discovery: Plan with purpose, ship with confidence - https://www.atlassian.com/software/jira/product-discovery 2. Vanta: Automate compliance, manage risk, and prove trust - http://vanta.com/aakash 3. Mobbin: Discover real-world design inspiration - http://mobbin.com/aakash 4. Maven: - The AI Evals Course for PMs & Engineers: You get $1250 with this link - https://maven.com/parlance-labs/evals?promoCode=ag-product-growth 5. Product Faculty: Get $550 off their #1 AI PM Certification with my link - https://maven.com/product-faculty/ai-product-management-certification?promoCode=AAKASH550C7 --- Key Takeaways: 1. OpenClaw is a proactive AI agent, not a reactive chatbot - Unlike ChatGPT or Claude, OpenClaw runs as a continuous daemon on your machine. It executes tasks at 3 a.m. while you sleep, maintains persistent memory across sessions, and acts autonomously based on scheduled cron jobs. 2. Installation takes three terminal commands - NPM install, openclaw onboard, and hatch the bot. If you do not see red text in the terminal, the installation worked. Yellow warnings are normal and safe to ignore. 3. The Slack integration has one critical step everyone misses - Every time you change bot permissions in the Slack API console, you must click Reinstall to Workspace. Without this step, no permission changes persist and the bot appears broken. 4. The workspace docs folder is your team's knowledge base - Drop PRDs, FAQs, and product docs into the local .openclaw/workspace/docs folder. Any team member can query the entire repository by mentioning the bot in any Slack channel, and the bot can write back to the docs. 5. Cron jobs replace manual PM rituals - Set up a morning stand-up summary that scans Slack channels overnight and posts a brief at 9 a.m. with what shipped, active blockers, and customer complaints. You describe it in English and OpenClaw writes the code. 6. Competitive intelligence runs on autopilot - OpenClaw can monitor competitor websites, reviews, and mentions every 30 minutes and post SWOT analyses to a private Slack channel. It tracks changes over time for trend analysis months later. 7. Voice of customer reports aggregate every feedback source - Connect Slack support channels, email, Google reviews, Reddit, and more. OpenClaw scans every 30 minutes and synthesizes a weekly report automatically. 8. Smart bug routing checks customer tier automatically - OpenClaw reads bug reports, looks up the reporter in a customer CSV, escalates enterprise bugs to engineering immediately, and routes free-tier bugs to design as low priority. 9. Security audit is non-negotiable before going live - Tell OpenClaw to analyze its own security vulnerabilities. It will flag unrestricted file access, disabled firewalls, and missing approval gates. Set up a weekly cron job to run the audit automatically. 10. Local deployment is safest for most PMs - A VPS gives 24/7 uptime but removes your physical kill switch. A dedicated Mac Mini is the most recommended option. Local deployment on your laptop is the safest because the bot sleeps when you close your laptop. --- 👨‍💻 Where to find Naman Pandey: LinkedIn: https://www.linkedin.com/in/namanpandey0796/ YouTube: @ReadySetDoNaman 👨‍💻 Where to find Aakash: Twitter: https://x.com/aakashgupta LinkedIn: https://www.linkedin.com/in/aakashgupta/ Newsletter: https://www.news.aakashg.com #openclaw #aipm --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications to get more videos like this.

AGAakash GuptahostNPNaman Pandeyguest

Mar 17, 2026·1h 40m·Watch on YouTube ↗

📖 CHAPTERS

1. 1
   1:55 – 5:02

   OpenClaw’s viral rise and why PMs should pay attention

   Aakash and Naman frame OpenClaw as a fast-rising, agentic tool that’s going viral and raising an obvious question: how should product managers actually use it. They contrast it with traditional LLM chat as a more proactive, always-on execution layer.

2. 2
   5:02 – 10:41

   Installing via terminal: the three key commands and onboarding flow

   They walk through installing OpenClaw with NPM and then running the onboarding flow. The onboarding enforces personality/identity configuration (including a generated “soul.md”), along with initial security acknowledgments.

3. 3
   10:41 – 14:27

   LLM key + gateway basics: choosing a model and understanding the control plane

   Naman shows how to obtain an LLM API key (example: Gemini) and choose a model variant depending on latency needs. He explains the ‘gateway’ concept as a single control plane that connects to multiple frontends (Slack, WhatsApp, etc.).

4. 4
   14:27 – 20:24

   Full Slack integration walkthrough (Socket Mode + scopes + tokens)

   They build a Slack app from scratch, enable Socket Mode, generate the app token (xapp), and configure bot token scopes. They stress Slack’s finicky parts—especially reinstalling the app after permission changes—and then connect tokens back into OpenClaw.

5. 5
   20:24 – 23:40

   Skills vs tools vs hooks: how OpenClaw “knows” and how it “acts”

   Naman clarifies the internal architecture using memorable metaphors: tools are capabilities, skills are know-how, and hooks/cron jobs drive automation. They show that many settings live as editable local files inside the OpenClaw workspace.

6. 6
   23:40 – 35:14

   Where to run it: local vs VPS vs separate machine (Mac mini) + risk tradeoffs

   They discuss deployment choices through the lens of security and operational reliability. Local is safer by default because sleeping your laptop stops the agent; VPS can keep it running but increases risk; a separate dedicated machine can reduce blast radius.

7. 7
   35:14 – 38:06

   Slack vs TUI vs gateway dashboard: how interfaces map to the same brain

   Aakash asks about limitations across interfaces; Naman explains the TUI, web gateway dashboard, and Slack are essentially different surfaces for the same underlying gateway. The dashboard is the debugging/control center, especially when Slack-side isn’t working.

8. 8
   38:06 – 47:47

   Use case 1: Turn a Slack channel into an AI knowledge base from local docs

   They create a ‘docs’ folder in the OpenClaw workspace and drop in product documentation (PRD + FAQ). In Slack, team members can ask questions and get contextual answers; OpenClaw can even edit the docs and append missing FAQs automatically.

9. 9
   47:47 – 54:46

   Use case 2: Automated stand-up summaries with cron jobs

   OpenClaw scans specified Slack channels on a schedule and posts a structured stand-up brief (ships, blockers, complaints). They show how plain-English instructions become cron jobs and how a trigger phrase can run the summary on demand.

10. 10
    54:46 – 1:13:26

    Use case 3: Competitive intelligence pipeline + Brave search key setup

    They build a competitive intel workflow that monitors competitor sources and posts a SWOT-style brief into a dedicated Slack channel. Setup includes creating a channel, providing channel IDs, and adding a Brave Search API key to enable reliable web browsing.

11. 11
    1:13:26 – 1:24:30

    Use case 4: Voice of Customer reports from Slack + email (persistent trends)

    They set up a pipeline to collect feedback from multiple sources (Slack support channels, emails, reviews) and generate recurring VoC reports. OpenClaw can classify themes, track severity, and maintain trend memory over time via local persistent files.

12. 12
    1:24:30 – 1:37:40

    Use case 5: Smart bug routing by customer tier (decisioning + logging)

    They demonstrate real decision-making: parse bug reports, match reporters against a local CSV of customers/tier, and route bugs differently for enterprise vs free users. The system escalates urgent items, replies with SLAs, and logs issues into a tracking file—showing OpenClaw as a self-building workflow engine.

13. 13
    1:37:40

    OpenClaw vs Claude vs Claude Cowork: autonomy, cost, and ‘always-on’ agents

    They compare tools: Claude is reactive and browser-bound; Cowork is more capable but still often reactive and can be costly; OpenClaw is positioned as an always-on daemon with persistent memory and flexible model choice (including cheaper models). They close with recommended next steps (multimedia workflows) and where to follow Naman.

14. 14

    Two setup paths: one-click “training wheels” vs full local install

    Naman outlines two approaches: a very easy hosted/one-click route (restrictive) and the more flexible local setup that unlocks full control. They set expectations: terminal can be intimidating, but troubleshooting is usually straightforward with search/LLMs.

15. 15

    Security reality check: risks, guardrails, and self-auditing prompts

    They address scary failure modes (accidental access to personal files, unintended messaging behavior) and recommend running periodic security audits by prompting OpenClaw to assess vulnerabilities without making changes. They emphasize default guardrails, least privilege, and being cautious with email/WhatsApp integrations.