<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nidhi Vyas on Medium]]></title>
        <description><![CDATA[Stories by Nidhi Vyas on Medium]]></description>
        <link>https://medium.com/@nidhivyas_17125?source=rss-68fd34282b5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2KqNOxV9e8Rof2QC.</url>
            <title>Stories by Nidhi Vyas on Medium</title>
            <link>https://medium.com/@nidhivyas_17125?source=rss-68fd34282b5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:38:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nidhivyas_17125/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ML SaaS: Improving Revenue Early On]]></title>
            <link>https://medium.com/@nidhivyas_17125/ml-saas-improving-revenue-early-on-a24b2e5ccd1d?source=rss-68fd34282b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a24b2e5ccd1d</guid>
            <category><![CDATA[ml-product]]></category>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[mlsaas]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nidhi Vyas]]></dc:creator>
            <pubDate>Sun, 20 Mar 2022 15:19:50 GMT</pubDate>
            <atom:updated>2022-03-20T15:19:50.233Z</atom:updated>
            <content:encoded><![CDATA[<p>A new era of ML <a href="https://en.wikipedia.org/wiki/Software_as_a_service">SaaS</a> has emerged as businesses are leveraging <a href="https://www.bmc.com/blogs/machine-learning-can-benefit-business/">user interaction patterns</a> to improve critical decisions. Similar to other SaaS products, <a href="https://userguiding.com/blog/product-success-metrics/">revenue</a> is an important factor to increase the likelihood of success. This article discusses some dimensions that can help grow the revenue for such tools early on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z5irMERChc2iTw-dqmXD0A.png" /></figure><p>The price of a product is always bounded by the potential value of business impact realized by their customers. While there can be additional factors, if one can maximize the value of their product, while also optimally conveying this value to their customers, it can significantly improve customer conversion rates, and eventually, increase product revenue.</p><h3>Increasing potential value</h3><h3>🥇 Build for users (first)</h3><p>As the buyers are more focused on general business issues, use their feedback to differentiate and rank the most critical themes. Contrary, the users care about improving their development processes. So the feedback from user experience should guide feature prioritization and product development. Tangible and quick iterations using interactive mocks, followed by <a href="https://www.lean.org/explore-lean/what-is-lean/">minimal features</a> can streamline this process. The overall value proposition should still align with the business needs, and so the product should be occasionally verified with the buyer. Going bottom-up in the initial stage will convert users to product champions, eventually leading to wider adoption.</p><h3>🔂 Aim for product stickiness</h3><p>Work on making the <a href="https://taplytics.com/blog/building-sticky-products-need-know/#:~:text=By%20definition%2C%20sticky%20products%20are,product%20lasts%20longer%20and%20longer.&amp;text=The%20stickier%20the%20product%2C%20the%20higher%20the%20retention%20rate.)">product sticky</a> early on. Besides improving the quality of individual features, it is important to stitch a more cohesive overall product experience. Identifying what is missing in core workflows to deliver a better solution, speaking to users to understand what they are finding most valuable, and decreasing time-to-value, empowering users to find the information support quickly, using <em>defaults</em> to minimize user decisions, providing customizations, and automating repetitive workflows are some ways to significantly improve the user experience.</p><h3>🧱 Reduce integration overhead</h3><p>Stress on reducing integration overhead. In ML, model artifacts are often treated as a black box, and new tools and frameworks are introduced very frequently. Due to such an ephemeral development environment, it is important to actively reduce friction from onboarding and maintenance. If the product has a higher learning curve for the users, educating via an onboarding program can unlock potential product value faster.</p><h3>🔎 Improve privacy and interpretability</h3><p>With ML software, the non-deterministic behavior can increase <a href="https://www.ey.com/en_us/banking-capital-markets/understand-model-risk-management-for-ai-and-machine-learning">business risks</a> associated with poor predictions. Hence, some degree of interpretability can help users prevent such damage. Informative actions to debug these errors can make users feel more assured when using the product. Finally, incorporating support for various regulatory requirements (e.g. <a href="https://en.wikipedia.org/wiki/System_and_Organization_Controls">SOC</a> and <a href="https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act#HIPPA">HIPPA</a> compliance) for sensitive data can foster trust.</p><h3>🧠 Increase mindshare</h3><p>For a growing community of ML developers, <a href="https://www.investopedia.com/terms/m/mindshare.asp">mindshare</a> can increase customer loyalty, which is essential to accelerate product usage for a fragmented market of ML SaaS. A few ways are running <a href="https://wandb.ai/site/tutorials">workshops or tutorials</a>, in-person classes or webinars, podcasts or conference talks, <a href="https://www.marktechpost.com/2021/11/08/hugging-face-introduces-datasets-a-lightweight-community-library-for-natural-language-processing-nlp/">open-source libraries</a> to engage users.</p><h3>Increasing probability of value realization</h3><h3>🚘 Provide product trials</h3><p>The value proposition can be conveyed more organically via quick ways to use and evaluate the product. For users landing on the product website, providing a sandbox with pre-populated data, a <a href="https://www.ventureharbour.com/saas-free-to-paid-upselling/">free trial of the full product</a>, customer testimonials, and demonstrating intuitive usage with documentation are some ways to achieve this. Additionally, establishing methods to capture <a href="https://www.crazyegg.com/blog/click-heatmap/">salient user behavior</a> in this phase can provide product insights. For users requesting a <a href="https://www.forbes.com/sites/forbescommunicationscouncil/2019/09/24/improve-b2b-marketing-in-the-middle-of-the-funnel-with-product-demos-and-trials/?sh=28f01e3d6144">demo</a>, a more bespoke solution with relevant industry data and metrics can increase relatability.</p><p>Early-stage tools can make potential enterprise customers apprehensive. <a href="https://www.heavybit.com/library/blog/saas-poc-paid-pilot-program/">Paid POCs</a> are a great way to deliver a measurable impact on their business needs, thereby eliminating their concerns. Defining success criteria is very crucial in this phase. Ideally, it should be a KPI related to business impact (e.g. engineering hours saved, increased ROI) or development processes (e.g. improvement in accuracy, improvement in latency). Mitigating UX struggles, and making users self-sufficient to repeatedly use the product are equally important for a successful POC.</p><h3>💸 Validate price-strategy early</h3><p>Like other SaaS products, not providing all features can harm the value realization process. So, a usage-based pricing model could be better suited than the freemium counterpart. Allowing customers to come in at a certain level and making them grow as they increase usage (and realize more value) is much better for <a href="https://www.profitwell.com/recur/all/outcome-based-value-metrics-for-growth">increasing revenue and decreasing churn</a>. Validating this strategy should be a part of initial feedback conversations with buyers. Understanding their current solutions, costs and frustrations can give strong insights about willingness to pay. Here, the highest points of resonance with product features should guide future price iterations.</p><p><em>Disclaimer: Opinions are my own and not the views of my employer</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a24b2e5ccd1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>