<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xslt" ?>
<rss
    xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
    xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:spotify="http://www.spotify.com/ns/rss"
    xmlns:psc="http://podlove.org/simple-chapters/"
    xmlns:media="https://search.yahoo.com/mrss/"
    xmlns:podcast="https://podcastindex.org/namespace/1.0"
    version="2.0">
    <channel>
        <title>Dear Ben</title>
                    <link>https://dearben.ai/episodes</link>
                <atom:link rel="self" type="application/rss+xml" href="https://feed.ausha.co/Zd0rgTx1vJ8Q"/>
        <description>Practical AI for CEOs Who Don’t Have Time for BS

Hosted on Ausha. See ausha.co/privacy-policy for more information.</description>
        <language>en</language>
        <copyright>2026</copyright>
        <lastBuildDate>Wed, 29 Apr 2026 23:53:41 +0000</lastBuildDate>
        <pubDate>Wed, 29 Apr 2026 23:53:41 +0000</pubDate>
        <webMaster>feeds@ausha.co (Ausha)</webMaster>
        <generator>Ausha (https://www.ausha.co)</generator>
                    <spotify:countryOfOrigin>us</spotify:countryOfOrigin>
        
        <itunes:author>Ben Fisher</itunes:author>
        <itunes:owner>
            <itunes:name>Ben Fisher</itunes:name>
            <itunes:email>ben@skinnyandbald.com</itunes:email>
        </itunes:owner>
        <itunes:summary>Practical AI for CEOs Who Don’t Have Time for BS

Hosted on Ausha. See ausha.co/privacy-policy for more information.</itunes:summary>
        <itunes:explicit>false</itunes:explicit>
        <itunes:block>no</itunes:block>
        <podcast:block>no</podcast:block>
        <podcast:locked>yes</podcast:locked>
        <itunes:type>episodic</itunes:type>
                    <itunes:subtitle>Practical AI for CEOs who don't have time for BS.</itunes:subtitle>
                
        <googleplay:author>Ben Fisher</googleplay:author>
        <googleplay:email>ben@skinnyandbald.com</googleplay:email>
        <googleplay:description>Practical AI for CEOs Who Don’t Have Time for BS

Hosted on Ausha. See ausha.co/privacy-policy for more information.</googleplay:description>
        <googleplay:explicit>false</googleplay:explicit>

                    <podcast:funding url="">Support us!</podcast:funding>
        
        <category>Technology</category>
    
            <itunes:category text="Technology"/>
        <category>Business</category>
    
        <itunes:category text="Business">
                    <itunes:category text="Entrepreneurship"/>
            </itunes:category>
    
                    <image>
                <url>https://image.ausha.co/ycj8OB6hMxcC5OWPWQu2Ki2m6f02NKb9oe1sIGIr_1400x1400.jpeg?t=1772428451</url>
                <title>Dear Ben</title>
                                    <link>https://dearben.ai/episodes</link>
                            </image>
            <itunes:image href="https://image.ausha.co/ycj8OB6hMxcC5OWPWQu2Ki2m6f02NKb9oe1sIGIr_1400x1400.jpeg?t=1772428451"/>
            <googleplay:image href="https://image.ausha.co/ycj8OB6hMxcC5OWPWQu2Ki2m6f02NKb9oe1sIGIr_1400x1400.jpeg?t=1772428451"/>
        
                    <item>
                <title>What AI Workflows Are You Sleeping On?</title>
                <guid isPermaLink="false">nirI-SXmkU0</guid>
                <description><![CDATA[<p>Andrew Warner asked: "Every time I talk to a founder, I hear about some AI workflow I never would have thought to try. What are the non-obvious ones you're seeing?"<br><br>Most people use AI to make stuff. The overlooked category: using AI to mirror things back to you. Scoring. Flagging. Routing. That's where the leverage is hiding.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>- The Make vs Mirror Matrix: you're probably doing Make — but Mirror is where the blind spots live<br>- Jeff Brewer gets rated on clarity, decisiveness, and interruptions after every single meeting<br>- Dan Shipper built a system that flags when he's avoiding confrontation<br>- Wade Foster (Zapier CEO) scores team meetings against Five Dysfunctions and sends individual feedback<br>- Pete Sena's mega prompt analyzed 13 years of my notes and surfaced patterns I'd forgotten<br>- Chris Brownridge routes meeting actions to Linear/calendar automatically via Claude agent<br>- One meeting. One mirror workflow. Ship it. Stack from there.<br><br>--<br><br># TOOLS MENTIONED<br><br>- Motion AI Exec Coach (meeting scoring)<br>- Granola (local-first meeting notes)<br>- Zapier (automation)<br>- Fireflies (meeting transcription)<br>- Claude Desktop / Claude Code (local file analysis)<br>- Linear (task routing)<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2x CEO, 3x CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Andrew Warner asked: "Every time I talk to a founder, I hear about some AI workflow I never would have thought to try. What are the non-obvious ones you're seeing?"<br><br>Most people use AI to make stuff. The overlooked category: using AI to mirror things back to you. Scoring. Flagging. Routing. That's where the leverage is hiding.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>- The Make vs Mirror Matrix: you're probably doing Make — but Mirror is where the blind spots live<br>- Jeff Brewer gets rated on clarity, decisiveness, and interruptions after every single meeting<br>- Dan Shipper built a system that flags when he's avoiding confrontation<br>- Wade Foster (Zapier CEO) scores team meetings against Five Dysfunctions and sends individual feedback<br>- Pete Sena's mega prompt analyzed 13 years of my notes and surfaced patterns I'd forgotten<br>- Chris Brownridge routes meeting actions to Linear/calendar automatically via Claude agent<br>- One meeting. One mirror workflow. Ship it. Stack from there.<br><br>--<br><br># TOOLS MENTIONED<br><br>- Motion AI Exec Coach (meeting scoring)<br>- Granola (local-first meeting notes)<br>- Zapier (automation)<br>- Fireflies (meeting transcription)<br>- Claude Desktop / Claude Code (local file analysis)<br>- Linear (task routing)<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2x CEO, 3x CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Sat, 17 Jan 2026 00:48:44 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/oKjgp7cnq3vg.mp3?t=1772428371" length="16527057" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/what-ai-workflows-are-you-sleeping-on-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>16:39</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Andrew Warner asked: "Every time I talk to a founder, I hear about some AI workflow I never would have thought to try. What are the non-obvious ones you're seeing?"

Most people use AI to make stuff. The overlooked category: using AI to mirror things...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/odfVH5Ya9N5UtfzrfIIMkCBmYg4FeBYnsI26LCny_1400x1400.jpeg?t=1772428347"/>
                    <googleplay:image href="https://image.ausha.co/odfVH5Ya9N5UtfzrfIIMkCBmYg4FeBYnsI26LCny_1400x1400.jpeg?t=1772428347"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>How Do I Turn Conversations Into Actual Work Artifacts?</title>
                <guid isPermaLink="false">6_mpSX9KdF4</guid>
                <description><![CDATA[<p>Work happens in conversations. The problem is it stays there.<br><br>You hash out a product idea, talk through requirements, make decisions — and then somehow you're supposed to recreate all of that in a document later. That's where everything falls apart.<br><br>I use AI to extract the work that already happened and turn it into artifacts that keep the momentum going. PRDs, user stories, requirements — pulled straight from the conversation.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Work happens in conversations — but it stays trapped there<br>• The "missing middle" — decisions made verbally rarely become documents<br>• Extract the work, don't recreate it — AI pulls out what you already figured out<br>• Zero-draft artifacts — PRDs, user stories, requirements from the conversation itself<br>• Pressure-test with clarifying questions — surface gaps before you build<br>• 95% of the work already done — you just need to extract it<br><br>--<br><br># TOOLS MENTIONED<br><br>• Fireflies.ai — Meeting recording and transcription<br>• Claude Desktop — Extraction and synthesis<br>• Claude Code — Workflow automation<br>• claude-code-requirements-builder — Requirements extraction workflow<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Work happens in conversations. The problem is it stays there.<br><br>You hash out a product idea, talk through requirements, make decisions — and then somehow you're supposed to recreate all of that in a document later. That's where everything falls apart.<br><br>I use AI to extract the work that already happened and turn it into artifacts that keep the momentum going. PRDs, user stories, requirements — pulled straight from the conversation.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Work happens in conversations — but it stays trapped there<br>• The "missing middle" — decisions made verbally rarely become documents<br>• Extract the work, don't recreate it — AI pulls out what you already figured out<br>• Zero-draft artifacts — PRDs, user stories, requirements from the conversation itself<br>• Pressure-test with clarifying questions — surface gaps before you build<br>• 95% of the work already done — you just need to extract it<br><br>--<br><br># TOOLS MENTIONED<br><br>• Fireflies.ai — Meeting recording and transcription<br>• Claude Desktop — Extraction and synthesis<br>• Claude Code — Workflow automation<br>• claude-code-requirements-builder — Requirements extraction workflow<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Sat, 20 Dec 2025 22:31:28 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/nZxY8Fq72A4K.mp3?t=1772428359" length="10959510" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/how-do-i-turn-conversations-into-actual-work-artifacts-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords></itunes:keywords>
                                <itunes:duration>10:58</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Work happens in conversations. The problem is it stays there.

You hash out a product idea, talk through requirements, make decisions — and then somehow you're supposed to recreate all of that in a document later. That's where everything falls apart....</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/8v5dmls8pQcEsJiJwBZkFaf8fPlwR8JkUMpuPEjQ_1400x1400.jpeg?t=1772428347"/>
                    <googleplay:image href="https://image.ausha.co/8v5dmls8pQcEsJiJwBZkFaf8fPlwR8JkUMpuPEjQ_1400x1400.jpeg?t=1772428347"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>Behind the Build: How I Prep Dear Ben Episodes with AI (Part 1)</title>
                <guid isPermaLink="false">Cydd3pFhAVY</guid>
                <description><![CDATA[<p>This isn't a Q&amp;A episode — it's for builders who want to see how I actually work.<br><br>I walk through using Claude Code and Every's skill creator to build the system that helps me prepare for Dear Ben episodes. The process: do it manually first, pay attention to what you repeat, then systematize.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Do it manually first, then systematize — I did this process by hand several times before building the automation<br>• AI is probabilistic, not deterministic — the agent built the skill but forgot to create the slash command<br>• ChatGPT's Prompt Optimizer genuinely improves prompt efficacy, even for Claude<br>• The LLM asking questions extracts your thinking — it's a brainstorming tool that forces you to articulate what you believe<br>• Four phases: Ideation, Content Development, Proof of Concept, Blind Spots<br><br>--<br><br># TOOLS MENTIONED<br><br>• Claude Code<br>• ChatGPT Prompt Optimizer<br>• Every's Skill Creator Agent<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>This isn't a Q&amp;A episode — it's for builders who want to see how I actually work.<br><br>I walk through using Claude Code and Every's skill creator to build the system that helps me prepare for Dear Ben episodes. The process: do it manually first, pay attention to what you repeat, then systematize.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Do it manually first, then systematize — I did this process by hand several times before building the automation<br>• AI is probabilistic, not deterministic — the agent built the skill but forgot to create the slash command<br>• ChatGPT's Prompt Optimizer genuinely improves prompt efficacy, even for Claude<br>• The LLM asking questions extracts your thinking — it's a brainstorming tool that forces you to articulate what you believe<br>• Four phases: Ideation, Content Development, Proof of Concept, Blind Spots<br><br>--<br><br># TOOLS MENTIONED<br><br>• Claude Code<br>• ChatGPT Prompt Optimizer<br>• Every's Skill Creator Agent<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Sat, 20 Dec 2025 22:04:45 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/6wX7RUnrLOO0.mp3?t=1772428381" length="23941597" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/behind-the-build-how-i-prep-dear-ben-episodes-with-ai-part-1-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords></itunes:keywords>
                                <itunes:duration>24:17</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
This isn't a Q&amp;amp;A episode — it's for builders who want to see how I actually work.

I walk through using Claude Code and Every's skill creator to build the system that helps me prepare for Dear Ben episodes. The process: do it manually first, pay a...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/0GfMqakdpexm5n0FvEDkfME21Q00dbLTAQSCjbto_1400x1400.jpeg?t=1772428358"/>
                    <googleplay:image href="https://image.ausha.co/0GfMqakdpexm5n0FvEDkfME21Q00dbLTAQSCjbto_1400x1400.jpeg?t=1772428358"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>How Do I Index Sales Collateral So My Team Can Find It?</title>
                <guid isPermaLink="false">LK5AXNLlGq4</guid>
                <description><![CDATA[<p>Murali asked: "I run a 600-person software dev agency. How do I index our sales material so my team can actually find what they need?"<br><br>Before jumping to AI, ask: is this a process problem or a familiarity problem? When the people creating docs aren't the ones searching, semantic search creates real leverage.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• First question: is this a structure problem? At 600 people with creators ≠ searchers, it's not<br>• Lindy gives full visibility into prompts — you can tweak and experiment, not just hope it works<br>• The agent builder gets you 85% there; you course correct the rest<br>• Use a smaller model for retrieval — it's not reasoning, save budget for generation<br>• 5-minute setup: Google Drive → Lindy → Slack integration<br>• Future extension: calendar triggers that auto-fetch docs before meetings<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy AI — automation platform with prompt visibility and agent builder<br>• Fireflies — AI note-taker with real-time knowledge base features (bonus)<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Murali asked: "I run a 600-person software dev agency. How do I index our sales material so my team can actually find what they need?"<br><br>Before jumping to AI, ask: is this a process problem or a familiarity problem? When the people creating docs aren't the ones searching, semantic search creates real leverage.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• First question: is this a structure problem? At 600 people with creators ≠ searchers, it's not<br>• Lindy gives full visibility into prompts — you can tweak and experiment, not just hope it works<br>• The agent builder gets you 85% there; you course correct the rest<br>• Use a smaller model for retrieval — it's not reasoning, save budget for generation<br>• 5-minute setup: Google Drive → Lindy → Slack integration<br>• Future extension: calendar triggers that auto-fetch docs before meetings<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy AI — automation platform with prompt visibility and agent builder<br>• Fireflies — AI note-taker with real-time knowledge base features (bonus)<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Sat, 20 Dec 2025 21:59:25 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/ewkVrUEO8z0q.mp3?t=1772428809" length="7677890" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/how-do-i-index-sales-collateral-so-my-team-can-find-it-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>07:35</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Murali asked: "I run a 600-person software dev agency. How do I index our sales material so my team can actually find what they need?"

Before jumping to AI, ask: is this a process problem or a familiarity problem? When the people creating docs aren't...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/l6HHD63Q6QFhwir56NbZXyEF1BN6bu5uTYaivtEu_1400x1400.jpeg?t=1772428798"/>
                    <googleplay:image href="https://image.ausha.co/l6HHD63Q6QFhwir56NbZXyEF1BN6bu5uTYaivtEu_1400x1400.jpeg?t=1772428798"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>How Do I Win at AI Search When Nobody Really Knows the Rules?</title>
                <guid isPermaLink="false">8JDdpFcY7TY</guid>
                <description><![CDATA[<p>Henry asked: "What's your best practice advice for winning AI search? Nobody really knows how to game the system."<br><br>There's a lot of speculation presented as fact in this space. But practitioners who've been deep in SEO are starting to converge on real patterns. I brought in Chirag from Taco to break down what's actually working.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• LLMs run web searches behind the scenes — if you don't rank on Google, you probably won't rank in ChatGPT<br>• Turn keywords into questions: "dandruff shampoo" becomes "what are the best dandruff shampoos for men?"<br>• Identify where LLMs pull citations from — Reddit, listicles, authoritative publications in your vertical<br>• Create content on third-party sites that LLMs already trust (Reddit threads, guest posts, affiliate sites)<br>• Spam tactics get plugged fast — same as traditional SEO<br>• Some startups have leapfrogged traditional SEO for LLM placement (Lenny's podcast goes deeper)<br><br>--<br><br># FEATURING<br><br>Chirag Kulkarni — Founder &amp; CEO, Taco (AI-powered SEO agency)<br>Forbes 30 Under 30 (Marketing). Former CMO at Medly Pharmacy (scaled 1→50 pharmacies, $100M+ revenue).<br>• Website: https://taco.co/<br>• LinkedIn: https://www.linkedin.com/in/chiragkulkarni/<br><br>--<br><br># TOOLS MENTIONED<br><br>• Scrunch<br>• Air Ops<br>• Profound<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Henry asked: "What's your best practice advice for winning AI search? Nobody really knows how to game the system."<br><br>There's a lot of speculation presented as fact in this space. But practitioners who've been deep in SEO are starting to converge on real patterns. I brought in Chirag from Taco to break down what's actually working.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• LLMs run web searches behind the scenes — if you don't rank on Google, you probably won't rank in ChatGPT<br>• Turn keywords into questions: "dandruff shampoo" becomes "what are the best dandruff shampoos for men?"<br>• Identify where LLMs pull citations from — Reddit, listicles, authoritative publications in your vertical<br>• Create content on third-party sites that LLMs already trust (Reddit threads, guest posts, affiliate sites)<br>• Spam tactics get plugged fast — same as traditional SEO<br>• Some startups have leapfrogged traditional SEO for LLM placement (Lenny's podcast goes deeper)<br><br>--<br><br># FEATURING<br><br>Chirag Kulkarni — Founder &amp; CEO, Taco (AI-powered SEO agency)<br>Forbes 30 Under 30 (Marketing). Former CMO at Medly Pharmacy (scaled 1→50 pharmacies, $100M+ revenue).<br>• Website: https://taco.co/<br>• LinkedIn: https://www.linkedin.com/in/chiragkulkarni/<br><br>--<br><br># TOOLS MENTIONED<br><br>• Scrunch<br>• Air Ops<br>• Profound<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Tue, 09 Dec 2025 23:47:31 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/3mMGJtQdljQ0.mp3?t=1772428806" length="5401873" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/how-do-i-win-at-ai-search-when-nobody-really-knows-the-rules-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>05:00</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Henry asked: "What's your best practice advice for winning AI search? Nobody really knows how to game the system."

There's a lot of speculation presented as fact in this space. But practitioners who've been deep in SEO are starting to converge on rea...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/U7JVqNTTlcVokPBpjYwyCEgvgqJ8Ko2bPZvNGJIc_1400x1400.jpeg?t=1772428796"/>
                    <googleplay:image href="https://image.ausha.co/U7JVqNTTlcVokPBpjYwyCEgvgqJ8Ko2bPZvNGJIc_1400x1400.jpeg?t=1772428796"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>Behind the Build: Building a Sales Collateral Bot with Lindy (Part 2)</title>
                <guid isPermaLink="false">P7JxLJjF5qo</guid>
                <description><![CDATA[<p>Part 2 of the behind-the-scenes series. I take Claude's workflow spec and build it in Lindy — and debug it live when things break.<br><br>The lesson: check templates first before building from scratch. Lindy has out-of-the-box knowledge base templates I could have started with.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Check templates first — Lindy has out-of-the-box knowledge base templates I should have used<br>• Debug in public — Google connections drop, folder IDs get lost, agents hang<br>• Multiple approaches exist — agent-built workflow vs. template, different tradeoffs<br>• Token efficiency matters — different workflow structures have different credit consumption<br>• Use Claude to generate test data — I had it create 10 fake sales documents for the demo<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy AI (agent builder, knowledge base templates)<br>• Google Drive integration<br>• Slack integration<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Part 2 of the behind-the-scenes series. I take Claude's workflow spec and build it in Lindy — and debug it live when things break.<br><br>The lesson: check templates first before building from scratch. Lindy has out-of-the-box knowledge base templates I could have started with.<br><br>Ask your own question at DearBen.ai.<br><br>--<br><br># SHOW NOTES<br><br>• Check templates first — Lindy has out-of-the-box knowledge base templates I should have used<br>• Debug in public — Google connections drop, folder IDs get lost, agents hang<br>• Multiple approaches exist — agent-built workflow vs. template, different tradeoffs<br>• Token efficiency matters — different workflow structures have different credit consumption<br>• Use Claude to generate test data — I had it create 10 fake sales documents for the demo<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy AI (agent builder, knowledge base templates)<br>• Google Drive integration<br>• Slack integration<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Thu, 04 Dec 2025 06:30:05 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/Kjgp7ce5pDrA.mp3?t=1772428835" length="11494321" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/behind-the-build-building-a-sales-collateral-bot-with-lindy-part-2-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>11:24</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Part 2 of the behind-the-scenes series. I take Claude's workflow spec and build it in Lindy — and debug it live when things break.

The lesson: check templates first before building from scratch. Lindy has out-of-the-box knowledge base templates I cou...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/FHULrY2WIJ1Kh2r2lpz8RqWaMM1ISS99p2vJfmh8_1400x1400.jpeg?t=1772428818"/>
                    <googleplay:image href="https://image.ausha.co/FHULrY2WIJ1Kh2r2lpz8RqWaMM1ISS99p2vJfmh8_1400x1400.jpeg?t=1772428818"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>How Do You Manage Junior Devs Using AI to Build Beyond Their Skill Level?</title>
                <guid isPermaLink="false">4dMYmULSAVQ</guid>
                <description><![CDATA[<p>Jason asked: "How do you manage junior developers when they're using AI to build systems more sophisticated than they understand?"<br><br>The solution isn't more oversight — it's constraints that force understanding. I share three practices that work together.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• Spec-driven development: write what the system should do in plain language before any code<br>• Opinionated frameworks: use Next.js or T3 stack to prevent AI from inventing architecture<br>• Test-driven validation: understand what each test proves, not just that tests exist<br>• Why these three rules create the same constraint: forced understanding<br>• Bonus: invest in a fractional coach for code reviews and AI workflow guidance<br><br>--<br><br># TOOLS MENTIONED<br><br>• Next.js<br>• T3 Stack<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Jason asked: "How do you manage junior developers when they're using AI to build systems more sophisticated than they understand?"<br><br>The solution isn't more oversight — it's constraints that force understanding. I share three practices that work together.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• Spec-driven development: write what the system should do in plain language before any code<br>• Opinionated frameworks: use Next.js or T3 stack to prevent AI from inventing architecture<br>• Test-driven validation: understand what each test proves, not just that tests exist<br>• Why these three rules create the same constraint: forced understanding<br>• Bonus: invest in a fractional coach for code reviews and AI workflow guidance<br><br>--<br><br># TOOLS MENTIONED<br><br>• Next.js<br>• T3 Stack<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Wed, 26 Nov 2025 00:29:42 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/BGgQvWCElP1g.mp3?t=1772428821" length="5149629" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/how-do-you-manage-junior-devs-using-ai-to-build-beyond-their-skill-level-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>04:48</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Jason asked: "How do you manage junior developers when they're using AI to build systems more sophisticated than they understand?"

The solution isn't more oversight — it's constraints that force understanding. I share three practices that work togeth...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/1s8btuk9RDdvflaVhbqUXyusGLhnc2HMu0cwY3PH_1400x1400.jpeg?t=1772428809"/>
                    <googleplay:image href="https://image.ausha.co/1s8btuk9RDdvflaVhbqUXyusGLhnc2HMu0cwY3PH_1400x1400.jpeg?t=1772428809"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
                    <item>
                <title>Can AI Create My Content, Let Me Approve It, and Post It Everywhere?</title>
                <guid isPermaLink="false">AxRbhGHGXeE</guid>
                <description><![CDATA[<p>Jeff asked: "Can AI generate my content, let me approve it in Slack, then auto-post to LinkedIn, X, and Reddit?"<br><br>The orchestration is easy — scheduling, APIs, multi-platform posting. That's solved. The hard part is content quality. Getting AI output that doesn't sound like AI.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• Why orchestration (scheduling, APIs) is the easy part — every platform handles that<br>• The real bottleneck: content quality and voice consistency<br>• AI writing tools vs. automation platforms: black boxes vs. build-it-yourself<br>• Lindy as middle ground: prompt visibility + Slack review + workflow automation<br>• 15-minute proof-of-concept walkthrough with Claude Sonnet 3.5<br>• Year one cost: ~$2,100 (vs. 260 hours of manual content creation)<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy.ai<br>• Zapier.com / Make.com<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></description>
                <content:encoded><![CDATA[<p>Jeff asked: "Can AI generate my content, let me approve it in Slack, then auto-post to LinkedIn, X, and Reddit?"<br><br>The orchestration is easy — scheduling, APIs, multi-platform posting. That's solved. The hard part is content quality. Getting AI output that doesn't sound like AI.<br><br>Ask your own question at DearBen.ai.<br><br>---<br><br># SHOW NOTES<br><br>• Why orchestration (scheduling, APIs) is the easy part — every platform handles that<br>• The real bottleneck: content quality and voice consistency<br>• AI writing tools vs. automation platforms: black boxes vs. build-it-yourself<br>• Lindy as middle ground: prompt visibility + Slack review + workflow automation<br>• 15-minute proof-of-concept walkthrough with Claude Sonnet 3.5<br>• Year one cost: ~$2,100 (vs. 260 hours of manual content creation)<br><br>--<br><br># TOOLS MENTIONED<br><br>• Lindy.ai<br>• Zapier.com / Make.com<br><br>--<br><br># ABOUT DEARBEN.AI<br><br>Practical AI for CEOs who don't have time to become AI experts.<br><br>Ben Fisher — 2× CEO, 3× CTO.<br>A founder-to-founder experiment answering real AI questions from operators running real companies.<br><br>Ask yours at https://DearBen.ai<br><br>--<br><br># CONNECT<br><br>Website: https://DearBen.ai<br>LinkedIn: https://fshr.co/profile<br>X: https://x.com/skinnyandbald</p><br/><p>Hosted on Ausha. See <a href="https://ausha.co/privacy-policy">ausha.co/privacy-policy</a> for more information.</p>]]></content:encoded>
                <pubDate>Wed, 26 Nov 2025 00:29:21 +0000</pubDate>
                <enclosure url="https://pdcn.co/e/https://audio.ausha.co/PqvQzHmJDPO5.mp3?t=1772428836" length="12547339" type="audio/mpeg"/>
                                    <link>https://podcast.ausha.co/dear-ben-ai/can-ai-create-my-content-let-me-approve-it-and-post-it-everywhere-dear-ben</link>
                
                                <itunes:author>Ben Fisher</itunes:author>
                <itunes:explicit>false</itunes:explicit>
                                    <itunes:keywords>Claude,ChatGPT,product development,artificial intelligence (ai)</itunes:keywords>
                                <itunes:duration>12:38</itunes:duration>
                <itunes:episodeType>full</itunes:episodeType>
                                <itunes:subtitle>
Jeff asked: "Can AI generate my content, let me approve it in Slack, then auto-post to LinkedIn, X, and Reddit?"

The orchestration is easy — scheduling, APIs, multi-platform posting. That's solved. The hard part is content quality. Getting AI output...</itunes:subtitle>

                
                <googleplay:author>Ben Fisher</googleplay:author>
                                <googleplay:explicit>false</googleplay:explicit>

                                    <itunes:image href="https://image.ausha.co/keM6wQTKEa3mjXgKsfZgEEaubDSH05IRRktFTMBn_1400x1400.jpeg?t=1772428819"/>
                    <googleplay:image href="https://image.ausha.co/keM6wQTKEa3mjXgKsfZgEEaubDSH05IRRktFTMBn_1400x1400.jpeg?t=1772428819"/>
                
                                    <psc:chapters version="1.1">
                                            </psc:chapters>
                
                            </item>
            </channel>
</rss>
