In this third installment of Claude Sessions, Danny is joined by Subash from Not A Square, who helps e-commerce brands scaling past seven figures implement AI without scaling headcount. Subash walks through real client case studies -- including a TikTok brand that boosted its customer satisfaction score from 4.2 to 4.5 in four weeks using a customer support agent built in Claude.

Danny then breaks down OpenClaw, the open-source personal AI agent that exploded in popularity, explains why he chose not to use it despite the temptation, and reveals Claude Flow -- his custom operating system built inside Claude Code with 11 engines, 300+ features, and a persistent memory layer powered by ChromaDB. The episode drives home one core message: document your operations first, pick one platform, go deep, and stop chasing every new tool.

Key Topics

Documenting operations before automation -- Why you cannot automate what is not documented
TikTok customer support case study -- Building an AI agent that raised satisfaction scores in four weeks
OpenClaw overview and security risks -- What it does, why it blew up, and why Danny built his own alternative
Claude Flow -- Danny's custom operating system inside Claude Code with persistent memory
The amnesia loop -- How context loss between sessions kills productivity and how ChromaDB solves it
Pixel-less environment -- The shift from structured prompts to contextual AI interaction
Go deep on one platform -- Why chasing multiple AI tools guarantees you build nothing

Timestamps

[00:00] Introduction -- Claude Sessions Week 3, delayed from the road
[01:03] Subash introduces himself and Not A Square
[02:01] Overview of three client projects and the problem founders face
[04:30] Why operational truth is the moat in AI commerce
[06:48] Three pillars: reduce costs, better governance, scale without headcount
[07:30] TikTok case study -- customer support agent boosting store score from 4.2 to 4.5
[09:04] OpenClaw -- history, capabilities, and the security nightmare
[15:30] Six core capabilities of OpenClaw (local-first, universal messaging, persistent memory, browser automation, system access, self-extending skills)
[18:00] Why OpenClaw matters -- moving from dumb LLMs to personal AI agents
[20:00] Security trade-offs -- 1.5M API keys exposed, malware in skills, Cisco tests
[22:00] Claude Flow -- Danny's 11-engine operating system built inside Claude Code
[24:26] The amnesia loop -- how sessions lose context and how ChromaDB fixes it
[28:19] Why Claude MD, agents, and skills are not enough without hooks and triggers
[32:40] Go deep on one platform -- stop chasing every new tool
[35:35] Subash on helping sellers adopt Claude Code fundamentals (Claude MD, skills)
[39:51] Wrap-up and contact info

Key Takeaways

Document before you automate -- If your business operations live in the founder's head and not on paper, any AI tool will amplify the chaos rather than fix it.
Operational truth is the moat -- Clean inventory, accurate catalogs, honest cashflow reporting. Get these right before touching AI.
One AI agent moved the needle -- A single customer support agent on TikTok raised a brand's satisfaction score from 4.2 to 4.5 in four weeks, directly improving store visibility.
Persistent memory changes everything -- ChromaDB captures decisions, patterns, and project context across sessions so Claude compounds in usefulness over time (zero entries in session one, 1,700+ by session 25).
Scaffolding beats raw building -- Danny's Claude Flow system means a project that took five days six months ago now takes 40 minutes. The investment in infrastructure pays exponential returns.
OpenClaw is proof of concept, not production-ready -- Broad permissions, prompt injection vulnerabilities, exposed API keys. Wait for the open-source community to patch the holes before diving in.
Pick one platform and go all the way in -- Chasing multiple AI tools means you learn none of them deeply and build nothing of value.