<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Roi on Rough Edges</title><link>https://roughedges.dev/tags/roi/</link><description>Recent content in Roi on Rough Edges</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://roughedges.dev/tags/roi/index.xml" rel="self" type="application/rss+xml"/><item><title>AI ROI Isn't Hours Saved</title><link>https://roughedges.dev/posts/ai-roi-isnt-hours-saved/</link><pubDate>Fri, 03 Jul 2026 00:00:00 -0400</pubDate><guid>https://roughedges.dev/posts/ai-roi-isnt-hours-saved/</guid><description>&lt;p&gt;There&amp;rsquo;s a number that shows up in almost every AI business case I&amp;rsquo;ve seen, and it always sounds like the end of the argument: &lt;em&gt;it saves our engineers X hours a week.&lt;/em&gt; It&amp;rsquo;s in the vendor deck, the board update, the memo justifying the spend. Sometimes X is four, sometimes it&amp;rsquo;s ten. Whatever it is, it&amp;rsquo;s presented as the return – the thing that makes the money back.&lt;/p&gt;
&lt;p&gt;It isn&amp;rsquo;t a return. It&amp;rsquo;s the beginning of a question about a return, and most of the time nobody asks the rest of it.&lt;/p&gt;</description></item></channel></rss>