[REDACTED]: Episode 3: A Sentient HubSpot for $2 a Brand
Taylor builds a local agent that dedupes a CRM brand for two bucks, David turns 876 sales calls into landing page copy with Claude Design, and a real debate on the code-vs-agent continuum.
We need help with upcoming episodes! Who's the most underrated AI builder you know? Someone running real systems inside a real business? Send us a message at contact@tweenerfund.com because we want to get them on the show!
What’s Redacted?
[Redacted] is a YouTube-first, twice-monthly show where we:
Walk through what they actually shipped that week
Screen share real systems inside their business
Break down what worked, what didn’t, and why
Episode 3
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 #1 objection in the space (is this a free deals site?) in one line. David says no one on his team has produced anything like it in ten years of writing copy.
Claude Design as a brand harness: David came in skeptical that it was just a Claude Code wrapper. He left convinced: same model, but the design harness around it makes the outputs materially better.
15–20 hours, one person: Total wall-clock on the landing page from raw transcripts to live wireframes. Historically the same work needed five people (founder, sales, copy, brand, design) and weeks of calendar time.
Skill folder structure: David’s pattern for non-trivial skills: a tiny top-level skill file that orchestrates, plus subfolders for context (inputs the skill ingests), data (outputs by run), and prompts (exposed so they can be QA’d independently).
How to watch:
It’s best viewed on YouTube to fully see the examples (make sure to subscribe!)
But also available on all audio podcast players through Tweener Talks!
https://tweenertalks.com/episodes/redacted-episode-3-a-sentient-hubspot-for-2-a-brand
PLUS we have a new spot for show notes and files discussed in the episode. Check cit out: https://github.com/instanttaylor/redacted-podcast
What’s Next?
New episodes drop twice a month/every other Wednesday. If you want to be on the show as a guest and show your [REDACTED] builds, email us here.