<?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 Dev Acharya on Medium]]></title>
        <description><![CDATA[Stories by Dev Acharya on Medium]]></description>
        <link>https://medium.com/@dipeshbhattacharya?source=rss-81f362e85512------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-0yCK206qJcXNyNj.</url>
            <title>Stories by Dev Acharya on Medium</title>
            <link>https://medium.com/@dipeshbhattacharya?source=rss-81f362e85512------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:58:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dipeshbhattacharya/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[Standard roadmap vs. big customers — Part I]]></title>
            <link>https://medium.com/build-for-enterprise/standard-roadmap-vs-big-customers-part-i-fb05686b3fda?source=rss-81f362e85512------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb05686b3fda</guid>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Dev Acharya]]></dc:creator>
            <pubDate>Tue, 15 Aug 2017 05:48:18 GMT</pubDate>
            <atom:updated>2017-08-15T05:48:18.101Z</atom:updated>
            <content:encoded><![CDATA[<p>The enterprise software world was dominated by on-premise software providers for many decades. These on-prem providers build an amazing ecosystem of partners and development teams around them and enabled customers to build large scale heavily custom solutions for their organizations. This meant that the on-prem providers were essentially platform plays, morphing themselves to provide infrastructure and support, but staying away from driving a point of view on best practice solutions. Customers essentially ran large in-house development shops and relied on multi-millions dollar partner driven implementations. They really liked their deep customization of their solutions.</p><p>However, over time these customizations became unmanageable. Upgrading to latest version of an on-prem solution required multi-year, multi-million dollar projects. End user experience required a lot to be desired. Cost of maintaining an in house development teams were sky rocketing.</p><p>Enter SaaS vendors. Late 90s and early 2000s saw the start of disruption on the enterprise software vendor. Led by Salesforce, SuccessFactors, and Workday, these SaaS providers had a new pitch — a standard configurable software, that dramatically reduces implementation time, in-house development cost, improved UX, better security, and continuous updates. The trade-off being those pesky customizations that customers loved. Sure, some of those can be met via configurations, but many of those customizations were not available in the SaaS world.</p><p>It took a while for customers to come around, but most businesses eventually realized the value of SaaS software eventually. However, not everyone was able to transition their mindsets.</p><p>One of the biggest product management challenges in the SaaS enterprise world is handling big customers who still have an on-premise mindset. With huge deals on the table, these customers tend to demand very specific enhancement that are not normally aligned with long term priorities. In part II I will dig deeper on how to acquire these customers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb05686b3fda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/build-for-enterprise/standard-roadmap-vs-big-customers-part-i-fb05686b3fda">Standard roadmap vs. big customers — Part I</a> was originally published in <a href="https://medium.com/build-for-enterprise">Build for Enterprise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprise Product Management is hard]]></title>
            <link>https://medium.com/build-for-enterprise/enterprise-product-management-is-hard-9d975f647e1d?source=rss-81f362e85512------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d975f647e1d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dev Acharya]]></dc:creator>
            <pubDate>Wed, 31 May 2017 07:03:23 GMT</pubDate>
            <atom:updated>2017-05-31T07:03:23.436Z</atom:updated>
            <content:encoded><![CDATA[<p>It is probably strange to start my blog with a topic like this. Some of you may think that it is obvious that enterprise PM is hard. However, having spoken with peers, experts, recruiters, the common perception is consumer PM is hard. Because it is hard to predict consumer behavior and you have to rely on deep statistical analysis, A/B testing to make product decisions. Even with all that, it doesn’t guarantee success in the consumer world. In addition, competition can be intense.</p><p>I agree that being a PM in a consumer PM is hard. But in my humble opinion, Enterprise PM is <em>harder. </em>Here’s why:</p><ol><li><strong>B2B product requires someone to pay</strong>: Yes, most B2B products have a simple revenue model. You sell licenses and get paid. There are no impressions to be monetized, no clicks to be harvested, no data to be sold. It is very simple — you sell seats and you get cash. And it is <em>very very hard</em> to get companies to open their checkbooks.</li><li><strong>Your product needs to solve a real pain point: </strong>No, your product cannot be click-bait articles, food recognition software, app that says “yo”, or any other such myriad of products that address only superficial problems. If you need enterprises to pay for your product, it should solve a key pain point, a business process that is critical to the company’s success. And it should be 100x (not just 10x) better than the incumbent</li><li><strong>Big entrenched incumbents: </strong>You would be competing with SAP, Oracle, Salesforce, and Microsoft. These four companies have cornered most of the enterprise revenue. And they have deep roots in their customer’s business. For example, Oracle sells databases, servers, finance and accounting software, HR software, and many other products to their customers. The more the customer buys, the greater the discount and higher the service levels they experience. CIOs have strong relationships with these incumbents. It takes a lot more than just better product to replace Oracle and SAPs. And no CIO has ever been fired for renewing with Oracle / SAP</li><li><strong>Long and rough sales cycle: </strong>Build a great product isn’t enough to earn success selling to businesses. Success requires staffing a capable and deep sales team that knows how to compete in enterprise sales. These are long sales cycle, sometimes lasting well over 6 months. Sales cycle would include RFP, questionnaire, multiple demos, sandbox environments, legal negotiations, price negotiations, proof of concept, and finally implementation. An entire infrastructure needs to be built out to support your product success.</li><li><strong>Building the boring and hard stuff: </strong>We all like to build great features in our products that our customers and users love. But to be successful with enterprise products, you have to build the hard and boring stuff as well. These are HIPAA compliance, SOX compliance, 508 compliance, Right to Left compatibility, configuration capabilities, security, single sign on, developer tools, extension platform etc. etc. Each of these are long and hard projects that take time off your innovation capacity. But each of these items are critical for lasting success.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d975f647e1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/build-for-enterprise/enterprise-product-management-is-hard-9d975f647e1d">Enterprise Product Management is hard</a> was originally published in <a href="https://medium.com/build-for-enterprise">Build for Enterprise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>