<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Business on Fernando Ruiz</title><link>https://www.fernandoux.com/tags/business/</link><description>Recent content in Business on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/tags/business/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Feature ROI: How to Measure Whether a Feature Is Worth Its Cost</title><link>https://www.fernandoux.com/en/wiki/ai/ai-feature-roi/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/ai-feature-roi/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 The &lt;strong&gt;ROI of an AI feature&lt;/strong&gt; is the ratio between the value it generates and the cost of running it, measured per outcome (per task, per customer or per feature) and compared against a baseline taken before launch. It is not measured by how many times people open the feature.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="why-measure-per-outcome-rather-than-per-use"&gt;Why measure per outcome rather than per use?&lt;/h2&gt;
&lt;p&gt;Usage is easy to count and misleading. A feature can have thousands of opens and still save no time and sell nothing. What matters is whether each outcome is worth more than it cost to produce.&lt;/p&gt;</description></item></channel></rss>