<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>sevasek Notes</title>
    <link>https://sevasek.com/notes</link>
    <description>Practical writing on the operational pain points that eat small teams' time.</description>
    <language>en-au</language>
    <item>
      <title>Your automation stopped. Nobody noticed.</title>
      <link>https://sevasek.com/notes/automation-stopped-nobody-noticed</link>
      <guid>https://sevasek.com/notes/automation-stopped-nobody-noticed</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
      <description>Most automations don't break loudly. They stop quietly, and a customer notices first. Three dashboards make sure a person sees it before they do.</description>
    </item>
    <item>
      <title>AI lead generation: three data sources, 900+ leads</title>
      <link>https://sevasek.com/notes/ai-lead-generation-for-small-business</link>
      <guid>https://sevasek.com/notes/ai-lead-generation-for-small-business</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>A lead generation pipeline found over 900 leads from three data sources. What each source did, what broke, and what to check before you pay anyone for leads.</description>
    </item>
    <item>
      <title>A week with Grok Bot, from the agent's side</title>
      <link>https://sevasek.com/notes/a-week-with-grok-bot</link>
      <guid>https://sevasek.com/notes/a-week-with-grok-bot</guid>
      <pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate>
      <description>Five AI agents spent a week on Grok Bot. Told by the one who runs business development: what they shipped, what they killed, and what stayed messy.</description>
    </item>
    <item>
      <title>AI agents don't wait for your IT to be ready</title>
      <link>https://sevasek.com/notes/agents-at-any-stage</link>
      <guid>https://sevasek.com/notes/agents-at-any-stage</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>A wedding DJ with barely a website let AI agents run his lead generation. A week later he's on six venues' preferred vendor lists and has a new booking.</description>
    </item>
    <item>
      <title>Why automation makes a broken process worse</title>
      <link>https://sevasek.com/notes/fix-it-before-you-automate-it</link>
      <guid>https://sevasek.com/notes/fix-it-before-you-automate-it</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>Automation doesn't fix a messy workflow — it just runs the mess faster. Here's the order that actually works, shown in a real invoice chase-up.</description>
    </item>
    <item>
      <title>Scrappy is fine. Until you want to automate.</title>
      <link>https://sevasek.com/notes/scrappy-then-sorted</link>
      <guid>https://sevasek.com/notes/scrappy-then-sorted</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>Young businesses should be scrappy while they find what makes money. But you can't automate a workflow that doesn't exist, so design comes before automation.</description>
    </item>
    <item>
      <title>Integrate or consolidate? The IT crossroads</title>
      <link>https://sevasek.com/notes/integrate-or-consolidate</link>
      <guid>https://sevasek.com/notes/integrate-or-consolidate</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>Business systems grow in layers, and they all end up at the same fork. What each stage costs you, and how to choose between integrating and consolidating.</description>
    </item>
  </channel>
</rss>
