<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Sentinel Fortune LLC — Articles, Guides &amp; Updates</title>
  <subtitle>Operational systems, field-tested tools, and practical intelligence for small businesses that run on execution.</subtitle>
  <link href="https://sentinelfortune.github.io/sentinelfortune/feed.xml" rel="self"/>
  <link href="https://sentinelfortune.github.io/sentinelfortune/"/>
  <id>https://sentinelfortune.github.io/sentinelfortune/</id>
  <updated>2026-08-01T00:00:00+00:00</updated>
  <author><name>Sentinel Fortune LLC</name></author>
  <entry>
    <title>Using AI safely in a licensed trade</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/articles/using-ai-safely-in-a-licensed-trade/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/articles/using-ai-safely-in-a-licensed-trade/</id>
    <published>2026-08-01T00:00:00+00:00</published>
    <updated>2026-08-01T00:00:00+00:00</updated>
    <category term="Article"/>
    <summary>A working boundary for AI in a business where some decisions legally require a licensed person — what to use it for, what to keep it away from, and what to put in writing before anyone starts.</summary>
  </entry>
  <entry>
    <title>AI drafts. Licensed people decide.</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/updates/ai-drafts-licensed-people-decide/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/updates/ai-drafts-licensed-people-decide/</id>
    <published>2026-08-01T00:00:00+00:00</published>
    <updated>2026-08-01T00:00:00+00:00</updated>
    <category term="Update"/>
    <summary>The single rule that makes AI safe to use inside a licensed trade — and what goes wrong the moment it is relaxed.</summary>
  </entry>
  <entry>
    <title>Choosing an AI operations system for a home-service business</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/guides/choosing-an-ai-operations-system/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/guides/choosing-an-ai-operations-system/</id>
    <published>2026-07-31T00:00:00+00:00</published>
    <updated>2026-07-31T00:00:00+00:00</updated>
    <category term="Guide"/>
    <summary>What to look for, what to ignore, and the questions that separate a usable system from a repackaged list of generic prompts.</summary>
  </entry>
  <entry>
    <title>The four questions that make an estimate defensible</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/updates/four-questions-defensible-estimate/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/updates/four-questions-defensible-estimate/</id>
    <published>2026-07-29T00:00:00+00:00</published>
    <updated>2026-07-29T00:00:00+00:00</updated>
    <category term="Update"/>
    <summary>Estimates lose money in what they leave out. Four questions, asked before the estimate goes out, close most of that gap.</summary>
  </entry>
  <entry>
    <title>Turning field notes into invoice-ready job records</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/articles/field-notes-to-job-records/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/articles/field-notes-to-job-records/</id>
    <published>2026-07-27T00:00:00+00:00</published>
    <updated>2026-07-27T00:00:00+00:00</updated>
    <category term="Article"/>
    <summary>Why the gap between what a technician writes and what the office needs costs real money, and a repeatable way to close it without asking technicians to write more.</summary>
  </entry>
  <entry>
    <title>What belongs in a field note</title>
    <link href="https://sentinelfortune.github.io/sentinelfortune/updates/what-belongs-in-a-field-note/"/>
    <id>https://sentinelfortune.github.io/sentinelfortune/updates/what-belongs-in-a-field-note/</id>
    <published>2026-07-25T00:00:00+00:00</published>
    <updated>2026-07-25T00:00:00+00:00</updated>
    <category term="Update"/>
    <summary>&quot;Replaced part, tested, ok&quot; is where invoicing disputes begin. Seven fields turn a fragment into a record that survives a callback.</summary>
  </entry>
</feed>
