<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Thomas the AI Consultant: the blog</title>
  <link>https://thomastheaiconsultant.com/blog/</link>
  <atom:link href="https://thomastheaiconsultant.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Plain notes on getting real work out of AI: defining processes, rolling AI out to a whole team, and keeping people in charge.</description>
  <language>en</language>
  <lastBuildDate>Thu, 17 Sep 2026 09:00:00 +0000</lastBuildDate>
  <item>
    <title>AI can only do work that's been defined</title>
    <link>https://thomastheaiconsultant.com/blog/ai-can-only-do-defined-work/</link>
    <guid isPermaLink="true">https://thomastheaiconsultant.com/blog/ai-can-only-do-defined-work/</guid>
    <pubDate>Thu, 17 Sep 2026 09:00:00 +0000</pubDate>
    <description>Most AI rollouts stall for the same reason: nobody wrote the work down. Here is how to define a process clearly enough that AI can actually run it.</description>
  </item>
  <item>
    <title>How to get a whole team using AI, not just the curious two</title>
    <link>https://thomastheaiconsultant.com/blog/whole-team-using-ai/</link>
    <guid isPermaLink="true">https://thomastheaiconsultant.com/blog/whole-team-using-ai/</guid>
    <pubDate>Thu, 17 Sep 2026 09:00:00 +0000</pubDate>
    <description>Every company has two people who love AI and twenty who tried it once. What actually moved a 25-person agency from a couple of users to the whole team.</description>
  </item>
  <item>
    <title>Drafts, never sends: keeping a human in the loop</title>
    <link>https://thomastheaiconsultant.com/blog/drafts-never-sends/</link>
    <guid isPermaLink="true">https://thomastheaiconsultant.com/blog/drafts-never-sends/</guid>
    <pubDate>Thu, 17 Sep 2026 09:00:00 +0000</pubDate>
    <description>An AI that works on your customer email needs hard limits. The four rules I built into a startup's sales pipeline, and why 'drafts only' comes first.</description>
  </item>
</channel>
</rss>
