Skip to main content

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. 

ISVs and SIs are often smaller ecosystem participants. They get access to customers and other participants of the ecosystem that complement their expertise. They might also see themselves merge with the platform provider. Worst case, the platform provider sees an opportunity and provides functionality that is similar to the one provided by one or more smaller partners. In this case, the platform provider becomes a competitor. We all have seen this.

Of course, there are also situations where partners compete with each other. The ecosystem is a place where coopetition happens, which is something that is mostly healthy.

The question that arises is how can small companies, especially ISVs, thrive and grow as part of an ecosystem. After all, it is the platform company that makes the rules and that has all the data while the other ecosystem players only have a partial view on it. For these smaller ISVs, this inherently bears the risk of becoming a commodity, which is not a desirable  position to be in, as commodity providers can be exchanged for each other.

This means that the  providers in an ecosystem need to be distinguishable from their  competition. In addition to the diminishing importance of product, price and promotion, another key factor is the experience that the company does provide, how hard (or rather easy) it is to work with the company, how easy its solution is to implement, and how well it fits into the core software that is provided by the controlling company, to name a few relevant points.

This ties back to the pyramid of customer expectations.

On an individual level

  • Information about the solution must be readily and easily available, accurate, and the solution itself must work as advertised, i.e. solve the customers’ problem
  • The solution must be easy to implement and efficient to use, which works best, if it is fully developed in the platform’s software stack, because that way the installation will be  smooth and users do see a user interface that they are used to

  • And it needs to be fun to use, which is a bit harder but goes in line with making life for the user easy by working like the users and not as if designed by someone who never did the job it shall help the user perform. Ideally, it is possible to work with the company to implement missing or additional functionality fast

And then, there is an additional stage that successful small ecosystem players master: They are capable of building temporary ecosystems, temporary partnerships with other ecosystem members to provide more value to customers. These partnerships may be limited to a single project but also involve joint product development and go-to-market. The important aspect is that these temporary ecosystems can generate further synergies

To give a concrete example, this is exactly what an ISV like Fastcall successfully does. Fastcall is a part of the Salesforce ecosystem. The company provides efficient CTI solutions that extend the Salesforce solution. The software seamlessly extends the Salesforce stack as it is a native app, which also makes it easy to install. Because of being a native app, it also seamlessly integrates into the Salesforce UI. The company uses the AppExchange, which makes it easy to find. The company is also very customer driven. This is shown, e.g. when it comes to implementing new requirements in a swift way, as Marshall Lager has recently described in his article Rising to Swift Challenges in App Development.

Comments

Last Year's Top 5 Popular Posts

You are only as good as your customer remembers

As you know, I am very interested in how organizations are using business applications, which problems they do address, and how they review their success. In a next instance of these customer interviews, I had the opportunity to talk with Melissa Gordon , Executive Vice President, Enterprise Solutions at Tidal Basin about their journey with Zoho. You can watch the full interview on YouTube. Tidal Basin is a government contractor that provides various services throughout the government space, including disaster response, technology and financial services, and contact centers. Tidal Basin started with Zoho CRM and was searching for a project management tool in 2019. This was prompted by mainly two drivers. First, employees were asking for tools to help them running their projects. Second, with a focus on organizational growth and bigger projects that involved more people, Tidal Basin wanted to reduce its risk exposure and increase the efficiency of project delivery. This way, the compa...

Sweet Transformation: Inside SugarCRM’s New Direction

Fresh from the 2025 SugarCRM Analyst Summit, waiting for my plane home, it is time to sort my thoughts. From Monday, 1/27 evening to Wednesday 1/29 in the morning we had some time jam packed with information and good conversations with SugarCRM execs, customers, and in between analysts. The main summit started with a bang, namely the announcement that industry icon Bob Stutz joins the SugarCRM board of directors , which is something that few of us, if any, had foreseen. This is exciting news.  With David Roberts , who succeeded Craig Charlton in September 2024, SugarCRM itself has a new CEO with a long time CRM pedigree.  As with every leadership change, this promises some change. Every new CEO evaluates what they see vs. where they want their company to go and then, together with the team, establishes and executes a plan to get there. Usually, this involves some change in the structure of the executive leadership team, too.  This is what happened and happens with SugarCR...

Data Wars: SAP Vs. Salesforce In The AI-Driven Enterprise Future

The past weeks certainly brought a lot of news, with SAP Sapphire and Salesforce's surely strategically timed announcement of acquiring Informatica , ranging at the top. I have covered both in recent articles. The enterprise software landscape is crackling with energy, and Artificial Intelligence (AI) is certainly the star of the show. It isn't anymore about AI as a mere feature; it's about AI as the strategic core of enterprise software. Two recent announcements underscored this shift: SAP's ambitious AI-centric vision that was unveiled at its Sapphire 2025 conference, and, arriving hot on its heels, Salesforce's agreement to acquire data management titan Informatica for $8 billion. Both signal an intensified battle for AI supremacy, where trusted, enterprise-wide data is the undisputed new monarch. Of course, SAP and Salesforce are not the only ones duking this one out. SAP's Sapphire Vision: An AI-Powered, Integrated Enterprise At its Sapphire 2025 event in ...

The CDP is dead – long live the CDP!

In the past few years, I have written about CDPs, what they are and what their value is – or rather can be. My definition of a CDP that I laid out in one of my column articles on CustomerThink is:  A Customer Data Platform is a software that creates persistent, unified customer records that enable business processes that have the customers’ interests and objectives in mind. It is a good thing that CDPs evolved from its origins of being a packaged software owned by marketers, serving marketers. Having looked at CDP’s as a band aid that fixes the proliferation of data silos that emerged for a number of reasons, I have ultimately come to the conclusion and am here to say that the customer data platform as an entity is increasingly becoming irrelevant – or in the typical marketing hyperbole – dead.  Why is that? There are mainly four reasons for it.  For one, many an application has its own CDP variant already embedded as part of enabling its core functionality. Any engageme...

CPQ, Meet Price Optimization: Your Revenue Lifecycle Just Got Serious

The news On October 1, 2025, Conga announced its intent to acquire the B2B business of PROS , following PRO’s acquisition by Thomas Bravo . At the same time, ThomaBravo and PROS announced that PRO’s travel business segment will be run as a standalone business . The bigger picture Revenue operations, revenue management and revenue lifecycle management have become a thing in the past years, as evidenced by the number of specialized companies that solve parts of the overall problem of optimizing revenue. It also got abused to some extent (e.g., surge pricing models) when the users of the corresponding capabilities consider optimizing being the same as maximizing. Reality check: It is not. While optimizing involves a bit of identifying how much a customer is willing to pay, it also involves the thought of repeat business, or in other words customer loyalty, even without a formal loyalty program. And that involves the customer experience, part of which the speed of creating a quote with mat...