<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Value AI Solutions — Journal</title>
    <link>https://valueaisolutions.com/blog</link>
    <atom:link href="https://valueaisolutions.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Founder-led workflow automation studio in Stockholm. We find the work worth automating, scope it in plain language, build it, and hand it over documented.</description>
    <language>en</language>
    <lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate>
    <item>
      <title>Why automation pilots stall before production</title>
      <link>https://valueaisolutions.com/blog/why-automation-pilots-stall-before-production</link>
      <guid isPermaLink="true">https://valueaisolutions.com/blog/why-automation-pilots-stall-before-production</guid>
      <pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate>
      <description>Most automation pilots don't fail at the demo. They die in the gap between a working proof of concept and something a team actually runs every day.</description>
    </item>
    <item>
      <title>How to tell which work is actually worth automating</title>
      <link>https://valueaisolutions.com/blog/what-work-is-worth-automating</link>
      <guid isPermaLink="true">https://valueaisolutions.com/blog/what-work-is-worth-automating</guid>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <description>Most automation projects fail for reasons that have nothing to do with the software. Here is the filter we use to decide what to build before anyone opens a tool.</description>
    </item>
  </channel>
</rss>
