Enterprise Software Lessons: The Risk of Building on Someone Else’s Platform

05 Jul

Late last night I was reading an article about an entrepreneur that has accomplished moderate success by building an enterprise software product that adds sine new capabilities to a popular platform provided by a big software company (you can tell I am trying to not mention names 😉 ). The entire article is centered around the benefits of this business model that allowed this entrepreneur to leverage an existing customer base and community in order to create a successful product. However, in my opinion, the article presents an oversimplified picture of that business model and ignores some of the biggest challenges startups can encounter when building an entire product that depends on somebody else’s platform

While the consumer market is packed with products that build on successful platforms like Facebook or Twitter, the enterprise game is quite different. The dynamics of the enterprise software market bring its own set of challenges and benefits when building a product that are dependent on a platform provided by another vendor. In the enterprise world, building a product on somebody else’s platform can be a very dangerous game that is not suited for every startup.

If you are a founder CEO building an enterprise software business on top of one of our old cousin’s platforms, you should consider some of the following challenges.

You don’t own your own destiny

The minute you build an enterprise software product that depends on another company’s platform, your destiny becomes tied to that vendor. From that point on, aspects such as product roadmap, pricing, sales strategies, customer acquisition models will stop being entirely dependent on the capabilities of your product and factoring in the strategies of the underlying platform.

Competing for attention

Big enterprise software vendors are notorious for implementing absurdly large partner programs. By building a product that is dependent on a big enterprise software platform, you will be constantly competing for the attention of the big enterprise software company with a pool of partners which sole purpose in life is to try to differentiate themselves in the eyes of the big enterprise software uncle.

You can become a feature not a product

Differently from the consumer market, enterprise software vendors rarely produce complete platforms that will enable a startup to build a unique product and customer identity. Instead, enterprise software vendors are more focused on providing feature rich product to their customers that while sometimes offer some room for new technologies that complement the ecosystem are far from being a platform to sustain a long term product strategy. In that sense, you should be clear whether you are building your product on an open platform that will allow you to build long term capabilities or you are just adding a feature to existing product.

That make that distinction clear, we can look at companies like Microstrategy and Quest Software. Over the last decade, BI vendors like Microstrategy have built super feature rich products with a long term identity on top of platforms such as Oracle or SQL Server. Contrary to that model, a company like Quest Software has built an incredible business by providing additional operational management capabilities on top of different IT product. While both companies have been incredibly successful, we can agree that Microstrategy is building a complete product while  Quest is adding features to existing products.

Sales cycle dependency

Building an enterprise software product on top of somebody else’s platform will certainly introduce dependencies on the sales cycles and commercial models of your product. In that sense, your customer acquisition strategy will always be somehow dependent on the parent vendor and your boundaries tied to theirs.

Pricing model dependency

Pricing is one of those dependencies we tend to ignore when building an enterprise software product on another vendors’ platform. When doing this, be aware that changes in the pricing or sales strategy changes of the parent technology can drastically affect your product pricing model. Having a strategy to mitigate those changes can be the difference between success or failure in your startup.


Posted by on July 5, 2012 in Uncategorized


Tags: , , , , ,

3 responses to “Enterprise Software Lessons: The Risk of Building on Someone Else’s Platform

  1. Saravana Kumar

    July 5, 2012 at 9:55 am

    Probably I won’t classify this as a Risk, it’s just another type of business model. You may not become another Facebook or Twitter or even Yammer, but it could turn up into a viable small-medium scale business.

    Companies like Red Gate are very successful, just building their products on top of SQL server, recent years they diversified themselves into other areas like .NET, Oracle etc. but primarily their model is to build products on top of someone else platform. Their home page says they got around 600,000 users, that’s really big number.

    You probably know very well about where we stand, we do exactly same on BizTalk server with BizTalk360. Yes, there is a risk, if Microsoft stops shipping BizTalk server in the future, then we don’t have a business. Most of the big vendors like Microsoft are good at building platforms (because they got resources to do that), and they are never going to cover each and every customer requirements. There will always be some gap. If we can fill up that gap, and solve a business problem then there is a viable business model.

    Only thing is always be prepared to move on if things change.

  2. jesusmrv

    July 5, 2012 at 10:38 am

    Sure its a risk but also has its benefits. RedGate or Quest has been able to capitalize on that business model by diversifying their product offering. Having said that, their opportunities their market segment is very well delineated by the products the products they manage.

    I dont think is about becoming Facebook or Yammer, is about having a room for growth that expands beyond somebody else’ market. There are a million and one risks with that model too.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: