Episode
[REDACTED]: Episode 3: A Sentient HubSpot for $2 a Brand
- Podcast
- NC Tweener Talks
- Published
- Jun 3, 2026
- Duration seconds
- 2669
- Processing state
not_requested- Canonical source
- https://share.transistor.fm/s/cf3e9b0b
Actions
POST https://stenobird.com/v1/public/podcasts/nc-tweener-talks-7053588/episodes/redacted-episode-3-a-sentient-hubspot-for-2-a-brand/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/nc-tweener-talks-7053588/redacted-episode-3-a-sentient-hubspot-for-2-a-brand.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
In episode 3 of [REDACTED], we (David and Taylor) run a live demo of an agentic CRM-cleanup pipeline (and finds out, on air, what it costs). We also walk through a landing page workflow that compresses what used to take five people and a month of meetings into something one person can do in an afternoon. The bulk of episode 3 is a live demo, just what we wanted. Plus, the best part of Redacted is that nothing is finished. Every episode is a midstream demo of something that might break, might cost more than it should, or might be the thing that quietly changes how a whole category of work gets done. Enjoy the conversation. What We Cover $1.98 to clean a brand: Taylor’s CRM pipeline ran live on air with one restaurant with two locations, 64 turns, 95% cache hit, total cost under two dollars. The code-vs-agent slider: Taylor built an interactive slider with pros and cons on each side. Fully deterministic code can’t handle ambiguity, fully agentic can’t be tested or priced. The “no brand graph” problem: There is no canonical source of truth for the restaurant industry. Google Places, SERP, and Yelp all return ranked top-20s — you can’t reconstruct the full graph locally. This is what makes the cleanup problem agentic by necessity. n8n’s flowers, n8n’s thorns: Taylor’s running joke is that every local agent he builds eventually looks like n8n. But debugging n8n at scale meant pulling down a million-token JSON dump every morning just to grep it. Local won on debuggability, not capability. Confidence tiers for copy extraction: “Act on it” = recurring in 6+ meetings. “Pattern” = 4–5. “Emerging” = 1–3. The model can suggest copy at any tier; the operator decides what gets shipped. The headline no human wrote: “Get found by foodies who are paying to find you.” This sidesteps the…