In an effort to make BI solutions less painful to deploy, some software providers have brought analytical applications to market that are based solely on specific data sources, like Salesforce or Oracle financials. The fundamental thinking behind this approach is: if it is so painful for customers to manually integrate and develop their own BI applications, wouldn’t it be easier if our organization just pre-built those manual configurations for them?
This was the fundamental value proposition behind the Sales Analytics Application family I developed while back at Siebel. Essentially, I used existing BI tools to create an out-of-the-box BI solution for the generic Siebel data model, including pre-configured ETL, data-warehouse, metadata, reports, and dashboards. The market responded so strongly to the promise of BI solutions that could be turned on in weeks that the product family grew from almost nothing to over $40 million a year in license revenue in just 3 years.
Pre-configuration doesn’t address the actual problem
The unfortunate reality, however, was that few companies (shhh!) actually used generic Siebel. Most organizations had taken advantage of Siebel’s metadata-driven application to highly configure their Siebel application, creating unique data models with custom objects and fields. This meant that the pre-built ETL, data-warehouse, metadata, reports and dashboards all had to be modified to reflect the actual data model employed by the customer.
In addition, most companies wanted to include some non-Siebel data in their data-warehouse (most commonly, this was back office sales data, since the Opportunity information typed in by a sales rep did not necessarily match the actual revenue the company received). This meant that the ETL, data-warehouse, metadata, reports, and dashboards had to be further modified to reflect this broader set of data that better captured the actual performance of the business.
Given the scale and scope of these changes for most companies, the speed-to-market benefit of buying a pre-built application quickly eroded. Most organizations found themselves facing the many months’ deployment timeline typical of most BI solutions. In short, masking the shortcomings of BI solutions by pre-configuring them doesn’t actually make the shortcomings go away.
“Pre-built” SaaS analytical applications don’t solve the problem, either
It is interesting to note that the market success of Siebel’s Analytical Applications has inspired several Software-as-a-Service companies to develop Analytical Applications that are limited to known data sources – most typically Salesforce.com. They are hoping that the promise of quick and easy BI will have similar success in the SaaS space as it did in the on premise.
While the basic idea seems sound and may generate revenue in the short term, I strongly suspect that those vendors (most of whom use existing open source tools like J-Pivot and Mondrian) will have a hard time meeting customer needs in the long run, because they still have to manually integrate and manage a solution across a highly fragmented stack. This means that these providers will struggle to adapt to each customer’s customized Salesforce data model and will likely be unable to cost-effectively integrate data from outside of Salesforce into the solution – thereby limiting the overall value of the system. I, for one, am very interested to see how the “pre-built” SaaS Analytical Application model fares.