How to create winning industry solutions
One of the terms du jour is „industry cloud“. We hear it even more often than even platform or CX at this time. Why is that? Why do we speak about them only now and not for a longer time? After all, we have seen industry solutions forever, albeit on premise. Yes, the concept of vertical solutions is that old. What is the value of an industry cloud? How does “industry cloud” differ from “industry solution”? And does this term really describe what industries need? These are only some of the questions that we wanted to discuss with Vinnie Mirchandani as part of aCRMKonvo. Hurricane Ian intervened and Vinnie had more important things to do than a CRMKonvo. Luckily, everything turned out well for him. Good for the CRMKonvos team, that friend and Enterprise Irregular Jon Reed could jump in to what turned out to be an even more interesting topic than we hoped for. We will continue this discussion with Vinnie on a later occasion. He has quite something to say about industry clouds, and comes from another angle than Jon. The problem with industry clouds Most business applications have started their life as horizontal applications. This makes a lot of sense, as a good deal of the functionality that a business needs, and the application offers, is not exactly industry specific. Instead, it is applicable across a range of industries. Therefore, business software vendors at first concentrated on developing horizontal functionality, as this functionality is reusable across and customized for numerous industries. Often with only little effort. This applies to SaaS software as well as it did apply to on premise...
Your ultimate 2021 hit list of most read articles
It is this time of the year and I want to extend a heart-felt Thank You! to all my readers who honour me by investing your time into reading my posts, sharing and commenting on them. Thank You! Below is the list of the top 10 posts read by you in 2021 #10: How to avoid the looming CRM crisis #9: The Dirty Dozen of 2021 Trends (maybe I should revise this one for 2022?) #8: CRMKonvo – Freshworks on Platform, CRM and useful AI #7: Outlaw Spirit – Lessons from The Zoho Analyst Day 2021 #6: How to orchestrate customer journeys in real time at scale #5: Digitization, Digitalization, Digital Transformation – A Stake in the Ground #4: With Oracle Fusion Marketing into the Future of CRM? #3: Together, Zoom and Five9 shape a new market (well, in the light of this merger having failed … they could have shaped a market. Still, a very readable one) #2: Nimble strengthens its ability to be where the user is #1: Ecosystem Play, One Game at a Time Obviously, I do not know yet in detail what I am going to write about in 2022. however, I strive to make it as valuable for you as this year – at least Bonne...
Ecosystems, how to play for small players
Lately, we have talked a lot about ecosystems, in particular business ecosystems. Normally, business ecosystems follow a hub and spoke model rather than a network approach; one major player sets it up, and then adds customers and partners like independent software vendors, systems integrators, analysts, consultants, suppliers, or other similar entities. Good examples of successful ecosystems are the ones around the big four enterprise software vendors: Microsoft, Oracle, Salesforce and SAP. Sure, there are other ones, but these are easy reference examples. In theory, ecosystems shall provide more value to customers, better serving their needs by making it easier for them to get access to information, knowledge, skills and productized enhancements to the core solution that they chose to implement. They also get a broader choice of possible enhancements, provided by different vendors in the ecosystem. Of course, this also benefits the other participating stakeholders. Customers are, of course, an important group of every ecosystem. Treating them as partners helps the platform company to create a transparent prioritization process for delivering requested new functionalities that extend the own solution in an optimal way. Not all customers provide the necessary input, though. For the platform provider, the ecosystem creates stickiness. Still, this company cannot develop and provide all the functionality that is ever needed by its customers. Nor can it provide sufficient implementation services. And it does not want to, either. So, it needs ISVs and SIs as members of its ecosystem to provide this functionality, either as products, or as consulting solutions. What these companies deliver on top of the core solution also increases the attractiveness of the ecosystem. ...